elihoole/asrs-aviation-reports huggingface dataset:
Date: 201507
Local time of day: 1801-2400
Location: DCA.Airport, DC
Flight conditions: VMC
Light: Night
Aircraft: B737 Undifferentiated or Other Model
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Taxi
Reporter organization: Air Carrier
Reporter function: Captain
Reporter qualification: Flight Crew Air Transport Pilot (ATP)
Human factors: Situational Awareness; Confusion; Communication Breakdown
Second reporter function: First Officer
Anomaly: Ground Event / Encounter Other / Unknown
Detector: Person Flight Crew
When detected: Taxi
Result: Aircraft Aircraft Damaged; General Maintenance Action
Contributing factors: Company Policy; Human Factors; Procedure; Airport
Primary problem: Airport

Narrative: Flight X departed XXX approximately 11 minutes late enroute to DCA. We landed approximately eight to ten minutes early on Runway 19. We exited the runway and began our taxi to Gate X. While taxiing to Gate X we called DCA Operations to let them know we were on the ground and to verify the gate; which was confirmed to be Gate X. We taxied into the alley and around to Gate X. There were no personnel to meet the aircraft and I taxied the aircraft onto the J-line and approximately halfway down. I did this because I believed another carrier was waiting on us so that they could push off Gate X. There was an aircraft on Gate X and X. We waited approximately one to two minutes for personnel to meet the aircraft; when one lady exited the Operations room she began to frantically look for wands; she had to go back into the building to get help; she exited the building with another person and they searched for wands and eventually found a pair of wands. They began to marshal the aircraft to the gate; we moved forward and began to taxi to the gate and were directed forward and to my left. We felt the aircraft nudge something and we thought we had run over a chock. The Marshaler continued to ask the aircraft to move forward; but the aircraft wouldn't move. Eventually they discovered that the aircraft's number one engine had struck a belt loader. The parking brake was set; tug hooked up; aircraft pushed back; tug moved and aircraft was towed to the gate. During this time I reminded the Passengers and Crew to remain in their seat with their seat belt on because we were not at the gate; I initially told the Passengers that we had a chock blocking our arrival to the gate because this is what I had thought had happened until I opened my window and looked out to see the tug. All Passengers and Crew exited the aircraft safely and without further incidence.


Second narrative: [Report narrative contained no additional information].


Synopsis: The flight crew reported that while being marshaled into the gate area an engine made contact with a stationary belt loader. After the belt loader was removed to a safe position; the aircraft was connected to a tug and pulled forward to the gate. No injuries were reported.
Date: 201902
Local time of day: 1201-1800
Location: ZZZ.Airport, US
Flight conditions: Marginal
Weather elements / visibility: 7
Light: Daylight
Aircraft: Bonanza 35
Operator: Corporate
Operating under: Part 91
Flight plan: VFR
Mission: Personal
Flight phase: Landing
ATC / advisory: Tower ZZZ
Aircraft component: Normal Brake System
Component problem: Failed
Reporter organization: Corporate
Reporter function: Single Pilot
Reporter qualification: Flight Crew Instrument; Flight Crew Multiengine; Flight Crew Commercial
Anomaly: Aircraft Equipment Problem Critical; Deviation / Discrepancy - Procedural Published Material / Policy; Ground Event / Encounter Loss Of Aircraft Control; Ground Excursion Runway
Detector: Person Flight Crew
When detected: Other On landing
Result: General None Reported / Taken
Contributing factors: Aircraft
Primary problem: Aircraft

Narrative: Brakes failed on landing rollout. Brakes went to the floor when depressed. Aircraft rolled off the side of the runway (at runway end) into grassy area. No right rudder authority with brakes; used left rudder to avoid hitting runway end lights. No damage to airplane; or ground equipment.




Synopsis: Bonanza pilot reported brakes failure during landing rollout resulted in a runway excursion.
Date: 201508
Local time of day: 1801-2400
Location: 2G2.Airport, OH
Flight conditions: VMC
Weather elements / visibility: 10
Light: Dusk
Aircraft: Small Aircraft
Operator: Personal
Operating under: Part 91
Flight plan: None
Mission: Personal
Flight phase: Landing
ATC / advisory: CTAF 2G2
Reporter organization: Personal
Reporter function: Pilot Flying; Single Pilot
Reporter qualification: Flight Crew Instrument; Flight Crew Private
Human factors: Distraction
Anomaly: Ground Event / Encounter Person / Animal / Bird
Detector: Person Flight Crew
When detected: In-flight
Result: Aircraft Aircraft Damaged; General Maintenance Action
Contributing factors: Airport; Environment - Non Weather Related
Primary problem: Environment - Non Weather Related

Narrative: Struck a deer immediately after touching down in wheel landing mode. Deer crossed in front of aircraft from left side while executing a normal landing on runway 32 at Jefferson County Airpark (2G2). I was able to maintain complete control of aircraft during the event. Visible damage caused by strike includes prop; right gear fairings; under belly panels; venture; and transponder antenna. No personal injuries to me or passenger were sustained. There was no time afforded to take evasive action prior to strike without risking a groundloop and risking further damage and/or personal injury. The landing lights were on during the landing and 2 notches of flaps were used which is the normal mode of configuration. A clearing approach to landing was made immediately prior to the landing in question in order to attempt to clear the area of wildlife.




Synopsis: A pilot of a vintage single engine aircraft reported striking a deer during landing rollout. No injuries were reported to either the pilot or his passenger; however the aircraft did sustain visible damage to exterior components.
Date: 201411
Local time of day: 0001-0600
Location: PCT.TRACON, VA
Aircraft: Military Transport
Operator: Military
Operating under: Part 91
Flight plan: IFR
Mission: Passenger
Flight phase: Final Approach
Airspace: Class B DCA; Special Use P56A; P56B
ATC / advisory: TRACON PCT
Reporter organization: Government
Reporter function: Approach
Reporter qualification: Air Traffic Control Fully Certified
Human factors: Communication Breakdown; Confusion; Situational Awareness; Workload
Anomaly: ATC Issue All Types; Deviation / Discrepancy - Procedural Clearance
Detector: Person Air Traffic Control
When detected: In-flight
Result: Air Traffic Control Separated Traffic
Contributing factors: Human Factors; Airspace Structure; Procedure; Aircraft
Primary problem: Procedure

Narrative: This is an ongoing situation involving VIP movements from ADW to P56A and P56B as well as movements to ADW.  There are no set procedures in place.  If the movement takes place during a slow traffic period; it's normally not too much of a problem.  On this particular day; Aircraft X was departing ADW to P56B during our most busy 30 minute arrival push with very strong winds.  Arrivals were stopped 3 minutes before Aircraft X lifted from ADW.  This caused all the arrival controllers to spin numerous aircraft with limited altitudes available.When Aircraft X got near DCA they decided to turn eastbound towards RFK stadium for some unknown reason causing more problems.  It's only a matter of time before one of these movements contributes to a major error or worse.  The expense to the airlines should also be factored in as well. There are two routes that are normally used.  One impacts traffic more than the other.  We never know what route they are on and if we ask; we are told as previously coordinated. Nobody at PCT has this information and I'm not sure if the DCA tower has it or not.  The route should be declassified for ATC eyes only; five minutes before lift-off.  Also Aircraft X never takes the least impacting route; which should be considered if the traffic volume at DCA is high.  A study should be done to assess the delays attributed to these movements.  Also the addition of other routes should be looked into that may be used to decrease or maybe even eliminate delays at DCA.  I've been told this issue has been raised before; but politically motivated entities have deterred improvements on our present way of doing things.




Synopsis: PCT Controller reports of confusion of routes when VIP flights depart the DCA airport.
Date: 202009
Light: Daylight
Aircraft: Commercial Fixed Wing
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Cruise
Airspace: Class A ZZZ
Reporter organization: Air Carrier
Reporter function: Flight Attendant (On Duty)
Reporter qualification: Flight Attendant Current
Human factors: Distraction; Communication Breakdown; Situational Awareness
Anomaly: Deviation / Discrepancy - Procedural Published Material / Policy; Flight Deck / Cabin / Aircraft Event Passenger Misconduct
Detector: Person Flight Attendant
When detected: In-flight
Result: General None Reported / Taken
Contributing factors: Company Policy; Human Factors
Primary problem: Human Factors

Narrative: Me and the C Flight Attendant were in the forward cabin just talking when a customer brought to the C Flight Attendant attention that a customer did not have his mask on.  I personally did not interact with the customer. The C just turned around and said that he was sleeping and that was that. I made PA during the flight reminding passengers of our mask policy.  I would make the PA if passengers were sleeping as a way to not single people out.Talk to all crew members so everyone is together on the mask policy so one person is not more easy going than the other and not making one flight attendant look bad for being scene as 'the mask police'.




Synopsis: Flight Attendant reported a passenger did not comply with face mask policy.
Date: 201909
Local time of day: 1801-2400
Location: ZZZ.Airport, US
Aircraft: A319
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Landing
Airspace: Class D ZZZ
ATC / advisory: Tower ZZZ
Reporter organization: Air Carrier
Reporter function: First Officer; Pilot Flying
Reporter qualification: Flight Crew Instrument; Flight Crew Air Transport Pilot (ATP); Flight Crew Multiengine
Human factors: Communication Breakdown; Training / Qualification
Anomaly: Deviation / Discrepancy - Procedural Published Material / Policy
Detector: Person Flight Crew
When detected: In-flight
Result: Flight Crew Overcame Equipment Problem
Contributing factors: Airport; Company Policy; Procedure
Primary problem: Company Policy

Narrative: I had the Pilot not Flying select the Tower frequency which was loaded in the #2 radio; and [to] click the microphone to turn the lights back on. He didn't know how I knew how to do that. In reflection; I thought that perhaps it would be a good training lesson for others that don't have much GA flying experience. I think a distance learning lesson reviewing communication procedures and lighting control at uncontrolled airfields might be beneficial to us all. We don't see it very often and it's something we are seeing more as we expand our services to smaller airports. In the interest of identifying a possible hazard to our SMS system; I just wanted to bring this to light. I know others would benefit from learning from this event. In our case; my prior experience allowed me to anticipate it and have a plan. I hope we can pass this along and prepare others for the same situation or maybe introduce it.




Synopsis: A319 First Officer reported instructing Pilot not Flying on the procedure to activate runway lights.
Date: 202010
Local time of day: 0601-1200
Location: ZZZ.Tower, US
Flight conditions: VMC
Weather elements / visibility: 10
Light: Daylight
Aircraft: Citation I (C500)
Operator: Personal
Operating under: Part 91
Flight plan: IFR
Mission: Personal
Flight phase: Climb
Aircraft component: Fuel Storage System
Component problem: Failed
Reporter organization: Personal
Reporter function: Captain
Reporter qualification: Flight Crew Flight Instructor; Flight Crew Instrument; Flight Crew Multiengine; Flight Crew Air Transport Pilot (ATP)
Anomaly: Aircraft Equipment Problem Less Severe; Flight Deck / Cabin / Aircraft Event Smoke / Fire / Fumes / Odor; Inflight Event / Encounter Fuel Issue
Detector: Automation Aircraft Other Automation; Person Air Traffic Control
When detected: In-flight
Result: Air Traffic Control Issued New Clearance; Air Traffic Control Issued Advisory / Alert; Flight Crew Returned To Departure Airport; Flight Crew Landed in Emergency Condition
Contributing factors: Aircraft
Primary problem: Aircraft

Narrative: [We] departed with an IFR plan from Runway 18. After liftoff handed off to Departure Control given clearance to heading 060 and climb to 5000 ft. Departure advised that Tower said we were trailing smoke from the right side of the aircraft. Concurrently; we got a fuel low pressure light for the right engine. We requested an immediate return to the tower frequency. [Tower] cleared us to an immediate left downwind Runway 18. Engine indications were normal. [We] executed the landing checklist and configured for possible single engine approach. The landing was uneventful. Upon rollout and abeam parking spot; Ground advised we were trailing fuel. [We] taxied to intersection Delta away from buildings; shutdown and evacuated aircraft. Fuel was beginning to pool under the wing; [so we] disconnected the battery and fire trucks and hazmat were notified. Total flight time was less than 5 minutes with an immediate return to nearest airfield.




Synopsis: CE-500 Captain reported a fuel leak which resulted in a return to departure airport.
Date: 202005
Local time of day: 1801-2400
Location: ZFW.ARTCC, TX
Weather elements / visibility: 20
Light: Dusk
Aircraft: Gulfstream G280
Operator: Corporate
Operating under: Part 91
Flight plan: IFR
Mission: Passenger
Flight phase: Descent
Airspace: Class A ZFW
ATC / advisory: Center ZFW
Second aircraft: B767 Undifferentiated or Other Model
Reporter organization: Corporate
Reporter function: Captain
Reporter qualification: Flight Crew Air Transport Pilot (ATP); Flight Crew Flight Instructor; Flight Crew Multiengine
Anomaly: Inflight Event / Encounter Wake Vortex Encounter; Inflight Event / Encounter Loss Of Aircraft Control
Detector: Person Flight Crew
When detected: In-flight
Result: Air Traffic Control Issued New Clearance; Flight Crew Regained Aircraft Control; Flight Crew Took Evasive Action
Contributing factors: Environment - Non Weather Related; Procedure
Primary problem: Environment - Non Weather Related

Narrative: While descending on the WESAT2 arrival into FTW; we encountered wake turbulence from a Boeing 767 that was approximately 20 miles in front of us and traveling in the same direction. Our aircraft banked to the left approximately 45 degrees and our autopilot disconnected. At this point I took over the controls and righted the aircraft while still fighting more of the turbulence. After a few seconds we were offered an offset from Fort Worth Center of which we accepted and made a right turn to put us more upwind. Soon after we were cleared direct to COWTN near FTW and we exited the event.




Synopsis: G280 Captain reported encountering wake turbulence on descent into FTW 20 miles in trail of a B767 that resulted in an uncommanded 45 degree roll to the left.
Date: 201210
Local time of day: 1201-1800
Location: ZNY.ARTCC, NY
Aircraft: Challenger Jet Undifferentiated or Other Model
Operator: Corporate
Operating under: Part 91
Flight plan: IFR
Flight phase: Climb
Airspace: Class A ZNY
ATC / advisory: Center ZNY
Reporter organization: Government
Reporter function: Enroute
Reporter qualification: Air Traffic Control Fully Certified
Human factors: Communication Breakdown
Anomaly: ATC Issue All Types; Deviation - Track / Heading All Types; Deviation / Discrepancy - Procedural Other / Unknown
Detector: Person Air Traffic Control
Result: General None Reported / Taken
Contributing factors: Human Factors; Procedure
Primary problem: Procedure

Narrative: Due to a hurricane approaching; rides in the local area were bad. An earlier report of severe turbulence at FL320 was reported approximately 45 minutes prior to me assuming the sector; so I made sure I issued advisories to all aircraft. My workload increased due to more time spent on the frequency. I received a call from Sector 10 asking if I noticed the routing on a Challenger. Initially I didn't know who they were talking about. He explained the aircraft was direct a fix I've never heard of. I told him I had no idea what he was talking about. After reviewing the situation I realized that the Challenger had a bad routing that was not corrected by TMU. The aircraft made a right turn much earlier than anticipated and entered Sector 73's airspace without any coordination from me. I do not know if Sector 10 caught the bad routing prior to him entering Sector 73's airspace. For years we have been complaining that TMU does a less than satisfactory job of catching bad routes out of New York Center. A study was done and concluded there was a problem. The report was given to one of the STMC's in TMU. A study was done by TMU and they determined there was such a minuscule number of bad routes no action would be needed.




Synopsis: ZNY Controller described an airspace incursion claiming that the TMU failed to correct a bad routing that led to the event.
Date: 201712
Local time of day: 1201-1800
Location: ORD.Airport, IL
Aircraft: B737 Undifferentiated or Other Model
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Parked
Reporter organization: Air Carrier
Reporter function: Captain
Reporter qualification: Flight Crew Air Transport Pilot (ATP)
Human factors: Confusion; Distraction
Anomaly: Deviation / Discrepancy - Procedural Published Material / Policy; Ground Event / Encounter Other / Unknown
Detector: Person Flight Crew
When detected: Aircraft In Service At Gate
Result: General None Reported / Taken
Contributing factors: Airport; Environment - Non Weather Related
Primary problem: Ambiguous

Narrative: While parked at ORD the passengers were disembarking and I was seated in my seat when suddenly the control wheel violently slammed back into me and simultaneous the aircraft started to slide sideways. I immediately placed the electrical hydraulic systems on and within a second the control wheel moved forward; I was able to apply brake pressure to stop the sideways movement of the aircraft. I called ramp control and asked who was behind me. He stated it was a B777. I informed him what happened. I then got up after everything appeared to be stable and went to the main cabin door to make sure everybody was ok. To my surprise; the aircraft moved about 2 feet. There was a 2-foot gap between the jet bridge and the aircraft. We were lucky no passengers fell through as they were getting off. I then went downstairs to make sure there were no injuries on the ground. I talked to the lead ramp person and he said all okay; by then maintenance was there and inspected the aircraft. He stated all was fine.




Synopsis: B737 Captain reported that while deplaning the aircraft at the gate; there was an abrupt aircraft movement. This movement was attributed to a heavy Boeing 777 taxiing behind his aircraft. No injuries were reported.
Date: 201502
Local time of day: 1201-1800
Location: LAX.Airport, CA
Flight conditions: VMC
Light: Daylight
Aircraft: B757 Undifferentiated or Other Model
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Final Approach
Airspace: Class B LAX
ATC / advisory: TRACON SCT; Tower LAX
Second aircraft: UAV - Unpiloted Aerial Vehicle
Reporter organization: Air Carrier
Reporter function: First Officer; Pilot Not Flying
Reporter qualification: Flight Crew Air Transport Pilot (ATP); Flight Crew Instrument; Flight Crew Multiengine; Flight Crew Flight Instructor
Human factors: Distraction
Anomaly: Conflict NMAC; Ground Event / Encounter Object; Inflight Event / Encounter Object
Detector: Person Flight Crew
When detected: In-flight
Result: General None Reported / Taken
Contributing factors: Human Factors
Primary problem: Human Factors

Narrative: We were on the ILS 25L coming into LAX on an unusually clear day with excellent visibility and none of the usual LA haze. The Captain (CA) was pilot flying (PF) and I was pilot monitoring (PM). We had just passed HUNDA by approximately 1 to 1.5 miles and were about to descend through an altitude of approximately 3;000 feet. I was just about to contact tower after being handed off by approach when something caught my eye slightly ahead and to the right of the aircraft. At first I thought it was a large bird soaring towards us; but as it passed outside of the right forward First Officer's (FO) window; I very clearly saw a large square-shaped bright red drone with black accents and black propellers. I had it in sight for approximately 3 seconds as it approached and passed. It appeared to be heading opposite our direction and I would estimate it was only about 50 to 100 feet higher than us when we were passing abeam it and it was probably only between 100 and 200 feet right of us. It was definitely close enough for me to very clearly see it and recognize what it was; but not close enough that I feared it would strike our right wing; engine; or stabilizer. Immediately after we passed it; I checked in with tower and reported that we had just passed a drone inside of HUNDA. The tower controller asked if an estimate of about 3;200 feet altitude for the drone was accurate and I agreed. A few seconds later he asked approximately how far away from us I thought it had passed and what color it was; and I gave a conservative estimate of approximately 200 feet away from us and red with black for the color.I'm not sure there is anything we as pilots or the tower controller could have done to prevent this uncomfortably close encounter between a drone and a large passenger airplane unless these objects are made to be detectable on radar and/or TCAS and traceable to their extraordinarily irresponsible owners/operators.




Synopsis: A B757 flight crew encountered a UAV on final approach to LAX as they descended through 3;000 feet MSL.