elihoole/asrs-aviation-reports huggingface dataset:
Date: 201504
Local time of day: 1201-1800
Location: ZZZ.Airport, US
Weather elements / visibility: 10
Aircraft: Skylane 182/RG Turbo Skylane/RG
Operator: FBO
Operating under: Part 91
Flight plan: VFR
Mission: Training
Flight phase: Descent
Airspace: Class E ZZZ1
ATC / advisory: TRACON ZZZ1
Aircraft component: Engine
Component problem: Failed
Reporter organization: FBO
Reporter function: Instructor
Reporter qualification: Flight Crew Multiengine; Flight Crew Flight Instructor; Flight Crew Instrument
Anomaly: Aircraft Equipment Problem Critical; Ground Event / Encounter Ground Strike - Aircraft
Detector: Person Flight Crew
When detected: In-flight
Result: Aircraft Aircraft Damaged; Flight Crew Landed in Emergency Condition
Contributing factors: Aircraft
Primary problem: Aircraft

Narrative: On a transitional flight in a C-182 with a private pilot we were approaching to land at [the] airport. While joining the downwind at 45 degree midfield and at about 1;100 feet MSL about to turn to base leg the engine stopped producing power. Until such time the student was at controls. When the engine failed; I took over control; established the best glide speed; did the emergency engine failure procedures and headed to the runway. We were low on altitude and came on finals. We crossed the airport fencing in a shallow turn and was left of the runway. I leveled the wings and flared for landing. The aircraft touched down with the left main gear on the soft grass area with slush and snow. We rolled and when the nose wheel touched down; it bogged down on the soft ground and the nose wheel collapsed. There were damage on the bottom cowl. There were no injuries to me or my student.




Synopsis: C-182 instructor pilot reported losing engine power in the pattern. A dead stick landing was made in the grass where the nose gear collapsed.
Date: 202107
Local time of day: 1801-2400
Location: ZZZ.Airport, US
Flight conditions: VMC
Weather elements / visibility: 10
Light: Daylight
Aircraft: Small Aircraft
Operator: FBO
Operating under: Part 91
Flight plan: None
Mission: Training
Flight phase: Taxi
Reporter organization: Personal
Reporter function: Pilot Flying; Single Pilot
Reporter qualification: Flight Crew Commercial; Flight Crew Flight Instructor; Flight Crew Instrument; Flight Crew Multiengine
Anomaly: ATC Issue All Types; Deviation / Discrepancy - Procedural Published Material / Policy; Deviation / Discrepancy - Procedural Clearance
Result: Air Traffic Control Issued New Clearance; Flight Crew Requested ATC Assistance / Clarification
Contributing factors: Human Factors; Procedure
Primary problem: Procedure

Narrative: I landed and was given taxi instructions to the ramp that included two runway crossings while still rolling on the runway. I was told to exit on [Taxiway] 1 and cross [Runway] XXL on [Taxiway] 2 and hold short of [Runway] XXR. I exited and rolled to hold short of XXL and verified that I was cleared to cross. I crossed and continued on 2 to XXR. Before XXR; I asked if I could taxi via 3 [and] 4 to the ramp; which was incorrect. I needed to taxi to 4X. I didn't recall getting instructions beyond holding short of XXR prior. After resolving some confusion; the tower controller told me to taxi on XXR and 4X to the ramp. That is what I heard. I read it back and was partially stepped on and someone said something else. The tower controller said 'what' then proceeded to talk to other traffic. At this point I was taxiing on the runway and was slightly thrown off. I exited the runway and was on the non movement area ramp. I continued to monitor the frequency until shutting down and didn't hear my callsign again. It was a confusing sequence from getting the instructions on the rollout and given two different runway crossings with two different instructions. It would have been nice to have been given time to clear the runway and then take down instructions when I wasn't still focused on the landing during a critical phase of flight. Simple taxi instructions such as one taxiway to the ramp or one runway crossing isn't too hard to remember but still hard during a critical phase of flight. However; two runway crossings while rolling and complex instructions were confusing. The controller had a high work load and asking for conformation on the runway crossing probably didn't help her but I felt like I needed to verify. Then the confusion on my end didn't help crossing XXR. Being told to taxi via XXR weren't the instructions I was thinking of getting and made me second guess crossing the runway. Coming to a stop and asking for more clarification on frequency would've been the best thing to do. XXR wasn't a runway in use at the time and I cleared the area so I felt comfortable to cross; along with being told to taxi via XXR; I believed I had been cleared onto the runway.




Synopsis: Pilot reported ATC issued complex and confusing taxi instructions during the landing rollout which led to confusion about being cleared to cross a runway.
Date: 202109
Local time of day: 1201-1800
Location: ZZZ.Airport, US
Aircraft: PA-46 Malibu Meridian
Operator: Personal
Operating under: Part 91
Flight phase: Taxi
ATC / advisory: Tower ZZZ
Aircraft component: Reciprocating Engine Assembly
Component problem: Failed
Reporter organization: Personal
Reporter function: Single Pilot; Pilot Flying
Reporter qualification: Flight Crew Instrument; Flight Crew Flight Instructor; Flight Crew Commercial; Flight Crew Multiengine
Anomaly: Aircraft Equipment Problem Critical; Deviation / Discrepancy - Procedural Published Material / Policy
Detector: Person Flight Crew
When detected: Taxi
Result: Flight Crew Requested ATC Assistance / Clarification
Contributing factors: Aircraft
Primary problem: Aircraft

Narrative: After landing on runway at ZZZ; the aircraft engine died when beginning a 180 degree turn to back taxi on the runway as commanded by the Tower. After multiple attempts to restart; the FBO was dispatched to retrieve the aircraft from the runway. The runway was closed; and then reopened after the aircraft was removed.




Synopsis: PA-46 pilot aircraft reported engine failure during taxi after landing.
Date: 201512
Local time of day: 0601-1200
Location: SRQ.Airport, FL
Flight conditions: VMC
Light: Daylight
Aircraft: Small Aircraft; Low Wing; 1 Eng; Fixed Gear
Operator: Personal
Operating under: Part 91
Flight plan: VFR
Mission: Personal
Flight phase: Takeoff / Launch
Airspace: Class C SRQ
ATC / advisory: Tower SRQ
Second aircraft: Small Aircraft; High Wing; 1 Eng; Fixed Gear
Reporter organization: Government
Reporter function: Supervisor / CIC
Reporter qualification: Air Traffic Control Fully Certified
Human factors: Situational Awareness; Training / Qualification
Anomaly: ATC Issue All Types; Conflict Airborne Conflict
Detector: Person Air Traffic Control
When detected: In-flight
Result: Air Traffic Control Issued New Clearance; Air Traffic Control Separated Traffic; Flight Crew Executed Go Around / Missed Approach; General Flight Cancelled / Delayed
Contributing factors: Procedure; Airspace Structure; Human Factors
Primary problem: Procedure

Narrative: Training in progress on Local control. First time instructor is observing trainee. Trainee had Aircraft Y in the pattern to Runway 22 and Aircraft Z on 5 mile final to Runway 32. Trainee asked the Aircraft Y in the pattern if he could make a short approach; to which he said yes. So the trainee had Aircraft Y make a short approach with Aircraft Z on 4.5 mile final. Then Aircraft X called up for departure at the approach end of Runway 32. The trainee cleared Aircraft X for an immediate departure; but Aircraft Y was already on the base turn to Runway 22. Aircraft X was airborne at about Taxiway B when the trainer sent Aircraft Y around on Runway 22. There was no loss of separation; the weather was clear but the timing could have been a lot better and Aircraft Y passed behind the departing Aircraft X. As Controller-in-Charge I noticed that the situation wasn't going to work and said so to the instructor. I also told the trainee that by having Aircraft Y make a short approach they created the situation with departing Aircraft X. A normal approach on Aircraft Y with Aircraft Z on final would have allowed plenty of room for Aircraft X to depart Runway 32.I told the instructor that I would have appreciated if they would have not let the situation continue even after I said I felt it wasn't going to work. I told the trainee the situation was created when having Aircraft Y make a short approach when it wasn't needed. I also told the trainer that I wanted traffic issued; but that wasn't done either.




Synopsis: Controller on the Job training was occurring at the Local Control position. The trainee Controller cleared an aircraft for takeoff with another aircraft on short final to an intersecting runway. The instructor took over and sent the arrival around preventing a loss of separation. The reporter was Controller-in-Charge at the time and felt the instructor should have resolved the situation in a timelier manner.
Date: 201204
Local time of day: 1201-1800
Location: ZZZ.ARTCC, US
Flight conditions: VMC
Light: Daylight
Aircraft: A321
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Flight phase: Cruise
Airspace: Class A ZZZ
ATC / advisory: Center ZZZ
Aircraft component: Hydraulic System
Component problem: Improperly Operated
Reporter organization: Air Carrier
Reporter function: Pilot Not Flying; Captain
Reporter qualification: Flight Crew Air Transport Pilot (ATP)
Human factors: Human-Machine Interface
Anomaly: Aircraft Equipment Problem Critical; Deviation / Discrepancy - Procedural Maintenance
Detector: Automation Aircraft Other Automation
When detected: In-flight
Result: Flight Crew Diverted; Flight Crew Landed in Emergency Condition; General Maintenance Action; General Declared Emergency
Contributing factors: Aircraft; Human Factors; Procedure
Primary problem: Procedure

Narrative: Prior to departure Contract Maintenance had removed some fluid from [the previously] over serviced Green and Yellow hydraulic systems. Approximately 2 hours into the flight an ECAM Alert indicated Green System Pressure Low. ECAM hydraulic page indicated lower than normal Green System quantity and pressure. All ECAM procedures and checklists were completed and system references were checked. ECAM subsequently alerted of Green System low quantity. Dispatch and Maintenance were contacted. The situation was discussed in detail and the decision was made to divert to a nearby airport. ATC; passengers and cabin crew were advised and an emergency was declared. Dispatch and Operations were advised that the flight would need Customs Service at the diversion airport and possibly a tow off of the runway. Due to loss of Green System; ECAM and QRH procedures were followed in order to manually lower the landing gear. The successful gear extension was followed by a normal landing. Nose wheel steering was effective and the aircraft cleared the runway. After emergency responders inspected outside of aircraft for hot spots; aircraft was taxied to a gate to clear customs and undergo repairs. Mechanical irregularities were written up in the log book.Contract Maintenance had failed to notice that; after they had completed their maintenance action; fluid was leaking from the Green System Reservoir. Contract Maintenance would be instructed to observe hydraulic lines for some time period after maintenance to ensure that no leaks are occurring.




Synopsis: An A321 flight crew were confronted with low yellow and green hyrdualic system quantities enroute following maintenance action at their departure airport. After draining excess fluid from the systems; Maintenance personnel had failed to insure that there was no leakage from the reservoirs.
Date: 202104
Local time of day: 1201-1800
Location: EUG.Airport, OR
Aircraft: Small Aircraft
Operating under: Part 91
Flight plan: IFR
Flight phase: Landing
Airspace: Class E EUG
ATC / advisory: TRACON EUG
Second aircraft: Any Unknown or Unlisted Aircraft Manufacturer
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 Advisory / Alert; Air Traffic Control Provided Assistance; Flight Crew Executed Go Around / Missed Approach
Contributing factors: ATC Equipment / Nav Facility / Buildings; Airport; Environment - Non Weather Related
Primary problem: Environment - Non Weather Related

Narrative: Aircraft X was IFR and requested the RNAV [Runway] 35 approach into CVO airport. I cleared them for the approach and advised them of traffic - multiple targets in the vicinity of CVO indicating 040 and below. There were probably about 10 VFR targets in the vicinity of CVO; all squawking 1200 not receiving ATC services. Several of the VFR targets were maneuvering near the IAFs for approaches into EUG Runways 16R and 16L; which could have easily caused more problems for arrivals into EUG if they had come then. I switched Aircraft X to advisory frequency at least 10 NM south of the airport. My focus then switched to other traffic I was working. After a few minutes; Aircraft X returned to my frequency to report that they were flying west to avoid traffic. They were not flying the published missed approach due to multiple other aircraft in that path. I also had to immediately issue a traffic alert to other traffic near them. They were flying on an IFR plan and maneuvering on their own below the MVA to avoid multiple other aircraft. Once they were above the MVA I vectored them further away from traffic.From what I could tell; there was not any orderly flow of the VFR traffic at CVO.CVO airport needs to have an air traffic control tower. There is too much VFR aircraft flying disorderly on their own in that vicinity; many of them student pilots and foreign; but also mixed with air taxis and jets; as well as regular aerobatic activity. This is just one example of pilots not being able to sequence themselves and pilots needing to take evasive action.Also; EUG should be upgraded to a Class C in order to require VFR aircraft flying at dangerous altitudes in the approach path of EUG to talk to ATC.




Synopsis: Eugene TRACON Controller reported an unsafe operation with numerous VFR aircraft at the CVO uncontrolled airport.
Date: 202001
Local time of day: 1201-1800
Location: ZZZ.Airport, US
Light: Daylight
Aircraft: B737-700
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: Turbine Engine
Component problem: Failed; Malfunctioning
Reporter organization: Air Carrier
Reporter function: Captain; Pilot Not Flying
Reporter qualification: Flight Crew Instrument; Flight Crew Air Transport Pilot (ATP); Flight Crew Multiengine
Human factors: Workload
Anomaly: Aircraft Equipment Problem Critical
Detector: Person Flight Crew
When detected: In-flight
Result: Air Traffic Control Provided Assistance; Flight Crew Diverted; Flight Crew Requested ATC Assistance / Clarification; Flight Crew Overcame Equipment Problem; Flight Crew Landed in Emergency Condition
Contributing factors: Aircraft
Primary problem: Aircraft

Narrative: Approximately 60 miles northeast of ZZZ at FL 380; the #1 engine rolled back to 68% N1. The engine would not respond to forward thrust lever movement; only to a lower thrust lever setting. Since this partial engine power was not addressed specifically in the QRH I thought that turning off the associated EEC (Electronic Engine Control) might allow us to regain control. The EEC was turned off; without effect and was turned back on. The decision to divert to ZZZ was an easy one. The Flight Attendants and Dispatch were notified. ATC was advised; vectors were provided to a Runway XX arrival.  The engine failed completely on downwind.The Engine Failure and One Engine Inop Landing QRH checklists were accomplished. The First Officer was the Flying Pilot; he continued to fly and did most of the communicating with ATC. Performance calculation flaps 15 engine out data was used and briefings completed. Aircraft control was transferred and I became the Pilot Flying.  A normal engine out flaps 15 landing was made. After clearing the runway; ZZZ Fire Rescue looked over the engine and detecting no threats; we taxied to our assigned gate.Two passenger PA's were made while airborne and one after landing. There were no Passenger issues that I was made aware of; our Flight Attendants must have done a wonderful job. My First Officer did a perfectly professional job of flying and communicating with ATC. KUDOS to all the SIM Instructors I have had over the years.




Synopsis: B737-700 Captain reported loss of power in the #1 engine while at cruise altitude which caused a diversion.
Date: 202010
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: Flight Attendant (On Duty)
Reporter qualification: Flight Attendant Current
Human factors: Other / Unknown
Anomaly: Deviation / Discrepancy - Procedural Published Material / Policy; Flight Deck / Cabin / Aircraft Event Illness / Injury
Detector: Person Flight Attendant
When detected: Other Post Flight
Result: General None Reported / Taken
Contributing factors: Environment - Non Weather Related; Human Factors
Primary problem: Environment - Non Weather Related

Narrative: Apparently I was exposed to the COVID on this flight.  I received a call from Flight Attendant G that Flight Attendant A has tested positive. I wasn't too concerned at the time. My time with her was minimal. But I heard from Flight Attendant D that she too had tested positive. So I called the company to set up a test. After the testing I was informed I could not fly until I received the results. Just an FYI; we flew the aircraft with the XX-day spraying using Product X. The cleaners in ZZZ were very rushed because we arrived late. I do know they did not spray; which they didn't need to. But they also didn't wipe down any of the tray tables. I am unsure what else they did or did not do.




Synopsis: Flight Attendant reported exposure to COVID-19 and described aircraft sanitizing concerns.
Date: 201909
Local time of day: 1201-1800
Location: ZZZ.Airport, US
Aircraft: A320
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Parked
Reporter organization: Air Carrier
Reporter function: Other / Unknown
Human factors: Situational Awareness
Second reporter function: Other / Unknown
Anomaly: Deviation / Discrepancy - Procedural Published Material / Policy; Deviation / Discrepancy - Procedural Weight And Balance; Deviation / Discrepancy - Procedural Hazardous Material Violation
Detector: Person Ground Personnel
When detected: Aircraft In Service At Gate; Pre-flight
Result: General None Reported / Taken
Contributing factors: Human Factors
Primary problem: Human Factors

Narrative: Ramp attempted to close out HZ [Hazmat] on DSTG [Departure Staging Guide] with only 14 bags and 1 quick-pac to secure it. I told them they needed to add 1 bag to pit 6 to meet [Company]'s Hazmat requirement. Aircraft pushed at XA17. They attempted several more times to close DSTG without changing anything on DSTG. Of course; no success. Captain called [Dispatch] and was patched thru to me. He advised he was at end of runway. At XA46 DSTG was changed to show 16 bags (15 bags and 1 quick-pac) securing the HZ. ZZZ1 did an audit-per [name]. They advised only 13 bags in pit 6 securing the HZ.


Second narrative: At ramp final; DSTG failed due to 15 bag minimum not being met for securing DG loaded in pit 6. Station was advised that 15 bag minimum was not met. LP [Load Planner] was advised flight was out and it was not convenient to return flight to correct error. After numerous calls between LP; ZZZ ramp; and ZZZ operations bag count was updated in pit 6 to 16. DSTG [Departure Staging Guide] and DDLR [Departure Load Report] were finalized and weights sent. [Load Control] requested ZZZ1 ramp audit the offload from pit 6. ZZZ1 ramp reported 13 bags; QPK's [Quick-pac] and freight were offloaded from pit 6. Flight out XA17; first DSTG auto-fail for minimum bag XA18; pit 6 bag count changed to 16 XA46; weights sent XA49 flight off XA58.


Synopsis: Airline Ground Personnel reported DSTG [Departure Staging Guide] updated to allow aircraft departure without correcting load errors. Destination unload audit reported load errors not corrected.
Date: 201808
Local time of day: 1201-1800
Location: ZZZZ.Airport, FO
Flight conditions: VMC
Aircraft: B767-300 and 300 ER
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Cruise
ATC / advisory: Center ZZZZ
Reporter organization: Air Carrier
Reporter function: First Officer
Reporter qualification: Flight Crew Air Transport Pilot (ATP); Flight Crew Instrument; Flight Crew Multiengine
Anomaly: Flight Deck / Cabin / Aircraft Event Illness / Injury; Flight Deck / Cabin / Aircraft Event Smoke / Fire / Fumes / Odor
Detector: Person Flight Attendant
When detected: In-flight
Result: Air Traffic Control Provided Assistance; Flight Crew Diverted; Flight Crew Landed As Precaution; General Maintenance Action
Contributing factors: Aircraft
Primary problem: Aircraft

Narrative: During my break; I was woken up notifying me that we were diverting to ZZZZ. Found out [a] number of flight attendants were feeling nauseous; dizziness and sluggish. After entering the cockpit; I also got tingling feeling and headache. Cockpit crew completed Smoke; Fire or Fumes checklist; and Overweight Landing checklist. Landed and taxied to gate uneventfully. There were no signs of visible smoke or identifiable smell in the cockpit or cabin during the event.After safely arriving on the gate; one of the flight attendants mentioned she might have smelled anti-freeze type smell coming from the chiller. Initially; I thought we might have experienced refrigerant poisoning; the symptoms were similar to symptoms of hypoxia. After Maintenance investigation that took two days found a cargo container with shoes and the glue that was used to attach soles was the cause of the symptoms. The chemicals used to manufacture the adhesive should be investigated; and if inhaled; what short and long term effects can we expect. If it's harmful to humans; it should not be carried on passenger air carriers.




Synopsis: B767 First Officer reported enroute diversion due to several Flight Attendants experiencing symptoms similar to hypoxia caused by unknown source. Further investigation by Maintenance determined fumes of cargo shipment of glue and shoes was the probable cause.