elihoole/asrs-aviation-reports huggingface dataset:
Date: 201411
Flight conditions: VMC
Aircraft: Caravan Undifferentiated
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Flight phase: Cruise
Aircraft component: De-Icing Fluid
Component problem: Design
Reporter organization: Air Carrier
Reporter function: Pilot Flying
Reporter qualification: Flight Crew Air Transport Pilot (ATP)
Human factors: Communication Breakdown; Distraction; Human-Machine Interface; Physiological - Other
Anomaly: Aircraft Equipment Problem Critical; Deviation / Discrepancy - Procedural Published Material / Policy; Deviation / Discrepancy - Procedural Hazardous Material Violation; Flight Deck / Cabin / Aircraft Event Illness / Injury
Detector: Person Flight Crew
When detected: In-flight; Taxi; Pre-flight; Aircraft In Service At Gate
Result: General Physical Injury / Incapacitation
Contributing factors: Aircraft; Human Factors
Primary problem: Aircraft

Narrative: TKS fluid hazmat contamination of cockpit. Entire Fleet was scheduled to have TKS anti ice system run day before on scheduled weekly test to try and prevent system clogging and failing. Pilot noted fluid residue on aircraft throughout day. While enroute at end of day I had cabin vents open; TKS off; I noticed noted throat irritation; voice becoming raspy; and difficulty breathing/ tightness in chest. TKS (a hazmat) MSDS warns of these symptoms with exposure. Multiple flight crews experiencing TKS contamination of cockpit and suffering health effects noted on warnings of MSDS. Flight crews very concerned about long term health effects of TKS on crews. Some crews including myself have been unable to operate cars after operating TKS system on aircraft. This is dangerous!




Synopsis: C-208 pilot reports suffering from exposure to uncontained TKS anti-icing fluid.
Date: 201601
Local time of day: 1201-1800
Location: MAF.Tower, TX
Flight conditions: VMC
Light: Daylight
Aircraft: Medium Large Transport; Low Wing; 2 Turbojet Eng
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Initial Climb
Airspace: Class C MAF
ATC / advisory: Tower MAF
Second aircraft: Helicopter
Reporter organization: Government
Reporter function: Local
Reporter qualification: Air Traffic Control Developmental
Human factors: Training / Qualification; Communication Breakdown; Time Pressure
Anomaly: ATC Issue All Types; Conflict Airborne Conflict
Detector: Person Air Traffic Control
When detected: In-flight
Result: Air Traffic Control Issued Advisory / Alert; Flight Crew FLC complied w / Automation / Advisory; Flight Crew Took Evasive Action
Contributing factors: Human Factors; Procedure
Primary problem: Human Factors

Narrative: I was working the Local Control position. I was made aware of a NORDO helicopter that was 4 miles west of the airport proceeding northeast bound. An air carrier called ready for departure. I already had the helicopter in sight and based on past experiences with aircraft performance I thought the departure would depart and climb at a more expedited rate. Once I realized that the helicopter was going to be a factor and it was too late to cancel the takeoff clearance; I quickly issued traffic. At that point; the departure notified me that he was responding to an RA. The helicopter remained NORDO for the whole event despite my efforts to contact him.In my opinion this was a onetime event of human error that could have been prevented if I had waited until the NORDO aircraft left my airspace.




Synopsis: Local Controller cleared an aircraft for takeoff with a NORDO (No Radio) helicopter crossing the departure path. The departure did not climb as the Controller expected. The aircraft received and responded to a TCAS RA.
Date: 202009
Location: ZZZ.TRACON, US
Flight conditions: IMC
Light: Daylight
Aircraft: Commercial Fixed Wing
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Initial Approach
Airspace: Class E ZZZ
ATC / advisory: TRACON ZZZ
Aircraft component: Autopilot
Component problem: Malfunctioning
Reporter organization: Air Carrier
Reporter function: Captain; Pilot Not Flying
Reporter qualification: Flight Crew Air Transport Pilot (ATP); Flight Crew Instrument; Flight Crew Multiengine
Human factors: Communication Breakdown; Distraction; Situational Awareness
Anomaly: Aircraft Equipment Problem Less Severe; Deviation / Discrepancy - Procedural Published Material / Policy; Flight Deck / Cabin / Aircraft Event Passenger Misconduct
Detector: Person Flight Crew
When detected: In-flight
Result: Flight Crew Overcame Equipment Problem
Contributing factors: Human Factors; Procedure; Environment - Non Weather Related; Aircraft
Primary problem: Human Factors

Narrative: At 11;000 feet Flight Attendant called; notified of passenger face mask non-compliance; causing a distraction with announcement location and announcement briefing. Once on course with Runway XX; approximately 2-3 miles before ZZZZZ; during flap extension to flaps 45; autopilot disconnected. We believe the autopilot disconnected because during flap extension speed dropped off. As the First Officer was adding power and correcting; autopilot disconnected. First Officer then hand flew and we tried autopilot again. It engaged normally.




Synopsis: Air carrier Captain reported being distracted by a Flight Attendant call and the autopilot disconnected during flap extension.
Date: 201303
Local time of day: 1201-1800
Location: ZZZ.Airport, US
Flight conditions: VMC
Light: Dusk
Aircraft: EMB ERJ 145 ER/LR
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Climb
Airspace: Class B ZZZ
ATC / advisory: Center ZZZ
Aircraft component: Hydraulic Main 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 Critical
Detector: Person Flight Crew
When detected: In-flight
Result: Flight Crew Returned To Departure Airport; General Declared Emergency
Contributing factors: Aircraft
Primary problem: Aircraft

Narrative: Just after rotation my First Officer saw that the EICAS has the HYD2 LO QTY advisory message. At our first level off at 4;000 feet we turned the autopilot on and ran the QRH for this message. The situation seemed to be fine; all systems operating normally and continued to monitor the system. Upon further climb the engine driven hydraulic pump failed and the standby hydraulic pump took over. We then ran the QRH for that specific problem. The problem still didn't remedy itself and we lost hydraulic system 2. We ran the QRH for that problem. The final part of this problem happened at FL260. We ACARS messaged Dispatch; notified Maintenance and Ops that we would be doing an air return for HYD SYS 2 failure. We followed the QRH and operated the aircraft accordingly. [After landing] we were followed to the gate by ARFF with no other incident. When we got off the aircraft there was a mechanic there to greet us. We went to the tail of the aircraft and found that one of the drains was leaking hydraulic fluid. The QRH gave great guidance and procedures.


Second narrative: [Narrative 2 had no additional information.]


Synopsis: EMB-145EP flight crew reported loss of Number 2 hydraulic system. An emergency was declared and they returned to departure airport.
Date: 201501
Local time of day: 0601-1200
Location: ZZZ.TRACON, US
Flight conditions: VMC
Aircraft: B767 Undifferentiated or Other Model
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Cruise
Reporter organization: Air Carrier
Reporter function: Pilot Flying; First Officer
Reporter qualification: Flight Crew Air Transport Pilot (ATP)
Human factors: Other / Unknown
Second reporter function: First Officer; Pilot Not Flying
Anomaly: Aircraft Equipment Problem Less Severe; Flight Deck / Cabin / Aircraft Event Smoke / Fire / Fumes / Odor
Detector: Person Flight Attendant; Person Flight Crew
When detected: In-flight
Result: Flight Crew Landed As Precaution; Flight Crew Returned To Departure Airport; General Flight Cancelled / Delayed
Contributing factors: Aircraft
Primary problem: Aircraft

Narrative: Climbing out of ZZZ at 6;000 feet; the Purser called the cockpit during sterile conditions to report multiple flight attendants smelling fumes aft of business class galley.  As climbout continued; the cabin crew report[ed] immediate dissipation of the smell.  No visible smoke or fire found.  Relief pilot sent to back to confirm no continuing threat.  Determined to be a transient condition with no secondary indications of malfunctions.  Flight continued to altitude of FL350.After another hour; Purser called again saying two other Flight Attendants had smelled an electrical smell similar to one when one plugs in a new computer for the first time.  It quickly dissipated as well.  Relief Pilot was awakened as a precaution to inspect the area.  He smelled nothing and found no secondary indications of smoke or fire.  He returned to the cockpit and a discussion of our situation followed.After lengthy discussions as we approached Coast Out to ETOPS airspace; we decided the most safe course of action was to turn the aircraft around and stay within close proximity of emergency alternates should the indications recur.  We briefed procedures and alternates throughout the return to ZZZ.  Since we never had a confirmed malfunction or irregular operation; we did not declare an emergency.  Safe landing in ZZZ occurred with no new indications of smoke or fire.  Maintenance and Dispatch were consulted throughout the evolution via SATCOM in flight and in person once blocked in.  Flight crew agreed that due to the possible escalation of the somewhat ambiguous indications; ours was the safest and most prudent response to this potentially catastrophic event.


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


Synopsis: A B-767 air crew on climb out were notified by flight attendants smelling fumes aft of business class galley.  The fumes dissipated.  Later; in cruise at FL350; additional flight attendants reported smelling the fumes.  The flight crew decided to not enter Oceanic airspace and to return to their departure airport.
Date: 201205
Local time of day: 1201-1800
Location: OPF.Airport, FL
Flight conditions: VMC
Light: Daylight
Aircraft: Citation II S2/Bravo (C550)
Operator: Corporate
Operating under: Part 91
Mission: Passenger
Flight phase: Taxi
ATC / advisory: Ground OPF
Reporter organization: Corporate
Reporter function: Captain; Pilot Not Flying
Reporter qualification: Flight Crew Air Transport Pilot (ATP)
Human factors: Confusion; Situational Awareness
Anomaly: Deviation / Discrepancy - Procedural Clearance; Ground Incursion Taxiway
Detector: Person Flight Crew
When detected: Taxi
Result: General None Reported / Taken
Contributing factors: Airport
Primary problem: Airport

Narrative: Received taxi clearance from the FBO at OPF to Runway 9L via Taxiway N. Upon reaching Taxiway N intersection observed sign for N with angle type arrows. We turned on what we thought was N; but instead were Taxiway P. No conflict resulted; but the signage is confusing.




Synopsis: A C-550 flight crew cleared to taxi to Runway 9L via (parallel) Taxiway N at OPF turned instead on Taxiway P which comes prior to and parallel to N toward the approach end of 9L. The reporter felt the taxiway sign at the intersection where he departed the FBO was unclear.
Date: 201408
Local time of day: 0601-1200
Location: ZZZ.ARTCC, US
Flight conditions: IMC
Light: Daylight
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: Thrust Reverser Control
Component problem: Malfunctioning
Reporter organization: Air Carrier
Reporter function: Captain; Pilot Flying
Reporter qualification: Flight Crew Air Transport Pilot (ATP)
Human factors: Training / Qualification; Confusion; Distraction; Troubleshooting
Anomaly: Aircraft Equipment Problem Critical
Detector: Automation Aircraft Other Automation; Person Flight Crew
When detected: In-flight
Result: Aircraft Automation Overrode Flight Crew; Flight Crew FLC complied w / Automation / Advisory; Flight Crew Landed in Emergency Condition; Flight Crew Diverted; General Declared Emergency
Contributing factors: Manuals; Aircraft; Chart Or Publication
Primary problem: Aircraft

Narrative: During cruise flight had system status display inoperative systems REVERSER 1 AND ENG 1 THR. WITH A DESCRIPTION STATING WHEN SLATS out; engine 1 at idle; on ground Engine 1 maximum power: idle. After discussing options and original destination [we] declared [an] emergency and diverted.Upon slat selection engine did not reduce to idle thrust as expected uneventful landing. We suspect an unknown possible autothrust lever TLA fault.




Synopsis: An A320 ECAM status alerted REVERSER 1 AND ENG 1 THR along with a note that with slat extension engine 1 thrust would idle and on ground max thrust available; idle. An emergency was declared; the flight diverted and crew suspected a thrust lever angle (TLA) fault.
Date: 201508
Local time of day: 1801-2400
Location: PDX.Tower, OR
Light: Daylight
Aircraft: Light Transport; High Wing; 2 Turboprop Eng
Operator: Air Carrier
Flight plan: IFR
Mission: Passenger
Flight phase: Taxi
Airspace: Class C PDX
ATC / advisory: Tower PDX
Second aircraft: Widebody; Low Wing; 2 Turbojet Eng
Reporter organization: Government
Reporter function: Ground
Reporter qualification: Air Traffic Control Fully Certified
Human factors: Situational Awareness
Anomaly: Conflict Ground Conflict; Less Severe; Ground Event / Encounter Other / Unknown
Detector: Person Flight Crew
When detected: Taxi
Result: Flight Crew Requested ATC Assistance / Clarification
Contributing factors: Human Factors; Procedure
Primary problem: Procedure

Narrative: Aircraft X exited Runway 28L and taxied via TWY T to gate XY. At about the same time Aircraft Y started taxiing out of the alley to Runway 28L via B3. Aircraft X was well ahead of Aircraft Y and normally would not be a factor; so I turned my attention elsewhere. Problem is that Aircraft X was delayed on the taxiway waiting for a marshaller; and Aircraft Y passed by him near the area where taxiways B and T converge before Aircraft X moved clear of the taxiway. The Aircraft X pilot claimed that Aircraft Y's wing passed over his wing.I didn't notice it until they were almost next to each other. Traffic had just slowed down after being a little busy and I let my guard down. I need to keep up my scan when traffic slows. When I did notice it; I could have told Aircraft Y to stop; but it looked like they had enough room to pass. It didn't seem worth the risk to have him slam on his brakes and possibly injure a flight attendant. I issued a caution to Aircraft Y; wasn't much else I could do at that point.I was a little surprised Aircraft Y didn't stop on his own and wait until there was more room. However; a pilot behind him had an excellent view and later told Aircraft Y there was plenty of room. It wouldn't hurt if Aircraft X had given me a heads up when he realized he would be delayed on the taxiway waiting for a marshaller. I later spoke to the Aircraft X pilot on the phone. He was cool about it.




Synopsis: PDX Tower Controller reported a large aircraft's wing went over a smaller aircraft; claimed by the smaller aircraft. Smaller aircraft was delayed going into the alley way and larger aircraft continued taxiing. Another aircraft said there was plenty of room.
Date: 201602
Local time of day: 0601-1200
Location: NJK.Airport, CA
Flight conditions: VMC
Weather elements / visibility: CAVU
Light: Daylight
Aircraft: Small Aircraft
Operator: Personal
Operating under: Part 91
Flight plan: None
Mission: Personal
Flight phase: Landing
Airspace: Class D NJK
ATC / advisory: Tower NJK
Reporter organization: Personal
Reporter function: Pilot Flying; Single Pilot
Reporter qualification: Flight Crew Private
Human factors: Confusion; Situational Awareness
Anomaly: Airspace Violation All Types; Deviation / Discrepancy - Procedural Clearance; Deviation / Discrepancy - Procedural Landing Without Clearance; Deviation / Discrepancy - Procedural Published Material / Policy; Ground Incursion Runway
Detector: Person Flight Crew
When detected: Taxi
Result: Flight Crew Became Reoriented
Contributing factors: Human Factors
Primary problem: Human Factors

Narrative: Accidentally overflew Imperial from the east which left KNJK [El Centro Naval Air Field] still directly on our nose. With nearly identical runway layout we assumed we were landing KIPL but landed KNJK. It was Sunday and for the previous 15 minutes there was not an airplane to be seen or heard (were monitoring both frequencies). Upon realizing our error we stopped on a taxiway and tried to contact KNJK tower on 119.1; with initial call admitting our mistake. Nobody answered and nobody was in sight so we taxied back and departed for the proper airport (KIPL) a mere 5 miles away.




Synopsis: A General Aviation pilot reported landing at a Naval Air Field (NAF) after mistaking it for the intended destination airport. The NAF was closed for the day and no one responded to the radio call after landing; so the pilot departed.
Date: 201509
Weather elements / visibility: Turbulence
Aircraft: B787-800
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Cruise
Aircraft component: Cabin Crew Seat
Component problem: Design
Reporter organization: Air Carrier
Reporter function: Flight Attendant (On Duty)
Reporter qualification: Flight Attendant Current
Anomaly: Deviation / Discrepancy - Procedural Published Material / Policy; Flight Deck / Cabin / Aircraft Event Other / Unknown; Inflight Event / Encounter Weather / Turbulence
Detector: Person Flight Attendant
When detected: In-flight
Result: General None Reported / Taken
Contributing factors: Procedure; Aircraft; Company Policy
Primary problem: Ambiguous

Narrative: About 5 hours after departure we hit unexpected turbulence. I was position 2 and was in the AFT galley with 3 other coach FAs. There are only 3 jumpseats so I was stuck standing during moderate turbulence. Every passenger seat was occupied and it was not safe to walk up the aisle to 3L or 3R.I was put at risk because there are not enough jumpseats in the AFT galley.[Company] needs to put in at least one additional jumpseat. 6 FAs work in coach and we need to have access to jumpseats or passenger seats in case of turbulence.




Synopsis: B787 Flight Attendant reported there was nowhere for her to sit when turbulence was encountered. Reporter stated they need more jumpseats in the aft galley area.
Date: 201809
Local time of day: 1201-1800
Location: DTW.Airport, MI
Flight conditions: VMC
Light: Daylight
Aircraft: Regional Jet 700 ER/LR (CRJ700)
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Climb
Airspace: Class B DTW
ATC / advisory: TRACON D21
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: Distraction; Fatigue
Anomaly: Deviation - Altitude Crossing Restriction Not Met; Deviation - Altitude Overshoot; Deviation / Discrepancy - Procedural Clearance; Deviation / Discrepancy - Procedural Published Material / Policy
Detector: Person Air Traffic Control
When detected: In-flight
Result: Air Traffic Control Issued New Clearance
Contributing factors: Human Factors
Primary problem: Human Factors

Narrative: On the LIDDS 1 RNAV departure out of DTW we leveled at the first crossing restriction per our clearance of climb via except maintain 7000 [ft]. Prior to JOELU we were told to proceed direct KZLOV after JOELU. I asked the FO/PM (First Officer/Pilot Monitoring) to configure the FMS per ATC's instructions. After JOELU I set 15000 [ft.] in the altitude pre-select and confirmed it with the FO. I then proceeded to climb to that altitude. Around 9000 ft. we were told to climb and maintain 17000 [ft.] and then received a phone number to copy. As soon as they said this I had realized my error. [This event] occurred after an early commute. I woke up at XX:00am to catch an [early] flight. After arriving in DTW; my schedule was modified to include a new flight not originally scheduled. In the brief I did not list new departures out of DTW as a threat; but rather focused on the LLWS. Below 10;000 ft. I was not keeping conversation to only pertinent flight matters; but discussing [CRJ]700 differences as I had not flown one in a while. I did cross check the altitude with the FO(PM) and he confirmed the altitude. Not that it was his job ultimately to catch my error but there was a breakdown of CRM here. Complacency also kept me from correctly adhering to the fundamental execution of a departure procedure and listening for standard phraseology - in this I simply acted in error. The Aviation Instructors Handbook would define this as a 'slip'. I suggest not commuting early without proper rest. Briefing an obvious threat - complacency due to familiarity of DTW remained even though we had an entirely new set of departures. Making more space for the PM to feel as though he can speak up. Also per the Aviation Instructors Handbook; it is recommended to use reminders and develop routines to reduce errors. Many use the nose wheel light as a reminder that they are cleared to land. I have several of these triggers in place to remind me of various task in different phases of flight. I will be developing one as well for climb via clearances.




Synopsis: CRJ-700 Captain reported overshooting a crossing restriction on the assigned RNAV departure.
Date: 201406
Local time of day: 1201-1800
Location: ZZZ.Airport, US
Light: Daylight
Aircraft: Cessna 152
Operating under: Part 91
Mission: Training
Flight phase: Cruise
Airspace: Class E ZZZ
ATC / advisory: Tower ZZZ
Aircraft component: Electrical Power
Component problem: Malfunctioning
Reporter function: Instructor
Reporter qualification: Flight Crew Flight Instructor
Human factors: Situational Awareness
Anomaly: Aircraft Equipment Problem Critical; Flight Deck / Cabin / Aircraft Event Smoke / Fire / Fumes / Odor
Detector: Person Flight Crew
When detected: In-flight
Result: Flight Crew Diverted; Flight Crew Landed in Emergency Condition; General Declared Emergency
Contributing factors: Aircraft
Primary problem: Aircraft

Narrative: Inflight electrical fire while enroute. Made an emergency landing at a nearby airport.




Synopsis: A C-152 instructor reported an electrical fire while cruising at 3;500 so he declared an emergency; then diverted to a nearby airport.