elihoole/asrs-aviation-reports huggingface dataset:
Date: 202106
Local time of day: 0601-1200
Location: ZZZ.Airport, US
Flight conditions: VMC
Weather elements / visibility: 10
Light: Daylight
Aircraft: Cessna 152
Operator: Personal
Operating under: Part 91
Flight plan: None
Mission: Training
Flight phase: Landing
Airspace: Class G ZZZ
Aircraft component: Rudder Pedal
Component problem: Improperly Operated
Reporter organization: Personal
Reporter function: Single Pilot; Pilot Flying
Reporter qualification: Flight Crew Student
Human factors: Training / Qualification
Anomaly: Aircraft Equipment Problem Critical; Deviation / Discrepancy - Procedural Published Material / Policy; Flight Deck / Cabin / Aircraft Event Other / Unknown; Ground Event / Encounter Loss Of Aircraft Control; Ground Excursion Runway
Detector: Person Flight Crew
When detected: Other Landing Roll Out
Result: Flight Crew Took Evasive Action; General Flight Cancelled / Delayed
Contributing factors: Aircraft; Procedure; Human Factors
Primary problem: Procedure

Narrative: Student went on first solo cross country to ZZZ. After touchdown; student lost pedal control and veered to the right into the grass. He proceeded to shut the aircraft down; inspect for damage; and call his instructor. He was able to push the airplane out of the grass and fly it back to the base




Synopsis: C152 Single Pilot reported losing pedal control causing a runway excursion.
Date: 201909
Local time of day: 0001-0600
Location: LAS.Airport, NV
Aircraft: A330
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Descent
Airspace: Class B LAS
ATC / advisory: TRACON L30
Second aircraft: B737 Undifferentiated or Other Model
Reporter organization: Government
Reporter function: Approach
Reporter qualification: Air Traffic Control Fully Certified
Human factors: Situational Awareness
Anomaly: ATC Issue All Types; Inflight Event / Encounter Loss Of Aircraft Control; Inflight Event / Encounter Wake Vortex Encounter
Detector: Person Flight Crew
When detected: In-flight
Result: Air Traffic Control Provided Assistance; Flight Crew Regained Aircraft Control; Flight Crew Took Evasive Action
Contributing factors: Aircraft; Environment - Non Weather Related
Primary problem: Environment - Non Weather Related

Narrative: Aircraft X a A330 was on the KEPEC arrival into LAS.  He checked on with speeds deleted from the Center.  I had to slow him to put him behind another arrival.  Aircraft Y was behind the Airbus by at least 11 miles.  Aircraft Y did not check in.  I reached out and they responded with they had an upset.  I asked if they were recovered and they said yes.  I slowed them to 230 kts.  Then Aircraft Y stated they had a crew member down.  I gave them a vector to get them in ASAP and told the FLM.  I handed off Aircraft Y to the final controller.I checked the replay and had 9 miles between the Heavy and Aircraft Y.  Also Aircraft Y was about 1;000 feet above the Airbus.I saw that the Center was deleting the speeds on the arrivals.  I should have reached out to them to have them stop doing that.  I thought I was safe with 9 miles with a heavy Airbus in front of the B737.




Synopsis: Las Vegas TRACON Controller reported a wake turbulence event with a B737 11 miles in trail of an Airbus 330.
Date: 201705
Location: POF.Airport, MO
Aircraft: No Aircraft
Reporter function: Observer
Reporter qualification: Flight Crew Air Transport Pilot (ATP); Flight Crew Multiengine; Flight Crew Instrument; Flight Crew Flight Instructor
Human factors: Communication Breakdown; Situational Awareness; Confusion
Anomaly: Deviation / Discrepancy - Procedural Published Material / Policy
Detector: Person Observer
When detected: Routine Inspection
Contributing factors: Airport; Chart Or Publication; Company Policy; Procedure
Primary problem: Airport

Narrative: Runway hold signs and runway hold markings are greater than 10 feet distance from each other. The signs and markings have been out of tolerance for years. I don't understand how a high cost taxpayer funded project can be completed with no quality control and airport management continually 'blows off' pilot concerns of compliance/standardization of airport signage/markings.




Synopsis: A pilot reported the runway hold signs and corresponding markings at POF airport are greater than 10 feet apart.
Date: 201704
Local time of day: 0601-1200
Location: ZZZ.Airport, US
Aircraft: Large Transport
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Flight phase: Taxi
ATC / advisory: Tower ZZZ
Aircraft component: Turbine Engine
Component problem: Malfunctioning
Reporter organization: Air Carrier
Reporter function: Dispatcher
Reporter qualification: Dispatch Dispatcher
Anomaly: Aircraft Equipment Problem Critical; Flight Deck / Cabin / Aircraft Event Smoke / Fire / Fumes / Odor
Detector: Person Air Traffic Control
When detected: Taxi
Result: Air Traffic Control Provided Assistance; General Maintenance Action
Contributing factors: Aircraft
Primary problem: Aircraft

Narrative: Crew called from their personal cell after landing that they had an emergency and were currently sitting [on a taxiway]. Crew stated they had been informed by the FAA Tower that they had smoke and possible fire coming from the Number 2 engine of the aircraft. Crew stated Crash Fire Rescue was at the aircraft and that they had shut down the Number 2 engine. Crew said they were fine; but asked that arrangements be made for the aircraft to be towed to our ramp due they would not be able to move under their own power. Crew also stated that they had ask CFR to stay with and follow the aircraft back to our ramp.




Synopsis: Air Carrier Dispatcher reported he was advised by a wide body flight crew that they were on a taxiway dealing with a possible engine fire that had been reported to them by the Tower.
Date: 201704
Local time of day: 1201-1800
Location: ZZZ.Airport, US
Light: Daylight
Aircraft: B777 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)
Anomaly: Flight Deck / Cabin / Aircraft Event Passenger Misconduct
Detector: Person Flight Attendant
When detected: Aircraft In Service At Gate
Result: General Flight Cancelled / Delayed
Contributing factors: Human Factors
Primary problem: Human Factors

Narrative: This is not the first incident of this kind of late; but FAs had to address a disruptive passenger who changed seats and then tried to extort some kind of compensation for causing disruption. The passenger threatened to film them and put it on the internet if the company would not pay him some kind of compensation. He baited them to forcibly remove him. The passenger feigned fear from the FA who was cordial and immensely patient throughout the incident. This is not the first such incident recently.The lack of sanction for any security violation that may have occurred due to recent events has now created a dangerous environment for our flight crews. Although one would hope this will blow over; the lingering effects are that some are taking advantage and compromising inflight security. The mob effect is a very real dynamic on an airplane; and the FAA needs to be aware of it and address it.

Callback: Reporter stated disruptive passenger was eventually coaxed back to his assigned seat; but said he wanted a meeting with the CEO after the flight. The reporter reaffirmed his concern that since no action was taken after recent passenger involved incidents; passengers are less mindful of crew member's instructions and even confrontational.



Synopsis: B777 Captain reported a disruptive passenger who changed seats and then tried to extort some kind of compensation for causing disruption.
Date: 201904
Local time of day: 0601-1200
Location: ELA.Airport, TX
Flight conditions: VMC
Weather elements / visibility: 10
Light: Daylight
Aircraft: Small Aircraft
Operator: Personal
Operating under: Part 91
Flight plan: None
Mission: Training
Flight phase: Taxi
ATC / advisory: CTAF ELA
Second aircraft: Small Aircraft
Reporter organization: Personal
Reporter function: Pilot Flying; Single Pilot
Reporter qualification: Flight Crew Commercial; Flight Crew Multiengine; Flight Crew Instrument; Flight Crew Flight Instructor
Human factors: Communication Breakdown; Situational Awareness
Anomaly: Conflict Ground Conflict; Critical; Deviation / Discrepancy - Procedural Published Material / Policy; Ground Excursion Runway
Detector: Person Flight Crew
When detected: Taxi
Result: Flight Crew Took Evasive Action
Contributing factors: Aircraft; Human Factors; Company Policy
Primary problem: Aircraft

Narrative: I was on a training flight in Aircraft X and was back taxiing to take off to the south on Runway 35/17. There is no parallel taxiway at ELA. We announced our back taxi and proceeded to the north when with approximately 1/3 of the runway left to go we saw Aircraft Y on short final. There were no radio calls from Aircraft Y. He did not seem to see us at first so I taxied off into the grass. He passed over us by 50 feet or so at the closest and had initiated a go-around. The Aircraft Y outfits at ELA do not use the radio- ever! It is an unsafe environment and the no radio use has created conflicts on multiple occasions. They do not use standard pattern entries of patterns either often entering at 200 or 300 feet. When approached about this they do not respond with any rationale or agreement to change.




Synopsis: Pilot reported a ground conflict and had to taxi into the grass when another aircraft overflew them at ELA non-towered airport.
Date: 201702
Local time of day: 1801-2400
Location: ZZZ.Airport, US
Light: Night
Aircraft: PA-28 Cherokee/Archer/Dakota/Pillan/Warrior
Operator: FBO
Operating under: Part 91
Flight plan: VFR
Mission: Training
Flight phase: Landing
ATC / advisory: Tower ZZZ
Reporter organization: Government
Reporter function: Local
Reporter qualification: Air Traffic Control Fully Certified
Human factors: Situational Awareness
Anomaly: Ground Excursion Runway
Detector: Person Air Traffic Control
When detected: Taxi
Result: Flight Crew Regained Aircraft Control
Contributing factors: Human Factors
Primary problem: Human Factors

Narrative: Aircraft X was given the option for RWY 16L upon landing they veered off to the left edge of the runway ground pointed out the aircraft off the runway.  I saw the aircraft re-entering the runway just north of Golf and maneuvered back to the centerline and gave them instructions to turn left at the end and contact ground point seven.  Wind was light and variable at 4 kts.




Synopsis: Tower Controller reported an aircraft landing and going off the runway; then entering the runway again.
Date: 201902
Local time of day: 0601-1200
Location: ZZZ.Airport, US
Aircraft: B737 Undifferentiated or Other Model
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Climb
Airspace: Class E ZZZ
ATC / advisory: Center ZZZ
Aircraft component: Waste Water Disposal System
Component problem: Failed
Reporter organization: Air Carrier
Reporter function: Captain
Reporter qualification: Flight Crew Commercial; Flight Crew Air Transport Pilot (ATP); Flight Crew Instrument; Flight Crew Multiengine
Human factors: Troubleshooting
Anomaly: Aircraft Equipment Problem Less Severe; Deviation / Discrepancy - Procedural Published Material / Policy; Deviation / Discrepancy - Procedural Weight And Balance
Detector: Person Flight Crew
When detected: In-flight
Result: Flight Crew Diverted
Contributing factors: Aircraft; Company Policy; Procedure
Primary problem: Aircraft

Narrative: We departed ZZZ with MEL 38-XX. Per the MEL; lavatories were tested for proper function above 16;000 feet and again at level off. All attempts failed to produce the expected results. Flight attendants attempted to operate all of the lavatories numerous times; yet they all remained inoperative. We contacted Dispatch and began a turn back to ZZZ.[Company Operations] determined ZZZ1 was a better choice to accommodate passengers for a follow on flight. After obtaining landing data and conferring with Dispatch; we elected to land overweight. ZZZ1 conducted a runway change. We obtained new landing data and completed an uneventful approach and landing. Uneventful overweight landing conducted on Runway XXR in ZZZ1 after consultation with Dispatch and [Company Operations] and obtaining landing data.Placing MEL 38-XX on an ETOPS flight might not be the best choice. Checking the system occurs above 16;000 feet and if not successful; requires either an overweight landing or a very lengthy delay to burn off fuel and reduce weight.




Synopsis: B737 Captain reported all of the aircraft lavatories did not work so they were forced to divert and land overweight.
Date: 201512
Local time of day: 0601-1200
Location: ABQ.Airport, NM
Flight conditions: VMC
Light: Daylight
Aircraft: B737-700
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Initial Approach
ATC / advisory: TRACON ABQ
Reporter organization: Air Carrier
Reporter function: Captain; Pilot Flying
Reporter qualification: Flight Crew Air Transport Pilot (ATP)
Human factors: Situational Awareness
Anomaly: Deviation / Discrepancy - Procedural Published Material / Policy; Inflight Event / Encounter CFTT / CFIT
Detector: Person Flight Crew
When detected: In-flight
Result: Flight Crew Became Reoriented
Contributing factors: Human Factors
Primary problem: Human Factors

Narrative: We were cleared the RNAV Visual to Runway 26 at ABQ. All points were briefed and altitudes confirmed during the approach briefing. The approach commenced normally until turning final. After turning final we were very low on the PAPI. At this point autopilot was turned off and I shallowed out the descent and made a normal landing. We were in visual conditions the entire time and from a visual standpoint everything looked normal. At some point during the approach the Actual Navigation Performance (ANP) bars turned amber. There were no real issues seeing that this approach was conducted in day VFR conditions. It might have been more of an issue at night. As far as I know there were no NOTAMs concerning this approach.




Synopsis: B737-700 Captain reported getting low on a visual approach to ABQ Runway 26.
Date: 201408
Local time of day: 1801-2400
Location: OMA.Airport, NE
Light: Night
Aircraft: Large Transport
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Final Approach
Airspace: Class C OMA
ATC / advisory: Tower OMA
Second aircraft: Medium Transport; Low Wing; 2 Turbojet Eng
Reporter organization: Government
Reporter function: Local
Reporter qualification: Air Traffic Control Fully Certified
Human factors: Communication Breakdown; Distraction; Situational Awareness; Confusion
Anomaly: ATC Issue All Types; Conflict Airborne Conflict; Deviation / Discrepancy - Procedural Clearance; Deviation / Discrepancy - Procedural Published Material / Policy; Ground Incursion Runway
Detector: Person Air Traffic Control
When detected: Other Vehicle on Runway
Result: Air Traffic Control Provided Assistance; Air Traffic Control Separated Traffic
Contributing factors: Human Factors; Procedure
Primary problem: Procedure

Narrative: I took the local control position in a north configuration.  Due to storms south of the field along final and winds favoring a south flow I decided to change to a south flow.  I coordinated this change after Aircraft X. There had been a bird strike prior to me taking the position.  When we notified the airport of the bird strike they did not close the runway; they only said they would go out and search.  The previous controller had advised two aircraft that there was a bird strike on 32L and if they still wanted to land. The visibility was 1 3/4 we couldn't switch them to the parallel.  A Operations vehicle came out and I was getting an aircraft off the runway.  The incoming CIC asked me what [the operations vehicle] was doing.  I looked and saw the vehicle on the runway with an aircraft on a two mile final.  I sent the aircraft around.  The confusion was around whether the runway was closed and it is the airports call to close the runway.  The ground controller thought the runway was closed and allowed city operations onto the runway.  When I realized city operations was on the runway I looked at the RID and placard and I had both in possession. To avoid further confusion put something in writing in the SOP.




Synopsis: OMA Tower Controller reports of a bird strike; calls city operations out to take a look.  Controller never clears city operations vehicle onto runway and an aircraft is on short final.  Controller sends aircraft around.
Date: 201406
Local time of day: 1201-1800
Location: EWR.Airport, NJ
Flight conditions: VMC
Aircraft: Large Transport
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Landing
Airspace: Class B EWR
ATC / advisory: Tower EWR
Reporter organization: Air Carrier
Reporter function: First Officer; Pilot Flying
Human factors: Time Pressure; Communication Breakdown; Workload
Anomaly: ATC Issue All Types; Conflict Ground Conflict; Less Severe
Detector: Person Flight Crew
Result: Flight Crew Took Evasive Action
Contributing factors: Airport; Procedure; Human Factors
Primary problem: Procedure

Narrative: We were given the LOC to Runway 11. Approach kept us high and wanted us to fly 210 KTS as long as possible then 180 KTS as long as possible. We had to configure and slow to get on the approach stabilized and descend. We were a little high initially; but were on VASI inside 500 FT. Auto brakes were low as briefed. We landed within 2;000 FT; and began deceleration when with only a couple of thousand feet remaining the Tower tells us to hold short of 29. It was way too late of a call. I braked heavily and the Captain jumped on the brakes as we barely got stopped in time. When we told the Controller that he issued the hold short way too late; he nonchalantly said; 'Well if you told me you couldn't stop I would have made company go-around. We should of have said unable; but we're quite busy bringing the aircraft to a stop and really had no time to evaluate if we could stop or even answer before the hold line was on us. Surely; the Tower has a responsibility not issue a hold short at the last minute during roll out on a 6;500 FT runway. My answer to all hold shorts in the future is unable. The Tower needs to use better decision making in giving those instructions.




Synopsis: Air carrier First Officer reports of Tower Controller telling pilot to hold short of another runway while they are on landing roll. Communication is too late and pilot has to brake heavily to comply.
Date: 201301
Local time of day: 1201-1800
Location: ZZZ.Airport, US
Flight conditions: VMC
Weather elements / visibility: 7
Light: Dusk
Aircraft: Cessna 152
Operator: FBO
Operating under: Part 91
Flight plan: VFR
Mission: Training
Flight phase: Landing
Airspace: Class D ZZZ
ATC / advisory: Tower ZZZ
Reporter organization: FBO
Reporter function: Instructor; Pilot Not Flying
Reporter qualification: Flight Crew Flight Instructor; Flight Crew Instrument; Flight Crew Commercial
Human factors: Other / Unknown
Anomaly: Aircraft Equipment Problem Critical; Inflight Event / Encounter Fuel Issue
Contributing factors: Aircraft; Human Factors
Primary problem: Human Factors

Narrative: I am the Flight Instructor of the solo student who made an off field emergency landing. This lesson; as part of the 141 syllabus; was his 3rd solo flight. I let him preflight and I was there for part of it. I did a cockpit check and noticed the fuel gauges indicated half; or 12 gallons usable fuel (which to 2.0 hours flight time). I then checked the exterior of the aircraft as well. As we were getting a quart of oil to put in the engine; he told me that he had visually checked the fuel tanks and they indicated that they were at half. He finished his preflight and I walked in to the Dispatch Office to monitor the Tower frequency. I did not take the step further and check the fuel tanks for myself. Given that he has flown before and that he has demonstrated proficiency in entering and leaving the practice area and that it was a one hour flight (with enough fuel to complete the lesson and have legal fuel reserves); I released him to fly. His flight duration was 1.7 hours.Looking back at all my solos except for my initial; I do not recall my instructors doing preflight with me and since nothing in the SOP for the school says I should be there to preflight with my student for solo flights; I let him fly; taking reasonable precautions in my mind and given my aviation experience regarding solo students. This is the first school in which I have let student pilots solo. I have soloed 2 other student pilots and let 5 part 141 student fly solo under commercial lessons (after having obtained their PPL). Above all else; I am grateful that my student walked away from the aircraft unharmed and is excited to fly again. The information I stated above has been filled to the best of my knowledge and memory with the resources I have available to me.




Synopsis: C152 Flight Instructor describes the preflight and departure of his student on his third solo that ends in an off field landing due to fuel exhaustion.
Date: 202006
Local time of day: 0601-1200
Location: RDG.Airport, PA
Flight conditions: VMC
Aircraft: Pilatus Undifferentiated
Operating under: Part 91
Flight phase: Takeoff / Launch
Second aircraft: Cessna Citation Undifferentiated or Other Model
Reporter function: Captain; Pilot Flying
Reporter qualification: Flight Crew Instrument; Flight Crew Air Transport Pilot (ATP)
Human factors: Situational Awareness
Anomaly: Conflict Ground Conflict; Critical; Deviation / Discrepancy - Procedural Published Material / Policy
Detector: Person Flight Crew
When detected: Other takeoff roll
Result: Flight Crew Rejected Takeoff; Flight Crew Took Evasive Action
Contributing factors: Human Factors
Primary problem: Human Factors

Narrative: Tower was closed at Reading and I was about to takeoff from Runway 13. I knew a Citation had just landed on Runway 36 so I announced I was taking off Runway 13 twice; once as I was entering the runway and once when I started the takeoff roll. I noticed the Citation on Taxiway Delta as I was in the takeoff roll. The Citation continued to cross Runway 13 as I was taking off. I aborted the takeoff and got off on Taxiway Foxtrot. The Citation then called and announced they were clear of the runway.  Be aware aircraft may not be on the right frequency at RDG and/or may not be making announcements.




Synopsis: Pilatus pilot reported rejecting the takeoff when a Citation taxied across the runway ahead of him.