elihoole/asrs-aviation-reports huggingface dataset:
Date: 202106
Local time of day: 0601-1200
Location: ZZZZ.ARTCC, FO
Flight conditions: IMC
Weather elements / visibility: Turbulence
Aircraft: EMB ERJ 170/175 ER/LR
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Cruise; Descent; Initial Approach
ATC / advisory: Center ZZZZ
Aircraft component: Turbine Assembly
Component problem: Malfunctioning
Reporter organization: Air Carrier
Reporter function: Pilot Flying; Captain
Reporter qualification: Flight Crew Instrument; Flight Crew Air Transport Pilot (ATP); Flight Crew Multiengine
Human factors: Troubleshooting; Situational Awareness; Distraction
Second reporter function: Pilot Not Flying; First Officer
Anomaly: Aircraft Equipment Problem Less Severe; Deviation / Discrepancy - Procedural Clearance; Deviation / Discrepancy - Procedural FAR; Deviation / Discrepancy - Procedural Published Material / Policy; Inflight Event / Encounter CFTT / CFIT; Inflight Event / Encounter Weather / Turbulence
Detector: Automation Aircraft Terrain Warning; Person Flight Crew
When detected: In-flight
Result: Flight Crew Took Evasive Action; Flight Crew Became Reoriented; General Maintenance Action
Contributing factors: Procedure; Aircraft; Weather
Primary problem: Aircraft

Narrative: While enroute to ZZZ we experienced unusually high LP vibrations; still within limitations. No amber indication was observed. However; the vibrations were strong enough to be felt in the aircraft. Descending into ZZZ ATC cleared us to descend to 16;000 and cleared us for the approach. We began to descend when we noticed the vibrations were getting worse. While running the QRH we encountered sudden turbulence; shortly after we received a terrain alert and immediately executed the escape maneuver. We continued to ZZZ without further difficulty and to a safe landing. Crew became task saturated by increasing engine vibrations; sudden unexpected turbulence and QRH checklist.Suggestions - Terrain awareness chart or company jepps. Company awareness video regarding descent and approach into ZZZ.


Second narrative: ATC cleared us for the approach into ZZZ and notifies us of no radar coverage under 16;000 feet. The Captain set the initial approach fix and we began a descent on a VNAV path toward the airport. During descent we were handling an engine vibration issue with the QRH along with some unexpected turbulence; when we received a terrain notification. The Captain executed an escape maneuver and we continued to a safe landing on Runway XX at ZZZ. Crew became task saturated with the engine vibrations; QRH; and unexpected turbulence in descent.


Synopsis: EMB-175 flight crew reported distractions from troubleshooting LP engine vibrations and turbulence caused a descent and a terrain alert requiring an escape maneuver.
Date: 202103
Local time of day: 1201-1800
Location: ZZZ.Airport, US
Flight conditions: VMC
Light: Daylight
Aircraft: B737 Undifferentiated or Other Model
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Parked
Aircraft component: Airframe Composite Structure
Component problem: Failed
Reporter organization: Air Carrier
Reporter function: Pilot Not Flying; Captain
Reporter qualification: Flight Crew Air Transport Pilot (ATP); Flight Crew Instrument; Flight Crew Multiengine
Anomaly: Aircraft Equipment Problem Less Severe; Deviation / Discrepancy - Procedural Published Material / Policy
Detector: Person Maintenance
When detected: Aircraft In Service At Gate; Routine Inspection
Result: General Maintenance Action; General Flight Cancelled / Delayed
Contributing factors: Aircraft
Primary problem: Aircraft

Narrative: Upon completing the flight in ZZZ Tech Ops requested me to look at aircraft exterior problem. I met him and he showed the forward drain mast had failed and was detached from fuselage but still attached by the drain tube. A visual inspection showed that the trailing 75% of the fairing attach point had been fatigued and failed for some time. There was a fresh break in the forward 25% of the fairing attach point. All components looked intact; but dangling by the drain tube. I did the walk around in ZZZ1; and with total certainty the fairing was in place and attached. It did not appear that a ground object or bird had caused the damage. I believe it just structurally failed during the flight. Tech Ops said they had entered the discrepancy.




Synopsis: B737 Captain reported that a drain mast had fatigued and failed during flight and was discovered at the destination airport by maintenance.
Date: 202105
Local time of day: 1201-1800
Location: ZZZ.Airport, US
Flight conditions: VMC
Light: Daylight
Aircraft: PA-32 Cherokee Six/Lance/Saratoga/6X
Operator: Personal
Operating under: Part 91
Mission: Passenger
Flight phase: Cruise
Airspace: Class D ZZZ
Aircraft component: Magneto/Distributor
Component problem: Failed
Reporter organization: Personal
Reporter qualification: Maintenance Powerplant; Maintenance Repairman; Maintenance Avionics; Maintenance Airframe
Anomaly: Aircraft Equipment Problem Less Severe; Deviation / Discrepancy - Procedural Maintenance; Deviation / Discrepancy - Procedural FAR; Deviation / Discrepancy - Procedural Published Material / Policy
Detector: Person Flight Crew
When detected: In-flight
Result: Flight Crew Landed As Precaution; General Maintenance Action; General Flight Cancelled / Delayed
Contributing factors: Aircraft; Procedure
Primary problem: Aircraft

Narrative: The aircraft in question came in for a dead left magneto which failed in flight. We troubleshot and determined it was in fact a dead left magneto. We removed and replaced the left magneto with a factory rebuilt magneto. Ops checked everything fine. Mag drop was perfect. The pilot ran it as well. No issues. He loads up his passenger; and they take off. Well; the right-hand magneto fails on takeoff; resulting in him turning back and landing at the airport. Back in (Month) 2020 that right hand magneto failed and we replaced it with a factory rebuilt magneto as well. I am writing this to see what can be done about these factory rebuilt magnetos. I feel they are failing too soon. Only 100 hours in between failures. If the left magneto would've held out and failed at the same time as the right hand just did; it could've been a catastrophic failure and maybe even loss of lives.




Synopsis: Technician reported multiple magneto failures of factory rebuilt magnetos on the same PA-32 aircraft.
Date: 201211
Local time of day: 1201-1800
Location: ZZZ.Airport, US
Flight conditions: VMC
Weather elements / visibility: 10
Light: Daylight
Aircraft: PA-31 Navajo/Chieftan/Mojave/T1040
Operator: Government
Operating under: Part 91
Flight plan: IFR
Mission: Passenger
Flight phase: Climb
Airspace: Class C ZZZ
ATC / advisory: TRACON ZZZ
Aircraft component: Magneto/Distributor
Component problem: Malfunctioning
Reporter organization: Government
Reporter function: Captain; Pilot Flying
Reporter qualification: Flight Crew Multiengine; Flight Crew Instrument; Flight Crew Flight Instructor; Flight Crew Air Transport Pilot (ATP)
Anomaly: Aircraft Equipment Problem Critical
Detector: Person Flight Crew
When detected: In-flight
Result: Flight Crew Diverted; Flight Crew Inflight Shutdown; General Maintenance Action; General Declared Emergency
Contributing factors: Aircraft
Primary problem: Aircraft

Narrative: After initial climbout; the right engine started to surge. The other pilot and I both noticed that the oil and cylinder head temperatures also started to rise. With no clear explanation of the cause; I performed a precautionary shutdown of the right engine. We informed ATC and declared an emergency when switched to Approach Control. They asked us if we needed CFR and; not knowing the extent of the situation; we requested the services. We proceeded to land without further incident. After inspection by a Mechanic; it was found that the right magneto had partially failed.




Synopsis: When the right engine of their PA-31 started to surge and display increasing oil and cylinder head temperatures the flight crew performed an in-flight shutdown; declared an emergency with ATC; and diverted to the nearest suitable airport.
Date: 201301
Local time of day: 1201-1800
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: 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)
Human factors: Situational Awareness
Anomaly: Inflight Event / Encounter Fuel Issue
Detector: Person Flight Crew
When detected: In-flight
Result: Flight Crew Diverted; General Declared Emergency
Contributing factors: Aircraft
Primary problem: Aircraft

Narrative: Fuel stop; emergency descent; diversion; 14 hour duty day.




Synopsis: A B757 Captain declared an emergency; perhaps after a loss of pressurization; and diverted for fuel.
Date: 202011
Local time of day: 0601-1200
Location: ZZZ.Airport, US
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 Instrument; Flight Crew Multiengine; Flight Crew Air Transport Pilot (ATP)
Human factors: Distraction; Confusion; Situational Awareness; Time Pressure
Second reporter function: First Officer; Pilot Not Flying
Anomaly: Deviation / Discrepancy - Procedural Published Material / Policy; Flight Deck / Cabin / Aircraft Event Other / Unknown
Detector: Person Flight Crew
When detected: Taxi
Result: General None Reported / Taken
Contributing factors: Company Policy; Environment - Non Weather Related; Human Factors
Primary problem: Environment - Non Weather Related

Narrative: When I arrived at the airplane for departure I was informed that the FA X had called in sick.  Apparently he had been exposed [to] COVID-19. I discussed the need for a new general declaration with the agent once they had found a replacement. About 30 minutes before push back they gave me the new declaration with all positions filled; and I signed it. About 20 minutes before pushing the agent returned and told me that they had pulled the new crew member off for another flight; and asked me if we could go with XX [number] of FAs. Not catching my error I said yes and asked for a new general declaration; it arrived just before departure time I signed it and we departed shortly thereafter.This was my first flight in over nine months with passengers; I had a discussion with the Lead FA about the FA that had called in sick; and wanted to be sure none of the other FAs had been exposed to him; apparently none had. We also discussed the fact that we would be getting a replacement. I just missed the fact that our duty time would require XY [number of] FAs.For myself having been on leave and away from flying for so long; I need to slow everything down; take a little more time.


Second narrative: Last minute flight attendant sick call and another reassignment. Misunderstood flight attendant minimum requirements. Was unaware that requirements were based on duty day and not flight time. Departed 1 flight attendant undermanned.Last minute changes at a critical time. COVID-19 concerns and maximum limit of XX passengers. We should seek waiver for restricted load passenger flights. Need assistance from dispatch; flight attendants and load to help watch for errors in manning requirements.


Synopsis: Air carrier flight crew reported inadvertently departing with one less Flight Attendant than required for the flight.
Date: 201702
Local time of day: 1201-1800
Location: ZZZ.TRACON, US
Flight conditions: VMC
Light: Daylight
Aircraft: Regional Jet 900 (CRJ900)
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Cruise
Airspace: Class E ZZZ
ATC / advisory: TRACON ZZZ
Reporter organization: Air Carrier
Reporter function: First Officer; Pilot Flying
Reporter qualification: Flight Crew Air Transport Pilot (ATP)
Human factors: Distraction; Confusion; Situational Awareness
Anomaly: ATC Issue All Types; Conflict Airborne Conflict; Deviation / Discrepancy - Procedural Clearance; Deviation / Discrepancy - Procedural Published Material / Policy
Detector: Person Flight Crew
When detected: In-flight
Contributing factors: Procedure; Airspace Structure; Human Factors
Primary problem: Procedure

Narrative: Were given new full route clearance on the ground and told to expect 8;000 feet as final. We asked for clarification and they said it was because of congestion in New York airspace. So we assumed it was just 8;000 to get us out of the New York area. After takeoff we were told to maintain 8;000; then about 30 minutes later told to descend to 6;000 for traffic. This was the highest altitude we could get for the remainder of the flight. We went from New York area to Georgia at 6;000 feet. We notified dispatch before we left and during flight a few times.We were handed off to multiple TRACONs along the route and some of them were unfamiliar with our call sign. One I think we missed a couple calls because he was calling us something else and we didn't catch it. Over one intersection we got a traffic call from ATC; a C172 I believe. Was passing off our right opposite direction. We had visual contact the entire time; but as he passed us we got a TCAS TA followed by any RA of 'monitor vertical speed.' He passed above and to the right of us +300 feet according to the TCAS. We reported the RA to ATC and he basically just said sorry. Later on we had a second TCAS RA same type with another GA aircraft. ATC never pointed that one out; but we had visual contact the entire time. The remainder of the flight was uneventful with the exception we were about 30 plus minutes late getting in due to the 250 knot restriction. Fuel wasn't an issue; we kept close track of it and landed with extra.I still don't know why we got this altitude. There were a couple of other 121 regionals at the same altitude as us in that direction. It would have been safer for ATC just to delay us getting out and give us a higher altitude than having us down at the same altitudes as GA operators for that long of a distance.




Synopsis: CRJ-900 pilot reported of a final altitude of 8;000 feet for the flight from the New York area to Georgia.
Date: 201902
Local time of day: 1801-2400
Location: ZZZ.ARTCC, US
Flight conditions: Mixed
Weather elements / visibility: 10
Light: Night
Aircraft: B737-700
Operator: Air Carrier
Operating under: Part 121
Mission: Passenger
Flight phase: Cruise
ATC / advisory: Center ZZZ
Reporter organization: Air Carrier
Reporter function: Captain; Pilot Flying
Reporter qualification: Flight Crew Instrument; Flight Crew Air Transport Pilot (ATP); Flight Crew Multiengine
Anomaly: Aircraft Equipment Problem Critical; Flight Deck / Cabin / Aircraft Event Smoke / Fire / Fumes / Odor
Detector: Person Flight Attendant
When detected: In-flight
Result: Flight Crew Overcame Equipment Problem
Contributing factors: Human Factors
Primary problem: Human Factors

Narrative: Cruising at FL300; our flight attendants reported an electrical burning smell in the cabin. I asked for a more exact location of the smell and told them to keep me updated. Less than one minute later; they said the smell was getting stronger and passengers were concerned. I again told them to keep me updated. There was no smell in the flight deck. Again; one minute later we received four chimes from the Flight Attendant and were informed that there was a fire in the overhead bin and that she was grabbing the fire extinguisher. I told her to call me back after she deals with the fire and we would begin our descent. We [advised ATC] at that time and began our checklist items. After our oxygen masks were donned; the Flight Attendant called again and said there was no fire and that the electrical smell had subsided. We then informed ATC of the situation and had a normal landing in ZZZ.




Synopsis: Flight attendants on a B737-700 reported an electrical smell in the overhead bin while during cruise flight.
Date: 201508
Local time of day: 1201-1800
Location: ZZZ.Airport, US
Flight conditions: IMC
Weather elements / visibility: Cloudy
Light: Daylight
Aircraft: Beechjet 400
Operator: Air Taxi
Operating under: Part 91
Flight plan: IFR
Mission: Ferry / Re-Positioning
Flight phase: Initial Approach
Airspace: Class E ZZZ
ATC / advisory: TRACON ZZZ
Aircraft component: Main Gear Door
Component problem: Malfunctioning
Reporter organization: Air Taxi
Reporter function: First Officer; Pilot Not Flying
Reporter qualification: Flight Crew Air Transport Pilot (ATP)
Human factors: Situational Awareness
Anomaly: Aircraft Equipment Problem Less Severe; Inflight Event / Encounter Weather / Turbulence
Detector: Person Flight Crew
When detected: In-flight
Result: Air Traffic Control Provided Assistance; Flight Crew Diverted; Flight Crew Requested ATC Assistance / Clarification; Flight Crew Overcame Equipment Problem; Flight Crew Landed in Emergency Condition; Flight Crew Executed Go Around / Missed Approach
Contributing factors: Human Factors; Aircraft; Procedure
Primary problem: Aircraft

Narrative: On approach into ZZZ gear was extended to the down position. 3 green lights and red gear handle warning light illuminated. Notified ATC of a missed approach and requested holding instructions. Climbed to 4000ft and entered holding pattern. Referenced abnormal landing gear checklist (no checklist exists for condition) completed 2 cycles same condition persisted. Advised ATC of diversion to towered airport with weather appropriate for gear confirmation by tower. Retracted the gear and climbed to 10;000 and diverted to ZZZ1. While enroute contacted company and company maintenance for assistance. Advised them of situation and that we would be doing a low pass at ZZZ1 for gear confirmation. Upon arrival at ZZZ1 while executing low pass advised by tower that 3 gear down and locked and main gear doors extended. Executed a missed approach and climbed to 4000 for delay vectors. Contacted company again and was advised to use emergency gear door retraction handle. With gear down and locked emergency door retraction handle pulled red gear warning light extinguished. Proceeded back to ZZZ1 for normal landing condition. Emergency personnel were on standby at ZZZ1 upon arrival but not used.




Synopsis: BE-400XP flight crew received an abnormal landing gear indication on approach; so they diverted to a VFR; Tower-controlled airport. With assistance from company Maintenance and with a visual inspection by the Tower. They followed an unusual procedure; received normal gear indications; and landed uneventfully.
Date: 201910
Location: ZZZ.Airport, US
Aircraft: B787 Dreamliner 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); Flight Crew Instrument; Flight Crew Multiengine
Human factors: Communication Breakdown
Anomaly: Aircraft Equipment Problem Less Severe; Ground Event / Encounter Other / Unknown
Detector: Person Flight Crew; Person Ground Personnel
When detected: Taxi
Result: General Flight Cancelled / Delayed; General Maintenance Action
Contributing factors: Human Factors
Primary problem: Human Factors

Narrative: After pushback; tow crew asked me to release brakes as they were unable to disconnect towbar. With brakes released after a minute or so felt bump. Recognized breakaway and set brakes. Just after that; tow crew came on and said 'set brakes; set brakes.' Told him already set. Called for Maintenance to come out. Disembarked passengers with people mover. Got new plane.




Synopsis: B787 Captain reported a breakaway during pushback that resulted in aircraft damage.
Date: 201506
Local time of day: 1801-2400
Location: ZOA.ARTCC, CA
Aircraft: Large Transport
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Descent
Airspace: Class A ZOA
ATC / advisory: Center ZOA
Reporter organization: Government
Reporter function: Enroute
Reporter qualification: Air Traffic Control Fully Certified
Human factors: Workload; Situational Awareness; Time Pressure; Distraction; Confusion; Communication Breakdown
Anomaly: ATC Issue All Types; Deviation / Discrepancy - Procedural Published Material / Policy; Deviation / Discrepancy - Procedural Clearance
Detector: Person Air Traffic Control; Person Flight Crew
When detected: In-flight
Result: Air Traffic Control Provided Assistance; Flight Crew Returned To Clearance; Flight Crew Requested ATC Assistance / Clarification
Contributing factors: Procedure; Human Factors; Chart Or Publication
Primary problem: Chart Or Publication

Narrative: I was training at R34.  At approximately XA:24Z my trainee descended Aircraft X via the OAKES1 west transition.  The pilot asked to verify west transition.  A minute later he asked us to verify transition he thought we said west; we verified west transition.  Another minute later he asked if west was a waypoint he didn't see it on the chart. My trainee patiently asked if he was looking at the chart and told him to look at the 'arrival route description'  and told him where to look in that part.  There are going to be numerous times when we don't have time to answer questions like this and it could lead to multiple errors.  The number and type of questions seems to be getting worse and when we start doing this to SFO with 5 times the planes it probably will get much worse.  I don't know if it is automation in the planes; or pilots are having lots of issues and trying to be extra careful; but this needs to improve.We need a different arrival name for every transition.  That means 3 different arrivals into OAK.




Synopsis: An Oakland Center (ZOA) Controller reports of confusion from pilots on the transition names of the STARs. The Controller would like a different arrival name for every transition.
Date: 201906
Local time of day: 1201-1800
Location: ZZZ.Airport, US
Flight conditions: VMC
Weather elements / visibility: 10
Light: Daylight
Aircraft: Skyhawk 172/Cutlass 172
Operator: FBO
Operating under: Part 91
Flight plan: VFR
Mission: Training
Flight phase: Landing
ATC / advisory: Tower ZZZ
Reporter organization: FBO
Reporter function: Instructor
Reporter qualification: Flight Crew Flight Instructor; Flight Crew Instrument; Flight Crew Commercial; Flight Crew Multiengine
Human factors: Distraction; Confusion
Anomaly: Ground Event / Encounter Loss Of Aircraft Control; Ground Excursion Runway
Detector: Person Flight Crew
When detected: In-flight
Result: Flight Crew Regained Aircraft Control
Contributing factors: Aircraft; Human Factors
Primary problem: Human Factors

Narrative: Landing phase of flight at end of a training flight. Student in left seat; CFI in right seat. No issues with any phase of flight until roll out after landing. Plane veered to right during roll out after engaging brakes to slow down. Plane exited Runway XXR to the right side of the runway prior to the intersection with Runway XY/XZ. Was able to exit between lights; cross a grass area between runways and get onto Runway XY/XZ. Was able to regain control and exited all runways onto Taxiway A. Stopped and contacted Ground requesting taxi to FBO. Tested brakes and steering during taxi and had no further issues. Unsure if the issue was related to brakes or excitable student. No runway lights were hit nor any damage to aircraft.Learned that after years of instructing that either a student or an aircraft can still surprise a CFI. Will be much more aware of this particular student's actions in the future and much more prepared for his potential engagement with the controls. Human factors involved included complacency with student after years of no student issues.




Synopsis: Cessna 172 instructor pilot reported a runway excursion during landing roll-out.