elihoole/asrs-aviation-reports huggingface dataset:
Date: 201909
Location: ZZZ.Airport, US
Aircraft: Commercial Fixed Wing
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Reporter organization: Air Carrier
Reporter function: Ramp; Vehicle Driver
Human factors: Confusion
Anomaly: Ground Event / Encounter Other / Unknown
Detector: Person Ground Personnel
When detected: Taxi
Result: General None Reported / Taken
Contributing factors: Airport
Primary problem: Airport

Narrative: There are several taxiway lines along the X2 concourse that are used for aircraft movement. There is a center line designated 'HEAVY' that is used by the Aircraft X that goes to [Gate X1]; then there is an inner and outer taxiway that all other aircraft use. The crews along the X2 concourse from [Gate X2] to [Gate X3] will be given push instructions which include direction and while line to place the aircraft on. These lines were repainted in May but the inner taxi line has become faded again and is difficult to see during inclement weather and at night. This affects the ramp crew's ability to drop aircraft off at the proper location which can affect other aircraft taxiing under their own power.




Synopsis: Ground employee reported tow/taxi lines need repainting.
Date: 201210
Local time of day: 0601-1200
Location: ZMP.ARTCC, MN
Flight conditions: VMC
Aircraft: Citation Excel (C560XL)
Operator: Fractional
Operating under: Part 91
Flight plan: IFR
Flight phase: Climb
Airspace: Class A ZMP
ATC / advisory: Center ZMP
Second aircraft: B737 Undifferentiated or Other Model
Reporter organization: Fractional
Reporter function: Captain; Pilot Flying
Reporter qualification: Flight Crew Air Transport Pilot (ATP)
Anomaly: Inflight Event / Encounter Wake Vortex Encounter
Detector: Person Flight Crew
When detected: In-flight
Result: Flight Crew Took Evasive Action
Contributing factors: Environment - Non Weather Related
Primary problem: Environment - Non Weather Related

Narrative: We were en route to MHR and leveled off at intermediate altitude of FL360. A B737 was ahead and to our 11 o'clock position at FL380. ATC advised that after we got adequate separation from B737 we would continue our climb to FL400. After several minutes; ATC cleared us to climb to FL400. As we passed thru FL380 we encountered the wake turbulence from B737. Our aircraft was on autopilot but pitched up and rolled left approximately 20 degrees. The autopilot disengaged at the same time I grabbed yoke and disconnect button. This was a momentary upset and I rolled wings level; lowered pitch to a 400 FT/minute climb and continued to FL400. We advised ATC of the upset. The B737 appeared to be 12-15 miles ahead of us on the TCAS. No one was injured.




Synopsis: CE-560XL Captain reported wake vortex encounter climbing through FL380 while 12-15 miles in trail of a B737.
Date: 202104
Location: ZZZ.Airport, US
Flight conditions: VMC
Weather elements / visibility: Turbulence
Light: Daylight
Aircraft: B737-800
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Landing
Airspace: Class C ZZZ
ATC / advisory: TRACON ZZZ; Tower ZZZ
Aircraft component: Emergency Equipment
Component problem: Failed
Reporter organization: Air Carrier
Reporter function: Other / Unknown
Anomaly: Aircraft Equipment Problem Critical; Deviation / Discrepancy - Procedural Published Material / Policy; Flight Deck / Cabin / Aircraft Event Other / Unknown; Inflight Event / Encounter Weather / Turbulence
Detector: Person Observer
When detected: In-flight
Result: General Maintenance Action; General Flight Cancelled / Delayed
Contributing factors: Aircraft; Environment - Non Weather Related; Human Factors; Weather
Primary problem: Weather

Narrative: While landing in ZZZ it was the worst turbulence ever experienced on landing. The aircraft had shifted on a sharp tilt aircraft left and sharply right. The door to the Portable Oxygen Bottles (POBs) opened and when the wheels/aircraft touched down with excessive velocity and force it catapulted the POB's forward into the isle of the aircraft. But; the grace of GOD; and physics; no one was injured! The latched locked failed. Passenger X was one of many witnesses; his kids were sitting in aft as well! I don't know how but lord I'm so thankful that no one was hit by the catapulted POB bottles. The landing was furious and as the gusts were up to 35 MPH and flaps and speed were notable not in conjunction of safety. It was clear on a not so perfect hard landing the locks failed easily. A very dangerous situation at the very least. As stated thank the lord no one was injured! The locks on cabinet failed and the brackets also failed to keep the POB's secure. It needs complete checks for the safety of the passengers and crew members alike.




Synopsis: Flight Attendant reported that latches and retaining brackets for the portable oxygen bottles failed on landing; allowing the bottles to come loose and catapult through the cabin.
Date: 202007
Local time of day: 0601-1200
Aircraft: Commercial Fixed Wing
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Cruise
Reporter organization: Air Carrier
Reporter function: Flight Attendant (On Duty)
Reporter qualification: Flight Attendant Current
Human factors: Other / Unknown
Anomaly: Flight Deck / Cabin / Aircraft Event Illness / Injury
Detector: Person Passenger
When detected: In-flight
Result: General None Reported / Taken
Contributing factors: Environment - Non Weather Related; Human Factors
Primary problem: Human Factors

Narrative: While in flight there was a medical emergency.  Aft FA had just finished with trash pick up; passenger pressed her FA call button. FWD FA went to check and passenger explained she can not breathe and she feels like she was going to pass out. I opened the air vents fully and asked if it was any better; passenger said no; she still can't breathe. I didn't offer water because there was a full bottle on passenger tray table; so I told the passenger to take a drink to see if would help. Passenger then stated she need O2. I told the passenger we have O2 on board; but I have to let the PIC know I'm using it. I called the flight deck told the PIC the situation and he stated I should let him know how the passenger feels after O2 was administered. I asked the passenger if she has emphysema; to which she said no. I also asked passenger if she would like for the aircraft to make an emergency landing and get medics. Passenger said no she was feeling better with the O2. I secured the O2 bottle in the seat next to passenger and told her to press her FA button if she need anything else or if O2 runs out and she needed more. The AFT FA checked on the passenger on her trash run. PIC called to ensure passenger didn't need medical attention once we land which the passenger declined; as the O2 had her feeling better. Passenger stated she was wearing her mask all morning in the airport and stated that could have been her reason for not being able to breathe.




Synopsis: Flight Attendant reported a passenger could not breathe; so oxygen was administered until passenger felt well.
Date: 201301
Local time of day: 0601-1200
Location: ZZZ.ARTCC, US
Flight conditions: VMC
Aircraft: B737-800
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 Fuel Filter
Component problem: Malfunctioning
Reporter organization: Air Carrier
Reporter function: Pilot Not Flying; Captain
Reporter qualification: Flight Crew Air Transport Pilot (ATP)
Second reporter function: First Officer; Pilot Flying
Anomaly: Aircraft Equipment Problem Critical
Detector: Person Flight Crew
When detected: In-flight
Result: Air Traffic Control Provided Assistance; Flight Crew Landed in Emergency Condition; Flight Crew Landed As Precaution; Flight Crew Requested ATC Assistance / Clarification; Flight Crew Returned To Departure Airport; General Declared Emergency
Contributing factors: Aircraft
Primary problem: Aircraft

Narrative: During climb out and passing FL200 the Number 1 Engine fuel 'filter bypass' light illuminated. I ran the checklist for the problem; and the First Officer coordinated a return to land. We declared an emergency due to the possibility of fuel contamination. Landing was uneventful.


Second narrative: On climb out the FILTER BYPASS light for engine Number 1 illuminated. Performed QRH procedures. The Captain decided to declare an emergency and return to departure airport. No special handling was requested. Landed without incident.


Synopsis: B737-800 fuel 'Filter Bypass' annunciator light illuminated during climb out; the flight crew ran the checklist; declared an emergency and returned to their departure airport.
Date: 201301
Local time of day: 0601-1200
Location: ZZZ.Airport, US
Light: Daylight
Aircraft: Dash 8-300
Operator: Air Carrier
Operating under: Part 121
Flight phase: Parked
Aircraft component: Powerplant Fuel Control Unit
Reporter organization: Air Carrier
Reporter function: Technician
Reporter qualification: Maintenance Airframe; Maintenance Powerplant
Human factors: Distraction; Communication Breakdown; Situational Awareness; Training / Qualification; Time Pressure
Anomaly: Aircraft Equipment Problem Less Severe; Deviation / Discrepancy - Procedural Published Material / Policy
Detector: Person Maintenance
When detected: Routine Inspection
Result: General Maintenance Action
Contributing factors: Human Factors
Primary problem: Human Factors

Narrative: I was assigned to train several new mechanics on the task of Engine Rigging Work Card. Upon completion of the Task; the trainees; Quality Assurance (QC) and I failed to notice the Condition Rod coming from the nacelle quadrant to the Mechanical Fuel Controller (MFC) was installed on the opposite side of the MFC Condition arm. The engine was trimmed and ran fine and flew for two months without any problem. At Heavy Check; the error was discovered and the Supervisor was notified. The rod end was repositioned to its correct location. I overlooked the rod being installed on the opposite side. Avoid training several mechanics at one task and pay attention to detail of work being performed.




Synopsis: An Aircraft Maintenance Technician Trainer was informed; after training several new mechanics on DHC8-300 Engine Rigging; that he; the trainees and Quality Assurance failed to notice a Condition Rod from the # 2 Engine nacelle quadrant to the Mechanical Fuel Control Unit; had been installed on the opposite side of the MFC Condition arm.
Date: 201303
Local time of day: 1201-1800
Location: ZZZZ.Airport, FO
Flight conditions: VMC
Light: Daylight
Aircraft: A320
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Final Approach; Landing
ATC / advisory: Tower ZZZZ
Aircraft component: Air Conditioning Distribution System
Component problem: Design; Malfunctioning
Reporter organization: Air Carrier
Reporter function: Flight Attendant (On Duty); Flight Attendant In Charge
Reporter qualification: Flight Attendant Current
Human factors: Physiological - Other
Anomaly: Aircraft Equipment Problem Less Severe; Flight Deck / Cabin / Aircraft Event Smoke / Fire / Fumes / Odor; Flight Deck / Cabin / Aircraft Event Illness / Injury
Detector: Person Flight Attendant
When detected: In-flight
Result: Aircraft Equipment Problem Dissipated; General Maintenance Action
Contributing factors: Aircraft; Human Factors; Procedure
Primary problem: Aircraft

Narrative: We experienced the toxic fumes (associated with dirty socks or laundry) after the gear came down on approach. The odor permeated the cabin from the exit rows to the rear of the aircraft. 'B' Flight Attendant immediately came forward to notify me and the 'C' to cover our noses and mouths. Except for having to speak and breathe for the arrival announcement; I kept my nose and mouth covered. Passengers toward the rear; Rows 23-25; were complaining of a foul musty smell. Passengers deplaned without incident. During our short turn; the Captain had another airline's Mechanic inspect the aircraft. My complaint after the incident entailed a bad taste in my mouth (metallic) that originally felt like I had hair on my tongue. Neither liquids nor gum would take it away. I also developed a dull headache. These symptoms stayed with me until I was almost back in my domicile. The other Flight Attendant and I stayed out on the stairs - in the fresh air - during our short turn. After the aircraft was checked out; we did fly the flight back to our domicile; no more incidents were reported upon landing. A Mechanic checked the aircraft out after we landed. He discussed with the Captain what could have caused the fumes/odor to permeate the cabin exit rows to the rear of the aircraft after the gear came down; on approach for landing. This is not the first time I've been involved in a toxic fume incident but it is the first time I have felt the effects. From what I could understand from listening to the Captain and the Mechanic; it is still an oil problem that leaks into the system that bleeds into the cabin air. The problem is still occurring.




Synopsis: An A320 Flight Attendant reported a dirty socks odor when the landing gear was extended after which she developed a headache; and a metallic taste in her mouth.
Date: 201508
Local time of day: 0601-1200
Location: LGA.Airport, NY
Flight conditions: Marginal
Weather elements / visibility: Turbulence
Light: Dawn
Aircraft: EMB ERJ 190/195 ER/LR
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Initial Approach
Airspace: Class B LGA
ATC / advisory: TRACON N90
Aircraft component: ILS/VOR
Component problem: Malfunctioning
Reporter organization: Air Carrier
Reporter function: Captain; Pilot Flying
Reporter qualification: Flight Crew Air Transport Pilot (ATP)
Human factors: Confusion; Workload
Anomaly: Aircraft Equipment Problem Less Severe; Inflight Event / Encounter Unstabilized Approach
Detector: Person Flight Crew
When detected: In-flight
Result: Flight Crew Became Reoriented; Flight Crew Overcame Equipment Problem
Contributing factors: ATC Equipment / Nav Facility / Buildings; Aircraft; Environment - Non Weather Related
Primary problem: Ambiguous

Narrative: We were on the base to final for ILS Runway 22 at LGA; ATC gave us clearance to turn on heading 250; descend to 2;000 feet and cleared for ILS Approach Runway 22; I turned on heading; descended to 2;000 feet in FLCH and armed approach ( LOC;GS were armed). Localizer moved and was captured on FMA around 7-8 DME and GS was alive; when LOC needle was less than 1 dot; the airplane suddenly roll wings level with increasing descent. The distance to the runway was around 6-7 miles. I checked FMA; it was in ROLL and Flight Path Angle (FPA) mode. I disconnected autopilot making correction to bring back the airplane on the correct flight path.I distrust the automation at this time and continued approach in the manual mode; monitoring raw data indication and VASI on the Runway 22. During the maneuver; I went slightly lower on the glide path and received twice EGPWS glideslope alert. I corrected glide path and landed uneventfully.My First Officer told me after landing that he experienced and observed 3 cases of these anomalies over the last several months and it was ILS approach Runway 22 and distance when anomalies occurred from 6 to 10 miles on final. I suggested him to submit a report about the anomalies too. I did not find any NOTAMs regarding these anomalies and ATC did not notify us about deviation.I could only suspect false LOC and GS or interference with ILS signals. The airplane equipment worked correctly on the next approach. The high workload and task saturation to correct the flight path after anomalies distracted me from monitoring the glide path.




Synopsis: EMB190 Captain experiences an autopilot anomaly during LOC and glide path capture of the ILS 22 at LGA. The autopilot initially seemed to capture the LOC then rolled wings level with increasing descent below the glide path and displaying ROLL and Flight Path Angle (FPA) in the FMA. The autopilot is disconnected and the approach continued manually. The First Officer informs the Captain that he has seen this anomaly occur several times during the ILS 22 to LGA over the last few months.
Date: 202008
Local time of day: 1201-1800
Location: ZZZ.ARTCC, US
Flight conditions: VMC
Light: Daylight
Aircraft: EMB ERJ 145 ER/LR
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Initial Approach
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: Human-Machine Interface
Anomaly: Inflight Event / Encounter CFTT / CFIT
Detector: Automation Aircraft Terrain Warning; Person Flight Crew
When detected: In-flight
Result: Air Traffic Control Provided Assistance; Flight Crew Took Evasive Action; Flight Crew Requested ATC Assistance / Clarification
Contributing factors: Human Factors
Primary problem: Human Factors

Narrative: The flight was on a visual approach clearance arriving from the south east. The flight remained at the MSA 4;100 ft. until terrain clearance was assured. At that time a gradual decent was initiated to reach the pattern altitude of 2;800 ft. A momentary EGPWS annunciation occurred just before the gear was down an locked.Aircraft annunciation [EGPWS]Approximate terrain clearance and aircraft configuration. EGPWS escape maneuver initiated. Event was less than a second in duration.Crew followed SOPs.




Synopsis: EMB-145LR Captain reported executing an uneventful evasive maneuver during initial approach due to a momentary EGPWS Terrain warning.
Date: 202011
Local time of day: 1201-1800
Location: ZZZ.TRACON, US
Aircraft: Small Transport; Low Wing; 2 Turbojet Eng
Flight plan: IFR
Flight phase: Descent
Airspace: Class E ZZZ1
ATC / advisory: TRACON ZZZ
Second aircraft: Small Transport; Low Wing; 2 Turbojet Eng
Reporter organization: Government
Reporter function: Approach
Reporter qualification: Air Traffic Control Fully Certified
Human factors: Situational Awareness
Anomaly: ATC Issue All Types; Conflict Airborne Conflict; Deviation / Discrepancy - Procedural Published Material / Policy
Detector: Person Air Traffic Control
Result: Air Traffic Control Issued New Clearance
Contributing factors: Staffing; Human Factors; Environment - Non Weather Related
Primary problem: Human Factors

Narrative: I was working all positions combined in RADAR. Traffic started to pick up far more than what we have had over the past few months due to COVID. Aircraft Y was level at 10k westbound and Aircraft X was east; inbound ZZZ out of 11 for 2500. I saw the traffic and turned Aircraft X 15 degrees left to maintain separation from Aircraft Y. I thought the turn would have been enough for 3 miles and degrees of divergence but ended up not being so. At the closest point I had 2.87 laterally and 800 ft. We went from a slow COVID season to busier than normal with a lot of crossing traffic.




Synopsis: TRACON Controller reported a loss of separation.
Date: 201710
Local time of day: 0601-1200
Location: ZZZ.Airport, US
Light: Daylight
Aircraft: Regional Jet 200 ER/LR (CRJ200)
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Parked
Aircraft component: APU
Component problem: Malfunctioning
Reporter organization: Air Carrier
Reporter function: Flight Attendant In Charge
Reporter qualification: Flight Attendant Current
Anomaly: Aircraft Equipment Problem Critical; Flight Deck / Cabin / Aircraft Event Smoke / Fire / Fumes / Odor; Ground Event / Encounter Other / Unknown
Detector: Person Ground Personnel
When detected: Aircraft In Service At Gate
Result: General Evacuated; General Flight Cancelled / Delayed
Contributing factors: Aircraft
Primary problem: Aircraft

Narrative: Flight Deck was getting ready to pushback and the APU shut down; all power in aircraft shut off. 2 times this happened. Ground crew communicated by signal there was a fire. Ground crew called the fire department; and banged on the door 'open and get everyone off.' Captain opened the flight deck and said 'open the main door.' There was white smoke coming from the aft of the aircraft. Captain said 'Ground crew says get everyone off the aircraft.' I could not/did not turn on any lights. I just stated; 'Ladies and gentlemen; we have a situation and would like everyone to get off the aircraft. Leave everything; take only what is in your hand; and exit the aircraft. There are people here to help....' and they all got off.The APU 'broke.' The white smoke and flames that the ground crew saw was excessive fuel. Our Captain went to talk to everyone in the gate and explained; what an APU is; that the smoke was excessive fuel; and that we will be able to safely take this aircraft. 2 passengers took a different flight because they were going to miss their international flight; 1 passenger declined to go. Everyone else went as scheduled.




Synopsis: CRJ-200 Flight Attendant reported an APU fire due to excess fuel just before pushback that resulted in all passengers exiting the aircraft.
Date: 201210
Local time of day: 1801-2400
Location: ZZZ.Airport, US
Flight conditions: VMC
Light: Night
Aircraft: Heavy Transport
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Cargo / Freight / Delivery
Flight phase: Takeoff / Launch
ATC / advisory: Tower ZZZ
Aircraft component: GPWS
Component problem: Design; Malfunctioning
Reporter organization: Air Carrier
Reporter function: Captain; Check Pilot
Reporter qualification: Flight Crew Air Transport Pilot (ATP)
Human factors: Communication Breakdown; Distraction; Physiological - Other; Training / Qualification; Workload
Anomaly: Aircraft Equipment Problem Less Severe; Deviation / Discrepancy - Procedural Other / Unknown
Detector: Automation Aircraft Other Automation; Person Flight Crew
When detected: In-flight
Result: Flight Crew FLC complied w / Automation / Advisory; Flight Crew FLC Overrode Automation; Flight Crew Rejected Takeoff
Contributing factors: Aircraft; Company Policy
Primary problem: Aircraft

Narrative: Cleared for takeoff Runway XX. At 25 KTS received an 'on taxiway' alert. Rejected. Complied with QRH and waited 21 minutes and departed. At a higher speed the alert happened again but takeoff was continued.  While running RTO checklist we received an ACARS message for employee X to report to flight operations immediately on arrival. We called about the message and were told; 'Everything will be explained when we land.'  Due to elderly parents and sick family members; the crew member was distracted throughout the flight. Captain flew the leg and flight safety suffered due to our concern for what might be wrong.  Strange to get this message during departure ground operations.  Major distraction during a rejected takeoff. I suggest fix database; and add 'collection site' to radio call or the ACARS message so we don't think something bad has happened to our family members.

Callback: The Reporter stated that this aircraft had RAAS installed and because the departure runway had an overrun usable for takeoff but not landing; when he attempted to takeoff from the overrun area the RAAS interpreted the aircraft to not be on the runway. This event occurred on the second takeoff but it was ignored and the takeoff completed. This particular RAAS volume did not interfere with ATC radio or inter-cockpit communications. The reporter also added that the ACARS message from the Company after the reject affected both pilots even though it was addressed to the First Officer who had an ailing parent. Those types of messages should be delivered to the crew only after they are in a situation where stress and worry will not interfere with safety of flight duties.



Synopsis: An aircraft with RAAS alerted ON TAXIWAY during takeoff on a runway overrun suitable for takeoff; but not landing so the Captain initiated a slow speed reject but ignored the warning on the subsequent takeoff.