elihoole/asrs-aviation-reports huggingface dataset:
Date: 201502
Local time of day: 1801-2400
Location: ZZZ.Airport, US
Flight conditions: IMC
Weather elements / visibility: 6
Light: Night
Aircraft: Cessna 210 Centurion / Turbo Centurion 210C; 210D
Operator: Personal
Operating under: Part 91
Flight plan: IFR
Mission: Personal
Flight phase: Cruise
Airspace: Class E ZZZ
ATC / advisory: Center ZZZ
Aircraft component: Switch
Component problem: Design; Improperly Operated
Reporter organization: Personal
Reporter function: Single Pilot
Reporter qualification: Flight Crew Instrument; Flight Crew Private
Human factors: Confusion; Other / Unknown
Anomaly: Aircraft Equipment Problem Less Severe; Deviation - Altitude Excursion From Assigned Altitude; Deviation / Discrepancy - Procedural Clearance; Inflight Event / Encounter Loss Of Aircraft Control
Detector: Person Flight Crew
When detected: In-flight
Result: Flight Crew Became Reoriented; Flight Crew Diverted; Flight Crew Landed As Precaution; Flight Crew Overcame Equipment Problem; Flight Crew Regained Aircraft Control; General Declared Emergency
Contributing factors: Aircraft; Human Factors
Primary problem: Human Factors

Narrative: VMC at 6000 requested climb to 8000. 8000 was IMC with temp. +1. Moved forward in seat to inspect wing leading edge for possible ice; negative. Panel went 'black' Chelton panel dark; MX20 dark; GNS 480 dark; no autopilot; no transponder; no comm radio; headset noise cancelling off.  Resulting panic. No transponder or comm but had an 'emergency'; needed time to assess; needed VMC.  Began descent to 6000 exiting clouds in unusual attitude; corrected attitude; assessed situation after selecting 'nearest' airport. FOUND AVIONICS MASTER TO BE IN OFF POSITION. Turned on avionics master; significant reduction in panic but still disoriented and seeking to land safely to assess calmly what happened. With radio back 'online' called center to explain and declare emergency and accept assistance in navigating. Still uncertain what to trust with multiple yellow flags on Chelton EFIS. Visual approach where I spent the night before resuming flight VMC next morning after analyzing what had happened.Assessment: While moving seat forward and twisting to inspect wing leading edge for icing caused knuckle; kneeboard; watch or something to unknowingly depress avionics master to off position. Sudden roar in headset (thinking rapid decompression) black panel; thinking catastrophic failure leading to panic.  Getting to VMC very helpful in rationalization of circumstances. Avionics master switch is recessed for protection from incidental switching but somehow must have hit it 'just right'! Have reviewed with recurrent trainer to incorporate in training scenario so others might recognize symptoms. I'll never forget!




Synopsis: A C210 pilot reports inadvertently switching off the avionics master switch while leaning forward to check the wing for ice. All panels go dark including COMMS (Communications) and autopilot. A descent is initiated; ATC is advised; and the aircraft is recovered in VMC. The switch position is detected and corrected; but the reporter elects to divert and spend the night.
Date: 201809
Local time of day: 0001-0600
Location: ZZZ.Airport, US
Flight conditions: VMC
Light: Daylight
Aircraft: PA-28 Cherokee/Archer/Dakota/Pillan/Warrior
Operator: FBO
Operating under: Part 91
Flight plan: None
Mission: Passenger
Flight phase: Landing
Reporter organization: FBO
Reporter function: Pilot Flying; Single Pilot
Reporter qualification: Flight Crew Private
Anomaly: Ground Event / Encounter Loss Of Aircraft Control; Ground Event / Encounter Object; Ground Excursion Runway; Ground Incursion Taxiway
Detector: Person Flight Crew
When detected: In-flight
Result: Flight Crew Regained Aircraft Control
Contributing factors: Human Factors; Weather
Primary problem: Ambiguous

Narrative: I was PIC of a Piper Cherokee landing at ZZZ. Weather was VMC and I was number three on arrival for XXR and looking for Citation traffic inbound. About 3/4 of a mile abeam the numbers; ZZZ Tower instructed me to make an immediate right base; and to switch to a cleared XXR landing; the parallel runway; for traffic (one Citation had just landed; another on the way in). I complied; responded to ATC; and began an immediate descent to avoid too high of a final approach onto XXL.I came in to land on XXL as normal. Just before touchdown; I felt a crosswind gust on the starboard side and felt the aircraft nose point to the right; so I applied left rudder to keep the nose straight. At this point the aircraft touched down; the nosewheel also then touched down and the aircraft began to slide to the left. I attempted to return rudder/nosewheel input to neutral but the aircraft began to skid to the left. This caused the aircraft to turn 45 degrees left of runway XXL centerline.The aircraft then entered the grass area left of XXL; cut across an intersecting taxiway (what I believe was taxiway  E); the right wing root impacted a taxiway location sign; the aircraft then went from the grass onto the taxiway B surface; I then applied rudder pedals to put the aircraft onto the taxiway centerline; and applied full braking power.I do not recall the time between the first jet landing on parallel XXR and my aircraft touching down on XXL; but it was within two minutes. The second Citation landing on parallel XXR was behind my aircraft at all times so I do not believe the second aircraft wake turbulence was a factor.I do not know if I could have avoided this accident with a go around. I remember thinking the landing was a particularly smooth one very briefly; under the nose wheel touched down and the aircraft began veering to the left. I attempted to bring it back to centerline but was afraid that too much right rudder would cause it to skid the other direction. Once I entered the grass; I recall trying to put all control surfaces to their neutral position until the aircraft returned to the tarmac that was taxiway B.




Synopsis: PA-28 pilot reported a loss of control on landing that resulted in a runway excursion.
Date: 201409
Local time of day: 1801-2400
Location: DWH.Airport, TX
Light: Night
Aircraft: Any Unknown or Unlisted Aircraft Manufacturer
Flight plan: IFR
Flight phase: Cruise
Airspace: Class E ZHU
ATC / advisory: Center ZHU
Reporter organization: Government
Reporter function: Enroute
Reporter qualification: Air Traffic Control Fully Certified
Human factors: Confusion; Situational Awareness; Training / Qualification
Anomaly: Airspace Violation All Types; Deviation / Discrepancy - Procedural Clearance; Deviation / Discrepancy - Procedural Published Material / Policy
Contributing factors: Airspace Structure; Human Factors; Procedure
Primary problem: Human Factors

Narrative: Yesterday I handed off a west bound aircraft which was landing at DWH; level at 060; to I90 Tomball sector. The undirected hand off flashed initially to the I90 DAS sector. Thinking that this was an ERAM anomaly I retracted the hand off and directed the hand off to I90 Tomball. Upon acceptance of the hand off I switched the aircraft to I90 Tomball sector and no further communication with the aircraft or any I90 controllers occurred after that. This afternoon; as colleagues were discussing the recent re stratification of some of I90's airspace it occurred to me that there were some changes made around the NE inbound gates. When I checked the sector map I found that the floor of the I90 DAS sector had indeed been dropped to 060 from its previous floor of 070 prior to the Optimization of Airspace & Procedures in the Metroplex (OAPM) changes last May. I am reasonably certain that I allowed the aircraft in question to enter I90 DAS sector without a point out or hand off. When an undirected hand off flashes to an unexpected sector that some effort is made to find out why this is occurring. Had I quickly reviewed the overhead chart I would have had my answer and would have avoided this event.




Synopsis: ZHU Controller describes a situation where he thought an undirected handoff was incorrect. The Controller took the handoff back and directed it to what he/she thought was the correct area. Controller later finds out other facilities airspace had changed; which resulted in an airspace deviation.
Date: 201710
Local time of day: 1201-1800
Location: OAK.Airport, CA
Flight conditions: VMC
Light: Daylight
Aircraft: Large Transport
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Descent
Airspace: Class B SFO
ATC / advisory: TRACON NCT
Second aircraft: Widebody Transport
Reporter organization: Government
Reporter function: Approach
Reporter qualification: Air Traffic Control Fully Certified
Human factors: Situational Awareness; Distraction
Anomaly: ATC Issue All Types; Airspace Violation 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; Air Traffic Control Separated Traffic
Contributing factors: Airspace Structure; Human Factors; Procedure
Primary problem: Human Factors

Narrative: Aircraft X was direct WUVON descending to 4;000 to intercept the final approach course to eventually get the field in sight and cleared for a visual approach. Aircraft Y was about 5 miles in trail direct FRNNY going slightly faster than Aircraft X. As Aircraft X was approaching the final; I observed that there was an unidentified VFR aircraft at their 11 o'clock northeast bound climbing out of 3;300 feet. I instructed Aircraft X to amend their altitude to 4;500 for traffic. VFR traffic and Aircraft X were going to merge so I turned Aircraft X to go behind the traffic. This in turn caused Aircraft X at 4;500 to cross the path of Aircraft Y who was level at 5;000.In the process of recovering separation between Aircraft X and Aircraft Y; Aircraft X descending to 5;000 may have penetrated Niles airspace. Aircraft X was turned to a heading of 340 to continue their descent and away from Niles airspace.I should have just turned Aircraft X northbound; climbed and possibly resequenced them when the VFR target further became a factor. With Aircraft Y 5SM in trail and keeping his speed at a higher velocity; it would have been the easiest option.




Synopsis: A TRACON Controller reported vectoring an aircraft off their approach to avoid unidentified VFR traffic lost required spacing with the arriving in trail traffic.
Date: 202202
Local time of day: 1801-2400
Location: ZZZ.ARTCC, US
Flight conditions: VMC
Light: Night
Aircraft: B787 Dreamliner Undifferentiated or Other Model
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: DC Rectifier
Component problem: Failed
Reporter organization: Air Carrier
Reporter function: Captain; Pilot Flying
Reporter qualification: Flight Crew Air Transport Pilot (ATP); Flight Crew Instrument; Flight Crew Multiengine
Human factors: Troubleshooting
Anomaly: Aircraft Equipment Problem Critical; Deviation / Discrepancy - Procedural Published Material / Policy; Deviation / Discrepancy - Procedural Clearance
Detector: Automation Aircraft Other Automation; Person Flight Crew
When detected: In-flight
Result: Air Traffic Control Provided Assistance; Flight Crew Took Evasive Action; Flight Crew Requested ATC Assistance / Clarification; Flight Crew Returned To Departure Airport; General Flight Cancelled / Delayed; General Maintenance Action
Contributing factors: Aircraft
Primary problem: Aircraft

Narrative: International flight from ZZZ to ZZZ1; Pilot Flying; Captain on this flight. In cruise for approximately 10 minutes at FL310 when we received an EICAS message of HYD pump failure and a CAC (Cabin Air Compressor) shut down due to load shed.Ran checklist for HYD pump failure. No checklist for CAC load shed...multiple other electrical system failure/ load shed status messages.Called Company Dispatch and Maintenance Control on SAT phone. Discussed failures and systems affected by the multiple electrical system load shed items. Original source of failure was indicated as an electrical Transformer/Rectifier failure.Myself; Dispatch and Maintenance Control all agreed that a diversion was best course of action and to not continue on flight to ZZZ1. ZZZ was chosen as diversion airport.Fuel dump was required in order to land below max landing weight.Return to ZZZ coordinated with ZZZZ Center; fuel dump also approved by ZZZZ Center and initiated at FL310.Dual flight management computer (FMCs) failures also occurred after turn around to ZZZ.Dispatch coordinated new flight plan; landing data and station coordination for our ZZZ arrival.Normal descent; approach; landing at ZZZ on Runway XXR in VFR conditions. Taxi to gate and normal shutdown.Debriefed Dispatch; Chief Pilot; Company Operations Manager after shut down and checklists completed.




Synopsis: B787 Captain reported multiple systems failures and electrical load shedding resulted in an air turn back and precautionary landing at departure airport.
Date: 201606
Local time of day: 1801-2400
Location: ZZZ.Airport, US
Flight conditions: VMC
Weather elements / visibility: 6
Light: Daylight
Aircraft: Bonanza 33
Operator: Personal
Operating under: Part 91
Flight plan: None
Mission: Personal
Flight phase: Initial Climb
Airspace: Class C ZZZ
ATC / advisory: TRACON ZZZ
Aircraft component: Landing Gear
Component problem: Malfunctioning
Reporter organization: Personal
Reporter function: Single Pilot
Reporter qualification: Flight Crew Private
Anomaly: Aircraft Equipment Problem Critical; Flight Deck / Cabin / Aircraft Event Smoke / Fire / Fumes / Odor
Detector: Person Flight Crew
When detected: In-flight
Result: Flight Crew Diverted; Flight Crew Overcame Equipment Problem
Contributing factors: Aircraft
Primary problem: Aircraft

Narrative: I departed [and] upon reaching approximately 300 feet AGL; I retracted the landing gear. Within 2-3 seconds; there was a distinct electrical burning odor and when I looked at the GPS unit; it was off. I looked at the gear light and it was off; and I noticed that the plane was not accelerating and instead was flying at 100-115 knots consistent with the gear still being down. I entered the traffic pattern and I cycled the gear and tried to power off and on the avionics. The GPS unit just flashed on and then off repeatedly upon restarting the avionics. The gear did not light up. I had no communication and initially squawked 7600 and made a low pass over the runway. I then had my passenger change my headset to my portable radio while I called [Unicom] on my cellphone. The Unicom person informed me that my gear was partially down and I instructed him to call [the airport] and notify them of my situation. I entered the pattern a second time to try to recycle the master and battery switch. Within 5-10 seconds the electrical burning odor returned. I tried the portable radio but Unicom could not read me. I did a second low pass and spoke to the Unicom again about if my gear came down when I cycled it and they said no. I decided to divert to [a nearby airport] due to the longer runway and emergency fire equipment in case of gear collapse. Unicom notified me that Approach was expecting me on their frequency. I [advised ATC] on my portable radio prior to entering their airspace. No response several times until an airliner relayed my [transmission] to Approach approximately 4 miles from the field. They cleared me for landing. My passenger manually cranked the landing gear as per the POH. I did a low pass over the field and asked the tower to confirm my gear was down. It was up. While maneuvering the aircraft back; the passenger cranked the gear in the opposite direction. On final; they confirmed that the gear was down and I was cleared to land. I landed and the gear stayed down.




Synopsis: BE33 pilot reported diverting to a nearby airport when the landing gear failed to fully retract. Gear was extended via the emergency method resulting in an uneventful landing.
Date: 201207
Local time of day: 0601-1200
Location: ZZZ.Airport, US
Flight conditions: VMC
Light: Daylight
Aircraft: B757-200
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Flight phase: Takeoff / Launch
Airspace: Class C ZZZ
ATC / advisory: Tower ZZZ
Aircraft component: AC Generation
Component problem: Failed
Reporter organization: Air Carrier
Reporter function: Captain; Pilot Flying
Reporter qualification: Flight Crew Air Transport Pilot (ATP)
Second reporter function: Pilot Not Flying; First Officer
Anomaly: Aircraft Equipment Problem Critical
Detector: Automation Aircraft Other Automation; Person Flight Crew
When detected: In-flight
Result: Flight Crew Returned To Departure Airport
Contributing factors: Aircraft; Weather
Primary problem: Aircraft

Narrative: During takeoff R GEN OFF EICAS message illuminated. We requested to remain in the local airport area to run checklists. ATC granted our request and authorized a return to the runway. We completed the checklist with the generator being reset. I elected to return as the safest option as we were VFR; the runway was right there; we had previously operated the aircraft with no indication of a generator issue for over 3 hours; en-route weather called for thunderstorms. I believed the return to determine the cause of the failure before proceeding to be the safest choice.After takeoff clearance was received and during taxi onto the runway; the off flag in the standby gyro appeared. We requested to taxi clear of the runway. After stopping on the taxiway the flag receded. I called the Chief Pilot and requested clearance from ATC back to the runway for departure and completed an uneventful takeoff.


Second narrative: At takeoff R GEN OFF EICAS message illuminated. We then requested time to run the check lists and were granted time in the local area for them to be completed. We completed the check list and the generator was reset at that point. With all systems operating normally we requested and were given clearance to land.


Synopsis: Although it reset and operated normally; the flight crew of a B757-200 opted to return to their departure airport when their EICAS advised the right generator was off.
Date: 201411
Local time of day: 1201-1800
Location: ZZZ.Airport, US
Flight conditions: VMC
Weather elements / visibility: 10
Light: Daylight
Aircraft: Amateur/Home Built/Experimental
Operator: Personal
Operating under: Part 91
Flight plan: None
Mission: Personal
Flight phase: Cruise
Airspace: Class D ZZZ
ATC / advisory: Tower ZZZ
Aircraft component: Powerplant Fuel System
Component problem: Malfunctioning
Reporter organization: Personal
Reporter function: Single Pilot; Pilot Flying
Reporter qualification: Flight Crew Private
Anomaly: Aircraft Equipment Problem Critical; Deviation / Discrepancy - Procedural Published Material / Policy; Deviation / Discrepancy - Procedural Maintenance
Detector: Person Flight Crew
Result: Flight Crew Landed in Emergency Condition; Flight Crew Diverted; General Declared Emergency
Contributing factors: Human Factors; Aircraft
Primary problem: Aircraft

Narrative: Lost fuel flow and pressure causing turbine engine to flame out. Emergency landing performed without power restored. Attempted contact with Tower but unable due to simultaneous aircraft warnings overcoming radio operations. Discussed with the tower the nature of the emergency post flight the aircraft ground support team who helped recover the aircraft from the runway. Aircraft maintenance was performed prior to the next flight by qualified maintenance personnel by bleeding the fuel control unit. Small amounts of air entered the fuel system and correct measures have been taken as future prevention.




Synopsis: The pilot of a turbine powered experimental aircraft experienced a flame out and emergency landing due to air in the fuel control system.
Date: 202104
Local time of day: 0601-1200
Location: ZZZ.TRACON, US
Flight conditions: VMC
Light: Daylight
Aircraft: Cessna Stationair/Turbo Stationair 6
Operator: Personal
Operating under: Part 91
Flight plan: IFR
Mission: Personal
Flight phase: Cruise
Airspace: Class E ZZZ
ATC / advisory: TRACON ZZZ
Second aircraft: Any Unknown or Unlisted Aircraft Manufacturer
Reporter organization: Personal
Reporter function: Pilot Flying; Single Pilot
Reporter qualification: Flight Crew Air Transport Pilot (ATP); Flight Crew Flight Instructor; Flight Crew Instrument; Flight Crew Multiengine
Human factors: Communication Breakdown
Anomaly: ATC Issue All Types; Conflict NMAC
Detector: Person Flight Crew
When detected: In-flight
Result: Air Traffic Control Provided Assistance; Flight Crew Overcame Equipment Problem; Flight Crew Requested ATC Assistance / Clarification; Flight Crew Took Evasive Action
Contributing factors: Human Factors
Primary problem: Human Factors

Narrative: I was in cruise from ZZZ to ZZZ1 at 3;000 feet MSL with the autopilot engaged. Flight following with Approach was established and we were in communication. I saw an aircraft converging from the left and took evasive action to avoid a collision. The aircraft appeared slightly lower; so I chose to climb.I reported the near miss to Approach (frequency we were on). They responded claiming to have called us multiple times about the converging traffic. We did not receive any transmissions in-regards to traffic. The radios were silent.




Synopsis: Cessna 210 pilot reported executing an evasive maneuver resulting in an uneventful NMAC event during cruise.
Date: 201711
Local time of day: 1201-1800
Location: SNA.Airport, CA
Flight conditions: VMC
Light: Night
Aircraft: B737 Next Generation Undifferentiated
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Final Approach
Airspace: Class C SNA
ATC / advisory: Tower SNA
Second aircraft: Commercial Fixed Wing
Reporter organization: Air Carrier
Reporter function: Captain; Pilot Flying
Reporter qualification: Flight Crew Air Transport Pilot (ATP)
Human factors: Situational Awareness
Anomaly: ATC Issue All Types; Conflict Ground Conflict; Less Severe; Deviation / Discrepancy - Procedural Published Material / Policy
Detector: Person Flight Crew
When detected: In-flight
Result: Air Traffic Control Issued New Clearance; Flight Crew Executed Go Around / Missed Approach; Flight Crew Requested ATC Assistance / Clarification
Contributing factors: Human Factors; Procedure
Primary problem: Human Factors

Narrative: We have a winner for the most unsafe airport in the country. For the umpteenth time; the tower has cleared an aircraft on to the runway with an aircraft on short final. In this instance; an air carrier (Aircraft Y) cleared to line up and wait while we were on short final. The controller delayed takeoff clearance for the Aircraft Y due to a previous aircraft having not cleared the runway. The controller realizing his error; instructed the Aircraft Y to start his roll; and then taxi clear of the runway. The pilot responded that jet engines take a while to spool up and when the tower tried to make an excuse of 'this is a normal op'; Aircraft Y responded; 'we are not [other carrier].' Good for him. The tower received an 'alarm' and instructed us to go-around. Pretty normal for this airport. This is a chronic problem at SNA with aircraft being cleared to line up and wait with an aircraft on short final. Landing aircraft are constantly given delayed clearance to land.Do not allow aircraft to be cleared to line up and wait with an aircraft on short final.




Synopsis: B737 Captain reported they were issued go-around instructions due to an aircraft on the runway.