elihoole/asrs-aviation-reports huggingface dataset:
Date: 201204
Local time of day: 1801-2400
Location: ZZZ.Airport, US
Flight conditions: VMC
Weather elements / visibility: 10
Light: Daylight
Aircraft: Bonanza 36
Operator: Air Taxi
Operating under: Part 135
Flight plan: IFR
Mission: Cargo / Freight / Delivery
Flight phase: Taxi
ATC / advisory: Tower ZZZ
Aircraft component: Normal Brake System
Component problem: Failed
Reporter organization: Air Carrier
Reporter function: Pilot Flying; Single Pilot
Reporter qualification: Flight Crew Commercial; Flight Crew Flight Instructor; Flight Crew Instrument; Flight Crew Multiengine
Human factors: Human-Machine Interface
Anomaly: Aircraft Equipment Problem Critical; Conflict Ground Conflict; Less Severe; Ground Event / Encounter Loss Of Aircraft Control; Ground Event / Encounter Object; Ground Excursion Taxiway
Detector: Person Flight Crew
When detected: In-flight
Result: General None Reported / Taken
Contributing factors: Human Factors; Aircraft
Primary problem: Aircraft

Narrative: Immediately upon engaging the brakes after landing the aircraft yawed to the right. I identified the problem as an apparent left brake failure. At this time ATC instructed me to exit the runway for landing traffic on final approach to the same runway. I was unable to comply and notified ATC of the brake issue. ATC responded and instructed me to continue to the end of the runway and exit on the last taxiway. I attempted to regain braking power by pumping the left brake pedal but was unable. I then began the 90 degree left turn to exit the runway but was unable to complete the turn. The aircraft rolled off the taxiway and onto low cut grass at a low rate of speed. I attempted to maneuver the aircraft to avoid lights and signs but struck a taxi light with the left main landing gear. I then shut down the engine and notified ATC.




Synopsis: A BE36 pilot was unable to remain on the hard surface when he attempted to exit the runway to the left after suffering a left brake failure on the landing roll. He struck a taxi light after departing the taxiway at the end of the runway.
Date: 201901
Local time of day: 0601-1200
Location: ZZZ.Airport, US
Aircraft: A321
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Other Take Off Position
ATC / advisory: Tower ZZZ
Reporter organization: Air Carrier
Reporter function: Pilot Flying; Captain
Reporter qualification: Flight Crew Instrument; Flight Crew Air Transport Pilot (ATP); Flight Crew Multiengine
Human factors: Communication Breakdown
Second reporter function: Pilot Not Flying; First Officer
Anomaly: ATC Issue All Types; Deviation / Discrepancy - Procedural Published Material / Policy
Detector: Person Flight Crew
When detected: Other Takeoff Position
Result: Air Traffic Control Provided Assistance; Flight Crew Took Evasive Action; Flight Crew Requested ATC Assistance / Clarification; General Maintenance Action
Contributing factors: Procedure; Human Factors; Weather
Primary problem: Procedure

Narrative: ATIS indicated a headwind. Upon receiving takeoff clearance; Tower reported strong tailwinds.  We cleared runway to make performance corrections. This is a common situation. ATC needs to issue specials when winds indicate a tailwind.  Further[more]; they should be required to issue a tailwind warning.


Second narrative: Taxied into position and hold on [Runway] XXR. Was given winds right before takeoff clearance and we noticed that it was now a tailwind condition; so we told the Tower Controller that we needed new takeoff numbers. There was no tailwind prior during taxi out; so we taxied off and called Dispatch for new numbers.


Synopsis: A321 flight crew reported receiving takeoff clearance with a tailwind component.
Date: 201508
Weather elements / visibility: Clear
Aircraft: Any Unknown or Unlisted Aircraft Manufacturer
Flight phase: Parked
Reporter organization: Air Carrier
Reporter function: Captain; Pilot Flying
Human factors: Distraction; Situational Awareness
Anomaly: Deviation / Discrepancy - Procedural Published Material / Policy
Detector: Person Flight Crew
When detected: Aircraft In Service At Gate
Result: Flight Crew Became Reoriented
Contributing factors: Human Factors
Primary problem: Human Factors

Narrative: On arrival at the outstation; we were slightly behind schedule; but the flight was uneventful. We stopped short of the gate area; and the no. 1 engine was shut down. After parking; I recall placing my hand on the #2 start/stop selector to shut down the engine; but got distracted with signalling the ground crew. Shortly thereafter; while doing the shutdown checklist; I was distracted again because of a need to contact maintenance regarding oil servicing for the #1 engine; and didn't notice that we hadn't properly completed the checklist. It wasn't until after refuelling was complete that we noticed that engine 2 had not been shut down. However; at no point in time was the cockpit unattended. The first officer had completed his external inspection.Tried to minimise distractions during checklists on ground. The cockpit door is kept closed during the preflight checklists; and stays closed until shutdown checklist is complete.




Synopsis: Air carrier Captain reported he failed to shut down the #2 engine after gate arrival when he was distracted by ground crew signaling.
Date: 201905
Local time of day: 1201-1800
Location: FXE.Airport, FL
Flight conditions: VMC
Weather elements / visibility: 10
Light: Daylight
Aircraft: Small Aircraft
Operator: FBO
Operating under: Part 91
Flight plan: None
Mission: Training
Flight phase: Other Traffic pattern
Airspace: Class D FXE
ATC / advisory: Tower FXE
Second aircraft: Small Aircraft
Reporter organization: FBO
Reporter function: Single Pilot; Pilot Flying
Reporter qualification: Flight Crew Instrument; Flight Crew Commercial; Flight Crew Multiengine
Human factors: Confusion; Situational Awareness; Communication Breakdown
Anomaly: ATC Issue All Types; Conflict NMAC
Detector: Automation Aircraft TA
Result: Flight Crew Took Evasive Action
Contributing factors: Human Factors
Primary problem: Human Factors

Narrative: Upon departure from Runway 09 at Ft. Lauderdale Executive Airport for pattern work; I was at approximately 700 feet when immediately before I started my right crosswind turn ATC inquired if I had the traffic at my 1 o'clock in sight and after confirming I did; I was told to follow the traffic on the downwind. After making the turn to crosswind; I noticed a target on the TCAS coming from my 9 o'clock on a right downwind for Runway 09. At the same time; ATC asked me if I was following the traffic and I observed the other traffic pass under me by about 200 feet (per information from the TCAS). I then told ATC that I had the traffic in sight and had thought that the traffic I was supposed to follow was another aircraft that had already passed abeam while I was on my crosswind leg. When ATC told me to identify traffic at my 1 o'clock; I saw an aircraft at about my 1-2 o'clock and misidentified it as the same aircraft ATC intended for me to identify. I was also not aware that there was another aircraft behind the misidentified aircraft. In the future I will try to develop a better picture of the aircraft that are in the traffic pattern by using better scanning techniques and not being so quick to presume traffic I identified is the correct traffic.




Synopsis: Small Aircraft pilot reported an airborne conflict during departure from FXE airport.
Date: 202006
Aircraft: B737 Next Generation Undifferentiated
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Other not stated
Aircraft component: Emergency Equipment
Component problem: Design; Improperly Operated
Reporter organization: Air Carrier
Reporter function: Pilot Flying; Captain
Reporter qualification: Flight Crew Instrument; Flight Crew Multiengine; Flight Crew Air Transport Pilot (ATP)
Human factors: Other / Unknown
Anomaly: Deviation / Discrepancy - Procedural Hazardous Material Violation
Detector: Person Flight Crew
When detected: In-flight
Result: General Maintenance Action
Contributing factors: Human Factors
Primary problem: Human Factors

Narrative: The EFB is now part of the cockpit. It is an iPad with a lithium battery. The containment bag (-700) or bags (-800) are in the cabin. Heat/Fire Gloves are in the cockpit but no containment bag. Besides the EFB; the working pilots and cockpit jump-seaters may have devices with lithium batteries also. Lithium battery thermal runaway is a noted concern; that can be managed with a containment bag placed in the cockpit. Include in all cockpits one containment bag as part of the cockpit emergency equipment to pair correctly with the fire resistant gloves.




Synopsis: B-737 crew member reported emergency equipment improperly located to effectively manage a lithium battery thermal runaway.
Date: 201310
Local time of day: 0601-1200
Location: SJC.Airport, CA
Aircraft: Medium Transport; Low Wing; 2 Turboprop Eng
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Takeoff / Launch
ATC / advisory: Tower SJC
Aircraft component: Turbine Engine
Reporter organization: Air Carrier
Reporter function: Captain; Pilot Flying
Reporter qualification: Flight Crew Air Transport Pilot (ATP)
Anomaly: Aircraft Equipment Problem Critical; Ground Event / Encounter Person / Animal / Bird
Detector: Person Flight Crew
When detected: In-flight
Result: Aircraft Aircraft Damaged; Flight Crew Returned To Gate; Flight Crew Rejected Takeoff
Contributing factors: Environment - Non Weather Related
Primary problem: Environment - Non Weather Related

Narrative: On takeoff roll we had a bird strike. Aborted takeoff at 78 KTS. Returned to gate. Post flight inspection revealed significant damage to the Number 1 engine fan blades.  Try outfitting the airport with carbide cannons (they use them to scare off predators and birds of prey on turkey farms). Have them fire off before takeoffs are initiated. Just an idea.




Synopsis: Captain experiences a bird strike during takeoff and rejects at 78 KTS. Significant damage to the number one engine fan blades is noted on post flight.
Date: 201912
Location: SEA.Airport, WA
Aircraft: Medium Transport; High Wing; 2 Turboprop Eng
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Taxi
ATC / advisory: Ramp SEA
Reporter organization: Air Carrier
Reporter function: First Officer
Reporter qualification: Flight Crew Air Transport Pilot (ATP); Flight Crew Multiengine; Flight Crew Instrument
Human factors: Situational Awareness; Confusion
Anomaly: Deviation / Discrepancy - Procedural Clearance; Ground Incursion Taxiway
Detector: Person Flight Crew; Person Ground Personnel
When detected: Taxi
Result: General None Reported / Taken
Contributing factors: Chart Or Publication; Human Factors
Primary problem: Chart Or Publication

Narrative: After arriving in SEA; we were assigned Gate X. Both myself and the Captain were unfamiliar with Gate X and it appeared to be blocked by another aircraft. We ended up turning south instead of east and were immediately informed of our mistake by south ramp. While this was happening; Operations informed us of a spot change. When then proceeded south on Taxiway Whiskey and parked without further incident.More detailed diagrams of Gate X in the airport information charts; and descriptions of where to look for ground personnel for guidance into a spot would have eliminated our confusion. While we had the Jeppesen plate up it was still unclear as to where we should go.




Synopsis: Air Carrier First Officer reported a ramp incursion at SEA airport.  First Officer stated more detail is needed in the airport charts.
Date: 201812
Local time of day: 0601-1200
Location: ZZZ.Airport, US
Aircraft: EMB ERJ 145 ER/LR
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Parked
Reporter organization: Air Carrier
Reporter function: Pilot Flying; Captain
Reporter qualification: Flight Crew Multiengine; Flight Crew Air Transport Pilot (ATP); Flight Crew Instrument
Anomaly: Deviation / Discrepancy - Procedural Hazardous Material Violation; Deviation / Discrepancy - Procedural Published Material / Policy
Detector: Person Ground Personnel
When detected: Routine Inspection
Result: General None Reported / Taken
Contributing factors: Human Factors; Procedure
Primary problem: Human Factors

Narrative: I was informed by email from the safety department that we had carried Hazmat onboard our flight. This was the first notice that this occurred as there was nothing on the [cargo load report] and we had not been informed face to face that Hazmat had been loaded onboard the cargo compartment. We were also not informed by ramp personnel that any Hazmat was noticed and or removed from our baggage compartment.




Synopsis: EMB145 Captain reported post flight notification of illegal Hazmat transport on prior trip.
Date: 202006
Local time of day: 1201-1800
Location: ZZZ.Airport, US
Weather elements / visibility: 20
Light: Daylight
Aircraft: Robinson R44
Operator: Personal
Operating under: Part 91
Flight plan: None
Mission: Personal
Flight phase: Cruise
Airspace: Class G ZZZ
Aircraft component: Engine Temperature Indication
Component problem: Malfunctioning
Reporter organization: Personal
Reporter function: Pilot Flying
Reporter qualification: Flight Crew Instrument; Flight Crew Private
Human factors: Situational Awareness; Troubleshooting
Anomaly: Aircraft Equipment Problem Critical; Airspace Violation All Types; Deviation / Discrepancy - Procedural Published Material / Policy
Detector: Automation Aircraft Other Automation; Person Flight Crew
When detected: In-flight
Result: Flight Crew Landed As Precaution; Flight Crew Returned To Departure Airport
Contributing factors: Aircraft
Primary problem: Aircraft

Narrative: On a flight to ZZZ; the MR Temp caution light came on. The ambient temperature in flight was about 90 degrees F. Due to the extremely rugged terrain and lack of landing spots; I determined to land as soon as practical as specificed in the POH. The nearest safe landing spot was at location which appeared in front of me shortly after the light illuminated. The location is a meadow; and in fact; appears to be an abandoned landing strip. It also appears that this location is within the Wilderness Area. Landing is not allowed in the Wilderness Area; however; landing at ZZZ and other landing strips within the Wilderness is permitted. Due to the urgent need to determine if the over-temp was transient or indicative of imminent failure; I believe the precautionary landing was warranted. After several minutes allowing the main rotor transmission to cool down; I restarted the helicopter and observed the indicators. The MR Temp light did not illuminate again; so I determined to abort the mission to ZZZ and return to my base where an A&P/IA was available for consultation. Continuation to ZZZ would have involved further climbing to the landing strip elevation. There were no further indications of MR Temp conditions in the return flight to the base. The A&P told me that I had take prudent action by making a precautionary landing. I believe that solid training and memorization of the recommended pilot actions in the event of any warning or caution lights or indicators helped me make the right decision to perform a precautionary landing for the safety of the helicopter and its occupants. We did not see anyone at the precautionary landing spot; and I hope we did not encroach upon anyone's enjoyment of the Wilderness.




Synopsis: Pilot reported a precautionary landing in a Wilderness Area due to a Main Rotor overheat.
Date: 201209
Local time of day: 1801-2400
Location: ZZZ.Airport, US
Flight conditions: VMC
Weather elements / visibility: Haze / Smoke
Aircraft: MD-82
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Flight phase: Initial Approach
Airspace: Class G ZZZ
ATC / advisory: CTAF ZZZ
Second aircraft: Small Aircraft
Reporter organization: Air Carrier
Reporter function: Captain; Pilot Flying
Reporter qualification: Flight Crew Air Transport Pilot (ATP)
Human factors: Communication Breakdown; Situational Awareness
Anomaly: Conflict Airborne Conflict
Detector: Automation Aircraft RA; Person Flight Crew
When detected: In-flight
Result: Flight Crew Took Evasive Action
Contributing factors: Human Factors; Airport; Airspace Structure
Primary problem: Ambiguous

Narrative: We were descending on a visual approach to Runway 26 when we noted traffic on our TCAS ahead about 5 miles and below us. To avoid a TCAS RA I stopped the descent. As the aircraft captured approximately 7;000 the TCAS commanded; 'Monitor vertical speed.' At that point we had 500 FT vertical and between 500 FT to 1;000 FT lateral separation. A moment later the TCAS commanded; 'end of conflict' as the aircraft passed behind us. Shortly after I resumed our descent TCAS commanded; 'Monitor vertical speed; climb; climb.' I disconnected the autopilot and began a climb as indicated. The traffic was behind us; but no longer diverging away but remained just slightly behind us with 300 FT vertical separation as we began to climb. We again received an; 'end of conflict' message from the TCAS. By that time we were too high to continue a strait in approach and the aircraft was too close to start another descent. This aircraft may have started practicing steep turns or other maneuvers as we flew over it because it did not appear to be diverging away from us as we typically see. To get well clear of this traffic we flew level for about a minute before executing a left 360 to lose altitude and enter a stable final approach to landing on Runway 26. We had made traffic announcements on CTAF starting from at least 20 miles out indicating we were an MD80 on a strait in to Runway 26. A small aircraft which I assume was the aircraft involved in this event responded. We notified him we would remain north of the highway. He acknowledged. We assumed he would not fly north of the highway after acknowledging our communication when in fact; he seemed to loiter directly in the approach path to Runway 26 while maneuvering.




Synopsis: MD82 Captain describes a TCAS RA event during a visual approach to an uncontrolled airport. After maneuvering for the RA a 360 degree turn is required to get back on the approach path.
Date: 201904
Local time of day: 1801-2400
Location: ZZZ.Airport, US
Weather elements / visibility: 30
Light: Dusk
Aircraft: SR22
Operator: Personal
Operating under: Part 91
Flight plan: VFR
Mission: Ferry / Re-Positioning
Flight phase: Landing
Reporter organization: Personal
Reporter function: Captain; Single Pilot
Reporter qualification: Flight Crew Multiengine; Flight Crew Instrument; Flight Crew Flight Instructor
Human factors: Other / Unknown
Anomaly: Ground Event / Encounter Ground Strike - Aircraft; Ground Event / Encounter Loss Of Aircraft Control; Ground Excursion Runway
Detector: Person Flight Crew
When detected: In-flight
Result: Aircraft Aircraft Damaged; Flight Crew Took Evasive Action
Contributing factors: Airport; Environment - Non Weather Related
Primary problem: Environment - Non Weather Related

Narrative: After touching down during the landing roll I began maneuvering the aircraft to the right to avoid hitting at least one deer that I saw on the left side of the runway.  As the aircraft entered into the grass I attempted to maneuver the aircraft back onto the runway while simultaneously attempting to become airborne again when the nose gear collapsed resulting in a propeller strike and sudden stoppage.I was the only person on board; there were no injuries; and there was no damage to any other property.




Synopsis: SR22 pilot reported avoiding a deer on landing resulting in a runway excursion; nose gear collapse and prop strike.
Date: 202104
Local time of day: 1801-2400
Location: ZZZ.Airport, US
Flight conditions: VMC
Weather elements / visibility: 25
Light: Night
Aircraft: Small Aircraft; High Wing; 1 Eng; Fixed Gear
Operator: Government
Operating under: Part 91
Flight plan: None
Mission: Training
Flight phase: Landing
Airspace: Class C ZZZ
ATC / advisory: Tower ZZZ
Reporter organization: Government
Reporter function: Pilot Flying
Reporter qualification: Flight Crew Commercial; Flight Crew Flight Instructor; Flight Crew Multiengine; Flight Crew Instrument
Human factors: Communication Breakdown
Anomaly: ATC Issue All Types; Deviation / Discrepancy - Procedural Clearance; Deviation / Discrepancy - Procedural Landing Without Clearance
Detector: Person Flight Crew
When detected: In-flight
Result: Air Traffic Control Issued New Clearance; Flight Crew Requested ATC Assistance / Clarification
Contributing factors: Environment - Non Weather Related; Human Factors
Primary problem: Environment - Non Weather Related

Narrative: We did night currency at our home airport. There was one Controller for Clearance [Delivery]; Ground; and Tower. It was pretty busy with military aircraft doing night landings and airliners coming in. I had to ask the Controller to clear us to land each time. Usually they say report downwind or base and then will clear us to land or have us extend after we report. He was probably overwhelmed because he was constantly talking while working three frequencies. I wanted to report just in case it was unclear at any point if we were actually clear to land. The second landing he sounded annoyed when I asked if we were cleared to land - I had to ask because he had not cleared us. It didn't help that we were going 150 knots over the ground because of the 40 knot tail wind. It would help if there were separate people working Ground and Tower.




Synopsis: Pilot reported having to ask Controller several times if they were cleared to land during approach.  Reporter stated the Controller was probably overwhelmed working three positions/frequencies at the same time.
Date: 201603
Local time of day: 0601-1200
Location: ZZZ.Airport, US
Flight conditions: VMC
Aircraft: B767-400 and 400 ER
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Flight phase: Takeoff / Launch
Airspace: Class B ZZZ
ATC / advisory: Tower ZZZ
Aircraft component: Turbine Engine
Component problem: Malfunctioning
Reporter organization: Air Carrier
Reporter function: First Officer
Reporter qualification: Flight Crew Air Transport Pilot (ATP)
Second reporter function: Pilot Not Flying; First Officer
Anomaly: Aircraft Equipment Problem Critical; Inflight Event / Encounter Bird / Animal
Detector: Person Flight Crew
When detected: In-flight
Result: Aircraft Aircraft Damaged; Flight Crew Landed in Emergency Condition; Flight Crew Returned To Departure Airport
Contributing factors: Aircraft; Environment - Non Weather Related
Primary problem: Environment - Non Weather Related

Narrative: B767-400 flight; reduced power takeoff; at 300 feet aircraft struck large bird. Instantly heard loud noise coming from right engine. Saw right engine vibration indicator at 5.0. We immediately reduced right throttle to decrease vibration and noise; left flaps at 15; climbed to 5000 feet and informed ATC; accomplished the QRH engine failure checklist; did not shut down engine but kept it at idle. We then proceeded to QRH fuel dumping procedure; dumped all fuel from center tank and prepared to land at 355;000 lbs. which is 5000 LBS over landing weight. Made a normal landing. Shut down right engine after landing and taxied to gate with one engine.


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


Synopsis: B767-400 flight crew experienced a bird strike at 300 feet after takeoff causing fan vibration. The engine was idled but kept running and the center tank fuel was dumped; before returning to land 5;000 pounds overweight.