elihoole/asrs-aviation-reports huggingface dataset:
Date: 201811
Location: ZZZ.Airport, US
Flight conditions: VMC
Light: Daylight
Aircraft: DA40 Diamond Star
Operator: FBO
Operating under: Part 91
Flight plan: VFR
Mission: Training
Flight phase: Cruise
Second aircraft: Any Unknown or Unlisted Aircraft Manufacturer
Reporter organization: FBO
Reporter function: Instructor; Pilot Flying
Reporter qualification: Flight Crew Commercial; Flight Crew Multiengine; Flight Crew Instrument; Flight Crew Flight Instructor
Human factors: Communication Breakdown
Anomaly: Conflict NMAC
Detector: Automation Aircraft TA; Person Flight Crew
When detected: In-flight
Result: Flight Crew Took Evasive Action
Contributing factors: Human Factors
Primary problem: Human Factors

Narrative: I was with a student [who] made the initial call of what we were; where we were; and altitude. Did not hear the other aircraft but saw him in the distance and on TCAS. He then popped off of our TCAS and about two minutes later they popped up directly in front of us with about 400 feet and closing in. I took controls from my student and veered the plane to the right. On TCAS he appeared to be climbing and I pulled back and got us up about 300-400 feet. I then made a call and said traffic at 6500 we were right above you. The pilot then stated we had a NMAC and then descended down. My student and I finished our lesson and went back to ZZZ.




Synopsis: GA flight instructor reported a NMAC while maneuvering near a practice area.
Date: 201510
Local time of day: 1801-2400
Location: ZZZ.Airport, US
Flight conditions: VMC
Aircraft: B737 Undifferentiated or Other Model
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Climb
Airspace: Class A ZZZ
ATC / advisory: Center ZZZ
Aircraft component: Engine Temperature Indication
Reporter organization: Air Carrier
Reporter function: Captain; Pilot Flying
Reporter qualification: Flight Crew Air Transport Pilot (ATP)
Human factors: Distraction; Situational Awareness; Workload
Anomaly: Aircraft Equipment Problem Less Severe
Detector: Person Flight Crew
When detected: In-flight
Result: Flight Crew Landed As Precaution; Flight Crew Returned To Departure Airport
Contributing factors: Aircraft
Primary problem: Aircraft

Narrative: Departed ZZZ during climb out engine number one temperature increased into the caution; yellow range.  Ran QRH. Landed uneventfully.




Synopsis: A 737 Captain reported a rising engine temperature indication in one engine during climb out; which resulted in a return to the originating airport.
Date: 201306
Local time of day: 1201-1800
Location: TA11.Airport, TX
Flight conditions: VMC
Aircraft: Sail Plane
Operator: Personal
Operating under: Part 91
Flight plan: None
Mission: Personal
Flight phase: Cruise
ATC / advisory: TRACON D10
Reporter organization: Personal
Reporter function: Single Pilot
Reporter qualification: Flight Crew Flight Engineer; Flight Crew Commercial
Human factors: Situational Awareness
Anomaly: ATC Issue All Types; Conflict Airborne Conflict
Detector: Person Flight Crew
Result: Flight Crew Took Evasive Action
Contributing factors: Airspace Structure; Procedure
Primary problem: Airspace Structure

Narrative: While thermalling at 3;800 FT MSL above TSA glider port South of DFW in Class E airspace two airliners became closer than I felt safe.  Exact distance was hard to judge maybe under 1/2 mile. The two airliners were very close behind each other. DFW Approach should consider that the largest glider port in the country is located just south of DFW Class B and should be cautious with airliners in this location.




Synopsis: Glider pilot reported NAMC events involving two air carrier aircraft inbound to the DFW area; the reporter suggesting more positive ATC separation procedures.
Date: 201604
Local time of day: 0601-1200
Location: ZZZ.ARTCC, US
Flight conditions: IMC
Weather elements / visibility: Thunderstorm
Light: Daylight
Aircraft: Citation II S2/Bravo (C550)
Operator: Air Taxi
Operating under: Part 135
Flight plan: IFR
Mission: Passenger
Flight phase: Cruise
Airspace: Class A ZZZ
ATC / advisory: Center ZZZ
Aircraft component: Pressurization System
Component problem: Malfunctioning
Reporter organization: Air Taxi
Reporter function: Captain
Reporter qualification: Flight Crew Flight Instructor; Flight Crew Air Transport Pilot (ATP); Flight Crew Instrument; Flight Crew Multiengine
Anomaly: Aircraft Equipment Problem Critical
Detector: Person Flight Crew
When detected: In-flight
Result: Air Traffic Control Provided Assistance; Flight Crew Took Evasive Action
Contributing factors: Aircraft
Primary problem: Aircraft

Narrative: Rapid decompression at FL360. Performed emergency descent followed by check list. No conflict was encountered and an emergency wasn't [reported to ATC]. ATC did a great job allowing us to address our situation without conflict.




Synopsis: CE-550 Captain reported experiencing a rapid decompression at FL360.
Date: 201507
Local time of day: 1201-1800
Location: Y90.TRACON, CT
Light: Daylight
Aircraft: Medium Transport; Low Wing; 2 Turbojet Eng
Flight plan: IFR
Flight phase: Climb
Airspace: Class E ZNY
ATC / advisory: TRACON Y90
Reporter organization: Government
Reporter function: Departure; Instructor; Approach
Reporter qualification: Air Traffic Control Fully Certified
Human factors: Communication Breakdown; Distraction; Situational Awareness; Training / Qualification; Workload
Anomaly: ATC Issue All Types; Airspace Violation All Types; Deviation / Discrepancy - Procedural Published Material / Policy
Detector: Person Air Traffic Control
When detected: In-flight
Result: Air Traffic Control Provided Assistance
Contributing factors: ATC Equipment / Nav Facility / Buildings; Human Factors; Procedure
Primary problem: ATC Equipment / Nav Facility / Buildings

Narrative: [Aircraft X] entered my airspace without completion of a handoff or other prior coordination. There is a known automation issue where these departures off of OXC from N90 flash to the wrong sector. I was distracted elsewhere due to training and did not see the aircraft until N90 called to make a verbal handoff. The airplane was already approximately 3 miles inside my airspace. There is little doubt to me that if I was not training I would have caught this before it became an issue. But a low time trainee not seeing it; and the opening of a third scope to relieve another sector forced me to move from an adjacent monitoring scope to being beside the trainee.  This combined with other traffic diverting my attention away from the N90 boundary allowed this to happen without me correcting it. Then again I might have just missed it too working solo.




Synopsis: Y90 Controller reports of an known automation problem within Y90 and N90. While training the Controller noticed an airspace deviation related to this automation problem.
Date: 201910
Local time of day: 0001-0600
Location: ZZZ.Airport, US
Aircraft: EMB ERJ 190/195 ER/LR
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Takeoff / Launch
Aircraft component: APU
Component problem: Malfunctioning
Reporter organization: Air Carrier
Reporter function: Pilot Flying; First Officer
Reporter qualification: Flight Crew Air Transport Pilot (ATP); Flight Crew Instrument; Flight Crew Multiengine
Human factors: Situational Awareness
Anomaly: Aircraft Equipment Problem Less Severe; Deviation / Discrepancy - Procedural MEL / CDL; Deviation / Discrepancy - Procedural Published Material / Policy; 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: After pushing back from the gate and starting engines; we got a bleed 1 fail message. We then ran through the QRH procedure; but the message persisted. We contacted Maintenance and were able to MEL the left engine bleed. The MEL required us to take off with the APU running. After completing the required paperwork and getting a new release we began our taxi to Runway XXR. Just after rotation on the climb out I began to smell fuel rich exhaust; similar to taxiing close to another aircraft. The smell became fairly strong; but not uncomfortable and in my mind attributed it to having the APU running and sucking in the exhaust from the engines. I didn't think much of it and continued to accelerate and clean up the aircraft. I asked for the autopilot on; and by this time I noticed the smell began to dissipate as we accelerated to 250kts. The Captain and I then discussed what could have caused the smell and we came to the same conclusion that we were probably sucking in exhaust due to the APU running and providing bleed air for the #1 pack. By the time we got to 3500/4000 ft the smell was completely gone. We considered it safe and continued on. The Captain reviewed the QRH procedure for smoke; fire; fumes; and climbing through 10;000ft he contacted the #1 flight attendant. He informed me that the #1 had smelled it too; but quickly dissipated and that the #2 in the back of the aircraft did not smell anything. We continued to ZZZ1 and landed uneventfully. We then took the same aircraft to ZZZ2 with no complications.




Synopsis: ERJ-190 Captain reported 'fuel rich exhaust' fume shortly after takeoff which dissipated by 4;000 AGL altitude. QRH procedures were reviewed before completing an uneventful flight.
Date: 201502
Local time of day: 0001-0600
Location: DCA.Airport, DC
Flight conditions: VMC
Light: Night
Aircraft: B737 Undifferentiated or Other Model
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Taxi
ATC / advisory: Ramp DCA
Aircraft component: Powerplant Fuel Valve
Component problem: Improperly Operated
Reporter organization: Air Carrier
Reporter function: Pilot Flying; Captain
Reporter qualification: Flight Crew Air Transport Pilot (ATP)
Human factors: Training / Qualification; Communication Breakdown; Distraction
Second reporter function: Pilot Not Flying; First Officer
Anomaly: Deviation / Discrepancy - Procedural Published Material / Policy; Ground Event / Encounter Other / Unknown
Detector: Person Flight Crew
When detected: Taxi
Result: Flight Crew Became Reoriented; Flight Crew Overcame Equipment Problem
Contributing factors: Human Factors
Primary problem: Human Factors

Narrative: Landing was uneventful and we taxied to the gate. After clearing gate area; turned Aircraft (A/C) into gate. I called for the First Officer (F/O) to shut down the number 2 engine. F/O accidentally started to shut down number 1 engine. I saw this out of the corner of my eye and stated not #1 shut down #2. F/O had moved the #1 start lever ever so slightly out of idle position. He put #1 back to idle and shut down the #2 engine.I did not know this; but ever so slight movement of start lever out of idle shuts down the engine. As a result; even though #1 start lever [was] placed back in idle; engine #1 shut down. Now with #2 shut down we were powerless taxiing [into the] gate. I stopped A/C. Made eye and verbal contact with ground personnel. Made and confirmed with ground personnel we were going to re-start the #1 engine to finish taxi to gate. Ground personnel gave us the all clear. We started the #1 engine and taxied the last 5 feet to the gate.


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


Synopsis: A B-737 air crew; taxiing to the gate had a miscommunication between the pilots. The Captain commanded shutdown of Engine Number 2 but the copilot began to shutdown Engine Number 1. Realizing his mistake he returned the Number 1 start lever to the detent and shutdown Engine Number 2. As a result both engines were shutdown and the aircraft coasted to a stop five feet from the gate. They restarted Engine Number 1 to finish the taxi to the gate.
Date: 201202
Local time of day: 1801-2400
Location: EWR.Airport, NJ
Flight conditions: VMC
Weather elements / visibility: 10
Light: Night
Aircraft: Widebody; Low Wing; 4 Turbojet Eng
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Cargo / Freight / Delivery
Flight phase: Landing
Airspace: Class B EWR
ATC / advisory: Tower EWR
Reporter organization: Air Carrier
Reporter function: Captain; Pilot Flying
Reporter qualification: Flight Crew Air Transport Pilot (ATP); Flight Crew Instrument
Human factors: Confusion; Fatigue; Situational Awareness; Time Pressure
Anomaly: Deviation - Track / Heading All Types; Deviation / Discrepancy - Procedural Published Material / Policy
Detector: Person Flight Crew
When detected: In-flight
Result: Flight Crew Became Reoriented; Flight Crew Took Evasive Action
Contributing factors: Human Factors
Primary problem: Human Factors

Narrative: Pilot performance issue due to fatigue brought on by days on end of minimum rest. Began day in Spain; a maintenance stop in Canada and then to Newark. Due to landing weight near maximum; the Captain was the flying pilot. The Crew had briefed the visual approach and side step to Runway 22R at Newark. The visual approach was entirely normal. As we neared the displaced threshold; the First Officer called 'centerline'. I immediately made a correction to centerline. The aircraft aligned with the runway centerline. Touch down was long at around 2;000 FT; the beginning of the declared usable runway for Runway 22R. The landing roll out was normal. Any more of a deviation would have required a go around. The illusion was the runway edge lights looked like the runway centerline lighting. Most of the time; we land on Runway 22L at Newark. Proper CRM by the First Officer alerted me to the slot alignment problem. Fatigue and crew rest were major players in this event.




Synopsis: A fatigued Captain nearly landed on the EWR 22R runway edge lights which he mistook for centerline lights but became reoriented by the First Officer's 'Centerline' alert. Fatigue and crew rest were major factors.
Date: 202011
Location: ZZZ.ARTCC, US
Aircraft: Commercial Fixed Wing
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Cruise
Airspace: Class A ZZZ2
ATC / advisory: Center ZZZ
Reporter organization: Air Carrier
Reporter function: Flight Attendant (On Duty)
Reporter qualification: Flight Attendant Current
Human factors: Confusion; Distraction
Anomaly: Deviation / Discrepancy - Procedural Published Material / Policy
Detector: Person Flight Attendant
When detected: In-flight
Result: General None Reported / Taken
Contributing factors: Environment - Non Weather Related; Human Factors
Primary problem: Human Factors

Narrative: Approximately 3 hours into our flight from ZZZZ-ZZZ; Flight Attendant X told me that his daughter had tested positive for COVID-19 the previous day.   Flight Attendant X said that he contacted Airline when he learned of his child's positive test result and was advised to continue with his pairing; despite his immediate family member receiving a positive COVID test result.  It made me extremely uncomfortable to hear that Flight Attendant X was directly exposed and that he chose to continue to work; possibly endangering the health and safety of others.   Flight Attendant X also mentioned that he is a [Medical Professional] and exposed to COVID positive patients regularly at his other job.  While Flight Attendant X may not have received the support from the company in line with our responsibility to keep one another as safe as possible during the global pandemic; common sense and personal ethos would dictate that one would remove them self from flying until they had a negative test result and quarantine period of 14 days.  I contacted ZZZ Supervisor upon landing in ZZZ and expressed my concerns.




Synopsis: Flight Attendant reported concerns with another Flight Attendant showing up for work after a family member had tested positive for COVID-19 the day before.
Date: 201601
Local time of day: 0601-1200
Location: IAH.Airport, TX
Flight conditions: VMC
Light: Daylight
Aircraft: A320
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Taxi
Reporter organization: Air Carrier
Reporter function: Pilot Flying; Captain
Reporter qualification: Flight Crew Air Transport Pilot (ATP)
Human factors: Situational Awareness; Training / Qualification
Anomaly: Conflict Ground Conflict; Critical; Deviation / Discrepancy - Procedural Published Material / Policy
Detector: Person Flight Crew
When detected: Taxi
Result: Flight Crew Took Evasive Action
Contributing factors: Equipment / Tooling; Human Factors
Primary problem: Equipment / Tooling

Narrative: Pulling into gate in IAH a truck drove directly thru the safety zone and the 'Safe Park' system did not tell us to stop due to an obstruction. Recommendation for improvement- ensure the scanning of the safety zone is accurate and provides instantaneous feedback to the crew via the signage. Useful improvement (do not have to wait on marshallers); but system must be out of beta and ready for prime-time. This example illustrates why it is not yet. Had we followed the signage and continued our approach to the gate; it is possible we would have hit the vehicle. My attention must be singularly focused on the lights guiding me to gate; which means the FO must back up the Safe Park scanning of safety zone.




Synopsis: A320 Captain reported a truck drove into the safe zone while he was parking at a gate in IAH and the 'Safe Park' system failed to warn him.
Date: 201904
Local time of day: 1201-1800
Location: LAX.Airport, CA
Aircraft: EMB ERJ 170/175 ER/LR
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Climb
Airspace: Class B LAX
ATC / advisory: TRACON SCT
Second aircraft: B777 Undifferentiated or Other Model
Reporter organization: Air Carrier
Reporter function: Captain; Pilot Not Flying
Reporter qualification: Flight Crew Multiengine; Flight Crew Instrument; Flight Crew Air Transport Pilot (ATP)
Human factors: Situational Awareness
Second reporter function: Pilot Flying; First Officer
Anomaly: Deviation - Altitude Crossing Restriction Not Met; Deviation - Altitude Overshoot; Deviation / Discrepancy - Procedural Clearance; Inflight Event / Encounter Wake Vortex Encounter
Detector: Person Air Traffic Control; Person Flight Crew
When detected: In-flight
Result: Air Traffic Control Issued Advisory / Alert; Flight Crew Returned To Clearance; Flight Crew Became Reoriented
Contributing factors: Airspace Structure; Procedure
Primary problem: Procedure

Narrative: Departing LAX on the LADYJ RNAV departure; we encountered wake turbulence; causing my First Officer to hand fly the airplane. Approaching the crossing restriction at the LADYJ fix of a hard 8;000 feet; we were informed of crossing traffic at our 12 o'clock. As I looked outside for the traffic; I heard the altitude alerter sound; called altitude and my First Officer effectively recaptured the altitude without floating the passengers. We corrected at 8;300 feet at LADYJ. ATC advised us our altitude was high and I let them know we were correcting. The lesson learned was [to] have the First Officer use the automation for level off in those types of situations and be more vigilant in watching as hard altitudes approach.


Second narrative: Climbing out of LAX on the LADYJ4; we complied with all altitude restrictions until LADYJ. We exceeded the 8;000 feet altitude restriction by 300 feet. We were a little distracted by some wake turbulence from a 777; complying with the SID; and verifying our top altitude for the departure. I glanced to check my chart; came back to the PFD as we reached 8;000 feet. Immediately started to nose over; not too fast or forceful since we have passengers; but we arced to 8;300 feet before we started to descend back to 8;000 feet. It was momentary but still noticed by us and ATC.I have flown this departure before; using the AP; just to make sure to meet all the altitude restrictions. After seeing it was not a problem to meet the restrictions; I decided to hand fly the departure today. Again; no problems initially; but I should have turned the AP on sooner to make sure we complied with the hard altitude since it is a high traffic area. Next time I will turn the AP on around MLIBU to make sure we level perfectly at LADYJ.


Synopsis: EMB-175 flight crew reported overshooting a crossing restriction departing LAX when they were distracted by a wake turbulence encounter.
Date: 201311
Local time of day: 1201-1800
Location: ZZZ.Airport, US
Flight conditions: VMC
Light: Daylight
Aircraft: B717 (Formerly MD-95)
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Takeoff / Launch
ATC / advisory: Tower ZZZ
Aircraft component: Turbine Engine
Component problem: Malfunctioning
Reporter organization: Air Carrier
Reporter function: Captain; Pilot Flying
Reporter qualification: Flight Crew Air Transport Pilot (ATP)
Human factors: Time Pressure
Second reporter function: First Officer; Pilot Not Flying
Anomaly: Aircraft Equipment Problem Critical
Detector: Person Flight Crew
When detected: In-flight
Result: Flight Crew FLC complied w / Automation / Advisory; Flight Crew Rejected Takeoff; Flight Crew Returned To Gate
Contributing factors: Aircraft
Primary problem: Aircraft

Narrative: During takeoff the ENG LEFT COMPRESSOR STALL level 2 alert displayed. This was accompanied by two loud bangs; vibration and loss of thrust on the left engine. We initiated the abort at approximately 120 kts and stopped on the runaway. After having the airport fire department inspect the tires and aft section of the plane for visible damage and shutting down the engine; we returned to the gate.


Second narrative: [Report adds no additional information.]


Synopsis: A B717 EICAS alerted ENG LEFT COMPRESSOR STALL in conjunction with two loud bangs; vibration and loss of engine thrust so the Captain rejected the takeoff at 120 KTS; had the aircraft inspected and returned to the gate.
Date: 202112
Local time of day: 0601-1200
Location: ZZZ.Airport, US
Flight conditions: VMC
Weather elements / visibility: 10
Light: Daylight
Aircraft: PA-28 Cherokee/Archer/Dakota/Pillan/Warrior
Operator: Personal
Operating under: Part 91
Flight plan: VFR
Mission: Training
Flight phase: Takeoff / Launch
Airspace: Class D ZZZ
ATC / advisory: TRACON ZZZ
Aircraft component: Air/Ground Communication
Component problem: Failed
Reporter organization: FBO
Reporter function: Instructor; Pilot Not Flying
Reporter qualification: Flight Crew Commercial; Flight Crew Multiengine; Flight Crew Instrument; Flight Crew Flight Instructor
Human factors: Communication Breakdown
Second reporter function: Pilot Flying; Single Pilot
Anomaly: Aircraft Equipment Problem Critical; Deviation / Discrepancy - Procedural Published Material / Policy; Deviation / Discrepancy - Procedural Clearance
Detector: Person Air Traffic Control
When detected: In-flight
Result: Air Traffic Control Issued Advisory / Alert; Flight Crew Diverted; Flight Crew Landed As Precaution
Contributing factors: Aircraft
Primary problem: Aircraft

Narrative: Student was flying a solo cross from ZZZ1 to ZZZ then back to ZZZ1. After climb out from ZZZ after a touch and go; the student experienced loss of Com 1 and Com 2. Loss of comms was noticed after ZZZ Approach advised on [course] and altitude our discretion. The student squawked 7600 and decided to land at ZZZ2 as was instructed by his instructor.


Second narrative: On climbout of ZZZ after receiving VFR on course back to ZZZ1 downtown from ZZZ Approach lost Comm 1 and Comm 2. After not being able to reach ZZZ Approach I squawked 7600 then proceeded to maintain VFR and landed soon as possible at non-towered airport ZZZ2 and a safe landing.


Synopsis: PA28 Solo Student Pilot and Instructor reported student loss of communication with ATC resulted in proceeding to diversion airport.