elihoole/asrs-aviation-reports huggingface dataset:
Date: 201701
Local time of day: 0601-1200
Location: APA.Airport, CO
Flight conditions: VMC
Weather elements / visibility: 10
Light: Daylight
Aircraft: Light Sport Aircraft
Operator: Personal
Operating under: Part 91
Flight plan: VFR
Mission: Personal
Flight phase: Takeoff / Launch
ATC / advisory: Tower APA
Reporter organization: Personal
Reporter function: Single Pilot; Pilot Flying
Reporter qualification: Flight Crew Sport / Recreational
Human factors: Troubleshooting
Anomaly: Ground Event / Encounter Loss Of Aircraft Control; Ground Excursion Runway; Inflight Event / Encounter Weather / Turbulence
Detector: Person Flight Crew
When detected: In-flight
Result: Aircraft Aircraft Damaged; Flight Crew Rejected Takeoff; General Evacuated
Contributing factors: Weather; Human Factors; Airport
Primary problem: Human Factors

Narrative: I was practicing touch and gos at Centennial Airport. I had done 5 touch and gos and decided to do a full stop taxi back. I was cleared to takeoff on Runway 17R and applied power and was tracking down the runway on centerline. The plane always needs a lot of right rudder to stay on centerline so I was using right rudder when the plane suddenly veered to the left. I tried to correct; but then the aircraft became unstable veering left and right and I went off the runway to the right of the runway into the grass and eventually rolled to a hard stop. Right after I went off the runway the traffic pattern was changed to use runway 35R. I noticed the current wind was now 310 at 9 knots. The wind had been coming from 110 per the previous ATIS. I believe the very fast; unstable change in wind direction and the fact I was still taking off on 17R per ATC had a detrimental effect on my takeoff roll.I have to wonder if the traffic pattern should have been changed to 35R prior to my attempt to takeoff. Several people at the scene; also pilots; definitely considered this as a potential cause for the incident.




Synopsis: Light sport aircraft pilot reported a runway excursion during takeoff roll.
Date: 202006
Local time of day: 0601-1200
Location: ZZZ.Airport, US
Flight conditions: VMC
Weather elements / visibility: 10
Light: Daylight
Aircraft: SR22
Operator: Personal
Operating under: Part 91
Flight plan: None
Mission: Personal
Flight phase: Landing
Airspace: Class D ZZZ
ATC / advisory: Tower ZZZ
Aircraft component: Nose Gear
Component problem: Failed
Reporter organization: Personal
Reporter function: Pilot Flying; Single Pilot
Reporter qualification: Flight Crew Instrument; Flight Crew Private
Human factors: Workload
Anomaly: Aircraft Equipment Problem Critical; Ground Event / Encounter Ground Strike - Aircraft
Detector: Person Flight Crew
When detected: Other Landing
Result: Aircraft Aircraft Damaged
Contributing factors: Aircraft
Primary problem: Aircraft

Narrative: Upon landing roll out I experienced a shimmy on from the front nose wheel; the rollout on the mains had already commenced when the nose came down normally. After a few seconds the nose wheel shimmied; I applied further back pressure but not noticeable effect; after approximately 3 seconds the nose wheel collapsed and the prop stuck the runway and I continued down the runway. I came to rest on the runway. During my approach everything was normal and stable. I was on approach with 82 kts. directly in line and stable with the runway. A wind call from the tower when I was cleared for the option was 140 degrees with 14 to 22 kts. I had a slight right cross wind. Approach and roll out was all normal. Landing was with full flaps which I put in during my Base leg. On final I had full flaps with 82 kts. on the PAPI approach.Post inspection showed the nose strut had completely failed.




Synopsis: SR22 pilot reported their nose gear collapsed while landing.
Date: 201505
Local time of day: 1801-2400
Location: ZZZ.Airport, US
Light: Night
Aircraft: EMB ERJ 170/175 ER/LR
Operator: Air Carrier
Operating under: Part 121
Flight phase: Parked
Reporter organization: Air Carrier
Reporter function: Technician
Reporter qualification: Maintenance Airframe; Maintenance Powerplant
Human factors: Communication Breakdown; Distraction
Anomaly: Deviation / Discrepancy - Procedural Maintenance; Deviation / Discrepancy - Procedural Published Material / Policy
Detector: Person Maintenance
When detected: Routine Inspection
Result: General None Reported / Taken
Contributing factors: Company Policy; Equipment / Tooling; Procedure; Human Factors
Primary problem: Company Policy

Narrative: At ZZZ Hangar; we only have one Ground Power Unit (GPU) for [ERJ]-170 work. We normally have two if not three 170s in the hangar every night. To provide power to the aircraft without the GPU; we must run the APU all night which wasn't too bad during the winter with the doors closed but has caused dangerous noise levels now that its summer and we must keep the doors open for cooling. So our current options are to wear hearing protection; but then you can't communicate with the other mechanics you are working with; which is also a hazard in itself (you would be unable to warn someone if they were in danger; etc.). Or to close the hangar doors which causes it to get extremely hot in the hangar. We have talked to management about this problem and they reported that it has been summited on the 2015 expense report; but that has been the answer since January when we first brought the coming problem to their attention. I also know that many have chosen not to wear hearing protection so that communication is possible; which will eventually lead to hearing loss. I feel it is sad that we have to choose immediate danger versus long term hearing loss because getting GPUs to the hanger is held up in red tape.




Synopsis: An Aircraft Maintenance Technician (AMT) describes his work environment where the lack of adequate Ground Power Units (GPUs) to supply electrical power to all their ERJ-170 aircraft requires the running of APU's all night in their hangar. As a result; due to the excessive noise levels; mechanics have chosen not to wear ear protection in order to communicate even though they face long term hearing loss.
Date: 202007
Local time of day: 1201-1800
Location: ZZZ.ARTCC, US
Light: Daylight
Aircraft: Citationjet (C525/C526) - CJ I / II / III / IV
Operating under: Part 135
Mission: Passenger
Flight phase: Cruise
Reporter function: Captain; Pilot Flying
Reporter qualification: Flight Crew Multiengine; Flight Crew Air Transport Pilot (ATP); Flight Crew Instrument
Anomaly: Aircraft Equipment Problem Critical; Deviation / Discrepancy - Procedural Published Material / Policy; Inflight Event / Encounter Fuel Issue
Detector: Person Flight Crew
When detected: In-flight
Result: Flight Crew Diverted
Contributing factors: Aircraft; Weather
Primary problem: Aircraft

Narrative: In cruise flight the left fuel filter bypass caution light came on. Going through the Emergency Checklist; the right fuel filter bypass light came on so I contacted ATC and asked for the closest large airport which was ZZZ. On descent to the airport somewhere around  15;000 ft.; both lights went out. I landed at ZZZ and had the fuel filters inspected. While that was being done I drove my passenger to city. Upon returning to ZZZ the inspection was complete with no contamination found so I flew the plane back to ZZZ1. The likely problem was ice with only a small amount of water found in the sump drains.




Synopsis: CE 525 pilot reported encountering fuel filter anomaly in flight.
Date: 201303
Local time of day: 1801-2400
Location: TEB.Airport, NJ
Aircraft: PA-60 600 Aerostar
Flight plan: IFR
Flight phase: Initial Climb
Airspace: Class B EWR; Class D TEB
ATC / advisory: TRACON N90
Reporter organization: Government
Reporter function: Departure; Approach
Reporter qualification: Air Traffic Control Fully Certified
Anomaly: Deviation - Track / Heading All Types; Deviation / Discrepancy - Procedural Clearance; Deviation / Discrepancy - Procedural Published Material / Policy
Detector: Person Air Traffic Control
Result: General None Reported / Taken
Contributing factors: Chart Or Publication; Human Factors; Procedure
Primary problem: Procedure

Narrative: An Aerostar departed IFR from TEB on the RUUDY4 departure. I heard TEB call in the speaker that the Aerostar was on the wrong transponder code. Since I was busy at the time with other traffic; the Aerostar did not check in until there was an opening. I advised him to reset his transponder. Subsequently; the FLM came to me and told me that they were going to look at the situation because it appeared that the Aerostar did not comply with the SID and there may have been an incident with the Newark final landing Runway 22L. I advised the pilot of the Aerostar of a possible pilot deviation and gave him the telephone number to call. While the onus is on the pilot to comply with the SID; this happens so often in the Newark Area that the problem may indeed be the SID.




Synopsis: N90 Controller described a probable pilot deviation involving an aircraft assigned the RUUDY4 SID off TEB; the reporter speculating that the SID itself might be the problem.
Date: 202201
Local time of day: 1201-1800
Location: ZZZ.Airport, US
Flight conditions: IMC
Weather elements / visibility: Wind
Light: Daylight
Aircraft: Small Transport
Operator: Air Taxi
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Landing
ATC / advisory: Tower ZZZ
Reporter organization: Fractional
Reporter function: Pilot Not Flying; First Officer
Reporter qualification: Flight Crew Commercial; Flight Crew Instrument; Flight Crew Multiengine
Second reporter function: Captain; Pilot Flying
Anomaly: Ground Event / Encounter Weather / Turbulence; Ground Event / Encounter Loss Of Aircraft Control; Ground Event / Encounter Object; Ground Excursion Runway
Detector: Person Flight Crew
When detected: In-flight
Result: General None Reported / Taken
Contributing factors: Human Factors; Weather
Primary problem: Weather

Narrative: Captain landed Runway XX and once he began to slow down; the aircraft began to slide off the runway due to possible unreported icing conditions for the runway. The aircraft had damage to the prop due to hitting multiple runway lights and ended up sliding off into a ditch from the ice.


Second narrative: Upon touching down on ZZZ; stepped on the brakes and the plane pulled to the left and exited the runway. It then went in the ditch and hit a few airport lights on the way.


Synopsis: Pilots reported losing control of the aircraft after landing and sliding off the runway.
Date: 201704
Local time of day: 1201-1800
Location: ZZZ.Airport, US
Flight conditions: VMC
Weather elements / visibility: 10
Light: Daylight
Aircraft: RV-12
Operator: FBO
Operating under: Part 91
Flight plan: None
Mission: Training
Flight phase: Climb
Airspace: Class D ZZZ
ATC / advisory: Tower ZZZ
Aircraft component: Engine
Component problem: Failed
Reporter organization: Personal
Reporter function: Instructor; Pilot Flying
Reporter qualification: Flight Crew Commercial; Flight Crew Multiengine; Flight Crew Instrument; Flight Crew Flight Instructor
Anomaly: Aircraft Equipment Problem Critical; Inflight Event / Encounter Other / Unknown
Detector: Person Flight Crew
When detected: In-flight
Result: Flight Crew Inflight Shutdown; Flight Crew Landed in Emergency Condition
Contributing factors: Aircraft
Primary problem: Aircraft

Narrative: Oil pressure dropped to zero shortly after takeoff. Airplane glided to land on highway after engine seized.




Synopsis: Vans RV-12 instructor pilot reported landing on a highway after the engine seized in flight.
Date: 201705
Local time of day: 1801-2400
Location: ZZZ.Airport, US
Light: Night
Aircraft: A319
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Final Approach
Airspace: Class B ZZZ
ATC / advisory: Tower ZZZ
Aircraft component: Air Data Computer
Component problem: Malfunctioning
Reporter organization: Air Carrier
Reporter function: Captain; Pilot Not Flying
Reporter qualification: Flight Crew Air Transport Pilot (ATP)
Human factors: Situational Awareness
Anomaly: Aircraft Equipment Problem Less Severe; Deviation - Speed All Types; Inflight Event / Encounter Unstabilized Approach
Detector: Person Flight Crew
When detected: In-flight
Result: Flight Crew Became Reoriented; Flight Crew Executed Go Around / Missed Approach
Contributing factors: Aircraft
Primary problem: Aircraft

Narrative: Aircraft had Auto Pilot #1 inoperative; FMGC #1 failure; #1 Nav Display failure; and previously placarded GPWS failure upon arrival. First Officer was Pilot Flying and during visual approach managed airspeed bug and airspeed appeared abnormally high based on configuration and descent rate. FO elected to go-around in accordance with procedures due to unstable parameters at 1;000 AGL. Tower gave non-standard go around instructions and combined with Pilot Monitoring being distracted with a malfunctioning nav display; we received a momentary flap overspeed warning at Flaps 1. During subsequent approach with speed in managed setting; we again observed the airspeed to be abnormally high and at one point the airspeed command bug appeared to be in the Flap Overspeed limit although the actual airspeed was within flap limits. FO disconnected auto pilot and auto throttles and was able to obtain stable approach parameters by 1;000 AGL and land safely. I entered all malfunctions in the logbook and called [Maintenance] to discuss the issues after parking at the gate.




Synopsis: A319 Captain reported executing a go-around after the approach became unstabilized following multiple system failures; including autopilot; FMGC; and nav display.
Date: 201204
Local time of day: 1201-1800
Location: ZZZ.Airport, US
Flight conditions: VMC
Light: Daylight
Aircraft: Amateur/Home Built/Experimental
Operator: Personal
Operating under: Part 91
Flight plan: None
Mission: Personal
Flight phase: Landing
ATC / advisory: CTAF ZZZ
Aircraft component: Main Gear
Component problem: Failed
Reporter organization: Personal
Reporter function: Pilot Flying
Reporter qualification: Flight Crew Air Transport Pilot (ATP); Flight Crew Flight Engineer; Flight Crew Multiengine; Flight Crew Instrument; Flight Crew Flight Instructor
Anomaly: Aircraft Equipment Problem Critical
Detector: Person Flight Crew
When detected: In-flight
Result: General Maintenance Action
Contributing factors: Aircraft
Primary problem: Aircraft

Narrative: While landing; the main gear collapsed on the runway. No one hurt in the experimental Glass Goose. Aircraft was moved off the runway a short time later.




Synopsis: A Glass Goose's main landing gear collapsed on landing.
Date: 201602
Local time of day: 1201-1800
Location: ZZZ.Airport, US
Light: Daylight
Aircraft: B737 Undifferentiated or Other Model
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Climb
Airspace: Class E ZZZ
ATC / advisory: TRACON ZZZ
Aircraft component: Turbine Engine
Component problem: Failed
Reporter organization: Air Carrier
Reporter function: Dispatcher
Reporter qualification: Dispatch Dispatcher
Anomaly: Aircraft Equipment Problem Critical
Detector: Person Flight Crew; Person Dispatch
When detected: In-flight
Result: Flight Crew Returned To Departure Airport; Flight Crew Returned To Gate; Flight Crew Landed in Emergency Condition; Flight Crew Inflight Shutdown
Contributing factors: Aircraft
Primary problem: Aircraft

Narrative: I noticed [a flight I was monitoring] had made what looked like a 180 degree turn and was descending. After waiting a few minutes and not wanting to disrupt the crew in case of an emergency; I elected to call the Tower and not ACARS the flight. I called the Tower; identified who I was; and asked if they were aware of any issues with [the flight]. The Controller informed me that they were informed it was an engine failure and the flight was returning to [departure airport]. I sent an ACARS to [the flight] letting them know that I was made aware of a possible emergency and would be monitoring ACARS and Ground freq if they needed anything. I notified [Operations] of the situation and at this point in time the issue was believed to be an engine failure but not confirmed. I notified [departure station] Ops that [the flight] was returning. While monitoring Ops Freq I was able to have voice contact with [the flight]. The crew notified me that while climbing thru 11;000 feet; the number 1 engine seized and they had performed the appropriate QRH checklist; [advised ATC] and were returning to [departure airport]. I stated that I would be monitoring ACARS and Freq if they needed anything additional; at this time I also notified [Operations] of the details.Flight landed without further incident; exited the runway was inspected by CFR; and taxied under its own power to the gate.In addition to monitoring ACARS and Company radio I followed the flight via [other means] to ensure positive flight following and operational control. I also maintained a timeline of the event that I incorporated into my report. The report was submitted within 2 hours of the emergency.




Synopsis: Air carrier Dispatcher reported he noticed a flight he was monitoring returned to the departure airport following an engine failure shortly after takeoff.
Date: 201510
Local time of day: 1801-2400
Location: EMT.Airport, CA
Flight conditions: VMC
Light: Dusk
Aircraft: Cessna 150
Operator: Personal
Operating under: Part 91
Flight plan: None
Mission: Training
Flight phase: Initial Approach
Airspace: Class D EMT
ATC / advisory: Tower EMT
Aircraft component: Intake Ice System
Component problem: Improperly Operated
Reporter organization: FBO
Reporter function: Instructor; Pilot Flying
Reporter qualification: Flight Crew Commercial; Flight Crew Flight Instructor; Flight Crew Instrument; Flight Crew Multiengine
Anomaly: Aircraft Equipment Problem Less Severe; Inflight Event / Encounter Weather / Turbulence
Detector: Person Flight Crew
When detected: In-flight
Result: Flight Crew Overcame Equipment Problem
Contributing factors: Weather; Aircraft
Primary problem: Aircraft

Narrative: I was providing primary flight instruction in a Cessna 150. We were inbound to the airport from the south; and were directed by Tower to enter left traffic for runway 19.At approximately 1400 feet MSL on the descent to traffic pattern altitude (1300 feet); I encountered a loss in RPM of approximately 500-600 RPM. At the time of the power loss; I had full power (2400 RPM) selected. Due to my low proximity to the ground; and the fact that runway 01 was almost directly in front of me; I elected to request a landing straight in to runway 01. I believed it to be carburetor icing; and I applied full carburetor heat. I knew that the carburetor on the O-200 engine on the Cessna 150 is very susceptible to carb icing; and the relative humidity on this day was also unusually high (approx 80%). The conditions to form carburetor icing were set.Following my landing on runway 01; I ran the engine up to full power; and the engine ran smooth; both with carb heat on and off. This confirmed by suspicion of carb ice. We taxied to the transient parking to shut down; and call the flight school to report it. We decided to go to the run up area and do another run up to check engine function. Engine ran fine; both with carb heat on and off. It was determined that the carb ice had been eliminated and the engine was running normally. I've encountered carburetor icing before. However; this is the first time I've encountered it at pattern altitude.Having noticed that the humidity level was higher than normal; I should have been more proactive with use of the carburetor heat on descent; even while operating the engine within the parameters where the POH says it is normally not required.




Synopsis: C150 Instructor Pilot reported encountering carburetor ice that resulted in a power loss in the pattern at EMT.
Date: 201302
Local time of day: 0001-0600
Location: IAH.Airport, TX
Aircraft: B737-900
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Flight phase: Landing
Airspace: Class B IAH
ATC / advisory: Tower IAH
Reporter organization: Government
Reporter qualification: Air Traffic Control Fully Certified
Anomaly: ATC Issue All Types
Detector: Person Air Traffic Control
Result: General None Reported / Taken
Contributing factors: Procedure
Primary problem: Procedure

Narrative: While fighting this scenario for around 5 years; and having it shoved down our throats with no regard for the safety of the flying public; I was left on Local South with departures and arrivals simultaneously. We have no authorized procedures for this flow except for Local West to work Runway 9 with the inbounds flying over his departing runways. Someone from higher up has decided that this is a safe operation and deemed it safe.




Synopsis: IAH Controller voiced concern regarding the current Local Control responsibility configurations; claiming the procedure in place for the past 5 years is unsafe.
Date: 201704
Local time of day: 1201-1800
Location: ZZZ.Airport, US
Flight conditions: Mixed
Light: Daylight
Aircraft: PC-12
Operator: Air Taxi
Operating under: Part 91
Flight plan: IFR
Mission: Ferry / Re-Positioning
Flight phase: Takeoff / Launch
ATC / advisory: Tower ZZZ
Aircraft component: Switch
Component problem: Improperly Operated
Reporter organization: Air Taxi
Reporter function: Captain
Reporter qualification: Flight Crew Flight Instructor; Flight Crew Multiengine; Flight Crew Instrument; Flight Crew Air Transport Pilot (ATP)
Human factors: Other / Unknown; Situational Awareness
Anomaly: Aircraft Equipment Problem Less Severe; Deviation / Discrepancy - Procedural Published Material / Policy
Detector: Person Flight Crew
When detected: In-flight
Result: Flight Crew Became Reoriented; Flight Crew Rejected Takeoff
Contributing factors: Aircraft; Human Factors
Primary problem: Human Factors

Narrative: We were cleared for takeoff on an IFR flight plan. When we began the takeoff roll I noticed that the battery was showing a discharge. We elected to abort the takeoff and check it out. It looks like we inadvertently had turned off generator 1 at some point. We reset it and ran the checklist. The battery was then charging properly and we elected to takeoff which was done without further issues.




Synopsis: PC12 Captain reported noting during the takeoff roll that the battery was discharging and elected to reject. Generator 1 was found to be turned off.