elihoole/asrs-aviation-reports huggingface dataset:
Date: 201202
Local time of day: 1201-1800
Location: ZZZ.Airport, US
Flight conditions: IMC
Weather elements / visibility: Icing; Snow
Light: Night
Aircraft: Regional Jet 200 ER/LR (CRJ200)
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Initial Approach
Airspace: Class D ZZZ
ATC / advisory: Tower ZZZ
Reporter organization: Air Carrier
Reporter function: First Officer; Pilot Not Flying
Reporter qualification: Flight Crew Commercial
Human factors: Situational Awareness; Workload; Confusion; Distraction; Fatigue; Human-Machine Interface
Anomaly: Deviation - Altitude Excursion From Assigned Altitude; Deviation / Discrepancy - Procedural Published Material / Policy; Inflight Event / Encounter Unstabilized Approach; Inflight Event / Encounter CFTT / CFIT
Detector: Automation Aircraft Terrain Warning; Person Flight Crew; Person Air Traffic Control
When detected: In-flight
Result: Flight Crew Became Reoriented; Flight Crew Diverted; Flight Crew Took Evasive Action; Flight Crew Executed Go Around / Missed Approach
Contributing factors: Weather; Environment - Non Weather Related; Human Factors
Primary problem: Human Factors

Narrative: We were at 2;600 FT and cleared for the approach. The Captain was pilot flying and I was pilot not flying. We were a little fast and trying to slow and configure. We captured the localizer. While tracking the localizer inbound; I preformed a landing check to the line; checked in with the Tower; and set the missed approach heading and altitude. When I looked up the Captain had the airplane in VS mode descending at 1;300 FPM. I checked the glide slope and it had not come 'alive' at all on both of our PFD's. I immediately stated 'Go Around.' Simultaneously; ATC said 'low altitude alert; check altitude.' We got the 'glide slope' aural warning and also 'terrain; terrain' aural GPWS warning. We executed a go around and diverted. We were at or just below 1;000 FT AGL when the go around was initiated. The threats were the mountainous terrain at night in icing conditions down to minimums. Also; we were on our 6th leg of the day. Errors were the pilot flying; the Captain; began a descent without a glide slope at 1;300 FPM. I will be extra vigilant when operating in these types of conditions; as I feel I already pretty much was.




Synopsis: A CRJ200 Captain was descending at 1;300 FPM and below the glideslope in mountainous terrain at night when the Terrain Warning sounded while ATC was calling low altitude alert. A go around was executed and the flight diverted.
Date: 202104
Local time of day: 1201-1800
Location: ZZZZ.Airport, FO
Flight conditions: VMC
Light: Daylight
Aircraft: Small Transport
Operator: Air Carrier
Operating under: Part 135
Flight plan: IFR
Mission: Passenger
Flight phase: Taxi
ATC / advisory: Tower ZZZZ
Aircraft component: Reciprocating Engine Assembly
Component problem: Malfunctioning
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; Time Pressure
Anomaly: Aircraft Equipment Problem Critical; Deviation / Discrepancy - Procedural Published Material / Policy; Ground Event / Encounter Fuel Issue
Detector: Person Flight Crew
When detected: Taxi
Result: Flight Crew Returned To Gate; General Evacuated; General Flight Cancelled / Delayed; General Maintenance Action
Contributing factors: Aircraft; Procedure
Primary problem: Aircraft

Narrative: While taxiing to Runway X; I noticed a GEN annunciator light on for the right engine. I then noticed the right engine had stopped. I stopped on taxiway close to the hold short line of Runway X. I notified Tower that one of my engines had failed and that we may need to get a ride back to the gate. I then told ZZZZ Ops that we may need a ride back to the gate. I made one attempt to restart the engine to taxi back to the gate; but it wouldn't start (it was likely flooded at this point). I told my two passengers that we were going to get a ride back to the gate. At about this time I noticed a stream of fuel coming from the right engine cowl drain tube. Out of an abundance of caution I decided it would be best to wait for our transportation away from the aircraft. I performed the ground evacuation memory items and walked the passengers to the grass off of [the] taxiway and called Ops. The van arrived within a few minutes of evacuating the aircraft and we were taken back to the gate. At this time I'm unsure as to why the right engine failed. As for the stream of fuel; it is likely due to the fuel pump remaining on after the engine failed. Regardless of whether or not this was the source of the fuel stream; I became distracted while coordinating transportation and forgot to turn the fuel pump off. In the future I should first focus on the aircraft and its systems before dealing with things like coordinating transportation. If the fuel pump were turned off; there is a possibility I could have avoided the evacuation part of this event.




Synopsis: Pilot reported engine failure during taxi and elected to evacuate the aircraft because of fuel streaming out of the engine drains.
Date: 201808
Local time of day: 0601-1200
Location: ZZZ.Airport, US
Flight conditions: VMC
Light: Daylight
Aircraft: Citation Excel (C560XL)
Operator: Fractional
Operating under: Part 135
Flight plan: IFR
Mission: Passenger
Flight phase: Climb
Airspace: Class C ZZZ
ATC / advisory: Tower ZZZ
Aircraft component: Turbine Engine
Component problem: Malfunctioning
Reporter organization: Air Taxi
Reporter function: Pilot Flying; Captain
Reporter qualification: Flight Crew Instrument; Flight Crew Air Transport Pilot (ATP); Flight Crew Multiengine
Human factors: Situational Awareness; Time Pressure; Troubleshooting
Anomaly: Aircraft Equipment Problem Critical
Detector: Person Flight Crew
When detected: In-flight
Result: Flight Crew Inflight Shutdown; Flight Crew Returned To Departure Airport
Contributing factors: Aircraft
Primary problem: Aircraft

Narrative: We departed with 3 passengers. At approximately 500 feet AGL a (R) LO OIL PRESS annunciator illuminated and the (R) oil pressure gauge indicted zero. At a safe altitude; power was reduced on the right engine; and the checklist was call for. Oil pressure did not respond to throttle movement and indicated 0 PSI. Therefore; we shut down the engine IAW (in accordance with) the emergency/abnormal checklist; secured it; and [advised ATC]. We returned to [the departure airport] and landed without incident. We elected to land at 19;300 LBS; 600 LBS over max landing weight.




Synopsis: Cessna Citation Excel Captain reported a complete loss of oil pressure in one engine; resulting in an engine shutdown; and a return to the departure airport.
Date: 201704
Local time of day: 0601-1200
Location: ZZZ.Airport, US
Flight conditions: VMC
Weather elements / visibility: 10
Light: Daylight
Aircraft: PA-28R Cherokee Arrow All Series
Operator: FBO
Operating under: Part 91
Flight plan: VFR
Mission: Personal
Flight phase: Landing
ATC / advisory: Tower ZZZ
Aircraft component: Main Gear
Component problem: Failed
Reporter organization: Personal
Reporter function: Single Pilot
Reporter qualification: Flight Crew Instrument; Flight Crew Private
Anomaly: Aircraft Equipment Problem Less Severe; 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
Contributing factors: Aircraft
Primary problem: Aircraft

Narrative: Upon landing; touched left main gear then right main gear; felt a 'wobble' in rear right main gear; touched nose wheel down and then felt the collapse of the right main and nose wheel which pulled me off the runway.




Synopsis: PA28R pilot reported the right and nose gears collapsed on landing resulting in a runway excursion.
Date: 201211
Local time of day: 0601-1200
Location: ZZZ.Airport, US
Aircraft: A319
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Parked
Aircraft component: Oxygen System/Crew
Reporter organization: Air Carrier
Reporter function: Captain
Reporter qualification: Flight Crew Air Transport Pilot (ATP)
Anomaly: Aircraft Equipment Problem Critical; Deviation / Discrepancy - Procedural Maintenance; Deviation / Discrepancy - Procedural Published Material / Policy
Detector: Person Maintenance
Result: General Maintenance Action
Contributing factors: Human Factors; Procedure
Primary problem: Ambiguous

Narrative: We had no discrepancies during our flight. Upon arrival at the gate a Mechanic came on the flight deck and stated that he had to perform maintenance on the aft flight attendant oxygen system. I contacted Maintenance Control to find out what this was all about. During the overnight Maintenance performed a 3 day inspection and cleared MEL 35-21-01g with the corrective action; R&R flight attendants emergency O2 container. At some point; I assume after our departure; Maintenance became aware that the O2 generator had been removed but not replaced even though it was signed off as being accomplished. The Mechanic was there to inspect and verify the situation with the O2 system. He wrote in the discrepancy column of the logbook 'inspection aft galley O2 container no generator installed' and signed off as corrective action; 'transfer to DMI IAW MEL 35-21-01l Cat B due [in three days] placard installed.' Note the difference in MEL #; the original was apparently incorrect. As a result the aircraft was not airworthy for the leg we had just flown. The flight attendants O2 panel was properly closed so the flight attendant had no indication that there was a problem. The logbook was signed off as the work was accomplished when in fact it had not been done. Also we should have been informed of the issue with the flight attendants O2 system while in flight so that we could brief the affected flight attendant of the situation and her options for O2 in the event of an emergency. As the situation was handled the flight crew and Flight Attendant C had no knowledge that her O2 system would not work if she were to need it. Communicate and coordinate with the flight crew when there is a safety of flight issue.




Synopsis: A319 Captain becomes aware after landing that a flight attendant oxygen generator was removed by Maintenance and not replaced although the logbook was signed off as being replaced. Maintenance did not inform the crew enroute had a mechanic standing by upon gate arrival.
Date: 202012
Local time of day: 0601-1200
Location: ZZZ.Airport, US
Weather elements / visibility: strong tailwinds
Aircraft: B737-700
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Final Approach
Reporter organization: Air Carrier
Reporter function: Approach; Captain; Pilot Not Flying
Reporter qualification: Flight Crew Air Transport Pilot (ATP); Flight Crew Multiengine; Flight Crew Instrument
Human factors: Human-Machine Interface; Situational Awareness
Anomaly: Deviation - Speed All Types; Deviation / Discrepancy - Procedural Clearance; Deviation / Discrepancy - Procedural Published Material / Policy; Inflight Event / Encounter CFTT / CFIT; Inflight Event / Encounter Weather / Turbulence; Inflight Event / Encounter Unstabilized Approach
Detector: Automation Aircraft Terrain Warning; Person Flight Crew
When detected: In-flight
Result: Aircraft Equipment Problem Dissipated; Flight Crew Became Reoriented; Flight Crew Overcame Equipment Problem; Flight Crew Returned To Clearance
Contributing factors: Human Factors
Primary problem: Human Factors

Narrative: While on the RNAVM XX in ZZZ1 we encountered a GPWS event. At the beginning of the approach we had a tailwind and the descent angle of the approach caused us to be a little fast starting the approach. As the pilot monitoring I should have caught this issue sooner and brought it to the attention of the PF (Pilot Flying). Because of the speed the PF disconnected the autopilot/auto throttles and slowed the plane to the proper approach speed. During the turn onto final the PF was visual with the runway and let the nose drop which caused a momentary don't sink. He corrected and the warning went away. Still with the airport visual he tried to correct on the VASI and received another momentary don't sink call at around 700 ft. We continued the approach and the landing was normal. I don't have anything to add for [this report].I have learned many lessons from this very short flight. I haven't had much ZZZ experience and my FO (First Officer) who was PF has had very little. We tried to mitigate the possible issues by having a slow cruise speed of 210 kts. and trying to get ready for the approach early. We briefed the 3.4 GP and felt we were in a good position for the approach. With the unfamiliarity of the situation and the weather in ZZZ this day I missed the strong tailwind that was making our situation worse. This put us behind and we had to play catch up. It was turbulent the whole flight and when he disconnected the AP/AT my [situational awareness] went down because I was worried about his flight path at that time. As I look back at the event and if I could do this again I would have us discontinue the approach early and come around to try again. Once we continued and got out of the [weather] and had the runway visually climbing back into it in that terrain did not seem the safest option. But if we had bailed early it would have made the situation easier the second time.




Synopsis: B737 Captain reported an uneventful landing after two GPWS alerts during approach due primary weather conditions.
Date: 201211
Local time of day: 1201-1800
Location: ZZZ.ARTCC, US
Aircraft: MD-82
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
ATC / advisory: Center ZZZ
Aircraft component: Oxygen System/Crew
Component problem: Failed
Reporter organization: Air Carrier
Anomaly: Aircraft Equipment Problem Critical
Detector: Person Flight Crew
When detected: In-flight
Result: Flight Crew Diverted
Contributing factors: Aircraft
Primary problem: Aircraft

Narrative: The O2 system was normal during the departure station preflight. While enroute the cockpit crew determined the flight crew O2 bottle was empty. They requested descent from ATC and then received a clearance to divert to the nearest suitable airport after consulting with Dispatch.




Synopsis: An MD-82 diverted to a nearby airport when they noted the flight crew oxygen pressure was zero.
Date: 201407
Local time of day: 0601-1200
Location: ZZZ.ARTCC, US
Flight conditions: VMC
Aircraft: A320
Operator: Air Carrier
Operating under: Part 121
Flight phase: Climb
Airspace: Class A ZZZ
ATC / advisory: Center ZZZ
Aircraft component: Turbine Engine
Component problem: Failed
Reporter organization: Air Carrier
Reporter function: Captain; Pilot Flying
Anomaly: Aircraft Equipment Problem Critical
Detector: Automation Aircraft Other Automation; Person Flight Crew
When detected: In-flight
Result: Flight Crew Diverted; Flight Crew Inflight Shutdown; Flight Crew Landed in Emergency Condition
Contributing factors: Aircraft
Primary problem: Aircraft

Narrative: Climbing through FL240; we experienced a thrust loss on Number 1 Engine with associated yaw. Coordinated to stop climb and descended back to FL240. We ran checklists which directed us to turn on engine and wing anti-ice and then check to see if engine thrust could be regained. Engine anti-ice came on normally but wing anti-ice would not come on with amber caret on system page. Thrust would not recover. We left the engine at idle with normal parameters; consulted with Dispatch and coordinated a divert. On short final; we got an Engine Fail ECAM. First Officer ran the ECAM and shut down the Number 1 Engine. Landed uneventfully and taxied to gate under our own power after consulting with Fire Department. Approximately 10;000 LBS overweight for landing which we entered into logbook.




Synopsis: A320 Captain experiences a loss of thrust on the Number One Engine climbing through FL240 and the aircraft is leveled there to asses. QRH procedures are complied with; without success and the flight diverts to a suitable airport with the engine at idle. An Engine Fail ECAM is annunciated on short final and the engine is shut down.
Date: 201807
Location: HND.Airport, NV
Flight conditions: VMC
Weather elements / visibility: 10
Light: Daylight
Aircraft: Aerobatic
Operator: Personal
Operating under: Part 91
Flight plan: VFR
Mission: Aerobatics
Flight phase: Descent; Climb; Cruise
Airspace: Class E L30
Second aircraft: Any Unknown or Unlisted Aircraft Manufacturer
Reporter organization: Personal
Reporter function: Pilot Flying; Single Pilot
Reporter qualification: Flight Crew Instrument; Flight Crew Flight Instructor; Flight Crew Commercial; Flight Crew Multiengine
Human factors: Situational Awareness
Anomaly: Conflict NMAC
Detector: Person Flight Crew
When detected: In-flight
Result: Flight Crew Took Evasive Action
Contributing factors: Airspace Structure; Procedure
Primary problem: Airspace Structure

Narrative: While flying aerobatic maneuvers; I experienced a near miss with a jet maneuvering between six thousand and seven thousand feet. Shortly after departing HND; I proceeded to an area southeast of the lateral limits of the Class B; approximately 20 miles southeast of the Henderson airport. After a series of maneuvers; which included clearing turns; I proceeded to climb vertically. As I climbed; a jet passed below me; headed in a northwesterly direction. At the time I saw the jet; I could see that my momentum would take me over his flight path; however; the distance was unacceptably close. There is a high concentration of aerobatic activity in this area and I believe that there should be a caution placed on the Las Vegas sectional and TAC chart. I will be contacting the FAA to start this process.




Synopsis: A pilot performing acrobatic maneuvers reported a NMAC in the area southeast of HND.
Date: 202010
Aircraft: B787-900
Operator: Air Carrier
Reporter organization: Air Carrier
Reporter function: Other / Unknown
Human factors: Situational Awareness; Training / Qualification
Anomaly: Aircraft Equipment Problem Critical; Deviation / Discrepancy - Procedural Published Material / Policy
Detector: Person Flight Crew
When detected: In-flight
Result: Flight Crew Returned To Departure Airport
Contributing factors: Human Factors; Procedure
Primary problem: Human Factors

Narrative: I believed [I] closed cap and tab locked the right engine oil fill cap but [it] wasn't locked. Then right engine [started] losing oil and pressure.[I recommend] to confirm cap closed and locked before closing service panel or panel can't close unless cap is locked.




Synopsis: Maintenance Technician reported a 787-900 engine oil fill cap was not closed and locked before departure.
Date: 201905
Local time of day: 0601-1200
Location: DEN.Airport, CO
Flight conditions: VMC
Aircraft: B737 Next Generation Undifferentiated
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Descent
Airspace: Class B DEN
ATC / advisory: TRACON D01
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
Anomaly: ATC Issue All Types; Deviation - Track / Heading All Types; Deviation / Discrepancy - Procedural Clearance
Detector: Person Air Traffic Control; Person Flight Crew
When detected: In-flight
Result: Air Traffic Control Issued Advisory / Alert; Air Traffic Control Issued New Clearance; Flight Crew Became Reoriented; Flight Crew Returned To Clearance
Contributing factors: Human Factors; Procedure
Primary problem: Human Factors

Narrative: Descending into Denver we were cleared to descend via the ANCHR4 Arrival and told to expect the RNAV Zulu RWY 35R. We loaded that approach into the FMS and sequenced the FMC from DOGGG way point. Just prior to the turn at FULLA the controller changed the approach to a Visual RWY 35R; so we loaded the FMC with the ILS 35R for back up guidance. The controller gave that clearance to expect the Visual about 6 miles from FULLA - which is the last point prior to a southbound 173 turn. In reprogramming the approach we did not get the FMC programmed in time for the FMC to make that turn. We immediately noticed the airplane not turning so I disconnected the auto pilot and made the southbound turn to 173 while leveling off at 11;000'. In the turn the controller asked if we were turning and replied that we were. The First Officer was still programing the FMC with the correct RWY while in the turn so we asked for a vector and the controller gave us a 170 heading. We don't think we deviated more than 1/8 to 1/4 mile from the arrival path. FMC reprogram completed just prior to DOGGG and Visual Approach complete without incident.




Synopsis: B737NG Captain reported a track deviation occurred on arrival into DEN following a late runway change.
Date: 202007
Local time of day: 1801-2400
Location: ZZZ.Airport, US
Aircraft: Commercial Fixed Wing
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Parked
Reporter organization: Air Carrier
Reporter function: Flight Attendant In Charge
Reporter qualification: Flight Attendant Current
Anomaly: Deviation / Discrepancy - Procedural Published Material / Policy; Flight Deck / Cabin / Aircraft Event Passenger Misconduct
Detector: Person Passenger
When detected: In-flight
Result: General None Reported / Taken
Contributing factors: Company Policy; Environment - Non Weather Related; Human Factors
Primary problem: Company Policy

Narrative: We had an Unaccompanied Minor (UM); on the descent; minor proceeds to tell FA B that Mom has COVID and that's why minor is on the way to ZZZ to stay with family. Both FA's were assisting minor plus a passenger sitting across. This child could possibly be a carrier.




Synopsis: Flight Attendant was told by an unaccompanied minor that the child's mother had COVID-19 and the child was on the way to stay with family.