elihoole/asrs-aviation-reports huggingface dataset:
Date: 201206
Local time of day: 0601-1200
Location: CLE.Airport, OH
Flight conditions: VMC
Light: Daylight
Aircraft: A320
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Initial Approach
Airspace: Class B CLE
ATC / advisory: TRACON CLE
Aircraft component: FMS/FMC
Component problem: Failed
Reporter organization: Air Carrier
Reporter function: Captain; Pilot Flying
Reporter qualification: Flight Crew Air Transport Pilot (ATP)
Human factors: Human-Machine Interface
Anomaly: Aircraft Equipment Problem Less Severe
Detector: Person Flight Crew
When detected: In-flight
Result: General None Reported / Taken
Contributing factors: Aircraft
Primary problem: Aircraft

Narrative: For the second time in as many attempts; I experienced a failure of both FMS-1 and FMS-2 while 'cleaning up the box' on approach into CLE. Please see my previous ASRS report for details; as this was an exact duplicate of my previous experience. Please note in my previous report; that both my First Officer; along with both the outbound Captain and First Officer had all experienced similar failures recently. Additionally; the mechanic who met our flight in CLE told me that he has seen a sudden spike in these failures. There is obviously a problem here. From my limited experience; it appears that the problem is associated with only certain airports.




Synopsis: A320 Captain experiences a dual FMGC lock up while attempting to 'clean up the box' during vectors for approach. This is the second occurrence the reporter has experienced recently.
Date: 202110
Local time of day: 1201-1800
Location: ZZZ.TRACON, US
Flight conditions: VMC
Aircraft: SA-227 AC Metro III
Flight phase: Climb; Initial Climb
Airspace: Class C ZZZ
ATC / advisory: TRACON ZZZ
Aircraft component: Engine
Component problem: Failed
Reporter function: Pilot Flying; Captain
Reporter qualification: Flight Crew Air Transport Pilot (ATP)
Anomaly: Aircraft Equipment Problem Critical
Detector: Person Flight Crew
When detected: In-flight
Result: Air Traffic Control Provided Assistance; Flight Crew Landed in Emergency Condition; Flight Crew Overcame Equipment Problem
Contributing factors: Aircraft
Primary problem: Aircraft

Narrative: During climb thru 1;400 MSL; number 1 engine; left engine; flame out. After confirming left engine had failed; left Engine Stop and Feather was pulled; left prop went to feather. ZZZ Approach was notified of the situation; requested priority handling; I entered on a left downwind for Runway XX; followed QRH procedures and landed without any further issues.Identification - Left engine power lost; left propeller was showing NTS; right rudder pressure was needed to maintain heading.Cause - Left engine component cause it to failed.




Synopsis: SA-227 Captain reported the left engine failed during climbout resulting in an immediate return to the departure airport.
Date: 201503
Local time of day: 0601-1200
Location: ZZZ.Airport, US
Flight conditions: VMC
Aircraft: Dash 8-400
Operator: Air Carrier
Operating under: Part 121
Mission: Passenger
Flight phase: Landing
Airspace: Class B ZZZ
ATC / advisory: Tower ZZZ
Aircraft component: Main Gear Tire
Component problem: Malfunctioning
Reporter organization: Air Carrier
Reporter function: First Officer; Pilot Not Flying
Second reporter function: Captain; Pilot Flying
Anomaly: Aircraft Equipment Problem Less Severe
Detector: Person Flight Crew
When detected: Aircraft In Service At Gate
Result: General Maintenance Action
Contributing factors: Aircraft
Primary problem: Aircraft

Narrative: Upon landing both the captain and I noticed the plane shaking/vibrating quite a bit. After slowing the plane down to a normal taxi speed; the vibrating ceased; however both the captain and I knew something was not exactly right with some part of the landing gear. The captain mentioned taking extra care when looking at the landing gear on the post flight walk around. Before exiting the plane; a passenger had mentioned that he saw the some of the tire shred off on the takeoff roll. Upon exiting the aircraft; I immediately noticed the left main inboard tire had something wrong with it. After looking at the tire more closely; we noticed half of the tire tread had shredded off the tire completely. Some of the debris damaged one of the rear wheel well doors and the gear fairing.


Second narrative: After landing and once at the gate; during the post flight walk-around we found that the left inboard main tire had blown and had caused damage to the aft gear door and landing gear fairing. As passengers were leaving the aircraft; a passenger had mentioned to the First Officer that on takeoff roll the inboard tire was wobbling. As I reflect back; I do recall a small amount of vibration during rotation; but nothing that raised alarm. The touchdown was normal with a little bit of vibration at which point I mentioned to the First Officer that we'll have to check during the post flight walk-around to see if there are any abnormalities. It was brought to my attention that the tire that had blown was a retread tire. While I am not an expert on tires; it was explained to me that this appears to be a trend with re-treaded tires.


Synopsis: DHC8-400 flight crew experiences vibration during landing roll. Upon arrival at the gate it is discovered that one of the left main tires has shed half of its tread. A passenger volunteers that he saw something fly off the tire during takeoff.
Date: 201912
Local time of day: 0601-1200
Location: BOW.Tower, FL
Flight conditions: Marginal
Weather elements / visibility: 6
Light: Daylight
Aircraft: Skyhawk 172/Cutlass 172
Operator: Personal
Operating under: Part 91
Flight plan: None
Mission: Training
Flight phase: Takeoff / Launch
Reporter organization: Personal
Reporter function: Pilot Flying
Reporter qualification: Flight Crew Instrument; Flight Crew Private
Human factors: Communication Breakdown; Confusion
Anomaly: Deviation / Discrepancy - Procedural Clearance; Deviation / Discrepancy - Procedural FAR; Deviation / Discrepancy - Procedural Published Material / Policy; Ground Incursion Runway
Detector: Person Air Traffic Control
When detected: In-flight
Result: Air Traffic Control Provided Assistance; Flight Crew Requested ATC Assistance / Clarification
Contributing factors: Procedure
Primary problem: Procedure

Narrative: After landing and requesting a taxi clearance we were instructed to do a back taxi for a departure. We took off without getting the proper clearance from the controller. Tower informed us of the requirements for the takeoff clearance for the next time we needed to back taxi.




Synopsis: Pilot reported departing the airport without ATC clearance for take off.
Date: 201309
Local time of day: 0601-1200
Location: ZZZ.Airport, US
Aircraft: B757 Undifferentiated or Other Model
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Takeoff / Launch
ATC / advisory: Tower ZZZ
Reporter organization: Government
Reporter function: Local
Reporter qualification: Air Traffic Control Fully Certified
Human factors: Situational Awareness
Anomaly: ATC Issue All Types; Deviation / Discrepancy - Procedural Published Material / Policy
Detector: Person Air Traffic Control
Result: General None Reported / Taken
Contributing factors: Human Factors; Procedure
Primary problem: Procedure

Narrative: Training a Developmental during Wake Turbulance RECAT; a B757 was facing north on Taxiway X. I instructed the Developmental to clear the B757 for takeoff on Runway XXR. The aircraft joined the runway at a speed that has not been the norm with the rest of the fleet. The B757 is a CAT 'D' and was following a CAT 'C' aircraft. I am not sure that separation was lost; but from the naked eye I believe that the aircraft did not have enough spacing with the previous aircraft. We were under pressure to fully utilize the Wake RECAT reduced separation; and on the first day of working this position since the new changes; and the Developmental's first day at this position as well; the timing required is still being understood on a learn-as-you-go basis. Recommendation is to allot for more time between departures until the separation and absolute timing is established.




Synopsis: Tower Controller described a RECAT Wake Turbulence event unclear if a loss of separation actually occurred; the reporter noting pressure to fully utilize the new reduced separation requirements.
Date: 201409
Local time of day: 0601-1200
Location: ELM.Airport, NY
Flight conditions: VMC
Light: Dawn
Aircraft: Regional Jet 700 ER/LR (CRJ700)
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Taxi
ATC / advisory: Ground ELM
Reporter organization: Air Carrier
Reporter function: Captain; Pilot Flying
Reporter qualification: Flight Crew Air Transport Pilot (ATP)
Human factors: Communication Breakdown; Situational Awareness
Anomaly: Deviation / Discrepancy - Procedural Published Material / Policy; Ground Incursion Taxiway
Detector: Person Flight Crew
When detected: Taxi
Result: Air Traffic Control Issued New Clearance; Flight Crew Became Reoriented
Contributing factors: Airport; Human Factors
Primary problem: Human Factors

Narrative: I had to make a tight spin out of the gate with a Dash 8 behind me and a CR9 in front of me. While making the turn with minimum and idle thrust; and keeping an eye on the ground crew; I crossed the line from the non-movement area onto Taxiway A before receiving a taxi clearance from ground. The First Officer (FO) was calling ground as we started our movement; and I was expecting to receive a taxi clearance quickly. Additionally; I did not realize how close the border of the non-movement area was to our gate. Unfortunately; the FO's headset was not plugged completely in and his first couple transmissions to ground was unsuccessful. As I realized I was now halfway onto Taxiway A; and the FO wasn't transmitting; I keyed the mike and got a taxi clearance immediately. There is no indication on the 10-9 diagram nor on the 10-7 pages of where the non-movement area ends. The main thing I can do to prevent this from happening is a behavioral and habit change. I'm used to; and in the habit of; expecting there to be plenty of room to make a turn off a gate before entering a movement area. I the future I will make a habit of calling ground to receive a proper taxi clearance before any aircraft movement regardless of how familiar I think I am with the airfield.




Synopsis: CRJ-700 Captain reports inadvertently entering the movement area during a U turn out of the gate at ELM due to the close proximity of the line and the First Officer's calls for clearance going unanswered.
Date: 201202
Local time of day: 1201-1800
Location: ZZZ.Airport, US
Flight conditions: VMC
Light: Daylight
Aircraft: Mooney Aircraft Undifferentiated or Other Model
Operator: Personal
Operating under: Part 91
Flight plan: VFR
Mission: Personal
Flight phase: Landing
ATC / advisory: CTAF ZZZ
Aircraft component: Gear Extend/Retract Mechanism
Component problem: Improperly Operated; Malfunctioning
Reporter organization: Personal
Reporter function: Single Pilot
Reporter qualification: Flight Crew Private
Human factors: Training / Qualification; Confusion
Anomaly: Aircraft Equipment Problem Critical; Deviation / Discrepancy - Procedural Published Material / Policy
Detector: Person Flight Crew
When detected: In-flight
Result: Aircraft Aircraft Damaged; General Maintenance Action
Contributing factors: Aircraft; Human Factors
Primary problem: Ambiguous

Narrative: Landing gear collapse on landing. It is possible the gear was not locked in the down position. On contact with the runway they retracted. This plane has manual gear lever. The gear is spring loaded and with a bounce it retracted. Minimal damage to aircraft; landing gear collapsed on landing.




Synopsis: A 1964 M20C with a manual landing hear lever landed gear up after the gear retracted following a bounced landing.
Date: 201409
Local time of day: 1201-1800
Location: ZZZ.Airport, US
Flight conditions: VMC
Light: Daylight
Aircraft: B737-700
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Taxi
ATC / advisory: Ground ZZZ; Ramp ZZZ
Aircraft component: Checklists
Component problem: Improperly Operated
Reporter organization: Air Carrier
Reporter function: Captain
Reporter qualification: Flight Crew Air Transport Pilot (ATP)
Human factors: Workload; Confusion; Distraction; Situational Awareness; Time Pressure; Communication Breakdown
Anomaly: Deviation / Discrepancy - Procedural Published Material / Policy
Detector: Person Flight Crew
When detected: Taxi
Result: Flight Crew Took Evasive Action; Flight Crew FLC complied w / Automation / Advisory; Flight Crew Became Reoriented
Contributing factors: Human Factors; Procedure; Aircraft; Chart Or Publication; Environment - Non Weather Related
Primary problem: Human Factors

Narrative: We received a change of runway and ATIS change during pushback following engine start of number 2 engine.  Single engine taxi was planned and information was briefed and changed in the performance computer and the CDU after engine start; but before the Before Taxi checklist was called. After making all the changes to the performance computer and CDU reviews were made; numbers and flap settings were still the same.  I missed calling for the checklist and when as we switched from Ramp Control to Ground Control for taxi instructions; we immediately saw that the flaps were not set for takeoff.




Synopsis: A B737-700 crew became distracted during pushback by a runway and ATIS change. During single engine taxi they realized the performance computer and FMC distractions caused them to miss lowering the flaps.
Date: 201512
Local time of day: 1801-2400
Location: MHT.Airport, NH
Flight conditions: VMC
Weather elements / visibility: 5
Light: Night
Aircraft: Widebody; Low Wing; 2 Turbojet Eng
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Cargo / Freight / Delivery
Flight phase: Initial Approach
Airspace: Class C MHT
ATC / advisory: TRACON A90
Aircraft component: FMS/FMC
Component problem: Malfunctioning
Reporter organization: Air Carrier
Reporter function: Captain; Pilot Flying
Reporter qualification: Flight Crew Air Transport Pilot (ATP)
Human factors: Distraction; Human-Machine Interface
Anomaly: Aircraft Equipment Problem Less Severe; Deviation - Altitude Overshoot; Deviation / Discrepancy - Procedural Clearance; Deviation / Discrepancy - Procedural Published Material / Policy; Inflight Event / Encounter CFTT / CFIT
Detector: Person Flight Crew
When detected: In-flight
Result: Air Traffic Control Issued Advisory / Alert; Flight Crew Returned To Clearance; Flight Crew Took Evasive Action
Contributing factors: Aircraft; Human Factors
Primary problem: Aircraft

Narrative: On the PURBL transition to the ILS 17; the PF notice that the aircraft was descending below the approach profile altitude from BLSSM to BLUUM. The PF arrested the descent and climbed back to a safe altitude. ATC then called and reminded us of the minimum safe altitude. PM notice that the altitude at BLUUM in the FMC had magically changed to field elevation. We were navigating in LNAV/VNAV; speed intervene activated with the autopilot engaged. An uneventful; stable approach and landing was performed. Altitudes and fixes were reviewed by both pilots during the approach brief. Cause of deviation in the FMC; from what we can determine is PFM. No explanation. One can prevent this from happening by believing nothing; ever. 'Constant Monitoring' would have prevented this event.




Synopsis: Air carrier flight crew on the ILS Runway 17 to MHT noticed the aircraft had descended below the minimum safe altitude (MSA) prior to BLUUM with LNAV/VNAV and SPD INT active. The crew noticed field elevation had replaced the BLUUM altitude in the FMC and climbed back to the MSA as ATC alerted.
Date: 201903
Local time of day: 1201-1800
Location: ZZZ.ARTCC, US
Flight conditions: VMC
Light: Night
Aircraft: EMB ERJ 145 ER/LR
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Cruise
Airspace: Class A ZZZ
ATC / advisory: Center ZZZ
Aircraft component: Air Conditioning and Pressurization Pack
Component problem: Malfunctioning
Reporter organization: Air Carrier
Reporter function: Pilot Flying; Captain
Reporter qualification: Flight Crew Multiengine; Flight Crew Air Transport Pilot (ATP); Flight Crew Instrument
Human factors: Situational Awareness
Anomaly: Aircraft Equipment Problem Critical; Deviation / Discrepancy - Procedural Published Material / Policy
Detector: Person Flight Crew; Person Flight Attendant
When detected: In-flight
Result: Flight Crew Landed As Precaution
Contributing factors: Human Factors; Aircraft
Primary problem: Aircraft

Narrative: The airframe we were operating had the number 2 pack MELed. In cruise flight the FA (Flight Attendant) called up and said it was warm in the back. So I adjusted the temperature on the number 1 pack to cool it down in the back. After a few minutes of no temperature change I set the number 1 pack into manual mode. After doing that the number 1 pack shut off. We were at 25000 ft. The cabin altitude climbed from 3500 to 7000 in a matter of seconds. I quickly selected the pack off and on to reset it but it stayed off. We began a descent with ATC and decided to divert. After descending for a while the pack came back on. We decided to make a precautionary landing anyways.




Synopsis: EMB-145 Captain reported a cabin pressurization issue after the sole operational pack failed to cool the cabin and malfunctioned.
Date: 201605
Local time of day: 1801-2400
Location: RNO.Airport, NV
Flight conditions: VMC
Weather elements / visibility: 10
Light: Night
Aircraft: Small Aircraft
Operator: Personal
Operating under: Part 91
Flight plan: VFR
Mission: Personal
Flight phase: Landing
Airspace: Class C RNO
ATC / advisory: Tower RNO
Reporter organization: Personal
Reporter function: Pilot Flying; Single Pilot
Reporter qualification: Flight Crew Flight Instructor; Flight Crew Instrument; Flight Crew Multiengine; Flight Crew Commercial
Human factors: Confusion; Distraction; Physiological - Other; Situational Awareness
Anomaly: Deviation / Discrepancy - Procedural Other / Unknown
Detector: Person Flight Crew
When detected: In-flight
Result: Flight Crew Became Reoriented; Flight Crew Requested ATC Assistance / Clarification
Contributing factors: Environment - Non Weather Related; Human Factors; Airport; ATC Equipment / Nav Facility / Buildings
Primary problem: ATC Equipment / Nav Facility / Buildings

Narrative: 34R/16L has new LED centerline lights. They are so bright and intense on their lowest setting (confirmed by tower) that it makes final approach to landing difficult at night.The main problem is that the runway edge lights have not been replaced with the newer style LEDs... so you can barely even make out the runway edge lights; whereas the centerline nearly blinds you!The lights (centerline/edge) need to be the same type of bulb so that the light they produce is the same intensity. This would make judging the flare at night in a such a critical phase of flight significantly easier.




Synopsis: A pilot landed on RNO Runway 34R/16L and reported the new LED centerline lights as too bright. The centerline LEDs obscured the runway ledge lights and made landing height estimates difficult.
Date: 201507
Local time of day: 0601-1200
Location: ZZZ.Airport, US
Light: Daylight
Aircraft: MD-83
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Parked
ATC / advisory: Ramp ZZZ
Aircraft component: Air Conditioning and Pressurization Pack
Component problem: Malfunctioning
Reporter organization: Air Carrier
Reporter function: First Officer; Pilot Not Flying
Reporter qualification: Flight Crew Air Transport Pilot (ATP)
Second reporter function: Pilot Flying; Captain
Anomaly: Aircraft Equipment Problem Less Severe; Flight Deck / Cabin / Aircraft Event Smoke / Fire / Fumes / Odor
Detector: Person Flight Attendant
When detected: Aircraft In Service At Gate
Result: General Evacuated
Contributing factors: Aircraft
Primary problem: Aircraft

Narrative: We had just closed the FWD cabin door prior to pushback; when the No. 1 Flight Attendant alerted the cockpit crew that the cabin was filling with smoke.  The Captain instructed me to notify ramp to have the jet bridge brought back into boarding position. As I was notifying ramp via the radio; the Captain and No.1 Flight Attendant were discussing evacuation.  Smoke began to enter the cockpit and a decision by the Captain and No.1 Flight Attendant was made to do an emergency evacuation due to the amount of smoke and the delay in getting the jet bridge back into position. Allowing the gate agent to remain at the jet bridge till the plane is pushed back could provide another avenue of exit/safety if this was to occur again.


Second narrative: After the cabin door was closed and we were preparing for pushback; the number one Flight Attendant stated that there was smoke in the cabin. After confirming the smoke; we called Ramp Control to have the gate agent return and reattach the jet bridge to the aircraft to remove the passengers. We also requested emergency vehicles to meet the aircraft. The smoke continued to get thicker pretty quickly so the number one Flight Attendant and the Captain elected to evacuate the aircraft.


Synopsis: MD83 flight crew was informed by the Lead Flight Attendant that the cabin was filling with smoke as the crew is preparing for push back. The jetway was unable to be moved into position in a timely manner and the Captain elects evacuate at the gate via the slides.
Date: 201906
Local time of day: 1201-1800
Location: ZZZ.Airport, US
Flight conditions: VMC
Weather elements / visibility: 10
Light: Daylight
Aircraft: PA-28 Cherokee/Archer/Dakota/Pillan/Warrior
Operator: Personal
Operating under: Other 141
Flight plan: None
Mission: Training
Flight phase: Landing
Airspace: Class E ZZZ
ATC / advisory: CTAF ZZZ
Reporter organization: Other Flight School
Reporter function: Single Pilot
Reporter qualification: Flight Crew Student
Human factors: Situational Awareness; Training / Qualification
Anomaly: Deviation / Discrepancy - Procedural Published Material / Policy; Ground Event / Encounter Loss Of Aircraft Control; Ground Excursion Runway
Detector: Person Flight Crew
When detected: In-flight
Result: General None Reported / Taken
Contributing factors: Human Factors
Primary problem: Human Factors

Narrative: I was flying on my first solo flight.  I had just completed my first pattern and landing when I had the excursion.  Everything looked fine until I touched down and lost directional control.  I attempted to use the rudders to bring the airplane back to centerline but the oscillations got bigger; and that is when I exited the runway.




Synopsis: A Student Pilot; on first solo flight; reported losing control during first landing; and exiting the runway surface.
Date: 201707
Local time of day: 0601-1200
Location: IAH.Airport, TX
Aircraft: EMB ERJ 145 ER/LR
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Flight phase: Initial Approach
Airspace: Class B IAH
ATC / advisory: Tower IAH
Second aircraft: UAV - Unpiloted Aerial Vehicle
Reporter organization: Air Carrier
Reporter function: Pilot Flying; Captain
Anomaly: Conflict NMAC; Conflict Airborne Conflict
Detector: Person Flight Crew
When detected: In-flight
Result: General None Reported / Taken

Narrative: At 1100ft MSL on LOC and slope for ILS 27 IAH I saw a drone. It passed off the left side of the nose by 15ish ft. It was white with black and green decals/paint. We were close enough I could even see a GoPro type camera on it. It passed off our left without further incident. Was shooting ILS but in VMC conditions. When I saw it I originally said bird. My FO looked on my side and saw it as I said it was a drone. I reported it to IAH tower on 135.15. Then landed without incident.




Synopsis: While flying an ILS approach in VMC; crew encountered a drone and reported the sighting to Tower.