elihoole/asrs-aviation-reports huggingface dataset:
Date: 201911
Local time of day: 1201-1800
Location: ZZZ.Airport, US
Flight conditions: VMC
Light: Daylight
Aircraft: PA-28R Cherokee Arrow All Series
Operator: Personal
Operating under: Part 91
Flight plan: VFR
Mission: Personal
Flight phase: Landing
Airspace: Class G ZZZ
ATC / advisory: UNICOM ZZZ
Aircraft component: Gear Extend/Retract Mechanism
Component problem: Malfunctioning
Reporter organization: Air Carrier
Reporter function: Single Pilot; Pilot Flying
Reporter qualification: Air Traffic Control Fully Certified; Flight Crew Private
Anomaly: Aircraft Equipment Problem Less Severe; Deviation / Discrepancy - Procedural Maintenance; Deviation / Discrepancy - Procedural Published Material / Policy
Detector: Person Flight Crew
When detected: In-flight
Result: Flight Crew Diverted; Flight Crew Landed in Emergency Condition; Flight Crew Overcame Equipment Problem; General Flight Cancelled / Delayed; General Maintenance Action
Contributing factors: Aircraft; Human Factors; Procedure
Primary problem: Aircraft

Narrative: I was taking a test flight after receiving my aircraft back from its annual inspection which was done at company at ZZZ. When I attempted to land my left main gear failed to deploy. After multiple attempts to deploy the gear and after the emergency release failed to work I attempted to contact the ZZZ UNICOM to request a visual inspection of my gear to see if it was deployed. I received no answer from the ZZZ UNICOM. I then requested priority handling on 121.5 and squawked 7700.  I was contacted by ZZZ1 who recommended that I divert to ZZZ2 where there was an ATC Tower. I continued to attempt to deploy the gear with the normal switch and also with the emergency release. While talking with ZZZ1 and formulating a plan the gear eventually deployed and gave me a solid green down light. I then landed the plane and called ATC in ZZZ1 as instructed to inform them that I was down safely. I believe that this could have been prevented by better quality work. My life was endangered by the poor quality of work being done by company.




Synopsis: PA28 pilot reported landing gear did not extend after annual inspection.
Date: 202106
Local time of day: 0001-0600
Location: ZZZ.Airport, US
Flight conditions: VMC
Light: Dusk
Aircraft: Queen Air 65/70 (Seminole)
Flight phase: Taxi
Aircraft component: Reciprocating Engine Assembly
Component problem: Failed
Reporter organization: Air Carrier
Reporter function: Captain; Pilot Flying; Single Pilot
Reporter qualification: Flight Crew Instrument; Flight Crew Multiengine; Flight Crew Commercial
Anomaly: Aircraft Equipment Problem Critical; Deviation / Discrepancy - Procedural Published Material / Policy; Flight Deck / Cabin / Aircraft Event Smoke / Fire / Fumes / Odor
Detector: Person Flight Crew
When detected: Aircraft In Service At Gate
Result: Aircraft Aircraft Damaged; Flight Crew Overcame Equipment Problem; General Evacuated
Contributing factors: Aircraft
Primary problem: Aircraft

Narrative: Started up the right engine and as I began to lean the mixture to stabilize the engine I heard a loud bang from the area of the right wing. As I looked out the right window of the cockpit I could see the wing had been severely damaged with flames coming out. I had not yet started the other engine and the airplane had not moved from its original position. After seeing the flames I immediately shut off the mixture to that engine and evacuated using the crew hatch. Once I was a safe distance away I call 911 to get the fire department and then notified supervisors.




Synopsis: Pilot reported evacuating the aircraft after the right engine failed and caught fire during start  up.
Date: 201206
Local time of day: 1801-2400
Location: ZZZ.Airport, US
Aircraft: SR22
Operator: Personal
Operating under: Part 91
Flight plan: IFR
Flight phase: Taxi
ATC / advisory: Tower ZZZ
Second aircraft: Bonanza 36
Reporter organization: Government
Reporter function: Local
Reporter qualification: Air Traffic Control Developmental
Human factors: Communication Breakdown; Situational Awareness
Anomaly: Conflict Ground Conflict; Critical; Ground Incursion Runway
Detector: Person Air Traffic Control
When detected: Taxi
Result: General None Reported / Taken
Contributing factors: Procedure; Airport; Chart Or Publication; Human Factors
Primary problem: Human Factors

Narrative: I was receiving OJT on Local Control 1 combined with Local Control 2. The field was VFR however the ceiling was overcast 1;200 FT with winds from east requiring a Runway 11 configuration. An SR22 had completed their landing roll after an IFR flight and exited Runway 11L at Taxiway H coming to a full and complete stop on Taxiway H behind the Runway 11R hold-short bars. An SR22 contacted Ground Control short of Runway 11R on Taxiway H. Ground Control coordinated with Local Control (myself) for a Runway 11R crossing at Taxiway H for the SR22. I issued Ground Control runway crossing authorization after a BE36 as Approach had issued the BE36's IFR departure release from Runway 11R. Ground Control instructed the SR22 to 'Hold short Runway 11R at H' and received a good read back from the pilot with a call sign. The BE36 was on takeoff roll; exceeding a speed for a safe 'cancel takeoff' instruction; at approximately 1/3 down Runway 11R 3;000 FT long. For an unknown reason; the SR22 commenced taxi crossing Runway 11R hold-short bars on Taxiway H and continued to taxi southbound toward Taxiway A. The BE36 passed over the SR22 by an estimated 100 FT or less. This location (Runway 29L/11R at Taxiway H) is an ongoing runway incursion hot spot.




Synopsis: Local Controller described a conflict event between an unauthorized runway crossing by an aircraft exiting Runway 11L via Taxiway H and departing aircraft from Runway 11R.
Date: 201812
Local time of day: 1201-1800
Location: ROA.Airport, VA
Flight conditions: VMC
Light: Daylight
Aircraft: Medium Transport; Low Wing; 2 Turbojet Eng
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Initial Approach; Descent
Airspace: Class C ROA
ATC / advisory: Tower ROA
Reporter organization: Air Carrier
Reporter function: First Officer; Pilot Flying
Reporter qualification: Flight Crew Multiengine; Flight Crew Air Transport Pilot (ATP); Flight Crew Instrument
Human factors: Situational Awareness
Anomaly: Inflight Event / Encounter CFTT / CFIT
Detector: Automation Aircraft Terrain Warning; Person Flight Crew
When detected: In-flight
Result: Flight Crew FLC complied w / Automation / Advisory
Contributing factors: Environment - Non Weather Related
Primary problem: Environment - Non Weather Related

Narrative: We were in VMC descending into ROA for the RNAV Runway 24 Approach. We were cleared to descend to 4;000 feet and were receiving radar vectors from Approach Control. We called the field in sight and approach cleared us for the visual to Runway 24. Just as the autopilot was about to level off at 4;000 feet we received the EGPWS warning for terrain and the subsequent pull up. I responded by disconnecting the autopilot and adding power to climb. After climbing to 4;400 feet the warning subsided and we continued the visual approach with no further issues. I responded to the pull up warning by disconnecting the autopilot and initiating a climb. The warning subsided; and as a crew we determined visually that we were clear of the mountainous terrain.




Synopsis: Air carrier First Officer reported a GPWS event during approach to ROA while in visual conditions.
Date: 201402
Local time of day: 1201-1800
Location: PSN.Airport, TX
Weather elements / visibility: Icing; Rain; Snow
Light: Daylight
Aircraft: Small Aircraft; Low Wing; 1 Eng; Retractable Gear
Operator: Corporate
Operating under: Part 91
Flight plan: IFR
Mission: Personal
Flight phase: Landing
ATC / advisory: CTAF PSN
Reporter organization: Corporate
Reporter function: Pilot Flying; Single Pilot
Reporter qualification: Flight Crew Air Transport Pilot (ATP); Flight Crew Flight Instructor; Flight Crew Multiengine; Flight Crew Instrument
Anomaly: No Specific Anomaly Occurred All Types
Detector: Person Flight Crew
When detected: Taxi
Result: General None Reported / Taken
Contributing factors: Airport
Primary problem: Airport

Narrative: This is not a specific event; rather an ongoing problem. The main runway (18/36) at PSN has not had the markings repainted in many years. As a result; they are virtually invisible in low light and low visibility conditions. The airport is home to daily commercial (cargo) and General Aviation activity. Repeated attempts to convince the airport authorities to repaint have gone unheeded.




Synopsis: A pilot reported PSN Runway 18/36 markings have not been repainted in many years and have become virtually invisible in low light; low visibility conditions.
Date: 202102
Local time of day: 0601-1200
Location: ZZZ.Airport, US
Flight conditions: VMC
Weather elements / visibility: 10
Light: Daylight
Aircraft: DJI Mavic 2 Zoom
Operating under: Part 107
Flight plan: None
Flight phase: Takeoff / Launch
Reporter organization: Commercial Operator (UAS)
Reporter function: Person Manipulating Controls (UAS); Remote PIC (UAS)
Reporter qualification: Flight Crew Commercial
Anomaly: Airspace Violation All Types; Deviation / Discrepancy - Procedural Unauthorized Flight Operations (UAS)
Detector: Person UAS Crew
Result: General None Reported / Taken
Contributing factors: Human Factors
Primary problem: Human Factors

Narrative: In the course of a [mission type X] using a DJI magic Zoom; I got confused with the workflow of Kittyhawk and believed it created a LAANC authorization as part of the mission set up. This was an incorrect assumption and I realized after the flight that the program did not automatically create the LAANC authorization as I expected. In the future; I will always verify and have a valid LAANC authorization code for the location of my flight prior to beginning operation of my drone.




Synopsis: DJI Mavic 2 Zoom drone pilot reported flying a mission without having the proper LAANC authorization.
Date: 201704
Local time of day: 1201-1800
Location: ZZZ.Airport, US
Flight conditions: VMC
Light: Daylight
Aircraft: Beechjet 400
Operating under: Part 91
Flight plan: IFR
Flight phase: Climb
Airspace: Class A ZZZ
ATC / advisory: Center ZZZ
Aircraft component: Turbine Engine
Component problem: Failed
Reporter function: Captain; Pilot Flying
Reporter qualification: Flight Crew Air Transport Pilot (ATP)
Anomaly: Aircraft Equipment Problem Less Severe
Detector: Person Flight Crew
When detected: In-flight
Result: Flight Crew Diverted; Flight Crew FLC complied w / Automation / Advisory; Flight Crew Landed in Emergency Condition
Contributing factors: Aircraft
Primary problem: Aircraft

Narrative: [I] was PIC and Pilot Flying; First Officer (FO) was SIC and Pilot Not Flying. Normal start; and taxi from ZZZ. After we departed we received vectors to our first fix. Normal climb through 10;000 feet. Once we past 18;000 feet; the airplane yawed to the left; I took control and at the same time I looked at my engine gauges from top to bottom; I saw my LEFT N1; LEFT ITT; LEFT fuel flow and LEFT N2 roll back. My LEFT oil pressure gauge went to zero but oil temp stayed in the green. Like I said I took control of the airplane. I told the FO to take out the emergency check list and to [advise ATC]. We requested a lower altitude and vectors to the nearest airport. ATC told us ZZZ1 was VFR and gave us vectors to go there. We followed the engine failure and shut down checklist; after that we did the single engine approach and landing checklist. Normal landing on Runway XYL and normal taxi in. Then a normal shut down.




Synopsis: BE40 Captain reported an engine failure on climbout and subsequent diversion.
Date: 201208
Local time of day: 1801-2400
Location: ZZZ.ARTCC, US
Aircraft: B737-800
Operator: Air Carrier
Operating under: Part 121
Flight phase: Cruise
Airspace: Class A ZZZ
ATC / advisory: Center ZZZ
Aircraft component: Pressurization System
Component problem: Malfunctioning
Reporter organization: Air Carrier
Reporter function: Captain; Pilot Flying
Reporter qualification: Flight Crew Air Transport Pilot (ATP)
Anomaly: Aircraft Equipment Problem Critical
Detector: Person Flight Crew
When detected: In-flight
Result: Flight Crew Returned To Departure Airport; General Declared Emergency; General Maintenance Action
Contributing factors: Aircraft
Primary problem: Aircraft

Narrative: Departed with one A/C pack inoperative; after a few minutes at cruise the 'Pressurization Flow' light came on and the cabin was showing a slow (300 FPM) climb. After QRH procedures complied with still unable to stop the cabin climb. With outflow valve closed and manually locked; airfoil switches off; and pneumatic crossfeeds closed the cabin continued to climb.  We were at FL240 and descended to FL180 before the cabin climb rate slowed down. I knew we cannot make it to [destination] at FL180 so we elected to return to [departure airport]. We declared an emergency for the overweight landing.




Synopsis: B737-800 Captain reported pressurization problems after departure with one pack deferred. Flight returned to departure airport.
Date: 201211
Local time of day: 0001-0600
Location: ZMP.ARTCC, MN
Aircraft: B737-800
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Cruise
Airspace: Class A ZMP
ATC / advisory: Center ZMP
Second aircraft: A380
Reporter organization: Air Carrier
Reporter function: Captain; Pilot Not Flying
Reporter qualification: Flight Crew Air Transport Pilot (ATP)
Human factors: Situational Awareness
Anomaly: Inflight Event / Encounter Wake Vortex Encounter
Detector: Person Flight Crew
When detected: In-flight
Result: General None Reported / Taken
Contributing factors: Procedure
Primary problem: Procedure

Narrative: While at cruise with the seat belt sign off; we encountered a double bump of heavy-moderate turbulence. I concluded that it was probably wake turbulence from an aircraft that had crossed sometime above us. After ensuring that the cabin crew and passengers were all okay; I called ATC (I believe it was MSP Center) to inquire what type of aircraft that had crossed above us. She told us that it was an A380 and it had crossed our path 6 minutes before. The First Officer stated that it was only 1;000 FT above us; but I can't swear to the actual crossing altitude as we had several aircraft crossing along our route at that time. It's my understanding that separation from A380 aircraft is supposed to be 2;000 FT and 5 minutes. Perhaps this should be reconsidered as the turbulence we encountered could have caused injuries to anyone up in the aisle or galley. We were fortunate that no one was injured. The incident happened at night so we were completely unaware that we were in the vicinity of an A380 and were not expecting any turbulence wake-related or otherwise. We were flying a B-737-800.




Synopsis: A B737-800 pilot experienced wake vortices from an A380 while en route.
Date: 202008
Local time of day: 1201-1800
Location: ZZZ.Airport, US
Flight conditions: IMC
Light: Daylight
Aircraft: Commercial Fixed Wing
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Descent
Airspace: Class B ZZZ
ATC / advisory: TRACON ZZZ
Reporter organization: Air Carrier
Reporter function: Captain; Pilot Not Flying
Reporter qualification: Flight Crew Air Transport Pilot (ATP); Flight Crew Instrument; Flight Crew Multiengine
Human factors: Situational Awareness
Anomaly: Deviation - Altitude Crossing Restriction Not Met; Deviation - Altitude Undershoot; Deviation / Discrepancy - Procedural Clearance; Deviation / Discrepancy - Procedural Published Material / Policy
Detector: Person Flight Crew
When detected: In-flight
Result: General None Reported / Taken
Contributing factors: Environment - Non Weather Related; Human Factors
Primary problem: Human Factors

Narrative: While descending on the ZZZZZ2 arrival and approaching the ZZZZZ intersection; PM was distracted by radio calls and clearances. Upon reaching ZZZZZ intersection PM identified that we were approximately 500 feet high crossing the way point. PF corrected by increasing rate of descent to reach 8;000 feet. Around the time that we were leveling off at 8;000 feet received clearance to 7;000 feet. While descending we identified that conditions had changed and that a full ILS approach brief would be warranted. Approaching 7;000 feet; ATC cleared up to descend to 4;000 feet and it was not noticed that the aircraft had captured the altitude after 4;000 feet was set. ATC later gave a clearance to descend to 4;000 feet and we identified our error and quickly initiated our descent.Both the PF and PM have been doing little flying over the last several months due to the COVID 19 pandemic. As such it had been some time since last arriving in ZZZ. As well as the short duration of flight and the changing weather conditions led to being behind the aircraft.Making more time by asking ATC for vectors in order to brief the approach. Briefing the full approach even when not expecting IMC conditions.




Synopsis: Air carrier Captain reported not making a crossing restriction during arrival and cited lack of flying as a contributing factor.
Date: 201811
Local time of day: 1201-1800
Location: ZZZ.Airport, US
Flight conditions: VMC
Weather elements / visibility: Rain; 10
Light: Daylight
Aircraft: Robinson R44
Operator: Air Taxi
Operating under: Part 135
Flight plan: VFR
Mission: Passenger
Flight phase: Cruise
Airspace: Class G ZZZ
ATC / advisory: Tower ZZZ
Aircraft component: Engine
Component problem: Malfunctioning
Reporter organization: Air Taxi
Reporter function: Pilot Flying; Single Pilot
Reporter qualification: Flight Crew Rotorcraft; Flight Crew Commercial; Flight Crew Flight Instructor
Human factors: Time Pressure
Anomaly: Aircraft Equipment Problem Critical
Detector: Person Flight Crew
When detected: In-flight
Result: Flight Crew Landed in Emergency Condition; Flight Crew Overcame Equipment Problem; Flight Crew Diverted
Contributing factors: Aircraft
Primary problem: Aircraft

Narrative: I departed the South Ramp on a [published] departure for a tour in a Robinson R44. Approx. 1-2 minutes after departure; I experienced what I believed to be a minor torque kick. There was no significant yaw or secondary indications; so I decided to continue the flight. I monitored the aircraft closely and all was normal until approximately 30 minutes into the flight. I slowed down to approximately 20 knots to ensure my passengers got a good photo opportunity.At this point; I made a radio call advising I was exiting [the scenic point]. As I completed the orbit at 2;000 feet; I experienced significant yawing of the aircraft to both sides; vibration and my RPM warning light and horn came on. I immediately entered auto-rotation and made a [priority request] radio call. I turned easterly and auto rotated down the valley searching for a safe landing spot. I noted my engine was still running; at 1;200 feet MSL; I increased throttle to gauge my power levels and noted my engine RPM and rotor RPM needles rejoined indicating full power. This enabled me to reach a grass landing spot. I made a normal approach to the spot; set down with full power and shut down as normal. My colleague was flying [another aircraft] a short distance behind me and had acknowledged my [radio] call. As I touched down; I advised her via radio that myself and the passengers were safely on the ground and requested she contact our Operations Manager. After I shutdown the engine; stopped the blades and checked there was no fire hazard; I confirmed both my passengers were OK and rang my boss (the Operator) to advise her of the situation. She told me to stay where we were and she would be arriving shortly. She arrived approx. 40 minutes later and I flew the passengers back to base in that aircraft. My boss remained to wait for the mechanic to arrive.




Synopsis: R44 pilot reported an engine malfunction resulted in an off-field landing.
Date: 201209
Local time of day: 1201-1800
Location: ZZZ.Airport, US
Flight conditions: IMC
Weather elements / visibility: Rain
Light: Daylight
Aircraft: EMB ERJ 145 ER/LR
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Flight phase: Climb
ATC / advisory: TRACON ZZZ
Aircraft component: Gear Extend/Retract Mechanism
Component problem: Malfunctioning
Reporter organization: Air Carrier
Reporter function: First Officer; Pilot Not Flying
Human factors: Human-Machine Interface; Troubleshooting
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; General Declared Emergency; General Maintenance Action
Contributing factors: Aircraft
Primary problem: Aircraft

Narrative: Upon liftoff we went to retract the landing gear after takeoff; and heard a clunk sound and then proceeded to look at the landing gear indicators. The left main and nose wheel indicator acted as normal by going from 'Green Down' to an amber 'Transient' to a grey 'Up' position; meanwhile the right main went from 'Green Up' directly to a grey 'Up' indication. We decided to recycle the gear to determine if it was a false indication or if it would happen again. The indication happened exactly as before so we then proceeded to contact maintenance via ARINC.Upon speaking with Maintenance they said that it would be better to divert to a Maintenance facility for further inspection. We organized with Dispatch to divert since it was the closest at the time with Maintenance. We then briefed we would do a low approach to have the Tower confirm three gears in the down position and then proceed to stay in pattern for a full stop landing. And determined at this time was not needed to declare the emergency; but as precaution to inform emergency equipment be standing by upon our landing. We briefed the approach at 22 degrees flaps and then the execution of the go-around for the pattern at normal profile MINUS retracting the confirmed gear in the down position. Upon execution of go-around and retracting the flaps to a departure setting of 9 degrees; the flaps then failed into 11 degrees. We performed the QRH action items including preparing for a reduced flap landing. At this point we declare an emergency got priority to the runway and made a successful/uneventful landing.Threat was an unusual landing gear indicator; lead to diversion. Upon executing a safety inspection by the tower by doing a low approach; the flaps locking in 11 degrees became an emergency situation. Executed reduced flap landing.




Synopsis: After receiving abnormal gear light indications after takeoff the flight crew of an EMB-145 opted to divert to a nearby maintenance facility where; after performing a low pass for ATC observation purposes; the flaps failed to respond. An emergency was declared and they landed uneventfully.