elihoole/asrs-aviation-reports huggingface dataset:
Date: 202010
Location: ZZZ.Airport, US
Flight conditions: VMC
Aircraft: Commercial Fixed Wing
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Taxi; Takeoff / Launch
Airspace: Class B ZZZ
ATC / advisory: Tower ZZZ
Aircraft component: Air Conditioning and Pressurization Pack
Component problem: Malfunctioning
Reporter organization: Air Carrier
Reporter function: Captain; Pilot Flying
Reporter qualification: Flight Crew Instrument; Flight Crew Air Transport Pilot (ATP); Flight Crew Multiengine
Human factors: Situational Awareness; Distraction
Second reporter function: Pilot Not Flying; First Officer
Anomaly: Aircraft Equipment Problem Less Severe; Deviation / Discrepancy - Procedural Published Material / Policy
Detector: Person Flight Crew
When detected: Taxi
Result: Flight Crew Overcame Equipment Problem
Contributing factors: Environment - Non Weather Related; Human Factors; Aircraft
Primary problem: Human Factors

Narrative: Received aircraft from maintenance base in ZZZ with AFT FUEL BOOST PUMP MEL.  Called and got another Dispatcher to patch Captain to Maintenance Control.  Still did not get my answer about having to carry an extra 5;000 pounds of unusable fuel.  Flying with a First Officer who was on different aircraft.  Very little recent experience in aircraft; because of the COVID and personnel issues.  Slowed pace considerably to accommodate; First Officer [was] very hard on himself and working hard on flows; but not smooth and habit like.  Dark on departure; and with amber fuel pump light shining in my eye; I did not catch the switch out of place after the Before Takeoff Checklist was done and we took the runway for takeoff.  Got the tattle tale message after takeoff and debriefed the situation.


Second narrative: For breeze-on/reduced thrust takeoff from Runway XXL at ZZZ; we set and left L PAC switch on high position.  While climbing; we received ACARS alert message for incorrect pack configuration. We immediately corrected the problem. We continued the flight then landed ZZZ1 without any incidents.


Synopsis: Air carrier flight crew reported departing with an incorrect pack configuration.
Date: 201302
Local time of day: 1801-2400
Location: ZZZ.ARTCC, US
Flight conditions: VMC
Light: Night
Aircraft: A320
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Cruise
Airspace: Class A ZZZ
ATC / advisory: Center ZZZ
Aircraft component: Hydraulic Main System
Component problem: Malfunctioning
Reporter organization: Air Carrier
Reporter function: Pilot Not Flying; First Officer
Anomaly: Aircraft Equipment Problem Critical
Detector: Automation Aircraft Other Automation; Person Flight Crew
When detected: In-flight
Result: Flight Crew Landed in Emergency Condition; Flight Crew FLC complied w / Automation / Advisory; General Declared Emergency
Contributing factors: Aircraft
Primary problem: Aircraft

Narrative: Accomplished steps on ECAM. Verified G HYD SYS level low. Referenced the FM for additional information. Declared an emergency with ATC. Flew aircraft to our filed destination. Gravity extended the gear per FM. Accomplished normal landing. Stopped the aircraft on runway. Shut down engines. Got inspected by crash; fire and rescue. Maintenance towed us to gate.




Synopsis: An A320 ECAM alerted HYD G RSVR LO LVL so the crew complied with the QRH; declared an emergency; and continued to their destination where the stopped on the runway; then were towed to the gate.
Date: 202009
Local time of day: 1201-1800
Location: ORD.Airport, IL
Flight conditions: VMC
Aircraft: B737 Next Generation Undifferentiated
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Climb
Airspace: Class B ORD
ATC / advisory: Tower ORD
Aircraft component: Horizontal Stabilizer Trim
Component problem: Malfunctioning
Reporter organization: Air Carrier
Reporter function: First Officer; Pilot Not Flying
Reporter qualification: Flight Crew Instrument; Flight Crew Multiengine; Flight Crew Air Transport Pilot (ATP)
Human factors: Troubleshooting
Anomaly: Aircraft Equipment Problem Less Severe
Detector: Person Flight Crew
When detected: In-flight
Result: Flight Crew Returned To Departure Airport; General Flight Cancelled / Delayed
Contributing factors: Aircraft
Primary problem: Aircraft

Narrative: Upon climb out from runway 28R in ORD the Captain was unable to trim the stabilizer nose up with the yoke electric trim switch. He advised me of this and I helped him with manual trim from the trim wheel. We leveled off at 5;000 ft. and 250 knots for controllability and received permission from ATC to fly a box pattern to troubleshoot. We subsequently slowed to 230 knots for the pattern.We accomplished the Electronic Stabilizer Trim Inoperative procedure and got a patch through to [Maintenance Control] with dispatch monitoring on radio. Maintenance agreed with the procedure and with our decision to return to ORD. A flaps 15 landing was safely performed per the checklist and the aircraft was returned to [the] Gate.




Synopsis: B737 flight crew reported stabilizer trim malfunction during climb out.
Date: 201903
Aircraft: SR20
Flight phase: Parked
Reporter function: Technician
Anomaly: Aircraft Equipment Problem Less Severe
Detector: Person Maintenance
When detected: Routine Inspection
Result: Aircraft Aircraft Damaged
Contributing factors: Aircraft
Primary problem: Aircraft

Narrative: During a scheduled phase inspection oil had been present on the bottom oil sump area of the engine. Also charring was discovered on the fuel servo linkage; alternate air cable; throttle cable; manifold and oil temp wire harness; bottom right engine mount and inside of the cowling on the right side. The plastic wire harness for the manifold and oil temp was melted as well. All damage was found in the bottom right engine area.




Synopsis: Technician reported; oil heat damage and charring was found in engine compartment and associated engine components during routine inspection of SR20 aircraft.
Date: 201901
Local time of day: 1801-2400
Location: MMCU.Airport, FO
Flight conditions: VMC
Light: Night
Aircraft: EMB ERJ 145 ER/LR
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Descent
ATC / advisory: Center MMFR
Reporter organization: Air Carrier
Reporter function: Captain; Pilot Flying
Reporter qualification: Flight Crew Instrument; Flight Crew Multiengine; Flight Crew Air Transport Pilot (ATP)
Human factors: Communication Breakdown
Anomaly: ATC Issue All Types
Detector: Person Flight Crew
When detected: In-flight
Result: Air Traffic Control Issued New Clearance; Flight Crew Requested ATC Assistance / Clarification
Contributing factors: Human Factors; Procedure
Primary problem: Human Factors

Narrative: On descent into CUU; approach cleared us to fly the KIPAL1C STAR; then to fly the RNP 18L approach to Runway 18L. We informed the Controller that we are unable to fly RNP approaches; and requested the VORDME2 to Runway 18L from the KIPAL waypoint; which we were approaching. The Controller instead issued a clearance to proceed direct to CUU VOR; without any further approach clearance. I was unsure of his intentions; but given the terrain I stated we were unable to fly direct to the VOR and again requested the VORDME2 to Runway 18L from KIPAL. The Controller granted the request and cleared us for the approach. It was clear that the Controller assumed we could fly RNP approaches; and it was my impression that Controller wanted to clear us for a visual approach which would not have been safe given the substantial terrain between our location and the airport.




Synopsis: EMB-145 Captain reported requesting a new arrival clearance to MMCU airport after the Controller issued an RNP approach that the aircraft was not equipped to execute.
Date: 202106
Local time of day: 0001-0600
Location: HMN.Airport, NM
Flight conditions: VMC
Aircraft: Large Transport; Low Wing; 2 Turbojet Eng
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Cargo / Freight / Delivery
Flight phase: Cruise
Airspace: Class A ZAB
ATC / advisory: Center ZAB
Aircraft component: GPS & Other Satellite Navigation
Component problem: Malfunctioning
Reporter organization: Air Carrier
Reporter function: Pilot Flying; Captain
Reporter qualification: Flight Crew Instrument; Flight Crew Air Transport Pilot (ATP)
Human factors: Workload; Human-Machine Interface
Anomaly: Aircraft Equipment Problem Less Severe
Detector: Person Flight Crew
When detected: In-flight
Result: Air Traffic Control Provided Assistance; Aircraft Equipment Problem Dissipated; Flight Crew Overcame Equipment Problem; Flight Crew Requested ATC Assistance / Clarification; Flight Crew Became Reoriented
Contributing factors: ATC Equipment / Nav Facility / Buildings; Airspace Structure; Software and Automation; Aircraft
Primary problem: ATC Equipment / Nav Facility / Buildings

Narrative: As we were en-route at cruise altitude FL360 feet 80 miles northwest of HMN VOR when we started to experience degraded navigation performance in the form of ATC fail alerts and an increasing ANP (Actual Navigation Performance) number relative to RNP (Required Navigation Performance). We notified ATC and were informed of GPS jamming somewhere north of El Paso. As we proceeded west; the navigation performance of our aircraft degraded more to the point where we received an UNABLE RNP message along with a GPS amber message. Once we got west of ELP and the TCS area; the navigation performance gradually improved and came back within normal parameters. Route track and actual position of aircraft were unaffected and there were no deviations from the planned and cleared routing. Not really any way to avoid other than don't jam GPS. But considering ATC was aware of it and able to keep aircraft notified of where and when the jamming effects would abate; it is not a huge hazard.




Synopsis: Captain reported experiencing GPS Jamming; which rendered RNP (Required Navigation Performance) unavailable.
Date: 201604
Local time of day: 0601-1200
Location: ZZZ.Airport, US
Light: Daylight
Aircraft: PA-28 Cherokee/Archer/Dakota/Pillan/Warrior
Operator: FBO
Operating under: Part 91
Mission: Training
Flight phase: Takeoff / Launch
ATC / advisory: Tower ZZZ
Reporter organization: FBO
Reporter function: Pilot Flying; Trainee
Reporter qualification: Flight Crew Private
Human factors: Other / Unknown
Second reporter function: Instructor; Pilot Not Flying
Anomaly: Ground Event / Encounter Loss Of Aircraft Control; Ground Excursion Runway
Detector: Person Flight Crew
When detected: In-flight
Result: Flight Crew Rejected Takeoff
Contributing factors: Aircraft; Human Factors
Primary problem: Human Factors

Narrative: When we lined up on the runway the instructor said nose wheel straight and feet off the brake. In the process of taking off; I was giving it power. Instructor said full power. Then she said more right rudder. I pushed in the right rudder. My foot got stuck and I could not pull it out. My instructor put in left rudder to correct. We skidded off the runway.


Second narrative: Flight review for a student. Student taxied with no issues. On takeoff roll he veered to the left. I instructed more right rudder. He hit the right brake hard and got his foot stuck under a section of the plane. He was unable to release. I tried to correct with hard left rudder. We skidded off the runway to the right.


Synopsis: PA28 flight instructor and trainee reported a runway excursion on takeoff when the trainee's foot got stuck with full right rudder and brake engaged.
Date: 201808
Local time of day: 1201-1800
Location: DSM.Airport, IA
Flight conditions: VMC
Aircraft: Regional Jet 700 ER/LR (CRJ700)
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Flight phase: Descent
Airspace: Class C ZMP
ATC / advisory: Center ZMP
Second aircraft: Commercial Fixed Wing
Reporter organization: Air Carrier
Reporter function: Captain; Pilot Not Flying
Reporter qualification: Flight Crew Instrument; Flight Crew Air Transport Pilot (ATP); Flight Crew Multiengine
Human factors: Situational Awareness
Anomaly: Airspace Violation All Types; Conflict NMAC; Deviation - Altitude Excursion From Assigned Altitude; Deviation / Discrepancy - Procedural Published Material / Policy
Detector: Automation Aircraft RA
When detected: In-flight
Result: Flight Crew FLC complied w / Automation / Advisory; Flight Crew Took Evasive Action
Contributing factors: Human Factors
Primary problem: Human Factors

Narrative: ATC gave initial instruction for a descent to an altitude of 11;000 feet by Chicago Center (I believe); and was given a frequency change right away and Minneapolis Center (I believe) said amend altitude and maintain FL200. I believe we were crossing FL230; and shortly after; we got a TCAS RA; and we were close to the traffic by about -300 feet. First Officer clicked off the autopilot; complied with the RA; and I reported the event to ATC. No further incident.




Synopsis: CRJ-700 Captain reported a NMAC in the vicinity of DSM.
Date: 202111
Local time of day: 1201-1800
Location: ZZZ.ARTCC, US
Aircraft: Regional Jet 900 (CRJ900)
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Cruise
Airspace: Class A ZZZ
ATC / advisory: Center ZZZ
Reporter organization: Air Carrier
Reporter function: Captain; Pilot Flying
Reporter qualification: Flight Crew Air Transport Pilot (ATP); Flight Crew Multiengine; Flight Crew Instrument
Human factors: Workload
Anomaly: Aircraft Equipment Problem Less Severe; Deviation / Discrepancy - Procedural Clearance; Deviation / Discrepancy - Procedural Published Material / Policy; Flight Deck / Cabin / Aircraft Event Smoke / Fire / Fumes / Odor
Detector: Person Flight Attendant
When detected: In-flight
Result: Air Traffic Control Provided Assistance; Flight Crew Diverted; Flight Crew Requested ATC Assistance / Clarification; General Flight Cancelled / Delayed
Contributing factors: Aircraft
Primary problem: Aircraft

Narrative: On the evening of [date] I was Captain on Aircraft X with scheduled service from ZZZ - ZZZ1. Once the flight reached cruise altitude we received a call from the flight attendants. The flight attendants informed us that there was a strong odor that resembled gasoline that was filling a specific [section]. We coordinated a diversion to ZZZ2 with Dispatch out of an abundance of caution. We were unable to determine the cause of the noxious odor.




Synopsis: CRJ900 Captain reported a fume event during cruise. Flight crew diverted to a suitable airport.
Date: 202011
Flight conditions: VMC
Aircraft: Commercial Fixed Wing
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Parked
Reporter organization: Air Carrier
Reporter function: Pilot Flying; Captain
Reporter qualification: Flight Crew Air Transport Pilot (ATP)
Anomaly: Deviation / Discrepancy - Procedural Published Material / Policy
Detector: Person Flight Crew
When detected: Aircraft In Service At Gate
Result: General None Reported / Taken
Contributing factors: Company Policy; Environment - Non Weather Related; Human Factors
Primary problem: Human Factors

Narrative: After all my pre-flight duties were complete; the Flight Attendant offered me a cup of coffee; which I took; and removed my mask to drink it; I'm pretty sure I also removed my mask on flight xxx after all of my pre-flight duties were complete to consume coffee also.




Synopsis: Air carrier Captain reported removing the face mask to drink coffee after completing pre-flight.
Date: 201403
Local time of day: 1201-1800
Location: ZDV.ARTCC, CO
Weather elements / visibility: Turbulence
Reporter organization: Government
Reporter function: Enroute; Traffic Management
Reporter qualification: Air Traffic Control Fully Certified
Anomaly: No Specific Anomaly Occurred All Types
Contributing factors: Weather
Primary problem: Weather

Narrative: I work as an STMC at ZDV. One of my duties includes the oversight of PIREPs at ZDV. ZDV is responsible for 285;000 miles of airspace. The Rocky Mountains are in the middle of ZDV's airspace. I don't understand why Mountain Wave is not a line item included in PIREPs?As a glider instructor for over 30 years and a Manager of Traffic Management; I have a good understanding of the power of Mountain Waves over the Rocky Mountains. An Airline made special Mountain Wave routes to avoid active areas [some time ago]. A PIREP that includes Mountain Wave is entered into the remarks section of the PIREP form. Changes in speed and/or altitudes are entered into remarks. My suggestion would be to created a separate line item for Mountain Wave and define it with Altitude Changes and Speed Fluctuations.We have had numerous flights over the years at ZDV that have injured people and caused accident reports to be filed. Having +/- 4;000 FPM or greater and +/- 30 KTS or greater is not uncommon. On most days when Mountain Wave is strong; many flights cannot hold altitude. This information could then translate through the Service B network and be available for plotting purposes for any Aviation Weather product; rather than not being sortable and becoming more likely to be overlooked by Dispatchers; Controller; and pilots.




Synopsis: ZDV ARTCC Controller suggests a way to report Mountain Waves and turbulence in the Denver Center area.
Date: 201809
Local time of day: 1201-1800
Location: ZZZ.Airport, US
Flight conditions: VMC
Weather elements / visibility: 10
Light: Daylight
Aircraft: Small Transport; Low Wing; 2 Recip Eng
Operator: Personal
Operating under: Part 91
Flight plan: IFR
Mission: Personal
Flight phase: Landing
Airspace: Class C ZZZ
ATC / advisory: TRACON ZZZ
Aircraft component: Engine
Component problem: Malfunctioning
Reporter organization: Personal
Reporter function: Pilot Flying; Single Pilot
Reporter qualification: Flight Crew Instrument; Flight Crew Air Transport Pilot (ATP); Flight Crew Multiengine
Anomaly: Aircraft Equipment Problem Less Severe; Conflict Ground Conflict; Less Severe; Deviation / Discrepancy - Procedural Clearance; Deviation / Discrepancy - Procedural Published Material / Policy; Ground Incursion Runway
Detector: Person Flight Crew
When detected: In-flight
Result: Air Traffic Control Provided Assistance; Flight Crew Requested ATC Assistance / Clarification; General Maintenance Action
Contributing factors: Aircraft; Procedure
Primary problem: Aircraft

Narrative: I was vectored to final and instructed to maintain 180 KTS to a point on final. This is the maximum speed of the aircraft. This resulted in a steep and fast final for a visual approach. This resulted in the throttles being pulled all the way back to idle all the way down final. This is a very atypical situation that I had not encountered in this [older] Piston [Twin-Engine]. This would be a very atypical throttle position on final. On landing rollout; the engines stalled due to the throttle position. I rolled off the runway at the taxiway but could not make it across the hold short line and was unable to pull forward until I restarted the engines; which took a couple minutes. A commercial flight was sent around because of this.This was an entirely new situation for me in this airplane and obviously have never happened before. The chain of events was started when ATC was directing me to hold full speed all the way to the glideslope. Knowing what I know now; I would have told him that I was unable. The engine loss took me as a surprise and as I rolled off the runway; my communication with tower could've been better. My focus was on restarting the engines so I could pull forward and should have been directed more toward giving tower a complete picture of what was happening.




Synopsis: Pilot of piston twin-engine reported the engines stalled on landing rollout precluded crossing runway hold short line.
Date: 201810
Local time of day: 1801-2400
Location: ZZZ.Airport, US
Light: Night
Aircraft: Regional Jet 900 (CRJ900)
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Taxi
ATC / advisory: Tower ZZZ
Second aircraft: B717 (Formerly MD-95)
Reporter organization: Air Carrier
Reporter function: Captain; Pilot Flying
Reporter qualification: Flight Crew Air Transport Pilot (ATP); Flight Crew Multiengine; Flight Crew Instrument
Human factors: Time Pressure
Anomaly: ATC Issue All Types; Conflict Ground Conflict; Critical; Ground Incursion Runway
Detector: Person Air Traffic Control; Person Flight Crew
When detected: Taxi
Result: Air Traffic Control Provided Assistance; Flight Crew Requested ATC Assistance / Clarification
Contributing factors: Human Factors; Procedure
Primary problem: Human Factors

Narrative: While taxiing to Runway XY on Taxiway P in ZZZ we were told follow Aircraft Y and cross Runway ZA at Taxiway Papa. We were cleared across Runway ZA and following Aircraft Y; with traffic landing on Runway ZA on short final. However; as soon as Aircraft Y crossed they immediately stopped and switched frequencies. This left the tail of our [aircraft] on Runway ZA. Ground desperately tried to raise Aircraft Y; advising them to pull forward; and allowing us to clear Runway ZA. They were unsuccessful and we remained on Runway ZA unable to move forward or clear the runway. As a result the landing traffic for Runway ZA was sent around. Ground control eventually made contact with Aircraft Y and informed them of the situation that had transpired. They then pulled forward and we were able to clear Runway ZA before any additional landing traffic had to be sent around.The flight was then completed without any additional occurrences.




Synopsis: CRJ-900 Captain reported being unable to exit the runway when a CRJ failed to completely clear the runway; which resulted in landing traffic being sent around.
Date: 201712
Local time of day: 0601-1200
Location: LAS.Airport, NV
Light: Daylight
Aircraft: Large Transport; Low Wing; 2 Turbojet Eng
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Initial Approach
Airspace: Class B LAS
ATC / advisory: TRACON L30
Aircraft component: Aero Charts
Component problem: Design
Reporter organization: Air Carrier
Reporter function: First Officer; Pilot Flying
Reporter qualification: Flight Crew Air Transport Pilot (ATP)
Anomaly: Deviation / Discrepancy - Procedural Published Material / Policy
Detector: Person Flight Crew
When detected: In-flight
Result: Flight Crew Became Reoriented
Contributing factors: Chart Or Publication; Procedure
Primary problem: Chart Or Publication

Narrative: I was cleared for the Visual for 26L and was flying the approach in LNAV/VNAV. I backed it up with the ILS and passing SHAND; I armed APP mode. I noticed that LOC and G/S were armed in the FMA but never activated. It wasn't until the next leg when I heard another Crew ask if the ILS was out that I realized what had happened. The frequency on the Jeppesen charts is incorrect and both crew members had the ILS tuned to what the chart indicated. I returned to the approach chart and confirmed the frequency was wrong as well as the date at the top said Date.  Jeppesen needs to correct the typo on the chart and in the meantime Approach should let everyone know the frequency is incorrect as well as post a NOTAM.




Synopsis: Air carrier First Officer reported that the Jeppesen chart for the LAS LOC or ILS Runway 26L has an incorrect frequency listed for the 'IRLE' Localizer.