elihoole/asrs-aviation-reports huggingface dataset:
Date: 201506
Location: ZZZ.Airport, US
Weather elements / visibility: Rain
Aircraft: Commercial Fixed Wing
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Taxi
Reporter organization: Air Carrier
Reporter function: Ramp
Human factors: Situational Awareness; Training / Qualification
Anomaly: Ground Event / Encounter Other / Unknown
Detector: Person Ground Personnel
When detected: Taxi
Result: Flight Crew Became Reoriented; Flight Crew Returned To Gate; General Maintenance Action
Contributing factors: Human Factors
Primary problem: Human Factors

Narrative: Today I was the designated wing walker on [a] flight. I was given the ok to disconnect the tow bar by the tug driver. I pulled the pin and moved the latch from left to right and made sure that the tow bar had disconnected. It felt a little bit tight so I wiggled the tow bar to help loosen the bar. It felt ok so I went ahead and gave the ok for the tug driver to reverse. At that moment the tow bar had a rough disconnect; which alerted the pilot to [ask] a mechanic to make sure all was ok. The mechanic showed up about 2 minutes or so later and deemed that all was well. However; the pilot still wanted to tow the aircraft back to the gate to make sure. Once we arrived back to the gate; the team of mechanics deemed that the aircraft was ok. They said that due to a very new towbar; the connection to the front landing gear can be tight. What I learned in this situation is that on newer equipment that I must really make sure that the tow bar is truly disconnected (which it was) but can still be very tight.




Synopsis: Ramp employee reported having some difficulty releasing the new tow bar from the aircraft after pushback; causing a 'rough disconnect.'
Date: 202201
Location: ZZZ.Airport, US
Aircraft: A321
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Initial Climb
Airspace: Class B ZZZ
Aircraft component: Turbine Engine
Component problem: Malfunctioning
Reporter organization: Air Carrier
Reporter function: Flight Attendant (On Duty)
Reporter qualification: Flight Attendant Current
Human factors: Troubleshooting
Anomaly: Aircraft Equipment Problem Critical; Deviation / Discrepancy - Procedural Published Material / Policy; Deviation / Discrepancy - Procedural Clearance
Detector: Person Flight Crew
When detected: In-flight
Result: Air Traffic Control Provided Assistance; Flight Crew Requested ATC Assistance / Clarification; Flight Crew Returned To Departure Airport; Flight Crew Overcame Equipment Problem; Flight Crew Landed in Emergency Condition; Flight Crew Inflight Shutdown; General Flight Cancelled / Delayed; General Maintenance Action
Contributing factors: Aircraft
Primary problem: Aircraft

Narrative: Aircraft X departed ZZZ on DATE on the climbout we experienced an engine shut down which resulted in some fire coming out of the engine. The Captain informed us we would be turning around and landing in ZZZ where we would be meet by Personal and then we would be going back to the terminal where we would then have maintenance look at the aircraft. After landing they determined we would need to switch aircraft so they found us another plane we boarded waited for fuel then we departed for ZZZ1.




Synopsis: A319 Flight Attendant reported an air turn back and precautionary landing after a reported engine fire and in flight shut down of the affected engine.
Date: 201701
Local time of day: 1801-2400
Location: ZZZ.Airport, US
Aircraft: Large Transport
Operator: Military
Flight plan: IFR
Flight phase: Initial Climb
Airspace: Class C ZZZ
ATC / advisory: TRACON ZZZ
Second aircraft: Medium Transport
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
When detected: In-flight
Result: Air Traffic Control Issued New Clearance; Flight Crew Executed Go Around / Missed Approach
Contributing factors: Procedure
Primary problem: Procedure

Narrative: Right after a runway change from RWY XY to RWY XX; Aircraft X checked in with the incorrect ATIS requesting an approach into ZZZ. I issued the correct ATIS; told him which approach to expect; and since he was only requesting one approach issued his abnormal missed instructions. Those instructions were runway heading; maintain 3000. At this time my sector became saturated with inbounds to ZZZ; it was abnormally busy because the airport was ground stopped earlier in the day due to hard IMC conditions. After clearing Aircraft X for the approach; another controller helped by coordinating the missed instructions to the tower. About this time we were notified of a priority handling inbound to ZZZ; requesting to land runway XY; I started breaking air carriers out of my sequence; notifying them of the priority handling and Aircraft X would be the last approach to RWY XX before Aircraft Y. I switched Aircraft X to the tower. I was then informed after getting relieved from the position; we possibly had a loss between Aircraft X going around RWY XX and Aircraft Y landing RWY XY.




Synopsis: Approach Controller reported of a possible loss of separation when an aircraft went around and was in conflict with an inbound opposite direction aircraft.
Date: 201403
Local time of day: 0001-0600
Location: ZZZ.Airport, US
Aircraft: EMB ERJ 170/175 ER/LR
Operator: Air Carrier
Operating under: Part 121
Aircraft component: Exterior Pax/Crew Door
Component problem: Improperly Operated
Reporter organization: Air Carrier
Reporter function: Flight Attendant (On Duty); Flight Attendant In Charge
Reporter qualification: Flight Attendant Current
Human factors: Human-Machine Interface; Other / Unknown
Anomaly: Flight Deck / Cabin / Aircraft Event Other / Unknown
Detector: Person Flight Attendant
When detected: Aircraft In Service At Gate
Result: General Flight Cancelled / Delayed; General Maintenance Action
Contributing factors: Aircraft; Human Factors
Primary problem: Ambiguous

Narrative: I was working Flight Attendant (F/A) position A and made the 'prepare doors for departure' announcement. The other F/A called me and asked me to come to the rear of the aircraft; because her hand was stuck in the door between the arming levers and vent flap. Her three middle fingers were stuck. There wasn't any blood or bruising on her hand that I personally saw. The First Officer and myself tried to help her free her hand. She was able to get one finger out; but the other two fingers remained jammed. EMT's came and were unable to help. Maintenance also came and they were able to help her out. I was in the front of the aircraft by that time and did not see what they ended up doing to help her or how they got her out. She was escorted out of the aircraft and a ready reserve crew member joined the trip.




Synopsis: EMB170 Flight Attendant is informed by the B Flight Attendant that the B has her hand stuck in the door between the arming lever and vent flap. The A Flight Attendant; the First Officer and EMT's are unable to free her hand. Finally Maintenance is called and successfully frees the hand.
Date: 201704
Local time of day: 1801-2400
Location: ZZZ.ARTCC, US
Aircraft: Widebody Transport
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: Pax Seat
Component problem: Malfunctioning
Reporter organization: Air Carrier
Reporter function: Flight Attendant (On Duty)
Reporter qualification: Flight Attendant Current
Human factors: Distraction; Situational Awareness; Workload; Communication Breakdown
Anomaly: Aircraft Equipment Problem Less Severe; Flight Deck / Cabin / Aircraft Event Passenger Misconduct
Detector: Person Flight Crew
When detected: In-flight
Result: Flight Crew Became Reoriented; Flight Crew Took Evasive Action; General Maintenance Action
Contributing factors: Aircraft; Human Factors; Procedure
Primary problem: Human Factors

Narrative: Passenger during initial service notified me that he had been shocked twice by the armrest Power Supply Unit (PSU). The unit had been pulled out so the wires were showing. I asked if he needed medical assistance and he refused. I moved him to [a different seat] and taped the armrest.  He complained over and over that he was having pain; but continued to refuse medical assistance. He said he was writing an email to my airline and was going to sue. I noticed that he was consuming alcohol and appeared to be inebriated. His eyes were red and his speech slurry.He had previously told me that he didn't have a card to pay for drinks only cash. He then said that he had paid some passenger to use their cards for his drinks. I slowed down his drinking explaining that we needed to monitor his possible medical situation. He became increasingly agitated and repetitive despite me trying to de-escalate the situation. He was following me around and came into the galley to video me. When I said that wasn't allowed he pushed me on the shoulder. I went up to the purser and we called a level one. That was the end of my contact with him.




Synopsis: A Flight Attendant reported an inebriated passenger claimed to have been shocked by exposed passenger service unit wires; but refused medical attention and became increasingly agitated and aggressive.
Date: 201402
Local time of day: 0601-1200
Location: ZZZZ.Airport, FO
Flight conditions: Mixed
Weather elements / visibility: 10
Light: Daylight
Aircraft: Citation III; VI; VII (C650)
Operator: Air Taxi
Operating under: Part 91
Flight plan: IFR
Mission: Ferry / Re-Positioning
Flight phase: Cruise
Airspace: Class A ZZZZ
ATC / advisory: Center ZZZ
Aircraft component: Turbine Engine
Component problem: Failed
Reporter organization: Air Taxi
Reporter function: Pilot Not Flying; First Officer
Reporter qualification: Flight Crew Air Transport Pilot (ATP)
Human factors: Confusion; Workload; Communication Breakdown
Second reporter function: Pilot Flying; Captain
Anomaly: Aircraft Equipment Problem Critical
Detector: Automation Aircraft Other Automation; Person Flight Crew
When detected: In-flight
Result: Flight Crew Diverted; Flight Crew FLC complied w / Automation / Advisory; Flight Crew Inflight Shutdown; Flight Crew Landed in Emergency Condition; General Declared Emergency
Contributing factors: Aircraft
Primary problem: Aircraft

Narrative: Engine 1 reduced power to flight idle enroute and remained unresponsive to power commands. A diversion to a nearby airport was initiated in which shortly after a total comm failure was experienced. Engine 1 flamed out shortly after the comm failure and relights were attempted (Battery and Windmilling). The engine showed no signs of damage or fire but was secured due to time constraints and failure to relight. 7600 was used and emergency declared (implied) and a visual approach to Runway 25 was utilized.


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


Synopsis: A CE650 left engine reduced power to flight idle and became un-response to attempted restarts so an emergency was declared with a divert to a nearby airport. Shortly thereafter; the aircraft had a total communications failure while squawking 7600.
Date: 202007
Local time of day: 1201-1800
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)
Human factors: Communication Breakdown
Anomaly: Deviation / Discrepancy - Procedural Published Material / Policy; Flight Deck / Cabin / Aircraft Event Passenger Misconduct
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: We had many passengers in main cabin to serve the service. Most of the passengers took their masks off to order their drinks with us. Even after the announcement 'Please leave your masks on until the Flight Attendants complete service at your row.'Bring the menu book back on each seat; to use as sign card between the passengers and FA; so they just point it to us and show us; instead of taking off their masks having the need to be heard properly through the masks which is the new way to communicate for all of us.




Synopsis: Flight Attendant reported that when passengers were ordering their drinks; most of them took their face masks off; even though an announcement was made to leave masks on.
Date: 201511
Local time of day: 0601-1200
Location: ZZZ.Airport, US
Flight conditions: Marginal
Light: Daylight
Aircraft: Challenger CL604
Operator: Fractional
Operating under: Part 91
Flight plan: IFR
Mission: Ferry / Re-Positioning
Flight phase: Climb
Airspace: Class A ZZZ
ATC / advisory: Center ZZZ
Aircraft component: Turbine Engine
Component problem: Malfunctioning
Reporter organization: Fractional
Reporter function: First Officer; Pilot Flying
Reporter qualification: Flight Crew Air Transport Pilot (ATP)
Human factors: Workload
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 Requested ATC Assistance / Clarification; Flight Crew Diverted; Flight Crew Inflight Shutdown
Contributing factors: Aircraft
Primary problem: Aircraft

Narrative: I was the flying pilot on a positioning leg to ZZZZ. While on a southerly heading and climbing through 26;400 feet MSL the red RIGHT ENGINE FIRE master caution light illuminated. Upon seeing the light and hearing the accompanying warning klaxon; monitoring pilot and myself performed the memory items associated with an engine fire. We next notified ATC that we had shut down an engine and would need to divert to ZZZ; the nearest suitable airport. After verifying with ATC that the reported weather at ZZZ was above the published minimums for the ILS approach; we requested that ATC give us vectors onto the localizer.As the Quick Reference Handbook was on my side of the cockpit at the time of the event; I transferred control of the aircraft to [the] Captain and performed the ENGINE DAMAGE/FIRE DURING FLIGHT and SINGLE ENGINE APPROACH AND LANDING checklist procedures. After several vectoring turns from ATC to allow us to lose altitude and avoid areas of heavy precipitation; we were vectored onto the localizer and flew the ILS and landed. After shutdown; I performed a post-flight inspection and was unable to find any evidence of damage to the right engine. Event occurred while we were momentarily in the clear after exiting a heavy line of precipitation.From a flight-crew standpoint; the incident appears to be unavoidable.




Synopsis: CL604 First Officer reported experiencing a right engine fire master caution warning light and associated audible klaxon. They accomplished the appropriate checklist items; shutdown the engine; and safely diverted to the nearest suitable airport. No damage was found while inspecting the engine post flight.
Date: 202011
Local time of day: 1201-1800
Location: ZZZ.Airport, US
Flight conditions: VMC
Aircraft: Commercial Fixed Wing
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Final Approach
Airspace: Class B ZZZ
ATC / advisory: Tower ZZZ
Reporter organization: Air Carrier
Reporter function: First Officer; Pilot Flying
Reporter qualification: Flight Crew Air Transport Pilot (ATP); Flight Crew Instrument; Flight Crew Multiengine
Human factors: Communication Breakdown
Anomaly: Deviation / Discrepancy - Procedural Landing Without Clearance

Narrative: I had been off from flying since [Month] due to the Covid19 slowdown and my leave over the summer. This was my OE after completing training to get me refreshed and up to speed with line flying. I was definitely a currency and recency of experience threat that was discussed in the cockpit and prior to the top of descent going into ZZZ. After being cleared for the ILS approach to XXR; we were using VNAV and either LOC or LNAV to track the approach course to the runway. There was a lot of haze and smoke from the fires in the area that was obscuring our ability to see the runway.  We flew the approach and eventually selected APPR mode on the MCP with approx 5 miles until touch down. Approach told us to contact tower around the Final Approach Fix. I was almost exclusively focused on flying and failed to cross-check the Captain to make sure he contacted Tower for our landing clearance. Even at the 1;000 foot call; I thought we were most likely cleared to land; and I was so focused flying that I didn't suggest the Captain query ATC. Poor workload management on my behalf. I felt very compressed as the work load increased. I flew a stabilized SOP ILS approach and landed uneventfully on XXR. Upon contacting Ground Control we realized that Tower was never contacted and clearance to land was never received. Ground Control made no mention of this failure and cleared us to our gate.




Synopsis: Air carrier First Officer reported that the crew landed without a clearance after forgetting to contact Tower. The First Officer cited poor workload management and lack of recent flying as contributing factors.
Date: 201209
Local time of day: 0601-1200
Location: ZZZ.Airport, US
Aircraft: EMB ERJ 170/175 ER/LR
Operator: Air Carrier
Operating under: Part 121
Flight phase: Taxi
ATC / advisory: Ground ZZZ
Aircraft component: Hydraulic System Pump
Component problem: Improperly Operated
Reporter organization: Air Carrier
Reporter function: Captain; Pilot Flying
Reporter qualification: Flight Crew Air Transport Pilot (ATP)
Human factors: Confusion; Human-Machine Interface; Training / Qualification; Situational Awareness
Anomaly: Aircraft Equipment Problem Less Severe; Deviation / Discrepancy - Procedural Published Material / Policy
Detector: Person Flight Crew
When detected: Taxi
Result: General None Reported / Taken
Contributing factors: Human Factors; Procedure
Primary problem: Human Factors

Narrative: As we cleared the runway I asked for 'shutdown #2 engine.' We made a right turn and as we straightened out on the taxiway the plane just sort of started drifting to the right side and I quickly noticed my steering was not working. I stopped. We noticed the 'steering off' message on EICAS. I tried resetting the steering disconnect switch with depressing the tiller down to again connect the steering but nothing worked. After talking to Ground and getting a tug coming out to help us; I called Maintenance Control. We did reset per QRH (not pulling any circuit breakers)...he agreed we'll just get towed to the gate and look at it there. It became evident the tug was going to be a while. I considered I would have a better chance to taxi using differential steering having both engines started. At that moment it occurred to me the engine shut down correlated soon after with this steering fail. I looked up at the hydraulic pumps and they were in the 'OFF' position. Mystery solved. First Officer simply turned pumps OFF when intending to turn them on. Turning pumps on; steering now worked and we taxied uneventfully to the gate. Never shut down engine approaching or turning a corner; just in case. Verify pumps are turned on.




Synopsis: ERJ-170 Captain reported that the aircraft started to drift to the right while taxiing after one engine was shutdown. Nosewheel steering was inoperative and Captain subsequently noted that the First Officer had turned the hydraulic pump off.
Date: 201701
Local time of day: 0601-1200
Location: TRK.Airport, CA
Flight conditions: Mixed
Weather elements / visibility: Fog; Turbulence; 8
Light: Daylight
Aircraft: Cessna 340/340A
Operator: Personal
Operating under: Part 91
Flight plan: None
Mission: Ferry / Re-Positioning
Flight phase: Cruise
Airspace: Class E ZOA
ATC / advisory: Center ZOA
Reporter organization: Personal
Reporter function: Single Pilot
Reporter qualification: Flight Crew Air Transport Pilot (ATP); Flight Crew Multiengine
Human factors: Situational Awareness
Anomaly: Inflight Event / Encounter VFR In IMC; Inflight Event / Encounter Weather / Turbulence
Detector: Person Flight Crew
When detected: In-flight
Result: Flight Crew Requested ATC Assistance / Clarification
Contributing factors: Human Factors; Weather
Primary problem: Human Factors

Narrative: Planning to ferry the airplane from TRK to another airport at a lower altitude in anticipation of IMC and extensive snow accumulation the next day; I checked weather and conditions at TRK (CAVOK) and in the Sacramento area (broken 3;000) I decided to attempt to fly VFR westbound along HWY 80. After departure TRK; I leveled off at 7;000 feet (>1;000 feet AGL) and followed HWY 80. After a few minutes of flight; the cloud layer on the other side of Donner Pass came into view. I decided to attempt fly underneath the clouds and descended to an altitude below the clouds. Approaching the highest elevation point of HWY 80; I determined there was not enough clearance over the pass and turned around. After turning around; I noticed a higher ceiling and better visibility over the old Donner Pass road and proceeded in that direction. After crossing Donner Pass at low altitude AGL; but clear of clouds; I started to realize that the ceiling was decreasing rapidly on the west side of the pass and I needed to take evasive action. Faced with the option of turning around at low altitude and cross the pass again in climb eastbound or climbing through the relatively thin layer of clouds; I elected to execute a maximum performance climb straight ahead in direction of the road and HWY through the clouds to a safe altitude and VMC where I contacted ATC and requested a clearance to complete the ferry flight IFR. My mistake was decision-making that relied on interpolating weather conditions in between two points that are too far apart and with too many weather-influencing factors. I was surprised by the sudden onset of low and descending ceiling after taking off in CAVOK minutes earlier. I should have never attempted to execute the flight VFR. Easily accessible additional real-time weather information for geographic locations between airports would have been helpful and could have resulted in better decision-making.




Synopsis: C340 pilot reported departing TRK in VFR conditions headed across Donner Pass westbound and encountered IMC conditions. Pilot climbed to VFR conditions and contacted ATC to complete the flight IFR.