elihoole/asrs-aviation-reports huggingface dataset:
Date: 201407
Local time of day: 0001-0600
Location: ZZZ.Airport, US
Weather elements / visibility: 10
Light: Daylight
Aircraft: PA-28 Cherokee/Archer/Dakota/Pillan/Warrior
Operator: Personal
Operating under: Part 91
Flight plan: None
Mission: Personal
Flight phase: Descent
ATC / advisory: Tower ZZZ
Aircraft component: Engine
Component problem: Malfunctioning
Reporter organization: Personal
Reporter function: Pilot Flying; Single Pilot
Reporter qualification: Flight Crew Instrument; Flight Crew Private
Human factors: Troubleshooting; Distraction
Anomaly: Aircraft Equipment Problem Critical
Detector: Person Flight Crew
When detected: In-flight
Result: Flight Crew Inflight Shutdown; Flight Crew Took Evasive Action; Flight Crew Landed in Emergency Condition; Flight Crew FLC complied w / Automation / Advisory
Contributing factors: Aircraft
Primary problem: Aircraft

Narrative: This all began during descent for landing. It was during this time that the aircraft engine began to run rough; the engine was barely producing power to maintain altitude. Immediately; I went through the emergency procedures checklist. By the time the checklist was completed; the aircraft engine was no longer producing adequate power to maintain altitude. I began looking for a suitable landing site. This site was found in the form of a large field (which was at least 2;500 feet long) that was slightly ahead of my current position on my south side. At this time; I was at approximately 1;800 feet. I began to descend to my chosen landing site. I set up for approach and prepared for an off airport landing. While lined up on my chosen landing field; and fully committed to landing the aircraft; the engine resumed normal operations. This resume in power occurred at approximately 300 feet MSL. I immediately closed the throttle as I was un-trusting of how long the return in engine power would last. I continued my approach and made a soft field landing on the grassy terrain. As soon as I was on the ground and confident in terrain solidity; I applied the brakes and brought the aircraft to a stop. Once the aircraft had come to a stop; I shut down the engine and tried to raise ZZZ Tower. I was unable to reach them by radio; so I powered down the aircraft and climbed out along with my passenger. I confirmed that both my passenger and I had received no injuries of any kind. Now that the injury check was complete; I began to try and reach ZZZ Tower via cell phone. While attempting to reach the Tower; I inspected the aircraft and determined that no structural damage had taken place. Approximately 15 minutes after getting out of the aircraft; I made contact with the Tower on my cell phone and reported to them that I; my passenger and my aircraft were all safe and without injury/damage.




Synopsis: A PA-28-151 was descending through 2;500 FT; 7 miles from his airport on a visual approach when the engine began running rough so he picked a landing site. During final approach at about 300 FT power restored but he choose to land safely off airport; without damage or injury.
Date: 201507
Local time of day: 1201-1800
Location: BWI.Airport, MD
Light: Daylight
Aircraft: B737 Undifferentiated or Other Model
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Parked
Aircraft component: Powerplant Fire/Overheat Warning
Component problem: Malfunctioning
Reporter organization: Air Carrier
Reporter function: First Officer
Reporter qualification: Flight Crew Air Transport Pilot (ATP)
Anomaly: Aircraft Equipment Problem Less Severe; Flight Deck / Cabin / Aircraft Event Smoke / Fire / Fumes / Odor
Detector: Automation Aircraft Other Automation; Person Flight Crew
When detected: Aircraft In Service At Gate
Result: General Maintenance Action
Contributing factors: Aircraft; Human Factors
Primary problem: Aircraft

Narrative: Captain informed me via phone; that while still preflighting the aircraft; the #2 engine caught on fire. Captain blew fire bottle; then blew the second bottle. He had passengers (about 16 through) evacuate the aircraft through the forward entry door. Fire department was called.




Synopsis: B737 First Officer is informed by the Captain via cell phone while preflighting the exterior that the number two engine had caught on fire and both fire bottles had been discharged.
Date: 202006
Location: ZZZ.Airport, US
Aircraft: Commercial Fixed Wing
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Parked
Reporter organization: Air Carrier
Reporter function: Flight Attendant (On Duty)
Reporter qualification: Flight Attendant Current
Human factors: Communication Breakdown; Distraction; Workload
Anomaly: Deviation / Discrepancy - Procedural FAR; Deviation / Discrepancy - Procedural Published Material / Policy
Detector: Person Flight Attendant
When detected: Pre-flight
Result: General None Reported / Taken
Contributing factors: Procedure; Company Policy; Environment - Non Weather Related; Human Factors
Primary problem: Human Factors

Narrative: I moved  passengers around and resolved a passenger conflict to maintain COVID-19 guidelines. One passenger was really upset with the process and their seat. Everything happened so fast. FA C even said get the Emergency Exit row briefing done and I'll finish up in the cabin. The main cabin door was closed already and I realized I didn't brief the emergency exits. It was accomplished before the safety demo but after the main cabin door closed.




Synopsis: Flight Attendant reported moving passengers around due to COVID-19; but didn't brief the emergency row until after the main cabin door was closed.
Date: 201409
Local time of day: 1201-1800
Location: A80.TRACON, GA
Light: Daylight
Aircraft: Large Transport
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Initial Climb
Airspace: Class B ATL
ATC / advisory: TRACON A80
Second aircraft: Small Aircraft
Reporter organization: Government
Reporter function: Approach
Reporter qualification: Air Traffic Control Fully Certified
Human factors: Situational Awareness; Confusion; Communication Breakdown; Workload
Anomaly: Airspace Violation All Types; Conflict Airborne Conflict; Deviation / Discrepancy - Procedural Clearance; Deviation / Discrepancy - Procedural Published Material / Policy; Inflight Event / Encounter Weather / Turbulence
Detector: Person Air Traffic Control
When detected: In-flight
Contributing factors: Human Factors; Procedure; Weather
Primary problem: Human Factors

Narrative: Due to weather; traffic was going around at ATL. I was working TAR D and had sent Aircraft X to TUNDR to hold at 070. This puts the aircraft in SAT F airspace. I called SAT F to point out the aircraft. SAT F responded with; 'Traffic observed.' In the heat of the moment I didn't catch the fact that he didn't say point out approved. Aircraft X traveled approximately 3 miles and a small prop aircraft was made yellow on my scope. This aircraft was west bound at 070 feet. I turned Aircraft X to a 030 heading to go behind the aircraft but separation was lost. The SAT F controller was less than a mile and a half from my boundary and I was more than a mile and a half from the boundary in my airspace. Because of poor phraseology or a miss use of terms the incident occurred. Had the SAT F controller informed my of the traffic at the time of the point out I would have turned Aircraft X to the southwest and remained with in my airspace. I believe the incident occurred because of a miss use of terms; and the fact that we keep too many aircraft in our airspace during thunderstorm conditions. At A80 it seems that we always fill the airspace when thunderstorms are going to affect the airport. When the weather does close down the airport we have a situation where we have 15-20 aircraft that have to come off the finals and be held. This creates unsafe situations on a daily basis.




Synopsis: A80 Controller describes a conflict in which he gives a sector a point out. The other Sector Controller says traffic observed. A conflict happens later between the aircraft he was trying to point out and an opposite direction aircraft displayed in yellow on his scope.
Date: 201305
Local time of day: 1801-2400
Location: ZZZ.TRACON, US
Aircraft: B757-200
Operator: Air Carrier
Operating under: Part 121
Mission: Cargo / Freight / Delivery
Flight phase: Climb
ATC / advisory: TRACON ZZZ
Aircraft component: Turbine Engine
Component problem: Malfunctioning
Reporter organization: Air Carrier
Reporter function: Captain; Pilot Not Flying
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: Flight Crew Landed in Emergency Condition; Flight Crew Returned To Departure Airport; General Declared Emergency
Contributing factors: Aircraft
Primary problem: Aircraft

Narrative: On climb out left engine surged badly and thumped. Captain took control of aircraft; declared an emergency with Departure and returned to land. Visual approach uneventful with left engine at idle.


Second narrative: On climb; left engine started surging. Control transferred to Captain for return.  Emergency declared.


Synopsis: B757 flight crew experiences left engine surging shortly after takeoff. An emergency is declared and the flight returns to the departure airport with the left engine at idle.
Date: 201508
Local time of day: 0001-0600
Location: ZZZ.Airport, US
Light: Night
Aircraft: B737-900
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Cruise; Descent
Airspace: Class A ZZZ
ATC / advisory: Center ZZZ
Reporter organization: Air Carrier
Reporter function: Captain; Pilot Not Flying
Reporter qualification: Flight Crew Air Transport Pilot (ATP)
Human factors: Workload; Troubleshooting; Physiological - Other
Second reporter function: Pilot Flying; First Officer
Anomaly: Aircraft Equipment Problem Less Severe; Flight Deck / Cabin / Aircraft Event Illness / Injury
Detector: Person Flight Attendant; Person Passenger
When detected: In-flight
Result: Flight Crew Took Evasive Action; General Physical Injury / Incapacitation
Contributing factors: Human Factors; Aircraft
Primary problem: Aircraft

Narrative: About an hour into the flight; during cruise at FL350; the A Flight Attendant (FA) called from the aft galley and informed us that all four of the FA's felt dizzy and nauseous as they worked or passed through rows 19 to 22.  They said they did not smell any type of odor.  At that time they informed us that they were feeling better and that they could continue on to our destination.  I then called [maintenance] via Satcom and discussed the issue with them.  We both agreed that since the FA's were feeling better that we would continue on. We also asked the FA's to walk through the cabin and check on the passengers; especially the ones seated between rows 19-22.  They responded a short time later and said everybody was doing well.About 30 minute from Top of Descent (TOD); the A FA notified us that there was a female passenger; 26 years of age; in seat 12F that had the same symptoms as the FA's.  She was put on O2 and we notified [medical services].  [Medical services] advised us to continue on to destination since we were only a few minutes from TOD.  The approach and landing were uneventful.  Upon arrival at destination the paramedics boarded the plane. The passenger in 12F walked off the aircraft without further assistance. The FA's had their blood pressure and pulse checked. The A FA needed to be replaced due to her condition.  Have since learned she deadheaded home and was admitted to the hospital with carbon monoxide poisoning. It looks as though this is an air quality issue.


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


Synopsis: A B737-900 Crew reported four flight attendants were nauseous and dizzy at cruise. Sometime later all were well but during descent a passenger developed the symptoms then departed unassisted. Paramedics examined the flight attendants: one was removed; deadheaded home and admitted to a hospital for carbon monoxide poisoning.
Date: 202102
Location: RJJJ.ARTCC, FO
Flight conditions: VMC
Aircraft: Commercial Fixed Wing
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Cruise
Airspace: Class A ZZZZ
ATC / advisory: Center RJJJ
Second aircraft: Any Unknown or Unlisted Aircraft Manufacturer
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; Communication Breakdown; Human-Machine Interface
Anomaly: ATC Issue All Types; Conflict NMAC; Deviation - Altitude Excursion From Assigned Altitude; Deviation - Track / Heading All Types
Detector: Automation Aircraft RA
When detected: In-flight
Result: Flight Crew Returned To Clearance; Flight Crew Took Evasive Action
Contributing factors: Procedure; Airspace Structure; Human Factors
Primary problem: Human Factors

Narrative: TCAS RA on flight route from ZZZZ AFB to ZZZ. We were on Y52. We noticed two aircraft on TCAS and with audio in contact with Fukuoka ATC Control radio in front of us heading directly in front; 12 o'clock towards us head on. Altitude of two aircraft varied from below 1000 and to our altitude of 26000 ft. TCAS alerts were activated. One of the involved aircraft's call sign was Aircraft Y. Opposing aircraft now at our same altitude; 26000 ft.; closing fast.TCAS warning; 'Traffic-Traffic;' aural followed by TCAS RA and; 'Descend;' aural warning followed. Initiated evasive maneuver. I; the Captain; with minimum map scale on display could see opposing aircraft also now descending into our flight path. Initiated flight control input with verbal command that co-pilot continue to fly while I also inputted left lateral evasive maneuver to avoid collision. I noted our separation on TCAS was less than 100 ft. in red color. Increased separation was noted and aircraft flight was stabilized back to 26000 ft. No visual contact. Possible loss of 300 to 1000 ft. of altitude of our aircraft due to evasive maneuver. Cabin crew felt evasive maneuver with no injuries reported of passengers or crew.




Synopsis: Air carrier Captain reported an NMAC with traffic from the opposite direction during cruise flight.
Date: 202007
Local time of day: 1201-1800
Location: ZZZ.Airport, US
Aircraft: Commercial Fixed Wing
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Taxi
ATC / advisory: CTAF 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
Anomaly: ATC Issue All Types; Deviation / Discrepancy - Procedural Published Material / Policy; Ground Event / Encounter Other / Unknown
Detector: Person Flight Crew
When detected: Taxi
Result: General Flight Cancelled / Delayed
Contributing factors: Environment - Non Weather Related; Staffing
Primary problem: Staffing

Narrative: Taxied onto runway after GA airplane landed; while waiting for them to exit runway our release void time expired. Had to exit runway to call for new release. There were probably at least 5 GA airplanes in the pattern or on CTAF since Tower was closed. We couldn't reach center on radios so called on phone holding short. Gave us a short release time of about 2 minutes; 39 past the hour. After the last GA plane landed I thought we had time to takeoff so we took the runway to line up. They took a long time exiting runway and our release time passed. Takeoff power was never applied; we exited the runway; taxied back to hold short and called Dispatch and then Center for a new release time.




Synopsis: Air carrier First Officer reported missing the IFR release time due to general aviation traffic in the pattern and the Tower being closed.
Date: 201809
Local time of day: 0601-1200
Location: ZZZ.Airport, US
Flight conditions: VMC
Weather elements / visibility: Strong crosswinds; 10
Light: Daylight
Aircraft: PA-28 Cherokee/Archer/Dakota/Pillan/Warrior
Operator: Personal
Operating under: Part 91
Flight plan: VFR
Mission: Training
Flight phase: Landing
ATC / advisory: CTAF ZZZ
Reporter organization: Personal
Reporter function: Single Pilot
Reporter qualification: Flight Crew Student
Human factors: Situational Awareness; Training / Qualification
Anomaly: Ground Event / Encounter Ground Strike - Aircraft; Ground Event / Encounter Loss Of Aircraft Control; Ground Excursion Runway; Inflight Event / Encounter Weather / Turbulence
Detector: Person Flight Crew
When detected: In-flight
Result: Aircraft Aircraft Damaged; Flight Crew Regained Aircraft Control
Contributing factors: Human Factors; Weather
Primary problem: Human Factors

Narrative: This was my first student pilot solo cross country flight. I checked weather this morning and everything appeared to be within my solo tolerances. The only concerning winds were at ZZZ; but were forecast to calm down by the time I would return. I then departed going to ZZZ1. Upon arriving at ZZZ1 there were stronger than anticipated crosswinds. I attempted landing twice and chose to go around both times. I decided to try once more and on the 3rd attempt didn't feel as strong a crosswind and decided to try and land the airplane. As I was touching down I felt a strong crosswind gust and I wasn't able to correct for it in time. Before I could power up to attempt to take off again I was turned sideways and attempted to correct with left rudder to straighten out. The airplane was skidding sideways and when it regained traction I was aimed towards the right side of the runway. I once again attempted to correct with rudder but over-corrected and proceeded to roll off the left side of the runway through the dirt and then came to a stop on the taxiway. The engine was still running and I was uninjured. I was able to taxi the plane over to self-service fuel where some fellow aviators helped me push the plane to the covered parking area. The only visible damage I could find was a gauge in the propeller.




Synopsis: PA28 pilot reported landing in strong crosswinds resulted in a loss of control and runway excursion.
Date: 201304
Local time of day: 0601-1200
Location: ZZZ.TRACON, US
Aircraft: Regional Jet 200 ER/LR (CRJ200)
Operator: Air Carrier
Operating under: Part 121
Mission: Passenger
Flight phase: Climb
Aircraft component: Pneumatic Ducting
Component problem: Failed
Reporter organization: Air Carrier
Reporter function: Pilot Flying; First Officer
Second reporter function: Captain; Pilot Not Flying
Anomaly: Aircraft Equipment Problem Critical
Detector: Automation Aircraft Other Automation; Person Flight Crew
When detected: In-flight
Result: Flight Crew Landed in Emergency Condition; Flight Crew Returned To Departure Airport; General Declared Emergency
Contributing factors: Aircraft
Primary problem: Aircraft

Narrative: On initial climbout we received a master warning 14th stage duct message with the associated bleed air aural message. No anti-ice was on as the weather was VFR. We completed the QRH for the 14th stage duct message which directed us to bring the engine to idle and return to the nearest suitable airport. We declared an emergency with ATC and returned with crash/fire/rescue on standby. We landed without incident; taxied clear of the runway and confirmed with the FA and the fire department that there were no indications preventing us from taxying to the gate. We proceeded to the gate and accomplished a normal deplaning of the passengers.


Second narrative: Shortly after takeoff; during the climb out; we received a master warning 14th Stage duct with an associated bleed air aural message. We ran the QRH which lead us to land at the nearest suitable airport. We declared an emergency with ATC and landed without further incident.


Synopsis: CRJ200 flight crew experiences a master warning for 14th stage duct leak with the associated bleed air aural. An emergency is declared and the flight returns to the departure airport.
Date: 201601
Local time of day: 0601-1200
Location: IAH.Airport, TX
Flight conditions: VMC
Aircraft: Large Transport
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Parked
ATC / advisory: Ramp IAH
Reporter organization: Air Carrier
Reporter function: Pilot Flying; Captain
Reporter qualification: Flight Crew Air Transport Pilot (ATP)
Human factors: Confusion; Situational Awareness
Anomaly: ATC Issue All Types; Deviation / Discrepancy - Procedural Published Material / Policy
Detector: Person Flight Crew
When detected: Pre-flight
Result: Air Traffic Control Provided Assistance; Flight Crew Became Reoriented; Flight Crew Requested ATC Assistance / Clarification
Contributing factors: Company Policy; Aircraft; Procedure
Primary problem: Ambiguous

Narrative: The ATC departure clearance we received today was somewhat ambiguous and confusing in the format we received. We were unable to print a copy (another issue) from our CDU and I do not have the FO's notes so going from memory here;We were planned to fly IAH-ZZZ. Our clearance read 'cleared to ABQ; BNDTO5; CRGER... (then something like as filed or flight plan route) ZZZ'The 'cleared to ABQ' caused the confusion because ABQ was not our destination; or re-dispatch point; although it was fix on our filed route. We called clearance delivery who did not understand our consternation initially; but then explained that this is a new system; the last couple days and the format is how the 'company' sends it to them now.As I recall; according to the AIM or maybe it was another FAA publication; and my experience the 'cleared to' on a departure clearance is the destination; with the cleared route to follow. If something in this practice is changing; some guidance would be helpful.Not being able to print our clearance anymore with the Controller Pilot Datalink Communications (CPDLC) system is a big deal and I think sets us up for more errors. It also makes complying with our new taxi check even more difficult; as the FO is supposed to verify the cleared SID; route and altitude; but without a printed copy of the PDC he will have to rely on some hastily done shorthand to review while we are taxiing or pull up the CPDLC message on the Captains CDU to compare it to his FMC and the MCP.




Synopsis: Air Carrier Captain reported receiving a PDC via controller pilot datalink communications (CPDLC) that does not follow standard clearance format. When queried; Clearance Deliver states that it is a new format that is an exact copy of the clearance as provided by the company. The lack of a printer with CPDLC equipped aircraft is also discussed.
Date: 201911
Location: ZZZ.Airport, US
Aircraft: B777-200
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Cargo / Freight / Delivery
Flight phase: Parked
Reporter organization: Air Carrier
Reporter function: Dispatcher
Reporter qualification: Dispatch Dispatcher
Human factors: Communication Breakdown
Anomaly: Deviation / Discrepancy - Procedural Hazardous Material Violation; Deviation / Discrepancy - Procedural Published Material / Policy
Detector: Person Flight Crew
When detected: Pre-flight
Result: Flight Crew Overcame Equipment Problem; General Maintenance Action
Contributing factors: Human Factors
Primary problem: Human Factors

Narrative: Flight had Dry Ice in the lower forward belly.  I was unaware of this until the Captain called and mentioned it in passing. This requires an over burn of .4% that was not on the flight plan. Informed the Captain about the need for the over burn.  Sent a new flight plan to the crew with the over burn on it.Cause: Most ramp agents are unaware of the need to relay to Operational Control about Dry Ice or perishables and the over burn requirementRamp agents in ZZZ need to be informed about notifying Dispatcher about Dry Ice or perishables on the airplane.




Synopsis: Dispatcher reported a communication breakdown between Dispatch and Ramp Agents regarding Dry Ice transport special requirements.