elihoole/asrs-aviation-reports huggingface dataset:
Date: 201204
Local time of day: 1201-1800
Location: ZZZ.ARTCC, US
Flight conditions: VMC
Light: Daylight
Aircraft: Citationjet (C525/C526) - CJ I / II / III / IV
Operator: Corporate
Operating under: Part 91
Flight plan: IFR
Mission: Personal
Flight phase: Descent
Airspace: Class A ZZZ
ATC / advisory: Center ZZZ
Aircraft component: Turbine Engine
Component problem: Failed; Malfunctioning
Reporter organization: Corporate
Reporter function: Pilot Not Flying
Reporter qualification: Flight Crew Air Transport Pilot (ATP); Flight Crew Flight Instructor; Flight Crew Multiengine; Flight Crew Instrument
Anomaly: Aircraft Equipment Problem Critical
Detector: Person Flight Crew
When detected: In-flight
Result: Aircraft Equipment Problem Dissipated; Flight Crew Overcame Equipment Problem; General Maintenance Action
Contributing factors: Aircraft
Primary problem: Aircraft

Narrative: After starting the descent from FL430 to FL370 as directed by ATC; the right engine rolled back and failed. We advised ATC of our situation and asked for a descent to a lower altitude and direct to the airport. We then followed procedures and initiated a restart at FL200 which was successful. We then advised ATC that we did not need any further assistance and landed without incident. We then called Maintenance and the aircraft is getting the problem fixed; which at this point seems to have been a faulty fuel delivery unit.




Synopsis: A C-525B flight crew suffered a right engine flame out as they descended from FL430. A subsequent restart attempt at a lower altitude was successful and they continued to a safe landing where they sought maintenance attention.
Date: 201211
Local time of day: 0001-0600
Location: ZZZ.Airport, US
Light: Night
Aircraft: B747-400
Operator: Air Carrier
Operating under: Part 121
Mission: Cargo / Freight / Delivery
Flight phase: Taxi
Aircraft component: Flap/Slat Control System
Component problem: Malfunctioning
Reporter organization: Air Carrier
Reporter function: Captain; Pilot Flying
Reporter qualification: Flight Crew Air Transport Pilot (ATP)
Human factors: Situational Awareness
Anomaly: Aircraft Equipment Problem Critical; Deviation / Discrepancy - Procedural Published Material / Policy
Detector: Person Flight Crew
When detected: Aircraft In Service At Gate
Result: Aircraft Aircraft Damaged; General Flight Cancelled / Delayed; General Maintenance Action
Contributing factors: Aircraft; Human Factors; MEL; Procedure
Primary problem: Procedure

Narrative: A B747-400 aircraft was released for departure with two MEL items. Number 1 Pack was 'Inoperative' and Number 4 Flap Canoe fairing had been removed from the aircraft. Made stabilized approach to Runway-15 and landed in the touchdown zone with a Flap setting of 25. The Post-flight walk-around inspection was performed by Captain Y. He discovered a flap control rod protruding a few inches from the top of the Number 3 Flap Canoe fairing. Captain X brought this to my attention and I made a personal inspection. In turn; I brought this circumstance to the attention of Contract Maintenance personnel. After Contract Mechanic performed his initial inspection; he decided to electrically lower the flaps for a more comprehensive inspection. His immediate assessment was damage of unknown origin to flap control rods on Number 3 and Number 4 flap track assemblies. I made a maintenance logbook entry; identifying the initial discovery made during the post-flight walk-around inspection of the aircraft. I believe voluntary removal of aircraft fairings and/or related protective equipment is not a good scenario.




Synopsis: Pilot reports finding a Flap Control Rod protruding a few inches from the top of Number 3 Flap Canoe fairing on a B747-400 aircraft during a post flight walk-around inspection. Maintenance noted damage of unknown origin had occurred to Number 3 and Number 4 Flap Control rods on both flap track assemblies.
Date: 201910
Aircraft: B777-200
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Climb
Reporter organization: Air Carrier
Reporter function: Captain; Pilot Flying
Reporter qualification: Flight Crew Multiengine; Flight Crew Air Transport Pilot (ATP); Flight Crew Instrument
Human factors: Physiological - Other
Anomaly: Flight Deck / Cabin / Aircraft Event Smoke / Fire / Fumes / Odor
Detector: Person Flight Crew
When detected: In-flight
Result: Aircraft Equipment Problem Dissipated; Flight Crew Overcame Equipment Problem
Contributing factors: Aircraft
Primary problem: Aircraft

Narrative: Before the fire return all 3 of us were coughing up a lung. I have seen this before due to the fact the 777 has powerful recirculating fans and the dust and impurities can be blown back up through the radio rack below our feet. Once the event began I never thought about it again since there was no obvious external signs. The air felt and looked clear but we were all hacking away. After we landed I realized that we were more than likely breathing the particles from the ensuing smoke event.




Synopsis: B777 Captain reported temporary health symptoms from 'smoke event.'
Date: 201511
Local time of day: 1201-1800
Location: ZZZ.Airport, US
Flight conditions: VMC
Light: Daylight
Aircraft: B737-700
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Final Approach
Airspace: Class B ZZZ
ATC / advisory: Tower ZZZ
Second aircraft: PA-31 Navajo/Chieftan/Mojave/T1040
Reporter organization: Air Carrier
Reporter function: Captain; Pilot Flying
Reporter qualification: Flight Crew Air Transport Pilot (ATP)
Human factors: Situational Awareness; Communication Breakdown; Time Pressure
Second reporter function: Pilot Not Flying; First Officer
Anomaly: ATC Issue All Types; Conflict Ground Conflict; Critical; Deviation / Discrepancy - Procedural Published Material / Policy
Detector: Person Flight Crew
When detected: In-flight
Result: Air Traffic Control Issued New Clearance; Flight Crew Executed Go Around / Missed Approach; Flight Crew Requested ATC Assistance / Clarification; Flight Crew Took Evasive Action
Contributing factors: Environment - Non Weather Related; Human Factors; Procedure
Primary problem: Human Factors

Narrative: I was Pilot Flying. At approximately four mile final; we were cleared to land on Runway XXR. I saw a smaller aircraft in position on runway. Pointed it out to FO who confirmed he saw it as well. Traffic was not rolling as we got closer. FO confirmed landing clearance with Tower. We then told Tower that there was an aircraft on the runway. I quickly reviewed go-around procedures. Tower told other aircraft to immediately exit runway to the left. Got down to about 300 ft AGL and aircraft appeared to have cleared safely; however; we did the go-around; visual pattern and return. End of event. Confirm conflicting traffic earlier. Seems like Tower forgot he was there.


Second narrative: On final approach in VMC conditions on ZZZ Runway XXR; we were cleared to land. On a mile final; the Captain noticed a small plane in position on Runway XXR. On short final; we asked if we were cleared to land. Tower confirmed we were cleared to land. I quickly asked about the plane on the runway. Tower was unaware of the small twin engine GA aircraft on the runway. The Tower told the small plane to quickly exit the runway. As the small plane was trying to clear the runway; the Tower told us to go around. We executed a normal go-around and came back for a visual approach without further incident.


Synopsis: Local Controller cleared an aircraft into position after the previous landing and became distracted by an ASDEX alarm; assumed to be an operations vehicle. The aircraft in position was forgotten until the next jet arrival crew asked about it and were sent around at 200 feet.
Date: 202110
Local time of day: 1201-1800
Location: ZZZ.ARTCC, US
Aircraft: EMB ERJ 145 ER/LR
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: Air Conditioning and Pressurization Pack
Component problem: Malfunctioning
Reporter organization: Air Carrier
Reporter function: Captain; Pilot Flying
Reporter qualification: Flight Crew Air Transport Pilot (ATP); Flight Crew Instrument; Flight Crew Multiengine
Human factors: Troubleshooting
Anomaly: Aircraft Equipment Problem Less Severe; Deviation / Discrepancy - Procedural Clearance; Flight Deck / Cabin / Aircraft Event Smoke / Fire / Fumes / Odor
Detector: Person Flight Attendant; Person Flight Crew
When detected: In-flight
Result: Air Traffic Control Provided Assistance; Flight Crew Diverted; Flight Crew Landed As Precaution; Flight Crew Overcame Equipment Problem; Flight Crew Requested ATC Assistance / Clarification
Contributing factors: Aircraft
Primary problem: Aircraft

Narrative: The time posted of XA:00 pm is approximate. Sometime after level off at cruise altitude; there was a noticeable burning odor in the cockpit followed by brief drizzle of smoke. The Flight Attendant shortly called up and said the burning odor was in the back also but no smoke. It was very brief and at that time was going away when the Flight Attendant called. I directed the Flight Attendant to continue to search areas of possible smoke and get back to me. We followed all our procedures. There were no engine or other indications of smoke; and it all went away. After discussion upfront we made the decision for safety to divert to nearest suitable airport which was ZZZ1 with no further incidents. Always follow company policy and procedures. And make decisions based on the safest alternatives. Using our basic knowledge of the aircraft; we suspected a pack may have ceased. That would be logical of the temporary odor and the drizzle of smoke.




Synopsis: Air Carrier Captain reported a temporary fume event during cruise and executed a precautionary diversion to the nearest suitable airport.
Date: 201809
Local time of day: 0001-0600
Location: D21.TRACON, MI
Aircraft: Regional Jet 700 ER/LR (CRJ700)
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Descent
Airspace: Class E D21
ATC / advisory: TRACON D21
Reporter organization: Government
Reporter function: Approach
Reporter qualification: Air Traffic Control Developmental
Anomaly: ATC Issue All Types; Deviation - Altitude Crossing Restriction Not Met; Deviation - Altitude Undershoot; Deviation - Speed All Types; Deviation / Discrepancy - Procedural Published Material / Policy
Detector: Person Air Traffic Control
When detected: In-flight
Result: Air Traffic Control Issued Advisory / Alert; Air Traffic Control Issued New Clearance; Flight Crew Returned To Clearance; Flight Crew Became Reoriented
Contributing factors: Human Factors
Primary problem: Human Factors

Narrative: Aircraft X checked in descending via KLYNK ONE with the ATIS. KLYNK ONE requires Aircraft X to cross BONZZ at 12;000 FT at 260kts. Aircraft X crossed BONZZ at 17;000 FT and very fast. I had to reduce speed; vector and point out the aircraft to multiple positions to allow time to descend. He did not remember his previous clearance after I assigned headings and altitudes and asked him for his previous clearance. I gave a brasher notification and was told the pilot called and thought he was on the BONZZ ONE Arrival; which is a south flow procedure. He was assigned Runway 3R on initial contact. Can a pilot program a north flow runway on a south flow arrival procedure? This seems like a safety issue as our north and south flow STARs have similar names and similar fixes. With the ATIS advertising Runway 3R and 4L; I think a pilot should not be able to program Runway 3R or 4L on a south flow only STAR. The notes on the STARs say which runway to expect when assigned the STAR. I had this pilot make a mistake today and another pilot yesterday say he couldn't accept the STAR without knowing what runway transition he was supposed to use; so maybe we need to highlight that note or provide additional training to flight crews to review notes more carefully.




Synopsis: D21 Approach Controller reported an inbound CRJ-700 failed to make an altitude restriction on the KLYNK ONE RNAV arrival into DTW; apparently because of improper FMC programming.
Date: 201908
Local time of day: 1201-1800
Location: ZDC.ARTCC, VA
Flight conditions: Marginal
Weather elements / visibility: Thunderstorm; Turbulence; Rain
Light: Daylight
Aircraft: Commercial Fixed Wing
Flight plan: IFR
Mission: Other ALL
Flight phase: Descent; Climb; Cruise
Airspace: Class A ZDC; Class E ZDC
ATC / advisory: Center ZDC
Reporter organization: Government
Reporter function: Enroute
Reporter qualification: Air Traffic Control Fully Certified
Human factors: Confusion; Workload; Distraction; Situational Awareness; Training / Qualification
Anomaly: ATC Issue All Types; Deviation / Discrepancy - Procedural Other / Unknown; Inflight Event / Encounter Weather / Turbulence
Detector: Person Air Traffic Control
When detected: In-flight
Result: Air Traffic Control Separated Traffic; Air Traffic Control Issued New Clearance
Contributing factors: Weather; Company Policy; Human Factors; Procedure
Primary problem: Company Policy

Narrative: Training a D-side developmental. Weather was building over RDU and a line of weather was west of GSO extending north. Majority of the aircraft in our sector were deviating around the weather. All the CLT departures and northbound traffic were not able to stay on their routes. Require numerous point outs and coordination. The EDST (Enroute Decision Support Tool) was over a page and the amount of coordination and work load was barely manageable with all 3 of us.We then received a phone call from ZJX Ridgeway saying that ZTL had been shut off on the MGM playbook over GSO and wanted to know what to do with the planes; could we take them; and what route to give them due to weather. We had weather over 70% of our sector so we told them we would have to call back. We did call back and told them to put them off SDZ to keep traffic running while our supervisor went to find out with TMU what was going on. No communication was passed from TMU to FLM or controllers on what playbooks were in effect; leading to us not know how much traffic was coming; what destinations were being routed into our airspace; or for how long.Now all of J75 are deviating south requiring us to take point outs and all the northbound are being routed into our sector. The weather over GSO and RDU had caused all the traffic to funnel through 36; 07; 32; 16. There are planes everywhere unable to meet crossing restrictions; unable to climb departures; have CLT arrivals at 380. We are taking point puts on DC metros that are being handoff to sector 16 not 20. The conflict alert is going off because no one is near their routes. We are begging planes to turn otherwise we will lose separation. It is completely unsafe.Not once were we able to call weather due to unsafe situation of workload and too many aircraft. Traffic needs to be slowed. Plans to be communicated. Playbooks cannot run planes directly at the weather.




Synopsis: ZDC Controller reported during a period of weather deviations lack of Traffic Management flow initiatives caused an unsafe workload.
Date: 201908
Local time of day: 1201-1800
Location: ZZZ.Airport, US
Flight conditions: VMC
Weather elements / visibility: 10
Light: Daylight
Aircraft: M-20 J (201) / Allegro
Operator: Personal
Operating under: Part 91
Flight plan: IFR
Mission: Ferry / Re-Positioning
Flight phase: Initial Approach
Airspace: Class E ZZZ
ATC / advisory: Tower ZZZ
Second aircraft: Beechcraft King Air Undifferentiated or Other Model
Aircraft component: Engine
Component problem: Malfunctioning
Reporter organization: Personal
Reporter function: Single Pilot
Reporter qualification: Flight Crew Multiengine; Flight Crew Instrument; Flight Crew Commercial
Human factors: Time Pressure; Troubleshooting; Communication Breakdown
Anomaly: Aircraft Equipment Problem Critical; Conflict Airborne Conflict; Deviation - Altitude Excursion From Assigned Altitude; Deviation / Discrepancy - Procedural Published Material / Policy; Deviation / Discrepancy - Procedural Clearance
Detector: Person Flight Crew
When detected: In-flight
Result: Aircraft Equipment Problem Dissipated; Flight Crew Landed As Precaution
Contributing factors: Human Factors; Aircraft
Primary problem: Aircraft

Narrative: Flying to ZZZ. Approximately 7nm NE of ZZZ at 4000 MSL. I was being vectored for a visual approach runway 18. The engine started running extremely rough to the point I felt like it was going to quit. I told the tower controller that I had engine issues and needed to land immediately; nearest runway. I didn't hear a response; or it sounded like the Controller was giving instructions to another plane. I turned directly towards Runway 13 and started descending. I felt like I had enough altitude to make Runway 13 if the engine died; so I started troubleshooting. I tried switching fuel tanks; no joy. I tried different positions on the key switch; no joy. I tried cycling the fuel tank selector; again; thinking that maybe I didn't quite select the opposite fuel tank detent. The engine started running a little better; at least to the point that the throttle was responding to power changes. The Tower Controller asked me if I needed any assistance; roll the fire trucks; I replied that the engine was running better and I knew I could safely land the plane. It was after I landed that the ZZZ Tower Supervisor called me and said there was a possible pilot deviation in that there was a Hawker jet below me when I started descending and that there was a loss of minimum separation.




Synopsis: M20J pilot reported communication breakdown with ATC while troubleshooting engine malfunction; resulted in an airborne conflict.
Date: 202108
Local time of day: 0601-1200
Location: ZZZ.Airport, US
Flight conditions: VMC
Aircraft: A300
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Flight phase: Taxi
Aircraft component: Hydraulic Main System
Component problem: Malfunctioning
Reporter organization: Air Carrier
Reporter function: First Officer; Pilot Flying
Reporter qualification: Flight Crew Air Transport Pilot (ATP); Flight Crew Multiengine; Flight Crew Instrument
Human factors: Physiological - Other; Troubleshooting
Anomaly: Aircraft Equipment Problem Less Severe; Deviation / Discrepancy - Procedural Maintenance; Deviation / Discrepancy - Procedural Published Material / Policy; Flight Deck / Cabin / Aircraft Event Illness / Injury; Flight Deck / Cabin / Aircraft Event Smoke / Fire / Fumes / Odor
Detector: Person Flight Crew
When detected: Taxi
Result: Air Traffic Control Provided Assistance; Flight Crew Requested ATC Assistance / Clarification; Flight Crew Returned To Gate; General Flight Cancelled / Delayed; General Maintenance Action
Contributing factors: Aircraft
Primary problem: Aircraft

Narrative: After pushing back on the ZZZ ramp; we went to start the engines.  During the start; the Blue Hydraulic pressure gauge came up low; just to the yellow line.  Note that the Blue Hydraulic system had been serviced in ZZZ by Maintenance while we hub turned.  In consultation with ZZZ Maintenance; we shut down in position and they went to service the Blue Hydraulic.  After some time the Blue Hydraulic was back in the Top Hat.  Cleared off Maintenance; and restarted engines.  After start; When the bleed air transferred over to the packs; we immediately started getting smoke in the cockpit.  I initially smelled it.  Then with the rising sun coming in my side window; you could clearly see the smoke (vaporized Skydrol?)  coming out of my air vent starting to fill the cockpit.  The intensity of smoke increased with time.  We opened the windows for fresh air and shut off the packs.  Approximate about 3 - 4 minutes of chemical exposure.  We wound up taxiing back to the gate and eventually shut down the engines.  I felt a little light head; a scratchy throat; and was beginning to cough.  Captain had some similar issues.   After speaking with Chief Pilot; and self-evaluating our symptoms; we were driven to the local ER to get checked out.  At the hospital; poison control was contacted; X-ray's were taken and a breathing treatment administered before being released. Exact cause for this issue is still unknown to me...but it clearly has to do with the servicing of the Blue Hydraulic system and possible failure of aircraft parts.




Synopsis: A300 First Officer reported a ground gate return due to a fume event during departure taxi.
Date: 201205
Local time of day: 0601-1200
Location: ZZZ.Airport, US
Flight conditions: VMC
Light: Night
Aircraft: EMB ERJ 145 ER/LR
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Flight phase: Initial Climb
Airspace: Class C ZZZ
ATC / advisory: TRACON ZZZ
Aircraft component: Hydraulic System
Component problem: Failed
Reporter organization: Air Carrier
Reporter function: Captain; Pilot Flying
Reporter qualification: Flight Crew Air Transport Pilot (ATP)
Second reporter function: Pilot Not Flying; First Officer
Anomaly: Aircraft Equipment Problem Less Severe
Detector: Person Flight Crew
When detected: In-flight
Result: Flight Crew Landed in Emergency Condition; General Declared Emergency
Contributing factors: Aircraft
Primary problem: Aircraft

Narrative: Lost Hydraulic System 1 on departure; [we] followed QRH procedures including abnormal gear extension. [We] declared an emergency. Contacted Dispatch and Maintenance Control and decided to continue to our destination with gear down. Landed without event and; because of lack of steering; was towed to gate.


Second narrative: [No substantive additional information was included in the secondary narrative.]


Synopsis: An EMB-145 crew continued to their destination; declared an emergency; landed uneventfully and were towed to the gate following a system one hydraulic failure after takeoff.