elihoole/asrs-aviation-reports huggingface dataset:
Date: 201908
Local time of day: 0601-1200
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: VFR
Mission: Personal
Flight phase: Cruise
Aircraft component: Engine
Component problem: Malfunctioning
Reporter organization: Personal
Reporter function: Pilot Flying; Single Pilot
Reporter qualification: Flight Crew Private
Human factors: Troubleshooting; Workload
Anomaly: Aircraft Equipment Problem Critical; Deviation / Discrepancy - Procedural FAR; Deviation / Discrepancy - Procedural Published Material / Policy
Detector: Person Flight Crew
When detected: In-flight
Result: Air Traffic Control Provided Assistance; Flight Crew Requested ATC Assistance / Clarification; Flight Crew Landed in Emergency Condition
Contributing factors: Aircraft
Primary problem: Aircraft

Narrative: Flying to see a friend and lost power at 9;500 feet. Intermittent power but not enough to maintain altitude. Ran through my checklist with no luck and requested priority handling with [ATC]. They gave me vectors to ZZZ which Copilot had already identified and we did a 16 nm glide and descent and made the airport. Kept fiddling with fuel and lean combos and had time to take down a phone number for ATC so I could call after landing then switched to the Unicom for ZZZ. Double checked the weather and made the airport with about 3;000 feet of altitude to spare. Spiral descent to downwind and landed without incident. There was a policeman waiting when we landed and mechanics on duty.I had 11 hours on the plane since a 100 hour inspection. The ignition harness had been replaced during that inspection at the same time a new electronic starter was installed. It was apparent to the mechanic at ZZZ that the spark plugs had not been removed; cleaned or replaced. One had ceased firing and was visibly oval shaped from wear and the other had corroded through the ceramic liner and was not firing properly and all 12 had not been cleaned. There was visible rust on the exterior of 2 of the other 10 (I'm not a mechanic but I read the 100 hour checklist to mandate a close look of any rusty parts). If the spark plugs were not removed; then they didn't do a compression test. The Cessna 100 hour checklist calls for a compression test and an inspection of all engine systems.According to [Mechanic:]Replaced ignition switch with new ACS A-510-2K with matching door locks.Replaced elevator tips with new SA-0532001-94 & SA-0532001-100Replaced aileron rod ends with (4) new S1819-3Replace landing/taxi light switch with new 0713035-1Replaced air filter with new BA6108Performed an Annual Inspection as described under Title 14 CFR 43 Appendix D and was determined to be in an airworthy condition at this time.Please contact for further information.




Synopsis: C172 pilot reported an engine failure and forced landing due to improper maintenance.
Date: 201201
Local time of day: 1801-2400
Location: ZZZ.Airport, US
Aircraft: B757 Undifferentiated or Other Model
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Parked
Aircraft component: Fuel Booster Pump
Component problem: Failed
Reporter organization: Air Carrier
Reporter function: Pilot Flying; Captain
Reporter qualification: Flight Crew Air Transport Pilot (ATP)
Human factors: Confusion; Troubleshooting
Anomaly: Deviation / Discrepancy - Procedural Published Material / Policy; Deviation / Discrepancy - Procedural MEL / CDL; Inflight Event / Encounter Fuel Issue
Detector: Person Other Person
When detected: Other After the fact
Result: General None Reported / Taken
Contributing factors: Manuals; Procedure; Aircraft; Human Factors
Primary problem: Ambiguous

Narrative: I was just notified of an inadvertent error in interpretation of a Maintenance Carry Over (MCO) item - an inoperative Right Aft Boost pump - by our Dispatcher; which we failed to catch as well. We were not 'rushed' during our preflight and took the time to thoroughly review the item. My copilot read the MEL line for line. Our only question was the minimum fuel value statement under the procedures section. Since it stated 'minimum fuel value' of 12;200 LBS and not specifically [individual] 'tank value' we did not challenge our dispatch fuel of 17;000 LBS for our short 50 minute flight. The Dispatcher also read the requirement to be total versus tank value. In hindsight; I should have called the Dispatcher to make sure that we were both on the 'same page' with the MEL interpretation.I consider myself a very meticulous Captain who asks questions and is not afraid to call for assistance when needed. However; in this case I was incorrect in my assumption that the flight plan was correct. In reviewing the situation; my First Officer and I believe the MEL should be updated with more specific wording. In the future I will be more vigilant and ask more questions of Dispatchers and Maintenance; especially when fuel totals are involved.I believe the MEL should be rewritten so that there is 'no doubt' about how much fuel should be on board. I was surprised to read the 767-300 procedures clearly stated what the minimum value was for takeoff and landing for the 'affected tank'. The 757 procedures simply stated 'minimum fuel values' next to these numbers. Had the 757 MEL mirrored the 767-300; I believe we would have caught the Dispatcher's error. In addition; I recommend that MEL also state the required minimum total fuel on board. Finally; the MEL should state the 'total unusable fuel' value of 3;000 LBS as well.




Synopsis: Both the B757 flight crew and their Dispatcher misinterpreted the minimum amount of fuel required in the affected tank when dispatched with the Aft Boost Pump inoperative.
Date: 201708
Local time of day: 0601-1200
Location: ZZZ.Airport, US
Flight conditions: VMC
Light: Daylight
Aircraft: B737 Undifferentiated or Other Model
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Takeoff / Launch
ATC / advisory: Tower ZZZ
Aircraft component: Main Gear Tire
Component problem: Failed
Reporter organization: Air Carrier
Reporter function: Captain
Reporter qualification: Flight Crew Air Transport Pilot (ATP)
Human factors: Communication Breakdown
Second reporter function: First Officer
Anomaly: Aircraft Equipment Problem Less Severe; Deviation / Discrepancy - Procedural Published Material / Policy
Detector: Person Air Traffic Control
When detected: In-flight
Contributing factors: Human Factors; Procedure
Primary problem: Human Factors

Narrative: We took off and blew number 3 main tire. We had no idea what happened. Tower was told that there was FOD on the runway from aircraft behind us that took off. Less than 60 minutes after we took off [company] maintenance sent a letter to mechanics [to our destination] to inspect the aircraft upon arrival. We were never told of this problem. When we landed we did a normal landing and taxi to the gate. When we arrived we were met by the gate agent when she informed us what had happened. That was the first we heard of it. The FO (First Officer) and I went outside and saw the damage. Several dents under the wing and an exploded tire. The aircraft was taken out of service and the return flight cancelled. Needless to say I am not happy with [the company] handling this situation. We should have been notified so we could properly prepare for a safe landing. We could have made plans for flaps 40 landing with minimal braking. I would have also had fire trucks standing by in case the other tire blew on landing. The communication between ATC should have found its way to us. I called the [duty manager]; Dispatcher and [maintenance control] after we found all this out and not one person knew anything about our blown tire. This could have been a really bad situation on landing that could have been avoided with proper planning. I believe we dodged a bullet on this event.


Second narrative: [Report narrative contained no additional information.]


Synopsis: B737 Crew reported being informed after a landing that aircraft blew a tire on take off. Crew was upset for not being advised prior to landing.
Date: 202008
Local time of day: 0601-1200
Location: ZZZ.ARTCC, US
Flight conditions: VMC
Aircraft: Commercial Fixed Wing
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Climb
Reporter organization: Air Carrier
Reporter function: Pilot Not Flying; First Officer
Reporter qualification: Flight Crew Air Transport Pilot (ATP); Flight Crew Instrument; Flight Crew Multiengine
Human factors: Human-Machine Interface; Time Pressure
Anomaly: Deviation - Track / Heading All Types; Deviation / Discrepancy - Procedural Clearance; Deviation / Discrepancy - Procedural Published Material / Policy
Detector: Person Air Traffic Control; Person Flight Crew
When detected: In-flight
Result: Air Traffic Control Issued New Clearance
Contributing factors: Environment - Non Weather Related; Human Factors
Primary problem: Human Factors

Narrative: Before we were able walk onboard our plane we had to go to gate XX for a temperature check.Once on board our FA said our crew meals were not boarded and airport operations informed us catering was shut down.  CA went to procure 2 sandwiches in the terminal while I set up the cockpit.  I rushed through the cockpit setup as we arrived later than planned to the plane. Our clearance was ZZZZZX.ZZZ then as filed. While loading the route in the FMC the ZZZZZX departure was loaded without selecting the ZZZ [VOR] transition.  Upon returning from the preflight inspection 15 minutes before scheduled departure time; I proceeded to verify the route.  I did not catch the error that the ZZZZZX departure was loaded without the ZZZ transition.On the before takeoff checklist; I missed another opportunity to catch the error when I read FMC ...ZZZZZX ZZZZZ.  The box should have been loaded ZZZZZX departure ZZZ transition. After takeoff during initial climb; I noticed the airplane symbol was off course on the Jeppesen ZZZZZX.ZZZ SID. I brought this to the CA's attention; but before we could investigate further ATC called to say we were off course.  We flew ZZZZZ direct ZZZ rather than the ZZZZZ.ZZZ; which was our clearance.ATC cleared us direct ZZZ.  The rest of the flight was uneventful.




Synopsis: Air carrier First Officer reported programming the FMC incorrectly for the SID; which resulted in a track deviation. Reporter noted several delays that contributed to rushing through cockpit set up.
Date: 201912
Local time of day: 0001-0600
Location: ZZZ.Airport, US
Flight conditions: VMC
Light: Daylight
Aircraft: UAV - Unpiloted Aerial Vehicle
Operator: Government
Operating under: Part 91
Flight plan: VFR
Mission: Training
Flight phase: Cruise
Airspace: Class G ZZZ
ATC / advisory: Tower ZZZ
Aircraft component: Electrical Power
Component problem: Failed
Reporter organization: Government
Reporter function: Pilot Flying; Single Pilot
Reporter qualification: Flight Crew Flight Instructor; Flight Crew Instrument; Flight Crew Multiengine; Flight Crew Commercial
Human factors: Troubleshooting
Anomaly: Aircraft Equipment Problem Critical; Deviation / Discrepancy - Procedural Published Material / Policy; Inflight Event / Encounter Loss Of Aircraft Control
Detector: Person Flight Crew
When detected: In-flight
Result: Aircraft Aircraft Damaged
Contributing factors: Aircraft
Primary problem: Aircraft

Narrative: UAV was flown on circular orbit that was within the fenced in area of ZZZ at 1;400 [feet] MSL. Up to the point of the accident; the flight lasted for about 45 minutes (approximate) with no system anomalies noted. Location of the GCS was on the center infield at ZZZ. The operation was within line of sight involving the remote pilot at the GCS; a sensor operator sitting next to the remote pilot; and three visual spotters looking at the aircraft. The first indication that an onboard system malfunction had occurred was that the camera sensor stopped working. This was closely followed by one of the spotters telling the remote pilot that the aircraft appeared to be descending. The UAV autopilot was no longer responsive to the active orbit over the cornfield inside the ZZZ area and the aircraft descended to the point of impact in a driveway. Minor ground damage; occurred during the post-crash fire.The exact cause of the loss is not clear at this time but appears to be consistent with total onboard electrical system failure. The flight was conducted in strict conformance with the manufacturer checklist and Certificate of Waiver or Authorization. The flight was conducted using waypoint orbits over the airport property coupled to the autopilot. No anomalous annunciations were indicated at the Ground Control Station prior to the aircraft becoming unresponsive.According to the Manufacturer; Aircraft X has only one main electrical bus. All electrical consumers; including the autopilot; are connected onto that bus that is driven by a single voltage regulator. Aircraft Y; according to the manufacturer; has multiple; independent electrical buses which would reduce the probability of total electrical loss to the avionics.




Synopsis: Remote pilot reported a complete loss of control of UAV due to electrical failure.
Date: 202007
Local time of day: 1201-1800
Location: ZZZ.Airport, US
Flight conditions: VMC
Light: Daylight
Aircraft: Cessna 402/402C/B379 Businessliner/Utiliner
Operator: Air Carrier
Operating under: Part 135
Flight plan: IFR
Mission: Passenger
Flight phase: Takeoff / Launch
Airspace: Class D ZZZ
Aircraft component: Exterior Pax/Crew Door
Component problem: Improperly Operated
Reporter organization: Air Carrier
Reporter function: Pilot Flying
Reporter qualification: Flight Crew Multiengine; Flight Crew Instrument; Flight Crew Air Transport Pilot (ATP)
Human factors: Other / Unknown
Anomaly: Aircraft Equipment Problem Critical; Deviation / Discrepancy - Procedural Published Material / Policy
Detector: Person Flight Crew
When detected: In-flight
Result: Air Traffic Control Provided Assistance; Flight Crew Landed As Precaution; Flight Crew Overcame Equipment Problem; Flight Crew Returned To Departure Airport; General Flight Cancelled / Delayed; General Maintenance Action
Contributing factors: Aircraft; Procedure; Human Factors
Primary problem: Human Factors

Narrative: Top Clam shell of cabin door opened on takeoff.Cause - Cabin door not secured properly? Did not notice if door warning.




Synopsis: Cessna 402 pilot reported the upper clamshell door half opened after takeoff.
Date: 201201
Local time of day: 0601-1200
Location: MIC.Airport, MN
Flight conditions: VMC
Light: Daylight
Aircraft: PA-28 Cherokee/Archer/Dakota/Pillan/Warrior
Operator: Personal
Operating under: Part 91
Flight plan: VFR
Mission: Personal
Flight phase: Takeoff / Launch
ATC / advisory: Tower MIC
Reporter organization: Personal
Reporter function: Single Pilot
Reporter qualification: Flight Crew Private
Human factors: Training / Qualification; Communication Breakdown
Anomaly: ATC Issue All Types; Deviation / Discrepancy - Procedural Published Material / Policy
Detector: Person Flight Crew
When detected: Other Post flight
Result: General None Reported / Taken
Contributing factors: Human Factors; Procedure
Primary problem: Human Factors

Narrative: I had filed a VFR flight plan electronically prior to engine start. Upon initial contact with MIC Ground Control; I requested VFR separation services and was given a squawk code and Departure frequency.When I received my takeoff clearance; I requested that the Tower activate my VFR flight plan (in accordance with AIM 5-1-4(f). I prefer to activate this way since during departure there's little time available to contact Flight Service to activate my flight plan. The Tower informed me that my flight plan would automatically be activated upon contacting Departure. This seemed unusual to me and differed from past experience but I acquiesced. When directed by Tower I switched to Departure and continued my flight. When I was approximately twenty miles from my destination and prior to descent Minneapolis Center terminated radar services.Upon arrival at my destination after shutdown I called Flight Service to close my flight plan. At that time I was informed that my flight plan had never been activated. Had something happened to me during the final twenty miles of my flight no search and rescue would have been initiated due to the controller's error. I later discussed the issue with a Tower Supervisor at MIC who verified my story with the tapes and confirmed that the Controller had made an error. The Supervisor indicated that many of the controllers were young and inexperienced. I learned from this that a healthy skepticism is required in aviation to insure personal safety.




Synopsis: A PA-28 pilot was surprised to learn that his VFR Flight Plan had never been activated as he had been advised it would be by the Tower right after takeoff. He was later advised by a Tower Supervisor that many of the Local Controllers were young and inexperienced.
Date: 201912
Local time of day: 1201-1800
Location: ZZZ.Airport, US
Flight conditions: VMC
Weather elements / visibility: 10
Light: Daylight
Aircraft: Light Sport Aircraft
Operator: Personal
Operating under: Part 91
Flight plan: None
Mission: Training
Flight phase: Landing
Airspace: Class G ZZZ
ATC / advisory: CTAF ZZZ
Reporter organization: Personal
Reporter function: Single Pilot
Reporter qualification: Flight Crew Private
Human factors: Distraction; Situational Awareness; Workload
Anomaly: Deviation / Discrepancy - Procedural Published Material / Policy; Ground Event / Encounter Gear Up Landing
Detector: Person Flight Crew
When detected: Other Landing
Result: Aircraft Aircraft Damaged
Contributing factors: Aircraft; Human Factors
Primary problem: Human Factors

Narrative: While practicing an engine out landing; power set to idle; I left the gear up to increase gliding distance and forgot to put it down on short final. The aircraft skidded 150 to 200 ft. down the runway ending up at the left edge. The hull was scraped; but the wear did not go through and one of the sea wing extensions sustained minor scrape damage. A smooth landing; one observer noted; but a little noisy leaving expensive white hull debris in my slide path. The aircraft was jacked up using wing jacks and manufacturer supplied jack points; the gear extended and was returned to its hangar under its own power.




Synopsis: A light sport aircraft pilot reported a gear up landing with no injuries and minor damage to the aircraft.
Date: 202001
Local time of day: 0001-0600
Location: ZZZ.Airport, US
Flight conditions: VMC
Aircraft: B757-200
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Takeoff / Launch
ATC / advisory: Tower 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: Confusion; Distraction; Human-Machine Interface
Anomaly: ATC Issue All Types; Ground Event / Encounter Other / Unknown
Detector: Automation Air Traffic Control; Person Flight Crew
When detected: In-flight
Result: Air Traffic Control Issued New Clearance; Flight Crew Rejected Takeoff; Flight Crew Requested ATC Assistance / Clarification; General Flight Cancelled / Delayed
Contributing factors: ATC Equipment / Nav Facility / Buildings; Airport
Primary problem: ATC Equipment / Nav Facility / Buildings

Narrative: Our aircraft was cleared for takeoff. The First Officer was pilot flying. Normal transfer from me to him. First Officer pushed power up and I did final thrust adjustments and called out 'thrust set'...all systems normal.' After adjusting thrust I looked out at the runway and noticed the red take off hold lights illuminate. I called out reject; took control of the aircraft and did the reject procedure. We were at approximately 80 knots. We called tower; cleared the runway; reviewed the QRC reject checklist and did the brake cooling chart. We went back to the gate to have a brake inspection per the operations manual guidance. I informed tower that the red THL lights had illuminated after we began our roll and Tower said they did not know why. There were no vehicles or aircraft on the runway that would have triggered the lights. I suggested they deactivate the system if that was the case. Good crew coordination with my excellent First Officer. Not sure why the lights illuminated but the runway was clear and they were not on when we began the take off roll.




Synopsis: Air carrier Captain reported a rejected takeoff due to the red runway incursion warning light activating during their takeoff.
Date: 201409
Local time of day: 0001-0600
Location: ZZZ.Airport, US
Aircraft: A321
Operator: Air Carrier
Operating under: Part 121
Mission: Passenger
Flight phase: Taxi
Aircraft component: Pneumatic System
Component problem: Malfunctioning
Reporter organization: Air Carrier
Reporter function: Flight Attendant (On Duty)
Reporter qualification: Flight Attendant Current
Human factors: Physiological - Other
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 Attendant
When detected: Taxi
Result: Flight Crew Returned To Gate; General Flight Cancelled / Delayed
Contributing factors: Aircraft; Human Factors
Primary problem: Aircraft

Narrative: Delay due to weather. Parked on tarmac for about 30 minutes when the toxic fumes became so strong in the cabin. I called the captain and told him possible TCP fumes. Smelled like burning chemicals and the odor was so strong I put a portable oxygen bottle on because I could not breathe and at that point I became incapacitated to assist in the cabin as a working flight attendant. The Captain returned to gate to let passengers and crew off the aircraft. A321 aircraft has bleed air into cabin; mechanical issue. This is maintenance or an engineering problem with the aircraft.




Synopsis: A321 Flight Attendant reports donning an oxygen mask; after 30 minutes of waiting for takeoff; due to foul smelling air in the cabin. The Captain is informed and the flight returns to the gate.