elihoole/asrs-aviation-reports huggingface dataset:
Date: 201904
Local time of day: 1201-1800
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: Final Approach
Airspace: Class B DEN
ATC / advisory: TRACON D01
Reporter organization: Air Carrier
Reporter function: First Officer; Pilot Not Flying
Reporter qualification: Flight Crew Multiengine; Flight Crew Instrument; Flight Crew Air Transport Pilot (ATP); Flight Crew Commercial
Human factors: Situational Awareness
Second reporter function: Pilot Flying; Captain
Anomaly: Deviation - Track / Heading All Types; Deviation / Discrepancy - Procedural Clearance; Deviation / Discrepancy - Procedural Published Material / Policy
Detector: Person Flight Crew; Person Air Traffic Control
When detected: In-flight
Result: Air Traffic Control Issued New Clearance; Flight Crew Returned To Clearance; Flight Crew Became Reoriented
Contributing factors: Procedure; Human Factors
Primary problem: Human Factors

Narrative: Just prior to the IAF on RNAV (RNP) Z Runway 35R; I thought I heard (and read back) 'Expect RNAV 35R.' I then queried whether ATC said cleared the approach; to which they answered 'Affirmative; cleared the approach.' We set the final approach fix altitude and just as we were passing the IAF noticed that we had not closed the discontinuity between the arrival and the approach. The aircraft did not follow the lateral line of the approach and we requested vectors for final. The remainder of the approach and landing was uneventful.


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


Synopsis: B737 NG flight crew reported a track deviation occurred on the RNAV (RNP) Z approach to 35R in DEN when they failed to notice a discontinuity in the FMC programmed route.
Date: 202108
Location: ZZZ.Airport, US
Weather elements / visibility: calm; 25
Light: Daylight
Aircraft: PA-18/19 Super Cub
Operator: Personal
Operating under: Part 91
Flight plan: None
Mission: Personal
Flight phase: Landing
Airspace: Class D ZZZ
Aircraft component: Main Gear
Component problem: Malfunctioning
Reporter organization: Personal
Reporter function: Pilot Flying; Single Pilot
Reporter qualification: Flight Crew Commercial; Flight Crew Multiengine
Anomaly: Aircraft Equipment Problem Critical; Ground Event / Encounter Ground Strike - Aircraft; Ground Event / Encounter Loss Of Aircraft Control
Detector: Person Flight Crew
When detected: Other Landing
Result: Aircraft Aircraft Damaged; General Flight Cancelled / Delayed; General Maintenance Action
Contributing factors: Aircraft
Primary problem: Aircraft

Narrative: Left gear collapsed upon landing. A part failed and allowed the gear to go up. I lowered the gear on downwind; all indicators showed gear down and locked. Upon touchdown; I slowly veered off the runway to the left. I immediately communicated my situation on the radio; still all indicators showed gear down and locked.




Synopsis: Pilot reported the left main gear collapsed on landing causing a runway excursion.
Date: 201908
Local time of day: 1201-1800
Location: ZZZ.Airport, US
Flight conditions: VMC
Light: Daylight
Aircraft: Skyhawk 172/Cutlass 172
Operator: FBO
Operating under: Part 91
Flight plan: VFR
Mission: Training
Flight phase: Landing
ATC / advisory: Tower ZZZ
Reporter organization: FBO
Reporter function: Single Pilot
Reporter qualification: Flight Crew Student
Human factors: Training / Qualification
Anomaly: Ground Event / Encounter Loss Of Aircraft Control; Ground Excursion Runway; Inflight Event / Encounter Weather / Turbulence
Detector: Person Flight Crew
When detected: In-flight
Result: Flight Crew Regained Aircraft Control
Contributing factors: Weather
Primary problem: Weather

Narrative: I was flying solo cross-country and when coming in to land on Runway XXL at ZZZ; winds were 060 at 6 knots; but gusting 16 knots. Came in to land; controlled safe landing up until just before the wheels touched down; where I was blown off to the left of the runway. I pulled up on the yoke as to not catch the front gear in the tall grass and then turned to the right and braked on the side/access road to the left of the runway (to the right of a nearby pond). In terms of human factors; I should have gone around and waited for the winds to die down before making an approach; knowing the winds had the potential to gust up to 16 knots.




Synopsis: C172 Student Pilot reported strong surface wind on landing that resulted in a runway excursion.
Date: 201907
Location: ZZZ.Airport, US
Light: Daylight
Aircraft: A321
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Parked
Airspace: Class B ZZZ
Reporter organization: Air Carrier
Reporter function: Flight Attendant (On Duty)
Reporter qualification: Flight Attendant Current
Human factors: Distraction; Training / Qualification
Anomaly: Aircraft Equipment Problem Less Severe; Deviation / Discrepancy - Procedural Published Material / Policy
Detector: Person Flight Attendant
When detected: Aircraft In Service At Gate
Result: General Maintenance Action
Contributing factors: Procedure; Human Factors
Primary problem: Procedure

Narrative: I; FA2 (Flight Attendant 2); had an [Inadvertent Slide Deployment] at 4r. I bent down to move a recycle bag out of the way before monitor/challenge & disarming door. I kneeled down and secured myself by reaching backward grabbing a hold of the door handle mistakenly. I pulled myself up along with the door handle and the door opened in the armed mode. I then immediately used the interphone to notify FA1 who said she would relay info to captain. Once the passengers all deplaned; the entire crew and CA stayed on the plane to be met by [flight operations personnel] and maintenance for further instruction.




Synopsis: A321 Flight Attendant reported inadvertent slide deployment during deplaning.
Date: 201501
Local time of day: 1201-1800
Location: PHX.Airport, AZ
Flight conditions: VMC
Light: Dusk
Aircraft: B737-700
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Final Approach
Airspace: Class B PHX
ATC / advisory: Tower PHX
Reporter organization: Air Carrier
Reporter function: First Officer; Pilot Not Flying
Reporter qualification: Flight Crew Air Transport Pilot (ATP)
Human factors: Situational Awareness
Anomaly: Deviation - Altitude Overshoot; Deviation - Altitude Crossing Restriction Not Met; Deviation / Discrepancy - Procedural Clearance; Inflight Event / Encounter CFTT / CFIT; Inflight Event / Encounter Unstabilized Approach
Detector: Automation Aircraft Terrain Warning; Person Flight Crew
When detected: In-flight
Result: Flight Crew Executed Go Around / Missed Approach
Contributing factors: Human Factors
Primary problem: Human Factors

Narrative: We were on a right base to final for Runway 26 at 4;000 feet MSL and 210 KIAS.  We were cleared for and accepted the Visual Approach. We were directed to maintain 170 KIAS to PRUNN.  As we intercepted final course in LNAV mode; I queried the Pilot Flying (PF) about selecting VOR/LOC in preparation for selecting APP.  He stated that we could continue in LNAV as he proceeded to program the 170 KIAS speed into the FMC for PRUNN.  As we crossed JAGAL; I stated that he should begin the descent to 3;000 feet MSL. At this point we were clean; 0 Flaps and Landing gear up.  I again called for the descent; at which point the PF came heads up; noted our position; and called for landing gear down; extended the speed brake and nosed the aircraft over in an attempt to acquire the glide path.  We continued past PRUNN well above 3;000 feet MSL with landing gear and speed brake extended.  Approaching approximately 2;500 feet - 2;300 feet MSL; we both commented that a go-around would be required.  Immediately thereafter; the go-around command was called at approximately 1;300 feet - 1;200 feet AGL.  As we began to execute the go-around; the GPWS alert PULL UP sounded and I noted a descent rate of approximately 3;500 feet FPM.  The go-around; approach and landing were uneventful.Preventative Measures: Continue to emphasize use of the appropriate level of automation as well as when it is and is not appropriate for the Pilot Flying to be heads down programming the FMC.  Consideration should also be given to standardizing procedures of who (PF vice Pilot Monitoring) should be responsible for programming and executing the FMC.  One option would be to have the Pilot Monitor (PM) input FMC changes; PF crosscheck; PM execute.




Synopsis: B737-700 First Officer reported an unstabilized approach to PHX airport that resulted in a GPWS alert and a go-around.
Date: 201405
Local time of day: 1801-2400
Location: DTW.Airport, MI
Flight conditions: VMC
Light: Daylight
Aircraft: Medium Large Transport
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Taxi
Airspace: Class B DTW
ATC / advisory: Tower DTW
Second aircraft: B737 Undifferentiated or Other Model
Reporter organization: Government
Reporter function: Ground
Reporter qualification: Air Traffic Control Fully Certified
Human factors: Communication Breakdown
Second reporter function: First Officer
Anomaly: Conflict Ground Conflict; Critical; Deviation / Discrepancy - Procedural FAR; Deviation / Discrepancy - Procedural Clearance; Deviation / Discrepancy - Procedural Published Material / Policy; Ground Incursion Runway
Detector: Automation Air Traffic Control
When detected: Taxi
Result: Air Traffic Control Provided Assistance; Flight Crew Returned To Clearance
Contributing factors: Airport; Procedure
Primary problem: Procedure

Narrative: Aircraft X called ready for taxi and I told him 'RWY 4R taxi via K-12; Yankee cross RWY 9L ATIS information  is current' A standard taxi route we give every day on a north flow. He said something like 'K-12 cross RWY 9L and we will pick up Kilo.' I am positive he read back the correct runway to cross but I did not correct him on the incorrect ATIS code. He said that he was going to pick up the ATIS so I thought that would suffice; I then turned around to get the proposed departure strips from CD and put them in their assigned bays as is one of my duties as a Ground Controller.  The ASDE-X alerted and I turned around to see that the aircraft had started to cross RWY 4R at Y-12 and an Air Carrier was on departure roll.  I told the pilot to speed up for traffic on the runway and continue across the runway as I thought this was the only option to get him off the runway in time. The Local Controller attempted to tell the departing carrier to abort takeoff but they were already lifting their nose-wheel off the ground. The departing carrier went over top of Aircraft X which was still at least partially on the runway I think. One factor I believe was the fact that we are required to tell them to cross RWY 9L even know that runway was and is almost always closed. I think this created confusion in the cockpit as to the fact that they were cleared across a runway.


Second narrative: Pushed back off gate and received full reroute clearance. Was given taxi instructions and taxi commenced while my head was down programming the FMS.Taxi instructions were not followed and a runway incursion took place with no event.  No aircraft deviation was required. Flight continued as planned.


Synopsis: DTW Ground Controller describes scenario where an aircraft crosses an active runway with a departure rolling down the runway. Pilot describes situation differently; where no aircraft deviation was required. Another Air Carrier over flew the taxiing aircraft.
Date: 201411
Local time of day: 0001-0600
Location: ZTL.ARTCC, GA
Flight conditions: Mixed
Light: Night
Aircraft: B757 Undifferentiated or Other Model
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Flight phase: Climb
Airspace: Class A ZZZ
ATC / advisory: Center ZTL
Aircraft component: Pneumatic Control Valves
Component problem: Failed
Reporter organization: Air Carrier
Reporter function: Pilot Not Flying; First Officer
Reporter qualification: Flight Crew Air Transport Pilot (ATP); Flight Crew Flight Engineer; Flight Crew Flight Instructor; Flight Crew Instrument; Flight Crew Multiengine
Anomaly: Aircraft Equipment Problem Critical
Detector: Person Flight Crew
When detected: In-flight
Result: Flight Crew Took Evasive Action; Flight Crew FLC complied w / Automation / Advisory
Contributing factors: Aircraft
Primary problem: Aircraft

Narrative: Climbing to cruise altitude Right Bleed EICAS Message followed by a Left Bleed EICAS message. Resulting in loss of both PACKS.  Resulting is CABIN ALT warning message.  We began descent to 10;000 while performing QRH procedures.




Synopsis: B757 First Officer reported losing cabin pressure when both pneumatic bleeds failed at FL350.
Date: 201706
Local time of day: 0601-1200
Location: SSI.Airport, GA
Flight conditions: VMC
Weather elements / visibility: 10
Light: Daylight
Aircraft: Small Aircraft; Low Wing; 1 Eng; Fixed Gear
Operator: FBO
Operating under: Part 91
Flight plan: VFR
Mission: Training
Flight phase: Climb
Airspace: Class E SSI
ATC / advisory: CTAF SSI
Second aircraft: Light Transport; Low Wing; 2 Turbojet Eng
Reporter organization: FBO
Reporter function: Instructor; Pilot Not Flying
Reporter qualification: Flight Crew Commercial; Flight Crew Flight Instructor; Flight Crew Instrument; Flight Crew Multiengine
Human factors: Communication Breakdown; Confusion; Distraction; Situational Awareness; Time Pressure; Workload
Anomaly: Conflict NMAC; Deviation / Discrepancy - Procedural Published Material / Policy
Detector: Automation Aircraft TA; Person Flight Crew
When detected: In-flight
Result: Flight Crew Became Reoriented; Flight Crew Took Evasive Action
Contributing factors: Aircraft; Human Factors; Procedure
Primary problem: Human Factors

Narrative: The aircraft I was giving instruction in; a single engine; was doing pattern work in SSI for a checkride later that morning. We were on the upwind on Runway 22. Wind was calm and clear. I heard an aircraft make a radio call for a base leg into 09J. Same CTAF frequencies. I saw a jet that appeared to be on a base leg for 09J. TCAS started going off when we were about to turn for our left crosswind leg. I kept my eyes on the jet and noticed no relative motion between the aircraft. We made an evasive turn to the right to avoid hitting the jet which just continued to turn final and land runway 4 without making any radio calls. I do not know if a jet landed in 09J the same time this happened and the pilot we almost hit just wasn't making radio calls; or was the pilot just at the wrong airport. His flight plan on [internet site] said destination SSI. The pilot saw us because he overshot the base to final turn to avoid hitting us. He never acknowledged us on the CTAF frequency. I know that airport is becoming more dangerous with incoming charter jets and general aviation flying around. If I had not known the about this particular airports traffic problem this might have been a different ending. The cause of the problem I believe is that the large aircraft are not used to coming into non-towered airfields and forget that they need to make radio calls for position reports. A tower would help with how busy SSI has become. I only fly into SSI now for taking a student for a checkride.




Synopsis: GA Instructor with student in the SSI Runway 22 pattern reported a near miss with a small corporate jet. The jet crew did not communicate on the SSI CTAF frequency as the FAA recommends.
Date: 201306
Local time of day: 1801-2400
Location: ZZZ.ARTCC, US
Flight conditions: VMC
Light: Daylight
Aircraft: Challenger 300
Operator: Fractional
Operating under: Part 135
Flight plan: IFR
Flight phase: Cruise
Airspace: Class A ZZZ
ATC / advisory: Center ZZZ
Reporter organization: Fractional
Reporter function: Pilot Not Flying
Reporter qualification: Flight Crew Air Transport Pilot (ATP)
Human factors: Distraction; Communication Breakdown
Second reporter function: Pilot Flying
Anomaly: ATC Issue All Types; Aircraft Equipment Problem Critical
Detector: Person Flight Crew
When detected: In-flight
Result: General None Reported / Taken
Contributing factors: Aircraft
Primary problem: Aircraft

Narrative: While at cruise erroneous EICAS messages started to appear on the message board. The messages would post for a few second and then disappear. Red; Amber; and Cyan messages were being displayed. Messages included pylon bleed-leak; engine fire; spoiler deployed; etc. Spoiler fault displayed red on the synoptic page. The messages continued to display throughout the rest of the flight. Sometimes many messages and other times just a few. Next we noticed the NAV frequencies flip flopping uncommanded. COMM 2 was going reversionary to the flying pilots PFD. All frequencies were turning from amber to green and back to amber. Multiple transmissions were required to communicate with Center because the COMM frequencies would switch after a few seconds and then drop out. At this point the Captain called Dispatch from the SAT phone to explain the situation and have then contact the TRACON. He also spoke to Maintenance Control to troubleshoot the problem. After troubleshooting with Maintenance there wasn't a fix. We decided to continue to the destination where the weather was reported 10;000 FT overcast. The rest of the flight we continued to work the radios to maintain our frequencies and communicate with Center. We descended below the clouds and had visual contact with [the airport]. Approach Control cleared us for a visual approach. We canceled IFR on the ground in [the airport].This event was unavoidable. We should have followed updated Bombardier procedures to tune 121.5 on the reversionary panel.


Second narrative: [No additional information was contained in the secondary narrative.]


Synopsis: Despite multiple; apparently erroneous; EICAS messages and malfunctioning communications radios the flight crew of a CL-300 elected to continue and complete their three hour IFR flight.
Date: 201412
Location: ZZZ.Airport, US
Flight conditions: VMC
Weather elements / visibility: 10
Light: Night
Aircraft: B757-200
Operator: Air Carrier
Operating under: Part 121
Mission: Cargo / Freight / Delivery
Flight phase: Takeoff / Launch
Aircraft component: Nosewheel Steering
Reporter organization: Air Carrier
Reporter function: Captain; Pilot Flying
Human factors: Confusion; Distraction; Troubleshooting
Second reporter function: Pilot Not Flying; First Officer
Anomaly: Aircraft Equipment Problem Less Severe; Inflight Event / Encounter Loss Of Aircraft Control
Detector: Person Flight Crew
When detected: In-flight
Result: Aircraft Equipment Problem Dissipated; Flight Crew Rejected Takeoff
Contributing factors: Weather; Aircraft
Primary problem: Ambiguous

Narrative: Captains Leg. As we taxied onto the runway we made a 90 degree right turn to line up with the center line of the runway and applied initial take off thrust; the aircraft made a hard right turn; I rejected the takeoff. Airspeed was less than thirty knots; the indicator had not moved yet. Informed the tower and exited the runway. Discussed the reject with the first officer and our conclusion was that the runway was wet from raining all day and the nose wheel was still turned to the right and was not completely centered. This combined with being on the painted portion of the runway caused the aircraft to veer right. Both engines spooled up normal and equal and the aircraft taxied normally; before and after the rejected takeoff.There did not seem to be anything wrong with the aircraft mechanically. Contacted the Chief Pilot on duty to verify that a subsequent takeoff could be attempted without a block turnback. Taxied to runway and took off without incident.


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


Synopsis: A B757-200 veered hard right after takeoff thrust was applied on a wet runway; so the Captain rejected at about 30 KTS. After investigating; the crew decided the nose wheel had not aligned straight and so completed a successful takeoff.
Date: 202009
Local time of day: 1801-2400
Location: ZZZ.ARTCC, US
Aircraft: B737-800
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: Captain; Pilot Not Flying
Reporter qualification: Flight Crew Air Transport Pilot (ATP); Flight Crew Instrument; Flight Crew Multiengine
Anomaly: Flight Deck / Cabin / Aircraft Event Smoke / Fire / Fumes / Odor
Detector: Person Flight Attendant; Person Other Person; Person Passenger
When detected: In-flight
Result: Air Traffic Control Provided Assistance; Flight Crew Diverted; Flight Crew Requested ATC Assistance / Clarification; Flight Crew Overcame Equipment Problem; Flight Crew Landed in Emergency Condition; General Maintenance Action
Contributing factors: Aircraft
Primary problem: Aircraft

Narrative: During cruise; FAs (Flight Attendants) and crewmembers/passengers reported strong odor in the aft cabin; with the strongest concentration in the aft galley. Smell was reported as both electrical burning and cloth burning. Advised ATC; and was cleared by ATC to start a descent and turn toward ZZZ and initiated the SMOKE; FIRE; OR FUMES QRC/QRH procedure. During the QRH procedure; turned off the R PACK and called FAs. All reported dissipation of the odors. Uneventful descent; approach; and landing at ZZZ uneventfully. ARFF inspected the aircraft on the runway and followed taxi in to gate. No reports of illness or injury by the passengers or crewmembers.Cause: Unknown source; but likely a problem in the Right Side Air Cond system.




Synopsis: B737-800 Captain reported an electrical burning" fumes event that resulted in a diversion."
Date: 201902
Local time of day: 1201-1800
Location: ORL.Tower, FL
Aircraft: Citationjet (C525/C526) - CJ I / II / III / IV
Operating under: Part 91
Flight plan: IFR
Flight phase: Descent
Airspace: Class D ORL
ATC / advisory: Tower ORL
Second aircraft: Any Unknown or Unlisted Aircraft Manufacturer
Reporter organization: Government
Reporter function: Local
Reporter qualification: Air Traffic Control Fully Certified
Human factors: Situational Awareness
Anomaly: ATC Issue All Types; Conflict Airborne Conflict; Deviation - Track / Heading All Types; Deviation / Discrepancy - Procedural Published Material / Policy
Detector: Person Air Traffic Control; Person Flight Crew
When detected: In-flight
Result: Air Traffic Control Issued Advisory / Alert; Flight Crew Took Evasive Action
Contributing factors: Airspace Structure; Human Factors
Primary problem: Human Factors

Narrative: Aircraft Y was cleared for takeoff with a suggested heading of 055 off of runway 25. I switched the aircraft when he started his right turn. Aircraft X was on final and I cleared him to land then I noticed Aircraft Y flying a 090 heading which made him a conflict with my aircraft on final. I told Aircraft X about the traffic and Aircraft X told me they were responding to a RA. I said roger and Aircraft X climbed to 1;400ft MSL and started it's descent to land.[I recommend we] change to Class Charlie airspace.




Synopsis: Orlando Executive Controller reported an unsafe situation when a departure turned towards an arrival causing a Resolution Advisory for the arriving aircraft.