elihoole/asrs-aviation-reports huggingface dataset:
Date: 201606
Local time of day: 0601-1200
Location: ZZZ.Airport, US
Light: Daylight
Aircraft: EMB ERJ 145 ER/LR
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Landing
ATC / advisory: Tower ZZZ
Aircraft component: Brake System
Component problem: Malfunctioning
Reporter organization: Air Carrier
Reporter function: Captain; Pilot Flying
Reporter qualification: Flight Crew Air Transport Pilot (ATP)
Human factors: Situational Awareness; Workload; Time Pressure
Second reporter function: Pilot Not Flying; First Officer
Anomaly: Aircraft Equipment Problem Less Severe; Deviation / Discrepancy - Procedural Maintenance; Flight Deck / Cabin / Aircraft Event Smoke / Fire / Fumes / Odor
Detector: Person Air Traffic Control
When detected: Taxi
Result: Aircraft Aircraft Damaged; Flight Crew Took Evasive Action; General Evacuated; General Maintenance Action
Contributing factors: Aircraft; Procedure
Primary problem: Aircraft

Narrative: I was the Pilot-in-Command and the pilot-flying. Upon a normal landing; the tower controller reported smoke coming from our aircraft's left main landing gear. An airport support vehicle confirmed the left main landing gear brake was on fire. We then coordinated and performed a ground evacuation of the aircraft in accordance with policies and procedures.


Second narrative: Increased maintenance attention to brake pads and hydraulic lines.


Synopsis: EMB-145 flight crew reported having a brake fire after landing. The Captain commanded a successful evacuation.
Date: 201206
Local time of day: 1801-2400
Location: ZZZ.Airport, US
Flight conditions: VMC
Weather elements / visibility: 20
Light: Daylight
Aircraft: Skyhawk 172/Cutlass 172
Operator: FBO
Operating under: Part 91
Flight plan: None
Mission: Training
Flight phase: Cruise
Airspace: Class G ZZZ
ATC / advisory: Tower ZZZ
Aircraft component: AC Generator/Alternator
Component problem: Malfunctioning
Reporter organization: FBO
Reporter function: Pilot Flying; Trainee
Reporter qualification: Flight Crew Commercial; Flight Crew Instrument
Human factors: Troubleshooting; Training / Qualification; Situational Awareness; Human-Machine Interface; Distraction; Workload
Anomaly: Aircraft Equipment Problem Critical
Detector: Person Flight Crew
When detected: In-flight
Result: Flight Crew FLC complied w / Automation / Advisory; Flight Crew Requested ATC Assistance / Clarification; Flight Crew Returned To Departure Airport; General Declared Emergency
Contributing factors: Human Factors; Aircraft
Primary problem: Aircraft

Narrative: While on a CFI training flight with my Instructor; I noticed that the display on the radios was pulsing; (bright; dim; bright; dim). The amp meter was not showing a discharge. We started the loss of electrical power checklist; which didn't help or correct the problem; so we decided to land at ZZZ1 airport and call the Mechanic. As we were approaching the airport; we tried to lower the gear; but it didn't extend; so we departed the airport pattern to troubleshoot and decided to go back to our departure airport. On the way back we went through the emergency gear extension checklist but were unable to get a green light indicating the gear was down. As is the flight school policy; the Instructor would do the landing. At 10 miles from the airport; we called the Tower on a handheld radio; declared an emergency and requested that the Tower visually check that our gear was down. On downwind for the runway; the Tower said that the gear appeared down. We landed with no problems and taxied to the ramp. This was a great learning experience. We used CRM to divide the tasks (checklists; pumping the gear; talking on the handheld radio; etc.); and we both remained calm and professional.




Synopsis: A pilot under going CFI training in a C172RG with his instructor; noticed signs of an electrical system failure and so together they split tasks to successfully extend the gear; complete the checklists and land.
Date: 201512
Local time of day: 1201-1800
Location: ATL.Airport, GA
Flight conditions: VMC
Weather elements / visibility: 10
Light: Daylight
Aircraft: Regional Jet 900 (CRJ900)
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Initial Climb
Airspace: Class B ATL
ATC / advisory: Tower ATL
Second aircraft: B757 Undifferentiated or Other Model
Reporter organization: Air Carrier
Reporter function: Captain; Pilot Flying
Reporter qualification: Flight Crew Air Transport Pilot (ATP)
Human factors: Situational Awareness
Anomaly: Deviation - Track / Heading All Types; Deviation / Discrepancy - Procedural Clearance; Deviation / Discrepancy - Procedural Published Material / Policy; Inflight Event / Encounter Wake Vortex Encounter
Detector: Person Flight Crew
When detected: In-flight
Result: Flight Crew Became Reoriented; Flight Crew Returned To Clearance
Contributing factors: Environment - Non Weather Related; Human Factors
Primary problem: Human Factors

Narrative: At 1000 AGL on takeoff from ATL on the MUNSN SID from RWY 27R; I called for the autopilot to be selected on by my FO. We encountered mild wake turbulence from the departing B757 in front of us simultaneously with my 'autopilot' call. The FO selected the autopilot but apparently did not depress the button hard enough and the A/P failed to engage. I thought that it had so I took my hands off the controls. I had placed the aircraft in a slight left turn and it continued to turn slightly past the departure course. Once I noticed the minor deviation; I immediately corrected back to the departure course and reintercepted. I then called for the A/P and the FO engaged it and verified it was on. No other deviation of outbound track occurred after that and we continued with the departure.




Synopsis: CRJ900 Captain reported a track deviation resulted when the autopilot was not engaged as the reporter thought it was. A mild wake turbulence encounter was cited as contributing.
Date: 201712
Local time of day: 1201-1800
Location: ALB.Airport, NY
Aircraft: Large Transport; Low Wing; 2 Turbojet Eng
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Final Approach
Airspace: Class C ALB
ATC / advisory: Tower ALB
Reporter organization: Air Carrier
Reporter function: Captain
Reporter qualification: Flight Crew Air Transport Pilot (ATP)
Human factors: Situational Awareness
Anomaly: Deviation / Discrepancy - Procedural Published Material / Policy; Inflight Event / Encounter CFTT / CFIT
Detector: Person Flight Crew
When detected: In-flight
Result: Flight Crew Took Evasive Action
Contributing factors: Environment - Non Weather Related; Airport
Primary problem: Airport

Narrative: On the RNAV approach Runway 28; the trees on a ridge line on short final appear to have grown into the critical flight path.  While the vertical indication showed us on glide path; the visual picture required us to level off; then when clear of trees; re-establish a glide path to the displaced threshold. Rwy 28 is rarely used by transport category aircraft.  (My first time in 30 years since using this runway - now I remember why - very rough ride with the wind over the high terrain).  The VASI shows one white and three red when on RNAV glide path. Decline the approach to Runway 28 and use ILS to Runway 01.  Cut down or top the encroaching trees on the ridge line.




Synopsis: Air carrier Captain reported noticing that while on approach to ALB runway 28 the ridgeline trees have grown into the critical flight path.
Date: 201412
Local time of day: 1201-1800
Location: MYNN.Airport, FO
Flight conditions: VMC
Weather elements / visibility: 10
Light: Daylight
Aircraft: Light Transport; Low Wing; 2 Turbojet Eng
Operator: Corporate
Operating under: Part 91
Flight plan: IFR
Mission: Cargo / Freight / Delivery
Flight phase: Taxi
ATC / advisory: Tower MYNN
Reporter organization: Corporate
Reporter function: First Officer; Pilot Not Flying
Reporter qualification: Flight Crew Air Transport Pilot (ATP); Flight Crew Flight Instructor; Flight Crew Instrument; Flight Crew Multiengine
Human factors: Communication Breakdown
Anomaly: Deviation / Discrepancy - Procedural Clearance; Ground Incursion Runway; Ground Incursion Taxiway
Detector: Person Air Traffic Control
When detected: Taxi
Result: Air Traffic Control Issued Advisory / Alert; Air Traffic Control Issued New Clearance; Flight Crew Requested ATC Assistance / Clarification
Contributing factors: Procedure; Airport; Human Factors
Primary problem: Ambiguous

Narrative: Aircraft had just landed at destination MYNN and was taxiing to FBO. Ground controller cleared aircraft from Runway 32 to taxi via D; H; A; hold short Runway 32. Crew read back the clearance verbatim and both crew members verified the taxi clearance with the integrated airport diagram on the copilots DU. The taxi clearance had the crew taxiing past the end of Runway 27 on Taxiway H; upon reaching that point while on the cleared route ground control informed the crew they had taxied past the approach end of runway 27 which he stated the crew was to hold short of. (The crew noticed no hold short lines nor was the route depicted on the chart as anything except taxiways and the crew had confirmed the clearance together and to ground control). Ground control re-cleared the aircraft to the FBO and the crew contacted tower via phone after shutdown to discuss the taxi clearance. The crew believed there was a miscommunication by the controller.




Synopsis: Corporate aircraft First Officer reports landing at MYNN and being cleared to taxi via H and A to hold short of Runway 32. The crew is admonished by Ground Control for taxiing past the end of Runway 27 without requesting clearance.
Date: 201808
Local time of day: 1201-1800
Location: ZZZ.ARTCC, US
Flight conditions: VMC
Light: Daylight
Aircraft: EMB-505 / Phenom 300
Operator: Fractional
Operating under: Part 91
Flight plan: IFR
Mission: Passenger
Flight phase: Climb
Airspace: Class A ZZZ
ATC / advisory: Center ZZZ
Aircraft component: Turbine Engine
Component problem: Malfunctioning
Reporter organization: Fractional
Reporter function: Captain; Pilot Flying
Reporter qualification: Flight Crew Air Transport Pilot (ATP)
Human factors: Troubleshooting; Situational Awareness; Distraction
Second reporter function: First Officer; Pilot Not Flying
Anomaly: Aircraft Equipment Problem Critical
Detector: Person Flight Crew
When detected: In-flight
Result: Flight Crew Diverted; Flight Crew Inflight Shutdown; Flight Crew Landed in Emergency Condition; General Maintenance Action
Contributing factors: Aircraft
Primary problem: Aircraft

Narrative: During climb crew noticed abnormal vibration and ran the Engine Abnormal Vibration checklist. While running the checklist; vibration increased and GEN 2 OFF BUS CAS message displayed and Gen 2 voltage dropped rapidly on the electrical synopsis page. Crew ran the GEN 2 OFF BUS checklist; which directed engine shutdown. Vibration continued to increase in amplitude during shutdown. After shutdown the vibration mostly ceased except for an occasional shudder. Crew [notified ATC] and requested a descent and clearance direct [a diversion airport]. After finishing checklists and preparation for the single-engine landing; the First Officer informed the passengers of the situation and planned divert; while the Captain informed company operations. The single-engine landing was uneventful.


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


Synopsis: An Embraer Phenom 300 flight crew reported experiencing an engine vibration which resulted in an engine shutdown and diversion.
Date: 201409
Local time of day: 1801-2400
Location: ZZZ.Airport, US
Light: Night
Aircraft: B757 Undifferentiated or Other Model
Operator: Air Carrier
Operating under: Part 121
Flight phase: Taxi
ATC / advisory: Ground ZZZ
Second aircraft: EMB ERJ 145 ER/LR
Aircraft component: Navigation Light
Component problem: Improperly Operated
Reporter organization: Air Carrier
Reporter function: Technician
Reporter qualification: Maintenance Airframe; Maintenance Powerplant
Human factors: Confusion; Communication Breakdown
Anomaly: Aircraft Equipment Problem Less Severe; Deviation / Discrepancy - Procedural FAR; Deviation / Discrepancy - Procedural Published Material / Policy
Detector: Person Maintenance
When detected: Taxi
Result: General None Reported / Taken
Contributing factors: Equipment / Tooling; Human Factors; Company Policy; Aircraft; Procedure
Primary problem: Human Factors

Narrative: While taxiing company B757 aircraft from gate to Hangar line; we were cleared by Ground Control to proceed via A-T-join runway XX. After receiving subsequent clearance to T1 [then associated taxiways] to the hangar; we caught up to a dark; apparently unpowered company livery RJ (ERJ-145) near the T1 intersection.  The RJ was being towed dark with absolutely no external lighting on; a completely dark aircraft.  This situation only presented itself as we drew close to the aircraft in tow.  The towbarless tractor (supertug) was lit externally; but minimally visible from our vantage point; with a completely dark aircraft between us and the tractor.  Once the towing operation completed a turn onto taxiway T; a single green light came in view which is somehow mounted on supertug; presented a similar appearance to a green wing navigation light common on all aircraft.  To say this presented a confusing situation is an understatement. [Aircraft] operation in Noncompliance with FARs; Policy and Procedures.  This is a situation never before observed in [my] 30 plus years as a taxi mechanic at our location.  There are long established standards in place regarding external light usage and requirements; both in gate areas; as well as movement in active controlled taxiways; most with an eye on safety regarding aircraft position (nav lights) and anti-collision lights signaling running engines and/or aircraft movement.




Synopsis: A Line Aircraft Maintenance Technician (AMT) taxiing a company B757 aircraft reports coming up on a dark; unpowered ERJ-145 aircraft with no external lighting on. Light on the towbarless Supertug tractor only minimally visible; with completely dark aircraft between their B757 and Tow tractor. Technician notes long established standards requiring Anti-Collision and Nav lights not enforced during aircraft tow.
Date: 201207
Local time of day: 1801-2400
Location: ZZZ.ARTCC, US
Flight conditions: VMC
Weather elements / visibility: Thunderstorm
Light: Night
Aircraft: Dash 8-300
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Cruise
Airspace: Class E ZZZ
ATC / advisory: Center ZZZ
Aircraft component: Powerplant Fuel Valve
Component problem: Malfunctioning
Reporter organization: Air Carrier
Reporter function: Captain; Pilot Not Flying
Reporter qualification: Flight Crew Air Transport Pilot (ATP)
Human factors: Workload; Training / Qualification; Time Pressure; Distraction
Second reporter function: Pilot Flying; First Officer
Anomaly: Aircraft Equipment Problem Critical
Detector: Person Flight Crew
When detected: In-flight
Result: Flight Crew Diverted; Flight Crew Landed As Precaution; General Maintenance Action
Contributing factors: Aircraft
Primary problem: Aircraft

Narrative: We were flying a filed alternate routing due to extensive convective activity along our normal routing. While deviating left of course for weather; the First Officer brought to my attention that the Number One Engine Fuel Shutoff Valve circuit breaker had popped. Looking at the Fire Protection Panel I noticed the Fuel Valve Open Light had extinguished. The First Officer continued Pilot Flying (PF) duties and I immediately placed a call via SATCOM to the Dispatcher and Maintenance Control. It was decided not attempt a reset of the breaker and divert the flight to a nearby airport. The remainder of the flight was uneventful and the passengers were deplaned at the gate. Maintenance met the aircraft at the gate; reset the popped circuit breaker; and found the shutoff valve to be continually cycling open and closed. Dispatch advised that a terminating light 15-20 minutes out and we should expect to swap into that aircraft to complete our flight. We re-dispatched on the alternate aircraft and completed the flight uneventfully.




Synopsis: A DHC-8-300's left engine fuel shutoff valve light was discovered extinguished in flight so the Captain diverted to a nearby airport where the valve was found to be constantly cycling.
Date: 201604
Local time of day: 0601-1200
Location: ZZZ.Airport, US
Flight conditions: IMC
Aircraft: B737 Undifferentiated or Other Model
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Takeoff / Launch
Airspace: Class B ZZZ
ATC / advisory: TRACON ZZZ
Reporter organization: Air Carrier
Reporter function: Pilot Flying; First Officer
Human factors: Situational Awareness
Anomaly: Aircraft Equipment Problem Less Severe; Deviation - Altitude Overshoot; Deviation - Speed All Types; Deviation / Discrepancy - Procedural Published Material / Policy; Inflight Event / Encounter Weather / Turbulence
Detector: Person Flight Crew
When detected: In-flight
Result: Flight Crew Returned To Departure Airport; General Maintenance Action
Contributing factors: Human Factors; Aircraft
Primary problem: Aircraft

Narrative: We departed with VNAV selected on the ground; 190 heading in the heading window; and 2;500 feet in the altitude window. The takeoff was normal [until] 1;500 feet; then we were giving instructions to climb to 6;000 feet and direct [to an] intersection. At this time we were in the clouds/IMC: I noticed 160 knots in the speed window. The Captain set 6;000 feet in the altitude window and line selected direct [the intersection] in the FMS. VNAV and LNAV would not engage. Heading would not engage for a back up roll mode. I was tracking the magenta line to [the intersection] while climbing to 6;000 feet. As we were approaching [the intersection]; I proceeded to make a left turn to the next fix; when the Captain said 'check altitude'. I was following the pitch command on the flight director and noticed we were climbing through 6;400 feet. I quickly descended back down to 6;000 feet and noticed the flight director was commanding a climb and left turn. The auto throttle switch was on; but the auto throttles did not retard to maintain 250 kts. At this time the gear warning horn was continuous and the Captain [elected] to return to [departure airport]. I turned off the flight director and flew the aircraft raw data at this time to the assigned heading. The Captain managed the situation by informing the passengers; flight attendants; and Operations of our situation and intentions. As we descended; the gear horn stopped and we starting getting back auto throttle mode; pitch; and roll mode. We commenced an ILS approach and landed normally at 10;000 lbs overweight. We taxied to the gate without any further issues. The occurrence was written up in the log book along with the overweight landing.




Synopsis: A B737 First Officer reported an altitude excursion after system anomalies affected their autoflight capabilities.
Date: 202002
Local time of day: 1801-2400
Location: NCT.TRACON, CA
Aircraft: B737 Undifferentiated or Other Model
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Final Approach
Airspace: Class B SFO
ATC / advisory: TRACON NCT
Reporter organization: Air Carrier
Reporter function: Captain
Reporter qualification: Flight Crew Air Transport Pilot (ATP); Flight Crew Instrument; Flight Crew Multiengine
Anomaly: Conflict NMAC; Deviation / Discrepancy - Procedural FAR
Detector: Person Flight Crew
When detected: In-flight
Result: General None Reported / Taken
Contributing factors: Airspace Structure; Procedure
Primary problem: Ambiguous

Narrative: On a visual approach at approximately 5 DME on the ILS 28L at 1;500 ft.; a large white drone passed approximately 3 ft. beneath the right wing outboard of the engine. No lights were illuminated on the drone. It was only visible due to our landing lights. We did not have time to take evasive action.




Synopsis: B737 Captain reported a NMAC with a drone while on an ILS approach.
Date: 202105
Local time of day: 1201-1800
Location: CLT.Airport, NC
Flight conditions: VMC
Light: Daylight
Aircraft: Commercial Fixed Wing
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Initial Approach
Airspace: Class B CLT
ATC / advisory: Tower CLT
Second aircraft: UAV: Unpiloted Aerial Vehicle
Reporter organization: Air Carrier
Reporter function: Captain; Pilot Flying
Reporter qualification: Flight Crew Air Transport Pilot (ATP); Flight Crew Instrument; Flight Crew Multiengine
Human factors: Situational Awareness
Second reporter function: First Officer; Pilot Not Flying
Anomaly: Airspace Violation All Types; Conflict Airborne Conflict; Deviation / Discrepancy - Procedural FAR; Deviation / Discrepancy - Procedural Published Material / Policy; Deviation / Discrepancy - Procedural Unauthorized Flight Operations (UAS)
Detector: Person Flight Crew
When detected: In-flight
Contributing factors: Human Factors
Primary problem: Human Factors

Narrative: Turning onto the LOC on 36R in CLT a drone passed extremely close to our aircraft. Same altitude heading the opposite direction. We both saw what we thought was a bird but as drone passed by the First Officer side he saw the propellers of the drone and confirmed that it was a drone. It was black in color. Continued on the approach.


Second narrative: Encountered a UAV drone at 2;700 feet while flying an intercept to the 36R localizer between LANSR and CIKDU for a visual approach to 36R at CLT. Originally thought it was a bird; then noticed the propellers and finer details on the drone.  It was a black quadcopter. Someone was flying a drone close to the ILS flight path; co altitude; for 36R at CLT. I originally called out 'bird 12 o clock;' then it maneuvered to our right; where I watched it pass off of our right wing; co altitude.  I notified the Captain it was a drone; and we immediately made a PIREP to CLT 36R Tower. Notify other pilots and attempt to inform the general; drone flying public how dangerous and illegal it is operate drones in Class B airspace.


Synopsis: Air carrier flight crew had a near miss with a UAS while on approach.