elihoole/asrs-aviation-reports huggingface dataset:
Date: 201201
Local time of day: 1201-1800
Location: ZZZ.Airport, US
Flight conditions: VMC
Weather elements / visibility: 10
Light: Daylight
Aircraft: Bonanza 36
Operator: Personal
Operating under: Part 91
Flight plan: None
Mission: Personal
Flight phase: Cruise
Airspace: Class C ZZZ
ATC / advisory: TRACON ZZZ
Aircraft component: Fuel Distribution System
Component problem: Improperly Operated
Reporter organization: Personal
Reporter function: Single Pilot
Reporter qualification: Flight Crew Multiengine; Flight Crew Commercial; Flight Crew Instrument
Human factors: Troubleshooting; Situational Awareness; Human-Machine Interface; Confusion; Training / Qualification
Anomaly: Aircraft Equipment Problem Critical; Deviation / Discrepancy - Procedural Published Material / Policy; Inflight Event / Encounter Fuel Issue
Detector: Person Flight Crew
When detected: In-flight
Result: Flight Crew Diverted; Flight Crew Landed in Emergency Condition; General Declared Emergency
Contributing factors: Aircraft; Human Factors
Primary problem: Human Factors

Narrative: Was cruising at 4;500 FT and switched tanks to even the fuel levels. After a few minutes; changed power settings and went to lean the engine to the new power setting. In the middle of the leaning process; the engine stumbled and quit. Since this was a break in flight on a new engine; I assumed that the stoppage had to do with the leaning. Called Approach and asked for the nearest airport. Was pointed to an airport 3 plus miles away and turned toward it immediately. As I set up for a landing; moved fuel and prop forward; put on the boost pump and refined my approach. Landed on the runway and coasted to a taxiway and pulled off the active and held short of the parallel. Called Approach on the phone and let them know that I was on the ground; OK; and proceeded to further troubleshoot. Found I had placed the fuel selector valve in the OFF position. [I] did not try to change tanks while focused on the airport. The prior number of weeks I had been flying a B36TC whose fuel selector is the exact opposite of the A36. OFF is in the 4 o'clock position and the left is at 10 and the right at 2. In the A36; the OFF is at the 10; left is at 8 and right is at 4. I was aware of this and conscious of this before leaving the ground; but somehow turned the handle the wrong way any way. I feel that if the runway that I landed on was not available and easy to get to; I probably would have gotten to the fuel selector and continued to troubleshoot.




Synopsis: A pilot flying a Beech A36 closed the fuel tank selector valve in flight causing the engine to shutdown because he had been flying the BE36TC; whose fuel selector is opposite the A36. An emergency was declared and the aircraft landed safely at a nearby field.
Date: 201508
Local time of day: 1801-2400
Location: N90.TRACON, NY
Flight conditions: VMC
Aircraft: Dash 8-400
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Initial Climb
Airspace: Class B N90
Second aircraft: B757 Undifferentiated or Other Model
Reporter organization: Air Carrier
Reporter function: Captain; Pilot Flying
Reporter qualification: Flight Crew Air Transport Pilot (ATP)
Anomaly: Deviation / Discrepancy - Procedural Published Material / Policy; Inflight Event / Encounter Wake Vortex Encounter
Detector: Person Flight Crew
When detected: In-flight
Result: General None Reported / Taken
Contributing factors: Environment - Non Weather Related; Procedure
Primary problem: Procedure

Narrative: We were departing behind a heavy 757. Due to the RECAT we were cleared for take off 1 minute after the 757 was. I tried to delay the departure as much as possible by taxiing onto the runway slowly. As we were climbing out on the departure we ran into the 757's wake turbulence. It was a very severe vertical acceleration with a significant roll as well. The RECAT program should be rethought. I would like to see the evidence that a DHC8-D is safe to fly with 2.5 nm separation on a 757. I realize the program includes aircraft handling characteristics along with weight; but do these people realize the Q400 is a truck that can barely get out of its own way? From now on I will insist on more spacing when departing behind a heavy.




Synopsis: Q400 Captain reported encountering wake turbulence on climb out from EWR in trail of a B757 that resulted in 'very severe vertical acceleration with a significant roll'. Reporter suggested 'the RECAT program should be rethought'.
Date: 202104
Local time of day: 0601-1200
Location: MIA.Airport, FL
Light: Daylight
Aircraft: Commercial Fixed Wing
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Descent
Airspace: Class B MIA
Second aircraft: Any Unknown or Unlisted Aircraft Manufacturer
Reporter organization: Air Carrier
Reporter function: Captain; SAFETY MANAGER
Reporter qualification: Flight Crew Instrument; Flight Crew Multiengine; Flight Crew Air Transport Pilot (ATP)
Anomaly: ATC Issue All Types; Conflict NMAC; Deviation / Discrepancy - Procedural Clearance
Detector: Automation Aircraft RA; Person Flight Crew
When detected: In-flight
Result: Flight Crew FLC complied w / Automation / Advisory; Flight Crew Took Evasive Action
Contributing factors: Procedure; Human Factors
Primary problem: Human Factors

Narrative: Today we flew to MIA; on the SSCOT5 approach; after the LECIT position; ATC authorized us to descend to 3;000 ft; later we hear on the radio frequency that an airplane is not paying attention; suddenly in the instrument appears an airplane below us in ascent; we locate it visually and it gives us the instruction to maintain the altitude and immediately after to ascend; we performed the evasion maneuver and informed ATC; who ordered us to maintain 8;000 feet.




Synopsis: Air carrier Captain reported NMAC on descent.
Date: 201309
Local time of day: 1201-1800
Location: PCT.TRACON, VA
Aircraft: EMB ERJ 145 ER/LR
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Final Approach
Airspace: Class B BWI
ATC / advisory: TRACON PCT
Reporter organization: Government
Reporter function: Approach
Reporter qualification: Air Traffic Control Fully Certified
Human factors: Communication Breakdown
Anomaly: ATC Issue All Types
Detector: Person Air Traffic Control
Result: General None Reported / Taken
Contributing factors: Procedure; Equipment / Tooling; Human Factors; Aircraft
Primary problem: Equipment / Tooling

Narrative: After placing Air Carrier X on a heading the aircraft read back the heading then failed to unkey their microphone. Initially the conversation contained what sounded like routine information; such as the aircraft's speed; between the pilots. However; the conversation became inappropriate regarding required cockpit conversation. I attempted to reach the aircraft on guard and inform them that their microphone was still hot keyed; shortly after another pilot attempted to inform the aircraft they were hot keyed. Numerous attempts failed to get the aircraft to unkey their microphone. At the time of the event the aircraft was on a vector to be number one to the aircraft; they were located approximately 5 to 6 miles southeast of the airport at 2;000 FT and being set up for a visual approach. At the same time another aircraft was inbound from the South; at the time being vectored to follow the Air Carrier Y aircraft. When Air Carrier X began to cross the Runway 33L localizer they finally unkeyed their microphone. At this time they were entering the departure corridor. I vectored the aircraft to the South to follow the following traffic and re-sequenced. The initial conversation between the pilots was regarding the speed of the aircraft and their proximity to the airport. They then began discussing Controller performance. Making these comments on an open microphone prevented me from being able to provide positive control to aircraft into BWI for approximately 45 seconds. Air Carrier X inability to maintain a sterile cockpit below 10;000 FT caused unnecessary risk to the NAS. The aircraft was in a high volume area where conflicts can be numerous. Had they not been maintaining the conversation they may have heard the numerous calls I attempted on guard.




Synopsis: PCT Controller described an unsafe condition when traffic being vectored to the final had a 'stuck' mike and failed to respond to numerous ATC instructions.
Date: 202110
Local time of day: 0601-1200
Location: ZZZ.Airport, US
Flight conditions: VMC
Weather elements / visibility: 100
Light: Daylight
Aircraft: Pitts S-2 All Series
Operator: Personal
Operating under: Part 91
Flight plan: None
Mission: Personal
Flight phase: Landing
Airspace: Class D ZZZ
ATC / advisory: Tower ZZZ
Aircraft component: Main Gear
Component problem: Malfunctioning
Reporter organization: Personal
Reporter function: Pilot Flying; Single Pilot
Reporter qualification: Flight Crew Air Transport Pilot (ATP); Flight Crew Flight Instructor; Flight Crew Instrument; Flight Crew Multiengine
Human factors: Situational Awareness
Anomaly: Aircraft Equipment Problem Critical; Deviation / Discrepancy - Procedural Published Material / Policy; 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; General Flight Cancelled / Delayed
Contributing factors: Aircraft; Human Factors
Primary problem: Ambiguous

Narrative: Upon landing at ZZZ for fuel; a normal wheel landing was conducted on Runway XX; which was in use per ATC. Landing was smooth and as airspeed bleed below 40 kts.; tail settled to ground smoothly after slightly floating. Once tail was on the ground; it felt like something bit into my right main and aircraft canted hard right. Full left rudder and left brake were applied but I was unable to maintain directional control of the aircraft as it skidded towards the runway edge at approximately 35 degrees. As the aircraft slowed and braking became more effective; the aircraft canted back towards the left and stuck the wingtip on the ground and came to a stop on the runway. I noticed that I had trouble moving the aircraft on the ground due to an issue with my right main gear but was still able to taxi off the runway. While I am not exactly sure what caused this incident; the week prior I spend working with a school that specializes in Pitts training. Being current on the aircraft after spending some time away from flying the Pitts was extremely helpful and this situation would have undoubtedly ended different if I had not attended that course.




Synopsis: Pilot reported a mechanical problem with the right main gear caused a runway excursion and ground strike; resulting in damage to the wing tip.
Date: 202103
Local time of day: 1201-1800
Location: ZZZ.Airport, US
Flight conditions: VMC
Weather elements / visibility: 10
Light: Daylight
Aircraft: Bonanza 35
Operator: Personal
Operating under: Part 91
Flight plan: None
Mission: Personal
Flight phase: Landing
Airspace: Class D Y
ATC / advisory: Tower ZZZ
Aircraft component: Gear Extend/Retract Mechanism
Component problem: Failed
Reporter organization: Personal
Reporter function: Pilot Not Flying
Reporter qualification: Flight Crew Commercial; Flight Crew Flight Instructor; Flight Crew Multiengine; Flight Crew Instrument
Anomaly: Aircraft Equipment Problem Critical; Ground Event / Encounter Ground Strike - Aircraft
Detector: Person Flight Crew
Result: Aircraft Aircraft Damaged
Contributing factors: Aircraft
Primary problem: Aircraft

Narrative: After landing at ZZZ on the roll out towards the taxiway exit the aircraft landing gear system failed and buckled in. Consequently the aircraft fell to the ground causing the propeller to strike the ground. Damage observed and assured by A&P was the propeller; aux tank drain sump fell off; scratches on the bottom of fuselage; side step and landing gear. Airport operations did not want us to load the plane on a flat dollie and insisted on using a crane. When the crane was used the flaps were bent. No further damage was observed.




Synopsis: BE35 pilot reported the landing gear collapsed during taxi after landing.
Date: 201904
Local time of day: 1201-1800
Location: ZZZ.Airport, US
Flight conditions: VMC
Light: Daylight
Aircraft: Cessna Aircraft Undifferentiated or Other Model
Operator: FBO
Operating under: Part 91
Flight plan: None
Mission: Training
Flight phase: Final Approach
Airspace: Class G ZZZ
ATC / advisory: CTAF ZZZ
Second aircraft: Piper Aircraft Corp Undifferentiated or Other Model
Reporter organization: FBO
Reporter function: Pilot Flying; First Officer
Reporter qualification: Flight Crew Flight Instructor; Flight Crew Instrument; Flight Crew Commercial
Human factors: Communication Breakdown; Situational Awareness
Anomaly: Conflict NMAC
Detector: Person Flight Crew
When detected: In-flight
Result: Flight Crew Took Evasive Action
Contributing factors: Airspace Structure; Human Factors; Procedure; Airport
Primary problem: Human Factors

Narrative: My student was turning left base-to-final RWY 25 for ZZZ; making appropriate calls on the UNICOM; when I noticed an Aircraft Y behind us turning in. We were closer and a lower altitude on final; and there's no way the other pilot couldn't see our plane. I took controls and we sidestepped the final approach course and watched the Aircraft Y land. I did a 360 on final and landed once the runway and final approach path were clear.




Synopsis: CFI reported a NMAC that occurred at a non-towered airport.
Date: 201205
Local time of day: 1801-2400
Location: BNA.Airport, TN
Aircraft: Commercial Fixed Wing
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Flight phase: Initial Climb
Airspace: Class C BNA
ATC / advisory: Tower BNA
Second aircraft: Helicopter
Reporter organization: Government
Reporter function: Instructor; Local
Reporter qualification: Air Traffic Control Fully Certified
Human factors: Situational Awareness
Second reporter function: Trainee; Local
Anomaly: ATC Issue All Types; Conflict Airborne Conflict; Deviation / Discrepancy - Procedural Published Material / Policy
Detector: Person Air Traffic Control
Result: General None Reported / Taken
Contributing factors: Airport; Procedure
Primary problem: Procedure

Narrative: We were having a helicopter spray vegetation control through the airport authority. Runway 31 was closed to facilitate this operation. The helicopter was operating west of Runway 2L. We were briefed about the helicopter but he had never talked to anyone via radio or telephone and had previously been operating but currently was nowhere to be seen. My trainee and I had just taken the position and I was looking for the helicopter with my binoculars while the trainee was working a little spurt of traffic but could not find him. I first saw the helicopter as he was executing some kind of Split-S style crop dusting maneuver just adjacent to Runway 2L on what would have been a collision course with a regional jet. The regional jet immediately complained and said something to the effect that he was so surprised; he would have aborted the take off if he would have been able to. I would imagine that the pilot is filing a near mid-air as we speak. This spraying was problematic last year with similar; if less dramatic problems. My main recommendation [is to] get a tractor to apply this stuff. If the airport has to use a helicopter to apply it; close all adjoining runways no matter what the impact to the traffic flow.


Second narrative: [Narrative #2 contained no additional information.]


Synopsis: BNA Controller described a conflict between an Air Carrier departure and a helicopter spraying on the airport; the reporter noting similar problems in the past and suggesting tractor spraying applications and/or additional runway restrictions.
Date: 201908
Local time of day: 1201-1800
Location: ORD.Airport, IL
Light: Daylight
Aircraft: Large Transport
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Taxi
ATC / advisory: Ground ORD
Reporter organization: Air Carrier
Reporter function: Captain; Pilot Flying
Reporter qualification: Flight Crew Multiengine; Flight Crew Instrument; Flight Crew Air Transport Pilot (ATP)
Human factors: Training / Qualification; Situational Awareness; Communication Breakdown; Confusion
Anomaly: ATC Issue All Types; Deviation / Discrepancy - Procedural Published Material / Policy
Contributing factors: Chart Or Publication; Human Factors; Procedure
Primary problem: Procedure

Narrative: We landed on 9L at ORD with no issues. On clearing the runway; Ground Control asked if we were familiar with the 'Standard Taxi Routes.' Since there were no taxi routes described in any [chart] pages; nor in any ATC NOTAMs; we responded 'No;' and were give taxi instructions that were simply 'Follow the aircraft in from of you; Hold Short of T-7.'This was not a simple taxi route; due to the ongoing ORD construction. As we taxied; even the aircraft in front of us admitted they had no guidance as to what 'Standard Taxi Routes' were in ORD. I followed his route; based on my last time I was there; and we all ended up in the right spot. The aircraft behind us also admitted that they had absolutely no written guidance on 'Standard Taxi Routes' at ORD.My issue is that ORD ATC Controllers insist there is a 'Standard Taxi Route' from Runway 9L/27R; yet there is absolutely nothing published in the [chart] pages. There was a time a few months ago that Standard Taxi Routes were issued by NOTAM; but that currently isn't the case. With no further direction than 'Follow the aircraft in front of you' in an area where I was not always able to keep them in sight; it was a real possibility that I could have ended up in the wrong area of the airport.




Synopsis: Air carrier Captain reported confusion when Air Traffic Control issued instructions to follow 'standard taxi routes' that were not published.
Date: 202105
Local time of day: 1801-2400
Location: ZZZ.Tower, US
Flight conditions: VMC
Light: Night
Aircraft: Commercial Fixed Wing
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Initial Approach
Airspace: Class C ZZZ
ATC / advisory: Tower ZZZ
Second aircraft: Cessna Aircraft Undifferentiated or Other Model
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: Situational Awareness
Anomaly: Conflict NMAC; Deviation / Discrepancy - Procedural Clearance; Inflight Event / Encounter Unstabilized Approach
Detector: Person Flight Crew
When detected: In-flight
Result: Flight Crew Executed Go Around / Missed Approach; Flight Crew Took Evasive Action
Contributing factors: Human Factors
Primary problem: Human Factors

Narrative: Night VFR RNAV Y XXR approach. Approaching FAF ZZZ tower advised us of Cessna  traffic on downwind turning base for short parallel runway XXL. Traffic in sight. As we passed our FAF; fully configured and stable we saw the Cessna pointing right at us on base and both remarked 'I hope they don't overshoot'. At approximately 800 feet AGL the Cessna was still pointing at us and I could see they were clearly going to overshoot slightly above us as they turned to final. I felt it was way too close and pushed over slightly as I estimated them to be no more than 100-200 feet above us as they crossed right over us and slightly behind. As our approach was now unstable in my estimation I executed an uneventful go-around. We advised tower of the close pass. We returned for a second; uneventful approach and landing to XXR. I called tower controller after landing and he said he would contact the Cessna pilot and talk to him about the incident. Cessna not keeping us in sight and possibly lining up on incorrect runway. Light VFR traffic maintaining better situational awareness with a large air carrier with approximately XXX people on board and all landing lights; fully configured on final approach.




Synopsis: Air carrier Captain reported an NMAC during approach with an aircraft on approach on the parallel runway.
Date: 201501
Local time of day: 0001-0600
Location: ZZZZ.Airport, FO
Flight conditions: VMC
Aircraft: B777 Undifferentiated or Other Model
Operator: Air Carrier
Mission: Passenger
Flight phase: Cruise
Airspace: Class A ZZZZ
Aircraft component: Turbine Engine
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: Taxi
Result: General Maintenance Action
Contributing factors: Aircraft
Primary problem: Aircraft

Narrative: I am new on the 777. After 10 years on the 747; I must admit; I have not yet achieved a comfort level in the 777. Therefore; I keep a very close eye on the engine instruments. I had the second break; and during the first 6 hours or so of the international flight; I did notice the engine vibration on the #1 engine was a little higher than #2; about 2.5. In the engine compacted mode; on the upper EICAS screen; which seems to be the SOP on the 777; there is no scale for engine vibration; just a number; so; I didn't worry about it; (much). After coming back to the cockpit from my break; about an hour and 10 minutes from destination; I noticed a note on the center pedestal from maintenance inquiring about the health of our #1 engine. After consulting with my crew; they assured me the engine the engine had been running fine the entire time I was on my break. Indeed the engine ran perfectly; and indicated normally; except for the engine vibration indication; during the remainder of the cruise; descent; approach and landing. During taxi in; we had to stop before turning into the gate. When I added power to turn into the gate; we heard a loud rubbing sound; and vibration from the #1 engine; which got louder and more pronounced when I shut the engine down. The mechanic then got on the headset; and said;'you broke it; we will have to replace the engine'. The next day; the mechanic told my flying first officer; 'I am surprised they didn't turn you back to departure airport' with the condition of that engine. It was very interesting to learn that maintenance knows more about the condition of the engines on my airplane than the flight crew does.




Synopsis: B777 Captain on an international overwater flight reported he experienced an engine failure on taxi in at destination. Reporter commented that maintenance was watching the engine with some concern; but the only cockpit indication of a problem was slightly elevated engine vibration indication.
Date: 201403
Local time of day: 1801-2400
Location: CLT.TRACON, NC
Aircraft: Regional Jet 700 ER/LR (CRJ700)
Operator: Air Carrier
Operating under: Part 121
Mission: Passenger
Flight phase: Initial Approach
Airspace: Class B CLT
ATC / advisory: TRACON CLT
Reporter organization: Air Carrier
Reporter function: Captain; Pilot Flying
Reporter qualification: Flight Crew Air Transport Pilot (ATP)
Anomaly: No Specific Anomaly Occurred All Types
Detector: Automation Aircraft RA; Automation Aircraft TA; Person Flight Crew
When detected: In-flight
Result: Flight Crew Took Evasive Action
Contributing factors: Aircraft; Company Policy; Procedure
Primary problem: Ambiguous

Narrative: Cleared visual 36L CLT. AP was engaged with shallow intercept. At 5;000 FT and about 10 miles out got TA and RA to descend. Complied with RA. Traffic was on localizer to 36C both aircraft appeared to be right where they were supposed to be. Tracking localizer. This is the third TCAS RA I have had between A/C approaching the center and west runways. It seems the separation between the runways in inadequate for the TCAS.




Synopsis: CRJ700 Captain experiences a TCAS RA during a visual approach to Runway 36L at CLT; caused by traffic on the localizer to Runway 36C. The RA descend command is complied with.