elihoole/asrs-aviation-reports huggingface dataset:
Date: 201202
Local time of day: 1801-2400
Location: ZZZ.Airport, US
Flight conditions: IMC
Aircraft: B757 Undifferentiated or Other Model
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Flight phase: Landing
Airspace: Class B ZZZ
ATC / advisory: TRACON ZZZ
Second aircraft: EMB ERJ 135 ER/LR
Reporter organization: Government
Reporter function: Approach; Departure
Human factors: Communication Breakdown; Situational Awareness
Anomaly: ATC Issue All Types; Deviation / Discrepancy - Procedural FAR; Deviation / Discrepancy - Procedural Published Material / Policy; Inflight Event / Encounter CFTT / CFIT
Detector: Person Air Traffic Control
Result: Air Traffic Control Issued New Clearance
Contributing factors: Human Factors
Primary problem: Human Factors

Narrative: Training; approach procedure; widely spaced weather conditions: IFR; The weather caused for longitudinal compression thus requiring extra spacing on final approach. My trainee vectored a B757 a little too close behind another B757 causing me to concentrate on that scenario and I missed the initial check of an E135 on the frequency. I did not hear the E135's assigned altitude of 3;000; towards the 3;500 MVA. My trainee initiated a frequency change of the B757 to Tower with insufficient wake turbulence spacing. I called Local Control to initiate a go-around. My trainee then noticed the E135 at 3;000 and issued a climb. I then issued an 'expedite climb' to the E135. The audio data indicates that the Feeder Controller assigned the Embraer 5;000 MSL but the pilot read back 3;000.




Synopsis: TRACON Controller providing OJT described an event where they cleared an aircraft to descend below the MVA while distracted by an overtake 'wake' situation on final and then failing to note an incorrect altitude assignment.
Date: 201602
Local time of day: 1801-2400
Location: IAD.Airport, DC
Light: Dusk
Aircraft: Medium Large Transport; Low Wing; 2 Turbojet Eng
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Taxi
ATC / advisory: Ground IAD
Reporter organization: Air Carrier
Reporter function: Pilot Not Flying; First Officer
Reporter qualification: Flight Crew Air Transport Pilot (ATP)
Human factors: Situational Awareness; Confusion
Anomaly: ATC Issue All Types; Conflict Ground Conflict; Less Severe; Ground Event / Encounter Other / Unknown
Detector: Person Flight Crew
When detected: Taxi
Result: General None Reported / Taken
Contributing factors: Human Factors; Weather
Primary problem: Ambiguous

Narrative: This event happened around dusk; upon landing 01C in KIAD; turning off to the taxiway Y2 high speed. Tower instructed us to expedite off the runway and instructed us to take next high speed which was Y2 and switch to ground. Once joining Y2; we observed a standing puddle that expanded the width of the taxiway. The captain came to an abrupt stop and slowly turned right into the reverse high speed taxiway Y3 but we were off the active runway. At the same time; I switched to ground. Ground came back with an upsetting tone and said 'I told you to get off the runway! You take it upon your liberty to take Y3 when you were instructed not to do so. I have a number for you; are you ready to copy?' At this time; I saw an aircraft do a go-around on our behalf.




Synopsis: Air carrier First Officer reported that the aircraft was cleared to exit Runway 1C at IAD on Taxiway Y2; but stopped and turned right on Y3 to avoid a puddle of water. This blocked the runway and resulted in a go-around for the aircraft landing behind them.
Date: 201309
Local time of day: 0001-0600
Location: PVD.Airport, RI
Flight conditions: VMC
Weather elements / visibility: 10
Light: Night
Aircraft: Medium Transport
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Initial Approach
Airspace: Class E ZBW
ATC / advisory: Center ZBW
Reporter organization: Air Carrier
Reporter function: Captain; Pilot Not Flying
Reporter qualification: Flight Crew Air Transport Pilot (ATP)
Anomaly: ATC Issue All Types
Detector: Person Flight Crew
When detected: In-flight
Result: General None Reported / Taken
Contributing factors: ATC Equipment / Nav Facility / Buildings; Environment - Non Weather Related
Primary problem: Ambiguous

Narrative: Received vectors from Boston as Providence Tower was closed. Cleared to descend to 2600 FT for vectors to final Runway 23 at Providence (PVD). On reaching 2600 FT we lost communication with [Boston Center]. First Officer was flying. We were visual with the airport so he entered a left base for a visual approach. I tried to contact approach on all the frequencies on the approach plate also transmitting our position on Unicom and transmitting blind on 121.5. I directed the First Officer to try transmitting on his radios and he was unable to receive either. Landed and taxied in. On reaching the ramp; we were able to receive Center again. Our Flight Mechanic tested all the radios and they appeared to be working. I tested the radios with the Airport operator and they were satisfactory. Called Boston Center and advised them of our inability to receive them and cancelled the IFR flight plan. The Controller stated that sometimes they encountered areas around PVD where they lost communications. The approach Controller had descended us quite early to 2600 FT; I believe the low altitude contributed to bad reception. We later took off from PVD and had difficulty receiving Boston until we climbed above 4000 FT.




Synopsis: Captain experiences lost communications during late night approach and landing at PVD with the Tower closed.  During the following departure Boston Center advises that his frequency coverage is spotty at low altitude around PVD.
Date: 201703
Local time of day: 0601-1200
Location: RSW.Airport, FL
Flight conditions: VMC
Aircraft: A320
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Flight phase: Taxi
ATC / advisory: Ground RSW
Second aircraft: B737 Undifferentiated or Other Model
Reporter organization: Air Carrier
Reporter function: Pilot Flying; Captain
Reporter qualification: Flight Crew Air Transport Pilot (ATP)
Human factors: Situational Awareness
Anomaly: Conflict Ground Conflict; Critical; Deviation / Discrepancy - Procedural Published Material / Policy; Ground Event / Encounter Other / Unknown
Detector: Person Flight Crew
When detected: Taxi
Result: Flight Crew Took Evasive Action
Contributing factors: Human Factors
Primary problem: Human Factors

Narrative: [Policy] states 'aircraft taxiing in to the gate area shall give way to aircraft pushing back from the gate area.'During our pushback sequence from RSW's gate; tug driver had to come to a quick stop because [another air carrier] aircraft inbound to its gate--directly opposite [our] gate; failed to yield to our pushback as if we weren't even there.  If the Flight Attendants were not seated; this stop may have caused injuries--in this case they were seated at their stations.




Synopsis: A320 Captain reported the tug operator had to come to an abrupt stop during push back when another air carrier aircraft failed to yield.
Date: 201508
Local time of day: 1201-1800
Location: JFK.Airport, NY
Flight conditions: VMC
Aircraft: Large Transport; Low Wing; 2 Turbojet Eng
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Flight phase: Final Approach
Airspace: Class B JFK
ATC / advisory: Tower JFK
Second aircraft: UAV - Unpiloted Aerial Vehicle
Reporter organization: Air Carrier
Reporter function: Pilot Not Flying; First Officer
Human factors: Situational Awareness; Distraction
Second reporter function: Pilot Flying; Captain
Anomaly: Airspace Violation All Types; Conflict NMAC; Deviation / Discrepancy - Procedural FAR; Deviation / Discrepancy - Procedural Published Material / Policy; Inflight Event / Encounter Object
Detector: Person Flight Crew
When detected: In-flight
Result: Flight Crew Requested ATC Assistance / Clarification
Contributing factors: Human Factors; Procedure
Primary problem: Human Factors

Narrative: On approach to 31R into JFK we had a near miss with a silver or white colored drone. It passed approximately 100 FT or less off the left wing at our altitude on approach. It appeared to be approximately 3 feet square in size. I only saw it momentarily as we flew past it. The Captain did not see it.


Second narrative: I was the pilot flying and at some point First Officer said he may have seen a drone out of one of the windows. There was no TCAS alert and I saw nothing while on visual approach and ATC didn't report any traffic in our area. Landed normally.


Synopsis: An air carrier First Officer on a JFK Runway 31R Visual Approach at 1;500 feet reported a 100 foot near miss with an UAV; approximately three square feet. The Captain; pilot flying; did not see the object.
Date: 201810
Local time of day: 1801-2400
Location: ZZZ.ARTCC, US
Flight conditions: IMC
Aircraft: EMB ERJ 190/195 ER/LR
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Ferry / Re-Positioning
Flight phase: Cruise
Airspace: Class A ZZZ
ATC / advisory: Center ZZZ
Aircraft component: Pneumatic Valve/Bleed Valve
Component problem: Failed
Reporter organization: Air Carrier
Reporter function: Captain; Pilot Not Flying
Reporter qualification: Flight Crew Multiengine; Flight Crew Air Transport Pilot (ATP); Flight Crew Instrument
Anomaly: Aircraft Equipment Problem Critical; Deviation / Discrepancy - Procedural MEL / CDL
Detector: Person Flight Crew
When detected: In-flight
Result: Air Traffic Control Issued New Clearance; Air Traffic Control Provided Assistance; Flight Crew Landed As Precaution; Flight Crew Diverted; Flight Crew Landed in Emergency Condition; Flight Crew Requested ATC Assistance / Clarification
Contributing factors: Aircraft; Weather
Primary problem: Aircraft

Narrative: Aircraft already had ENG BLEED 1 on MEL. At 23;000 while in freezing rain; received two master caution messages: 'A-I WING FAIL' and 'ENG 2 BLEED FAIL.'FO (First Officer) was the PF (Pilot Flying). I took control of the aircraft and initiated an emergency descent to 10;000 feet. This was further followed by a descent down to 4;000 feet to completely exit icing conditions. FO [notified] Center and immediately performed all QRH procedures.After we were in VMC conditions and the FO had completed all QRH procedures; I transferred control back to the FO and we were vectored for an uneventful ILS into ZZZ.We had no passengers or flight attendants onboard since this was a maintenance reposition flight to ZZZ for scheduled maintenance.CFR (Crash Fire Rescue) met us on the runway. We taxied to the maintenance hangar and I spoke to the fire chief after deplaning.After making appropriate AML entries; I contacted our dispatcher to brief him on what had happened.ENG BLEED 1 on MEL.Loss of wing anti-ice and engine bleed 2 while in icing conditions.




Synopsis: EMB-190 Captain reported receiving a Master Caution 'A-I WING FAIL' and 'ENG 2 BLEED FAIL' during cruise with Number 1 engine bleed already deferred.
Date: 202103
Local time of day: 0601-1200
Location: ZZZ.Airport, US
Flight conditions: VMC
Light: Daylight
Aircraft: Cessna 180 Skywagon
Operator: Personal
Operating under: Part 91
Mission: Personal
Flight phase: Initial Approach
Airspace: Class G ZZZ
ATC / advisory: CTAF ZZZ
Second aircraft: Vans Aircraft Undifferentiated or Other Model
Reporter organization: Personal
Reporter qualification: Flight Crew Air Transport Pilot (ATP); Flight Crew Flight Instructor; Flight Crew Instrument; Flight Crew Multiengine
Human factors: Situational Awareness
Anomaly: Conflict NMAC; Deviation / Discrepancy - Procedural Published Material / Policy
Detector: Person Flight Crew
When detected: In-flight
Result: Flight Crew Took Evasive Action
Contributing factors: Human Factors
Primary problem: Human Factors

Narrative: Inbound to ZZZ from the south. Reported on CTAF 5 nm south of airport inbound for landing on Runway XX. A flight of 3 RVs reported taxiing out for XX. Approaching the airport RVs reported their takeoff roll; just prior to entering the downwind leg RVs reported they would be departing southbound. I then reported I was 2 minutes south. At that time; I observed the RVs over the departure end turning left. At this time; I could see them on a direct course toward me; they were climbing; I was level at pattern altitude (900 feet MSL). They were basically climbing or about to climb through my altitude; my best option was to descend underneath them; as they were climbing. At that point one of the RVs; I assume the leader reported seeing me headed underneath them. After we passed; I climbed back to pastern altitude and turned downwind; the RVs continued southbound.I saw the RVs from their x-wind turn. I thought they would make a standard 45 departure from the x-wind leg prior to turning southbound but they continued south. I should have been a little more to the East so that I joined the downwind at mid-field. They should have departed on a 45 to the x-wind. Fortunately; I was watching for them and saw them in time to avoid them. Everybody being on frequency was a positive.




Synopsis: Pilot reported that during their approach to the airport; a flight of 3 aircraft departed and failed to use the correct pattern departure procedure; resulting in an NMAC. The inbound pilot had to descend in order to avoid the other aircraft.
Date: 201209
Local time of day: 1801-2400
Location: ZZZ.Airport, US
Flight conditions: VMC
Aircraft: A320
Operator: Air Carrier
Operating under: Part 121
Mission: Passenger
Flight phase: Initial Approach
Airspace: Class B ZZZ
ATC / advisory: Tower ZZZ
Aircraft component: Hydraulic System Lines; Connectors; Fittings
Component problem: Malfunctioning
Reporter organization: Air Carrier
Reporter function: Pilot Not Flying; First Officer
Anomaly: Aircraft Equipment Problem Critical
Detector: Automation Aircraft Other Automation; Person Flight Crew
When detected: In-flight
Result: Flight Crew Executed Go Around / Missed Approach; Flight Crew Landed in Emergency Condition; General Declared Emergency; General Maintenance Action
Contributing factors: Aircraft
Primary problem: Aircraft

Narrative: We were on a visual approach following an uneventful flight. At approximately 2;000 FT; the Captain; who was flying the leg; asked for the landing gear extension. I lowered the landing gear and almost immediately; we starting receiving numerous ECAM messages. The Captain continued flying while I began running the ECAM sequence. We quickly deduced that we had lost all quantity in the Green Hydraulic System. After a brief analysis and discussion; we informed Tower that we would be going around. After beginning the go around sequence; we were handed off to Approach Control. The Captain instructed me to declare an emergency and inform ATC that we would like vectors to sort out the issue and accomplish appropriate checklists. We also requested an eventual return to [the long runway]. After completing all procedures; communicating with company and cabin crew; we agreed that we were ready to return for landing and were vectored for a visual approach. We informed Tower that there was a good possibility that we would have to stop on the runway due to no steering capabilities. The Captain flew the approach and landing and we touched down without incident. The Captain was able to steer the aircraft clear of the runway on a high speed taxiway. After stopping the aircraft; we shut down the engines allowing inspection by the emergency/fire personnel. They informed us everything appeared normal; and we waited for the arrival of our tow-in vehicle. We were subsequently towed to the gate without incident.




Synopsis: A320 crew experienced a Green Hydraulic System failure during approach when the landing gear was extended. A go around initiated; an emergency declared; and ECAM actions complied with before returning to land on the longest runway.
Date: 201707
Local time of day: 1201-1800
Location: ZZZ.Airport, US
Flight conditions: VMC
Weather elements / visibility: 10
Light: Daylight
Aircraft: M-7
Operating under: Part 91
Flight plan: None
Mission: Training
Flight phase: Takeoff / Launch
Airspace: Class G ZZZ
ATC / advisory: CTAF ZZZ
Reporter function: Pilot Flying; Single Pilot
Reporter qualification: Flight Crew Commercial; Flight Crew Flight Instructor; Flight Crew Multiengine; Flight Crew Instrument
Human factors: Situational Awareness
Anomaly: Aircraft Equipment Problem Critical; Inflight Event / Encounter Fuel Issue
Detector: Person Flight Crew
When detected: In-flight
Result: Flight Crew Landed in Emergency Condition; Flight Crew Took Evasive Action
Contributing factors: Human Factors
Primary problem: Human Factors

Narrative: I departed with a Switzer 2-33 glider on glider orientation flight in tow. At about 400 feet the engine lost power; I signaled the glider to release (easily made it back to the runway); and I quickly sought a place to make an off-airport landing (did not have sufficient altitude to make it back to airport). I landed in a field of low stubble and soggy grass without incident. The aircraft did not appear to be damaged. There were no structures on the ground and no damage/injuries.  While there appeared to be more than sufficient fuel for the flight; fuel starvation made have been the cause for the loss of power.




Synopsis: Glider tow pilot reported a loss of power after takeoff that resulted in an early release of the glider and an off-field landing.
Date: 202107
Local time of day: 1201-1800
Location: ZZZ.TRACON, US
Flight conditions: VMC
Weather elements / visibility: 10
Light: Daylight
Aircraft: PA-28 Cherokee/Archer/Dakota/Pillan/Warrior
Operator: Personal
Operating under: Part 91
Flight plan: VFR
Mission: Training
Flight phase: Climb
Airspace: Class E ZZZ
ATC / advisory: TRACON ZZZ
Aircraft component: Engine
Component problem: Malfunctioning
Reporter organization: Personal
Reporter function: Pilot Flying
Reporter qualification: Flight Crew Commercial; Flight Crew Instrument
Human factors: Time Pressure; Troubleshooting; Workload
Anomaly: Aircraft Equipment Problem Critical; Ground Event / Encounter Ground Strike - Aircraft
Detector: Person Flight Crew
When detected: In-flight
Result: Aircraft Aircraft Damaged; Flight Crew Landed in Emergency Condition; Flight Crew Requested ATC Assistance / Clarification; General Evacuated
Contributing factors: Aircraft
Primary problem: Aircraft

Narrative: I was conducting a local flight in the training area doing practice maneuvers for my CFI (Flight Instructor) check ride. I am a commercial rated pilot with instrument rating. I conducted some ground reference maneuvers and after completing those I started a climb for 2;500 feet. During the climb; my 30 minute timer went off and I changed the fuel tanks.  Within a couple minutes after changing the tanks; the engine suddenly suffered partial power loss and the RPM dropped to 1;000 RPM and stayed there. I began to troubleshoot (my first thought was that it was related to the fuel selector.) I ensured that the throttle and mixture were full; the then swapped the fuel selector back to the left tank. I attempted to crank the engine; but it was still running. I continued my ABC emergency checks and called Approach and alerted them to my engine trouble. The engine did not stop at any time; but the RPM stayed at 1000 RPM. I told Approach of the situation and told them I was landing in a grass field. At this point; I fully committed to landing in the grass field. The field had tall grass and lots of berms. The berms and drag from the grass caused the nose gear to collapse and the right wing to hit the ground. After landing I turned everything off and we exited the aircraft. I used a hand held radio to contact Approach and let them know we were fine and no injuries. We proceeded to contact local authorities; the company I rented from and the owner.




Synopsis: Pilot reported losing engine power and landing in a grass field when the gear collapsed and right wing struck the ground.
Date: 201605
Location: ZMP.ARTCC, MN
Flight conditions: VMC
Light: Daylight
Aircraft: B737-700
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Flight phase: Descent
Airspace: Class A ZMP
ATC / advisory: Center ZMP
Aircraft component: FMS/FMC
Component problem: Design
Reporter organization: Air Carrier
Reporter function: First Officer; Pilot Not Flying
Reporter qualification: Flight Crew Air Transport Pilot (ATP)
Human factors: Situational Awareness
Anomaly: Aircraft Equipment Problem Less Severe; Deviation - Altitude Crossing Restriction Not Met; Deviation - Altitude Undershoot; Deviation / Discrepancy - Procedural Clearance; Deviation / Discrepancy - Procedural Published Material / Policy
Detector: Person Flight Crew
When detected: In-flight
Result: Aircraft Automation Overrode Flight Crew
Contributing factors: Aircraft; Human Factors
Primary problem: Ambiguous

Narrative: We were level at 39;000 feet and given a crossing restriction of OHHMY at 31;000 feet. The FMC was programmed correctly and VNAV engaged. During the descent; the aircraft reverted from VNAV PATH to VNAV SPEED. I called out the deviation to the Pilot Flying (PF). He selected Vertical Speed mode and extended the speedbrakes. We still had time to make the cross. But the Vertical Speed selected was not enough. I pointed out we were still going to be high; and the PF increased the descent rate selected. But then as we were catching up the aircraft entered 'ALT ACQ' around 1000 feet above our altitude and slowed its descent much more than typical for this situation almost leveling 600 feet high. I again pointed out we were going to be high in this configuration but the PF chose to keep the autopilot engaged. We were around 400 feet high. When this happens a more immediate and adequate response needs to be initiated keeping in mind the time required to level off.




Synopsis: B737-700 First Officer as the Pilot Monitoring noted that the aircraft had reverted from VNAV PATH to VNAV SPEED while descending to make a crossing restriction. The Captain attempted to use vertical speed and the speed brake to make the restriction with the autopilot engaged; but Altitude Acquire occurs a 1;000 feet above and the fix is crossed 400 feet high.