elihoole/asrs-aviation-reports huggingface dataset:
Date: 201711
Local time of day: 1801-2400
Location: ZZZZ.Airport, FO
Flight conditions: VMC
Aircraft: B747-400
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Flight phase: Landing
ATC / advisory: Tower ZZZZ
Reporter organization: Air Carrier
Reporter function: Captain; Pilot Not Flying
Reporter qualification: Flight Crew Air Transport Pilot (ATP)
Second reporter function: First Officer; Pilot Flying
Anomaly: Deviation / Discrepancy - Procedural Published Material / Policy; Ground Event / Encounter Other / Unknown
Detector: Person Flight Crew
When detected: In-flight
Result: General Maintenance Action
Contributing factors: Procedure
Primary problem: Procedure

Narrative: We were on the ILS [approach]. Weather conditions were variable winds. Approach was normal and stable. Landing was hard due to insufficient flare by the First Officer. The firm landing resulted in a bounce back in the air; after which I took the aircraft from the First Officer and recovered the landing. A go-around was not performed due to our very low proximity to the runway; the aircraft being in a good position for a second proper touchdown; and in my opinion a go-around could have resulted in a possibly worse outcome than a full landing.


Second narrative: Arrival and approach were in accordance with company SOP. A 'hard landing' was experienced upon touchdown.


Synopsis: B747 flight crew reported a hard landing; resulting from insufficient flare; caused the inertia escape reels to dislodge from their housings.
Date: 201707
Local time of day: 1201-1800
Location: ZZZ.Airport, US
Flight conditions: Mixed
Weather elements / visibility: Rain; 5
Light: Daylight
Aircraft: Citation II S2/Bravo (C550)
Operator: Personal
Operating under: Part 91
Flight plan: IFR
Mission: Ferry / Re-Positioning
Flight phase: Landing
Airspace: Class E ZZZ
ATC / advisory: CTAF ZZZ
Aircraft component: Turbine Engine Thrust Reverser
Component problem: Malfunctioning
Reporter organization: Personal
Reporter function: Captain; Pilot Flying
Reporter qualification: Flight Crew Air Transport Pilot (ATP); Flight Crew Flight Instructor; Flight Crew Instrument; Flight Crew Multiengine
Human factors: Time Pressure
Anomaly: Aircraft Equipment Problem Less Severe; Ground Excursion Runway; Inflight Event / Encounter Weather / Turbulence
Detector: Person Flight Crew
When detected: Taxi
Result: Flight Crew Took Evasive Action
Contributing factors: Aircraft; Weather; Procedure; Airport
Primary problem: Ambiguous

Narrative: We landed on speed at the runway threshold. I applied brakes and actuated the speed brakes and thrust reversers as per the normal procedures.  There was an inordinate time delay for the thrust reversers to deploy.  I used maximum reverse thrust the aircraft failed to stop prior to the end of the runway.There were no fatalities or injuries as a result of this incident. There was no damage to the aircraft. There was no damage to the airport assets.




Synopsis: A CE-550 Captain reported after landing on a wet runway; he applied brakes; extended the speed brakes and selected reverse which activated slowly. The aircraft ran off the end of 4;100 ft runway without injury or damage.
Date: 201708
Local time of day: 1801-2400
Location: ZZZ.Airport, US
Light: Dusk
Aircraft: B757 Undifferentiated or Other Model
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: Hydraulic Main System
Component problem: Failed
Reporter organization: Air Carrier
Reporter function: Captain
Reporter qualification: Flight Crew Air Transport Pilot (ATP)
Anomaly: Aircraft Equipment Problem Critical
Detector: Automation Aircraft Other Automation
When detected: In-flight
Result: Flight Crew Diverted; Flight Crew Landed in Emergency Condition
Contributing factors: Aircraft
Primary problem: Aircraft

Narrative: In cruise FL360; L HYD (hydraulic) systems failure and total L system loss. We diverted and coordinated with company; and ATC. Emergency configuration procedures for gear; flaps and landing on longest runway. Aircraft was towed to gate and event ended.




Synopsis: B757 Captain reported a left hydraulic system failure at FL360 and diverted to the nearest suitable airport.
Date: 201906
Location: ORD.Airport, IL
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: Landing
ATC / advisory: Tower ORD
Reporter organization: Air Carrier
Reporter function: Captain
Reporter qualification: Flight Crew Air Transport Pilot (ATP); Flight Crew Instrument; Flight Crew Multiengine
Human factors: Distraction; Situational Awareness
Anomaly: Ground Event / Encounter Other / Unknown
Detector: Person Flight Crew
When detected: In-flight
Result: General None Reported / Taken
Contributing factors: Airport
Primary problem: Airport

Narrative: The rubber deposits on Runway 28C need to be removed. The runway markings are difficult to see when landing.




Synopsis: B737 Captain reported runway markings at ORD airport are difficult to see during landing due to rubber deposit buildup.
Date: 201405
Local time of day: 1801-2400
Location: ZZZ.Airport, US
Flight conditions: VMC
Weather elements / visibility: 10
Light: Daylight
Aircraft: Baron 55/Cochise
Operator: Personal
Operating under: Part 91
Flight plan: VFR
Mission: Personal
Flight phase: Landing
Airspace: Class D ZZZ
ATC / advisory: Tower ZZZ
Aircraft component: Main Gear
Component problem: Failed
Reporter organization: Personal
Reporter function: Pilot Flying; Single Pilot
Reporter qualification: Flight Crew Private; Flight Crew Multiengine; Flight Crew Instrument
Human factors: Situational Awareness
Anomaly: Aircraft Equipment Problem Less Severe; Ground Event / Encounter Ground Strike - Aircraft; Inflight Event / Encounter Loss Of Aircraft Control
Detector: Person Flight Crew
When detected: Taxi
Result: Aircraft Aircraft Damaged; General Evacuated
Contributing factors: Aircraft
Primary problem: Aircraft

Narrative: I departed late afternoon and made a normal flight to a nearby airport. For the return flight; I departed Runway 17R; made a left turnout and flew directly to my home airport. [I] was cleared by the Tower at my destination for right downwind visual approach to Runway 19. Approach was normal and landing checklist was completed; gear was verified in the down position with three green lights. The wind was within 10 degrees of runway heading at approximately 9 KTS with gusts to 15 KTS. Touchdown was normal. On rollout; the aircraft became uncontrollable; veering to the left. All attempts to keep the aircraft on the runway failed; and the aircraft skidded into the grass. At some point after touchdown; the left main gear folded; causing the left propeller; flap and wingtip to impact the terrain. When the aircraft came to a stop; I verified mixture levers were in the cutoff position; shut off the magnetos and master; put the fuel valves in the off position; and exited the aircraft. I made a verbal report to the Tower from a phone in the FBO.




Synopsis: During roll out after a normal landing; a BE-55 left main landing gear collapsed causing the aircraft to skid off the runway damaging the propeller; flap and wing tip but not injuring the pilot who evacuated the aircraft after securing it.
Date: 201211
Local time of day: 1201-1800
Light: Daylight
Aircraft: Regional Jet 200 ER/LR (CRJ200)
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: Cockpit Window
Component problem: Malfunctioning
Reporter organization: Air Carrier
Reporter function: Captain; Pilot Flying
Reporter qualification: Flight Crew Air Transport Pilot (ATP)
Anomaly: Aircraft Equipment Problem Critical
Detector: Person Flight Crew
When detected: In-flight
Result: Aircraft Aircraft Damaged; Flight Crew Diverted; Flight Crew Landed in Emergency Condition; General Declared Emergency
Contributing factors: Aircraft
Primary problem: Aircraft

Narrative: Cruise at FL340. Received L WSHLD HEAT caution MSG. Performed QRH and MSG did not reset. Noticed small damage in  bottom left of left windshield. Approximately 1 to 2 minutes later outer layer of windshield shattered with a loud pop. Performed descent and accomplished QRH for windshield damage. Declared Emergency and diverted. First Officer performed landing due to lack of visibility out of left windshield. Landed otherwise normally and taxied to gate.




Synopsis: After a CRJ-200 EICAS alerted L WSHLD HEAT which would not reset; the windshield outer layer shattered so an emergency was declared; the QRH completed and the First Officer conducted the landing at the divert airport.
Date: 202201
Local time of day: 0001-0600
Location: ZZZ.Airport, US
Flight conditions: VMC
Light: Night
Aircraft: Airliner 99
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Cargo / Freight / Delivery
Flight phase: Climb; Initial Climb
Airspace: Class D ZZZ
ATC / advisory: Tower ZZZ
Aircraft component: Gear Lever/Selector
Component problem: Malfunctioning
Reporter organization: Air Carrier
Reporter function: Pilot Flying; Captain
Reporter qualification: Flight Crew Instrument; Flight Crew Multiengine; Flight Crew Commercial
Human factors: Troubleshooting
Anomaly: Aircraft Equipment Problem Critical
Detector: Person Flight Crew
When detected: In-flight
Result: Air Traffic Control Provided Assistance; Flight Crew Overcame Equipment Problem; Flight Crew Returned To Departure Airport; General Flight Cancelled / Delayed; General Maintenance Action
Contributing factors: Aircraft
Primary problem: Aircraft

Narrative: Shortly after gear retraction; I heard an electrical pop and looked down to see a shower of sparks coming from beneath the instrument panel raining down on my legs. I immediately requested left traffic to return to land on Runway XXR at ZZZ. After the initial pop and sparking; there were no further indications of malfunctioning equipment or any signs of smoke or electrical smell. I returned to land without further incident. [Tower called for fire rescue]. The equipment followed me from the runway to the parking spot. The firemen collected my information and used a thermal camera to look for hot spots on the panel.




Synopsis: Beech 99 Captain reported a shower of sparks from behind the control panel after takeoff and returning to the departure airport.
Date: 201702
Local time of day: 1201-1800
Location: MKE.TRACON, WI
Light: Daylight
Aircraft: B737-700
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Climb
ATC / advisory: TRACON MKE
Reporter organization: Air Carrier
Reporter function: Pilot Flying; Captain
Reporter qualification: Flight Crew Air Transport Pilot (ATP)
Human factors: Situational Awareness; Communication Breakdown
Second reporter function: Pilot Not Flying; First Officer
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 Provided Assistance; Flight Crew Returned To Clearance
Contributing factors: ATC Equipment / Nav Facility / Buildings; Human Factors; Procedure
Primary problem: Human Factors

Narrative: We were being vectored and Departure Control issued us direct to HAWKN. We did not see that fix in our FMC. The First Officer (FO) Pilot Monitoring (PM) queried Departure Control and they asked if we had gotten our clearance via Pre-Departure Clearance (PDC) or verbally. The FO replied that we got it via PDC. Departure then issued us direct HAWKN..ROBBY....[on course].  We loaded that in the FMC and proceeded on. We reviewed the PDC en route and I realized that I had missed the amended routing on the PDC. Later; Center gave us a phone number for Milwaukee Approach to call after landing.


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


Synopsis: B737 Flight crew reported that ATC had to correct their route shortly after departure. Crew reported it was an issue with the Pre-Departure Clearance form of Clearance Delivery.
Date: 202110
Local time of day: 1201-1800
Location: ZZZ.Airport, US
Flight conditions: VMC
Light: Night
Aircraft: Citationjet (C525/C526) - CJ I / II / III / IV
Operator: Personal
Operating under: Part 91
Flight plan: IFR
Mission: Passenger
Flight phase: Descent
Aircraft component: Cargo Compartment Fire/Overheat Warning
Component problem: Malfunctioning
Reporter organization: Personal
Reporter function: Captain
Reporter qualification: Flight Crew Air Transport Pilot (ATP); Flight Crew Flight Instructor; Flight Crew Instrument; Flight Crew Multiengine
Anomaly: Aircraft Equipment Problem Critical; Deviation / Discrepancy - Procedural Published Material / Policy; Flight Deck / Cabin / Aircraft Event Smoke / Fire / Fumes / Odor
Detector: Person Flight Crew
When detected: In-flight
Result: Flight Crew Landed in Emergency Condition
Contributing factors: Aircraft
Primary problem: Aircraft

Narrative: Aircraft was on descent for ZZZ. A baggage smoke annunciation illuminated. The check list was run and [priority handling was requested]. The aircraft landed at ZZZ. Aircraft was met by ZZZ CFR (Crash Fire Rescue). At my request CFR conducted an infrared sweep of the aircraft. No issues were found. The aircraft was taxied to an FBO where the aircraft was determined by fire crew and myself of no sign of smoke. The aircraft master switch was turned off when aircraft was shutdown and could not replicate condition. No annunciation was present at restart. An aggressive inspection was conducted. Additionally the baggage smoke indicators are considered INOP per AFM (Airplane Flight Manual) and aircraft placards.




Synopsis: Citation Captain reported a baggage compartment smoke indication on descent. After landing; an inspection did not find any evidence of smoke.
Date: 202005
Local time of day: 0601-1200
Location: ZZZZ.ARTCC, FO
Flight conditions: IMC
Weather elements / visibility: Rain; 3
Light: Night
Aircraft: Gulfstream IV / G350 / G450
Operator: Fractional
Operating under: Part 135
Flight plan: IFR
Mission: Passenger
Flight phase: Descent
ATC / advisory: Center ZZZZ
Aircraft component: Air Data Computer
Component problem: Malfunctioning
Reporter organization: Air Carrier
Reporter function: Pilot Flying; Captain
Reporter qualification: Flight Crew Instrument; Flight Crew Flight Instructor; Flight Crew Air Transport Pilot (ATP); Flight Crew Multiengine
Human factors: Workload; Distraction; Troubleshooting
Second reporter function: Captain; Pilot Not Flying
Anomaly: Aircraft Equipment Problem Critical
Detector: Automation Aircraft Other Automation; Person Flight Crew
When detected: In-flight
Result: Flight Crew FLC complied w / Automation / Advisory; Flight Crew Landed in Emergency Condition
Contributing factors: Aircraft
Primary problem: Aircraft

Narrative: During cruise flight at FL450 about one hour prior to decent we experienced a DADC (Digital Air Data Computer) fault. A DADC Miscompare CAS Message was displayed and the appropriate AFM Quick Reference Handbook procedure was accomplished. We continued the flight with both Captain and First Officer operating with a single DADC. As we commenced our decent into ZZZZ; the Air Data information displayed by the remaining DADC did not agree with the Standby Flight Instruments; all automation was disengaged and the remainder of the flight was conducted by reference to the Standby Flight Instruments. We [advised ATC] and continued to land on Runway XX.


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


Synopsis: G-IV flight crew reported an air data computer failure and the arrival flown using standby instruments.
Date: 202111
Local time of day: 0601-1200
Location: 1Z1.Airport, AZ
Flight conditions: VMC
Light: Daylight
Aircraft: Small Aircraft
Operator: Personal
Operating under: Part 91
Flight plan: None
Mission: Personal
Flight phase: Descent
Airspace: Special Use GRAND CANYON SPECIAL FLIGHT RULES AREA
Reporter organization: Personal
Reporter function: Pilot Flying; Single Pilot
Reporter qualification: Flight Crew Air Transport Pilot (ATP)
Human factors: Situational Awareness
Anomaly: Airspace Violation All Types; Deviation / Discrepancy - Procedural FAR; Deviation / Discrepancy - Procedural Published Material / Policy
Detector: Person Flight Crew
When detected: In-flight
Result: Flight Crew Exited Penetrated Airspace
Contributing factors: Environment - Non Weather Related; Human Factors
Primary problem: Ambiguous

Narrative: Descent into 1Z1 for a fly-in; many aircraft approached field at same time.  I descended to avoid traffic and was on the edge of the restricted Grand Canyon airspace.  Tried to stay with 3 miles but may have defended a early.

Callback: Reporter confirmed it was the Grand Canyon Special flight rules area. Attempted to remain clear of the restricted area but was unsure of exact location and prioritized remaining clear of other inbound traffic.



Synopsis: GA pilot reported a possible Grand Canyon special flight rules area airspace entry while trying to avoid other aircraft in the area.
Date: 201708
Local time of day: 0601-1200
Location: SBD.Airport, CA
Flight conditions: VMC
Weather elements / visibility: 10
Light: Daylight
Aircraft: Light Transport
Operator: Air Taxi
Operating under: Part 135
Flight plan: IFR
Mission: Passenger
Flight phase: Final Approach
Airspace: Class D SBD
ATC / advisory: Tower SBD
Reporter organization: Air Taxi
Reporter function: Captain; Pilot Flying
Reporter qualification: Flight Crew Air Transport Pilot (ATP); Flight Crew Multiengine; Flight Crew Flight Instructor; Flight Crew Flight Engineer
Human factors: Fatigue
Anomaly: Deviation - Track / Heading All Types; Deviation / Discrepancy - Procedural Clearance; Deviation / Discrepancy - Procedural Published Material / Policy
Detector: Person Flight Crew
When detected: In-flight
Result: Flight Crew Executed Go Around / Missed Approach
Contributing factors: Human Factors
Primary problem: Human Factors

Narrative: Approaching SBD from the north; we were cleared for the visual approach to runway 24 at an altitude of greater than 10000 feet. Our position was on a high upwind for runway 24; but since we arrived on runway 6 that morning; I heard 'cleared for visual approach' and did not pay attention to the 'runway 24' part of the transmission.Upon seeing the runway far below and to my left; I set up a left pattern with a steep approach to runway 6. When we were on final; approximately 2 miles out; the co-pilot questioned the runway; and I realized I had set up for the wrong runway. I executed a go-around; entered downwind for runway 24; and completed a normal landing.I believe among the causes for this error were: Fatigue; complacency due to familiarity with the area and our earlier experience at the airport; and our relative position and altitude when cleared for the visual approach. Our prime concern on the descent was to make a smooth and rapid descent while ensuring the comfort of our passengers.The fatigue factor can be attributed to our [early] duty time start; the co-pilot's busier schedule (he had flown several times in the past few days; and though he had legal rest; was very tired from the start); and my poor sleep in the hours before the flight.This could have been avoided by a more thorough briefing as we approached the airport. This would have given my co-pilot a heads-up that I was about to set up on the wrong runway. We discussed the event after our passengers had been picked up; and plan to be even more vigilant when we know ourselves to be fatigued.




Synopsis: Corporate Jet Captain reported setting up for the wrong runway at SBD; executed a missed approach and completed a normal landing on the runway in use.
Date: 202104
Local time of day: 1201-1800
Location: M98.TRACON, MN
Aircraft: Small Aircraft; High Wing; 1 Eng; Fixed Gear
Operator: Personal
Operating under: Part 91
Flight plan: IFR
Flight phase: Cruise
Airspace: Class E ZMP
ATC / advisory: TRACON M98
Reporter organization: Government
Reporter function: Approach
Reporter qualification: Air Traffic Control Fully Certified
Human factors: Confusion; Situational Awareness
Anomaly: ATC Issue All Types; Deviation / Discrepancy - Procedural Clearance; Deviation / Discrepancy - Procedural Published Material / Policy; Inflight Event / Encounter CFTT / CFIT
Detector: Person Air Traffic Control
When detected: In-flight
Result: Air Traffic Control Issued New Clearance
Contributing factors: Chart Or Publication; Human Factors; Airspace Structure; Procedure
Primary problem: Human Factors

Narrative: Aircraft X [was] cleared for an RNAV GPS Runway 32 approach into MIC and [I] instructed [the] aircraft to cross a fix at 3;000 ft. I checked [the] chart twice on this new approach and was not comfortable with 3;000 ft. and climbed the aircraft to 3;500 ft. until [I] passed the obstruction of some antennas. Upon further review; the aircraft should have crossed WAKUD at 3;400 ft. for [the] MVA of 3;500 ft. by the chart. I have reviewed the chart and SOP's to become familiar with this new approach as well as obstructions in airspace for currency. [I] also reviewed IFR chart legends and procedures in general to make sure [I was] reading them correctly.




Synopsis: A TRACON Controller reported clearing an aircraft for a new approach and issued a crossing restriction below the MVA.