elihoole/asrs-aviation-reports huggingface dataset:
Date: 202006
Location: ZZZ.ARTCC, US
Flight conditions: VMC
Light: Daylight
Aircraft: Golden Eagle 421
Operator: Personal
Operating under: Part 91
Flight plan: IFR
Mission: Ferry / Re-Positioning
Flight phase: Cruise
Airspace: Class E ZZZ
ATC / advisory: Center ZZZ
Aircraft component: Horizontal Stabilizer Control
Component problem: Malfunctioning
Reporter organization: Personal
Reporter function: Captain; Pilot Flying
Reporter qualification: Flight Crew Air Transport Pilot (ATP); Flight Crew Instrument; Flight Crew Multiengine
Anomaly: Aircraft Equipment Problem Critical; Deviation - Altitude Excursion From Assigned Altitude; Deviation / Discrepancy - Procedural Clearance; Deviation / Discrepancy - Procedural Published Material / Policy
Detector: Person Flight Crew
When detected: In-flight
Result: Flight Crew FLC Overrode Automation; Flight Crew Overcame Equipment Problem; Flight Crew Regained Aircraft Control
Contributing factors: Aircraft
Primary problem: Aircraft

Narrative: Level in cruise flight the aircraft started to oscillate. I decide to disconnect the autopilot and hand fly. After disconnecting the autopilot at some point notice the pitch trim running away nose up. I was fumbling looking for the pitch trim circuit breaker and trying to fly the airplane. This was the first time I had flown this particular aircraft and the autopilot configuration was different from other 421's I currently fly. Eventually the control forces became too strong to maintain good control of the aircraft. I had entered a descent with the spoilers extended to maintain control and killed all avionics power in an effort to take power from pitch trim actuator. I had another pilot with me which was helping; at some point we got the aircraft trimmed up manually. Pulled the circuit breaker and then turned on avionics bus back on and established communications with ATC. Decided not to declare an emergency only because he had gained control and were in normal operations after that point. We were a few minutes away from ZZZ and had regained control of the aircraft. Made and uneventful landing ZZZ to ops-check the trim and autopilot system.




Synopsis: C421 Captain reported a runaway pitch trim system during cruise. Captain disconnected the autopilot; regained control of the aircraft and landed at the nearest suitable airport.
Date: 201509
Local time of day: 0601-1200
Location: ZZZ.Airport, US
Flight conditions: VMC
Weather elements / visibility: 10
Light: Daylight
Aircraft: Champion Citabria Undifferentiated
Operator: Personal
Operating under: Part 91
Flight plan: None
Mission: Training
Flight phase: Landing
ATC / advisory: Tower ZZZ
Reporter organization: Personal
Reporter function: Pilot Flying
Reporter qualification: Flight Crew Private
Human factors: Situational Awareness
Second reporter function: Pilot Not Flying; Instructor
Anomaly: Aircraft Equipment Problem Less Severe; Ground Event / Encounter Loss Of Aircraft Control; Ground Event / Encounter Object; Ground Excursion Runway
Detector: Person Flight Crew
When detected: In-flight
Result: Aircraft Aircraft Damaged
Contributing factors: Human Factors; Aircraft
Primary problem: Aircraft

Narrative: During tailwheel flight training with an instructor I completed 8 landings in a slight crosswind to a full stop. We noticed tailwheel shimmy during the landings. The last takeoff was a crosswind wheel takeoff departing to home base. For landing we established a glide slope appropriate for a 60 mph touchdown. After flare the aircraft touched down smoothly but initiated a drift to the left. Full right rudder had no effect on the diversion and as we slowed the aircraft veered further to the left into tall grass and then impacted a clump of bushes with the right wing damaging the leading edge of the right wing.After exiting the plane we noticed the right tailwheel spring was missing. Inspection of the grass runway showed touchdown on the centerline with the tailwheel dragging an approximately 4 inch wide [groove] in the grass all the way off the left side of the runway.Corrective actions: tailwheel shimmy should have been inspected by an A&P before we departed.


Second narrative: [Report Narrative Contained No Additional Information]


Synopsis: Aeronca 7AC instructor and student pilot reported loss of directional control on landing due at least in part to a missing tailwheel spring.
Date: 201509
Local time of day: 1201-1800
Location: ZZZZ.Airport, FO
Flight conditions: IMC
Light: Daylight
Aircraft: Regional Jet 700 ER/LR (CRJ700)
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Takeoff / Launch
ATC / advisory: Tower ZZZZ
Aircraft component: Air Data Computer
Component problem: Failed
Reporter organization: Air Carrier
Reporter function: Captain; Pilot Flying
Anomaly: Aircraft Equipment Problem Critical
Detector: Person Flight Crew
When detected: In-flight
Result: Flight Crew Diverted; Flight Crew Landed in Emergency Condition
Contributing factors: Aircraft; Procedure
Primary problem: Aircraft

Narrative: Flight was [delayed] due to maintenance. When a plane was finally established for [trip #]; I found that it had a LONG history of ADC 1 and 2 failures over the past few days.  I spent a LONG period of time on the phone discussing the issues I had with the aircraft and after a 3 way phone call with [Chief Pilot]; it was agreed that he shared my concerns; but it was signed off airworthy.  I accepted the flight.  After Take off; at approximately 5-600 feet; both ADCs failed and air data went blank on both PDCs.  We were able to re-acquire ADC1 (probably)...and returned...for normal landing in gusting winds.  It is my belief that continued behavior to reset systems with recency of failure problems and return them to line service will have a disastrous outcome.




Synopsis: A CRJ700 Captain expressed concerns about taking an aircraft with a long history of ADC failures. On takeoff; ADC 1 and 2 failed and the aircraft returned to departure airport.
Date: 202007
Local time of day: 1201-1800
Location: ZZZ.Airport, US
Flight conditions: VMC
Weather elements / visibility: 10
Light: Daylight
Aircraft: Small Aircraft; Low Wing; 1 Eng; Fixed Gear
Operator: Personal
Operating under: Part 91
Flight plan: VFR
Mission: Personal
Flight phase: Taxi
Airspace: Class D ZZZ
ATC / advisory: Tower ZZZ
Reporter organization: FBO
Reporter function: Pilot Flying; Single Pilot
Reporter qualification: Flight Crew Private
Human factors: Training / Qualification; Confusion; Situational Awareness
Anomaly: Deviation / Discrepancy - Procedural Clearance; Ground Incursion Runway
Detector: Person Air Traffic Control
When detected: Taxi
Result: Air Traffic Control Issued New Clearance; Flight Crew Returned To Clearance; Flight Crew Returned To Gate
Contributing factors: Environment - Non Weather Related; Human Factors
Primary problem: Human Factors

Narrative: I made several mistakes today when taxiing at ZZZ. First; I entered the taxiway from the flight school without contacting Ground. Where I trained; ZZZ2; you taxi to the ramp area to perform the run up then contact Ground for instructions to the runway. The flight school at ZZZ is immediately next to the ramp area; so I went there mistakenly without first contacting Ground. Secondly; when I was holding short of the runway I was given taxi instructions. I repeated back those instructions correctly; but I thought the Controller said cross after I repeated them; and I began crossing the runway. I was having a hard time hearing through the headset; but heard the Controller stating I was in the wrong and I immediately turned around and exited. I then taxied correctly to the other runway and back to the flight school.I'm embarrassed by these errors. I have been trying not to fly as much in rented airplanes due to COVID; due to the risk of having so many people in and out of them; and have lost some proficiency being a newly minted pilot. The last time I flew at ZZZ it was under heavy construction and we were routed another direction. I went that same direction and repeated the instructions back correctly to ATC but was writing notes and accidentally made a mistake of crossing. The load of not flying in a while and a new airport was a too much. Next time; I will take a CFI with me and also do ground training to ensure I know the airport to avoid any future mistakes; and will also try to fly more consistently in the future to maintain proficiency.I panicked after I made the error which caused me to not communicate correctly and efficiently. I'm fortunate I learned this lesson on the ground rather than in the air and will continuously train to ensure I maintain focus and calm in case an emergency situation ever does happen.I'm deeply sorry for any trouble I may have caused today. I will work to correct these mistakes to be a better pilot.




Synopsis: Pilot reported a runway incursion and cited lack of flying and unfamiliarity with the airport as contributing factors.
Date: 201202
Local time of day: 1801-2400
Location: PHL.Airport, PA
Aircraft: A320
Operator: Air Carrier
Operating under: Part 121
Mission: Passenger
Flight phase: Landing
ATC / advisory: Tower PHL
Second aircraft: B757 Undifferentiated or Other Model
Reporter organization: Air Carrier
Reporter function: Pilot Not Flying; First Officer
Human factors: Distraction; Situational Awareness
Second reporter function: Captain; Pilot Flying
Anomaly: Deviation / Discrepancy - Procedural Clearance; Deviation / Discrepancy - Procedural Published Material / Policy; Ground Incursion Taxiway; Inflight Event / Encounter Wake Vortex Encounter
Detector: Person Air Traffic Control; Person Flight Crew
When detected: Taxi
Result: General None Reported / Taken
Contributing factors: Environment - Non Weather Related; Human Factors
Primary problem: Human Factors

Narrative: On landing in PHL on [Runway] 27R we followed a B757 and experienced wake turbulence in the flare. This extended our touchdown in the touchdown zone. We were in reverse and slowing when ATC told us to exit and turn right onto Kilo to the gate. I advised them that we missed the right 90 turnoff and ATC advised us to hurry down to the next right turnoff which turned out to be K5. We kept our speed up on the runway and were slowing to try to hurry and exit at K5 for traffic on final. At this time we were given taxi instructions again. The clearance was right on Kilo and hold short of Tango. I answered as we were distracted by slowing in a hurry to turn off. I answered to turn right on Kilo like our first taxi instructions; but I am not sure if I acknowledged the hold short. As we taxied up to the parallel Kilo we saw [the other aircraft] landing and exiting on the high speed. We were short of the high speed and just slowing for [the other aircraft] to exit when ATC told us we were supposed to hold short of Tango. I looked to the left and saw the K4 taxi sign coming up. I knew we had to stop for [the other aircraft] to exit and I guess I thought that the high speed was Tango; not Kilo 4. [The other aircraft] was told to taxi to parking in front of us and then ATC advised us to taxi to parking. We taxied to the gate and we noticed I had forgotten the flaps in my after landing flow due to the hurried exit and answering ATC. The combination of the hurry to exit and answering ATC at the same time probably led to the confusion.


Second narrative: We encountered some wake turbulence (air was completely smooth until the last 50 FT). This did have [some] effect on the landing performance. We did land in the touchdown zone but further rather than closer to the approach end of the runway.


Synopsis: An A320 flight crew reported encountering wake turbulence just before touchdown at PHL behind a B757 that extended their touchdown point and caused some issues with ATC.
Date: 201705
Local time of day: 1801-2400
Location: ZZZ.Airport, US
Light: Night
Aircraft: A320
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Taxi
ATC / advisory: Ground ZZZ
Aircraft component: Air Conditioning and Pressurization Pack
Component problem: Malfunctioning
Reporter organization: Air Carrier
Reporter function: Captain; Pilot Flying
Reporter qualification: Flight Crew Air Transport Pilot (ATP)
Anomaly: Aircraft Equipment Problem Less Severe; Flight Deck / Cabin / Aircraft Event Illness / Injury; Flight Deck / Cabin / Aircraft Event Smoke / Fire / Fumes / Odor
Detector: Person Flight Crew
When detected: Taxi
Result: Flight Crew Requested ATC Assistance / Clarification; General Physical Injury / Incapacitation
Contributing factors: Aircraft
Primary problem: Aircraft

Narrative: During taxi-in to the ramp the FO and I noticed a mild burning smell with no cockpit indications of fire or overheat. Shortly thereafter; the D FA called the cockpit and notified us of the same burning smell but without the presence of any smoke. The burning odor began increasing in intensity as we pulled abeam the Deice pad. We notified the ramp of the burning odor and told the controller that we wanted to proceed directly to the gate and requested that the controller move aircraft out of our way as both taxiways were blocked by company aircraft awaiting gates. I called for the QRH smoke/fumes and we opened a cockpit window to evacuate the fumes. As we began the smoke/fumes checklist we received an ECAM for AIR PACK 1 OVHT this was quickly followed by AIR PACK 1 and 2 FAULTS. As the overheating pack was the most likely source of the fumes; we stopped the QRH and completed the ECAM. The fume odor; which smelled like burning oil or strong; acidic exhaust; began to dissipate. The D FA called the flight deck and reported that she; the C FA; and some passengers were feeling nauseous. I again notified ramp tower to move all aircraft out of our way so that we could get to a gate. I requested EMS to meet the aircraft. As the aircraft began to move; we began the smoke/fume removal checklist in the QRH.At this point; all checklists have been completed and I have very few options to remove the fumes from the cabin due to the inadequacies of the smoke/fumes removal checklist. The checklist is designed for an aircraft in flight and both of my packs have been shut down. My best and most reasonable option; the course of action I elected; was to get to proceed to the gate as quickly as possible.We were able to get to the gate quickly and the passengers were offloaded. The firefighters that met the aircraft ordered that all bags be left on the aircraft and assisted in expediting the offloading of the aircraft. I do not believe that any passengers sought medical attention. However; both the C and D flight attendants were taken to the hospital after evaluation by EMS.




Synopsis: A320 Captain reported an odor on taxi in to the gate and air pack overheat alerts. Two flight attendants were taken to the hospital.
Date: 201708
Local time of day: 1201-1800
Location: SMX.Airport, CA
Flight conditions: VMC
Light: Daylight
Aircraft: Amateur/Home Built/Experimental
Operator: Personal
Operating under: Part 91
Mission: Personal
Flight phase: Cruise
Airspace: Class G SBA
Reporter organization: Personal
Reporter function: Single Pilot
Reporter qualification: Flight Crew Private
Anomaly: Inflight Event / Encounter Object
Detector: Person Flight Crew
When detected: Other Post Flight
Result: Aircraft Aircraft Damaged
Contributing factors: Human Factors
Primary problem: Human Factors

Narrative: Made contact with at drone at 600-700 ft AGL. Speed 180 kts over Twitchell Reservoir 8 miles northeast of SMX.

Callback: The reporter stated his aircraft was struck by an object that was discovered on post-flight inspection to have punctured the aircraft's fuel tank. Although he had not seen anything in flight; the pilot initially suspected that the aircraft had been struck by a drone. He was able to determine during subsequent investigation that the fuel tank puncture was not caused by a drone collision.



Synopsis: GA pilot reported his aircraft was struck by an object while flying over Twitchell Reservoir at 600 AGL.
Date: 201403
Local time of day: 0601-1200
Location: CHD.Airport, AZ
Flight conditions: VMC
Light: Daylight
Aircraft: PA-28 Cherokee/Archer/Dakota/Pillan/Warrior
Operating under: Part 91
Flight phase: Initial Approach
Second aircraft: PA-44 Seminole/Turbo Seminole
Reporter function: Instructor; Pilot Flying
Reporter qualification: Flight Crew Commercial; Flight Crew Flight Instructor
Human factors: Communication Breakdown
Anomaly: Conflict NMAC
Detector: Person Flight Crew
When detected: In-flight
Result: General None Reported / Taken
Contributing factors: Airport; Human Factors
Primary problem: Human Factors

Narrative: We were climbing out from CHD and setting up an approach into CGZ. The traffic alerting system was not working at the time. While setting up the GPS I looked up and saw another aircraft (a PA-44) over head less than 500 feet. By the time of recognition the PA-44 had already passed. There was no communication between the two aircraft. Aircraft 2 was inbound to CHD and in a descent.




Synopsis: An instructor pilot aboard a PA-28 suffered an NMAC with an inbound PA-44 while departing CHD to the south.
Date: 201909
Local time of day: 1201-1800
Location: ZZZ.Airport, US
Flight conditions: VMC
Weather elements / visibility: 10
Light: Daylight
Aircraft: Skyhawk 172/Cutlass 172
Operator: Personal
Operating under: Part 91
Flight plan: None
Mission: Personal
Flight phase: Climb
Airspace: Class D ZZZ
ATC / advisory: Tower ZZZ
Second aircraft: PA-28 Cherokee/Archer/Dakota/Pillan/Warrior
Reporter organization: Personal
Reporter function: Pilot Flying; Single Pilot
Reporter qualification: Flight Crew Private
Human factors: Situational Awareness; Distraction; Confusion; Communication Breakdown; Training / Qualification
Anomaly: Conflict NMAC; Deviation / Discrepancy - Procedural Clearance; Deviation / Discrepancy - Procedural Published Material / Policy
Detector: Person Flight Crew
When detected: In-flight
Result: Flight Crew Took Evasive Action
Contributing factors: Human Factors
Primary problem: Human Factors

Narrative: ATC cleared me for takeoff; and at the end of the clearance indicated that I was following a Cherokee. I did not hear the part about following a Cherokee; and I did not read back that part of the takeoff clearance. I also did not see the airplane taking off before me; I assume because I was doing my final checks before takeoff. After taking off; I did frequently lower my nose to check for traffic but saw none. At 700 feet MSL; I made a left turn onto the crosswind leg as I continued climbing. At about 1000 feet MSL; I suddenly observed an aircraft above me at my 2 O'Clock flying towards my aircraft. I turned left; and the other aircraft turned left. I informed the tower and the tower indicated that the other aircraft was traffic that I was supposed to be following. At the time I believed the other aircraft to be either in distress and attempting an emergency landing or mistakenly approaching runway XX from the wrong direction (opposite runway). Upon reviewing the ATC transmissions; it became clear that I did not hear the transmission from ATC regarding the Cherokee and that the Cherokee was in the pattern before I was.There are several contributing factors to this incident in my opinion. The ATC's words were not very clear and may have contributed to me not hearing him. I still cannot make out exactly what he said. It sounds like '...you have to follow me up one Cherokee.' It would also have helped if he would have requested me to acknowledge the part of the clearance regarding following a Cherokee. I also believe that; given the relatively low amount of traffic at the airport at the time; greater spacing between takeoffs was warranted. Finally; I believe that I have to pay more attention to the aircraft departing as I make my final preparations for takeoff.




Synopsis: C172 pilot reported a near miss with a Cherokee in the traffic pattern.
Date: 201401
Local time of day: 1801-2400
Location: HOU.Airport, TX
Flight conditions: VMC
Light: Night
Aircraft: Commercial Fixed Wing
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Initial Approach
ATC / advisory: Tower HOU
Reporter organization: Air Carrier
Reporter function: Other / Unknown
Human factors: Confusion
Anomaly: Inflight Event / Encounter Other / Unknown
Detector: Person Flight Crew; Person Observer
When detected: In-flight
Result: Air Traffic Control Issued Advisory / Alert; Flight Crew Requested ATC Assistance / Clarification
Contributing factors: Airport
Primary problem: Airport

Narrative: While riding as flight deck observers on approach for Runway 12R in HOU; it appeared that there was an aircraft or vehicle on the assigned runway. The flying crew mentioned it and queried ATC who stated the runway was clear of traffic. It appears the airport is beginning to install LED in ground taxi guidance lights. The two strings are the turn off guidance for Taxiways M1 and M3 off of 12R. All of the lights are visible from the air while on approach. The terminating light; which is aligned with the runway centerline in both instances; creates the illusion of a vehicle or aircraft on the runway for aircraft on approach to 12R. Dallas has this same configuration off of 31L at D intersection yet the lights are only visible on the ground not during approach. Ensure correct installation of these lighting systems. If they are correctly installed then some type of shielding to ensure these lights are visible for ground operations only. Ensure the flight crews are aware of this illusion until it can be fixed. New LED turn off lights create appearance of aircraft or vehicle on runway.




Synopsis: A flight deck observer reports that he and the crew are distracted during approach to HOU by a bright light on the Runway 12R center line; which turns out to be the first light of the new in ground high speed taxiway lead off lights at both Taxiways M1 and M3.
Date: 201712
Local time of day: 1201-1800
Location: STP.Airport, MN
Flight conditions: VMC
Weather elements / visibility: 10
Light: Night
Aircraft: UAV - Unpiloted Aerial Vehicle
Operator: Personal
Operating under: Other 107
Mission: Personal
Flight phase: Cruise
Airspace: Class D STP
Reporter organization: Personal
Reporter function: Observer
Reporter qualification: Flight Crew Private
Human factors: Training / Qualification; Situational Awareness
Anomaly: Deviation / Discrepancy - Procedural Published Material / Policy; Deviation / Discrepancy - Procedural FAR
Detector: Person Observer
When detected: In-flight
Result: General None Reported / Taken
Contributing factors: Human Factors
Primary problem: Human Factors

Narrative: A small unmanned aerial systems operator was flying a multi rotor copter at night over non-participating people at [a park] in St. Paul. The operator did not maintain situational awareness and line of sight at all times as the air vehicle passed behind trees. The waterfowl in the area were disturbed by the presence of the sUAS and moved away from the sUAS. Como Lake serves as a visual reporting point for approach to St. Paul Downtown Airport. The operator was on the east side of the lake on a peninsula jutting out into the lake just inside the Class D airspace for St. Paul Downtown Airport. The sUAS was equipped with nonstandard aircraft lighting. A person with me stated they saw a second sUAS without any aircraft lighting. I was unable to see the second one. The lighted aircraft stayed over nonparticipating people for about a minute.




Synopsis: A ground observer reported a UAV was operated at night over a group of people in a public park.