elihoole/asrs-aviation-reports huggingface dataset:
Date: 201204
Local time of day: 0001-0600
Location: ZGSZ.Tower, FO
Flight conditions: IMC
Weather elements / visibility: 1
Light: Night
Aircraft: B757-200
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Ferry / Re-Positioning
Flight phase: Landing
ATC / advisory: Tower ZGSZ
Aircraft component: Cockpit Window
Component problem: Malfunctioning
Reporter organization: Air Carrier
Reporter function: Pilot Flying; Captain
Reporter qualification: Flight Crew Air Transport Pilot (ATP)
Human factors: Communication Breakdown; Confusion; Physiological - Other; Situational Awareness; Time Pressure
Anomaly: Aircraft Equipment Problem Less Severe; Deviation / Discrepancy - Procedural Clearance; Inflight Event / Encounter Weather / Turbulence
Detector: Person Air Traffic Control
When detected: In-flight
Result: Air Traffic Control Issued New Clearance; Flight Crew Became Reoriented
Contributing factors: Human Factors; Aircraft; Environment - Non Weather Related; Weather
Primary problem: Ambiguous

Narrative: I was the pilot flying; I briefed the ILS approach to 16 at ZGSZ and I briefed that I will clear off to the left on high speed Taxiway E7.  The weather was IMC with moderate rain on final and throughout the landing roll.  My windshield heat was turned off as per the checklist; due to arcing during cruise; also; my windshield was not clearing rain water off the upper half of my windshield window.  During the landing roll on Runway 16 and while I was aiming for the green lead in taxi lights to what I thought it was Taxiway E7; the Tower Controller called us and asked to expedite clearing off the runway due to traffic on 4 miles final behind us.  Unfortunately; at that point the First Officer felt the urgency to clear off and called out loud and clear that I missed Taxiway E7 and that I needed the taxi off the very next taxiway.  Since I had limited visibility due to the windshield issues I mentioned above; I felt that the First Officer may be 100% sure that I did in fact miss Taxiway E7; at which point I felt compelled to clear off the taxiway that was immediately to our left; and in which we later found of that it was Taxiway E6 and in fact we never passed Taxiway E7.  Of course E6 was listed as closed in the NOTAMs; the Tower queried us; and we told him where we were; he then told us that E6 was closed; proceeded to instruct us to taxi to the first part of Romeo and Taxiway Sierra and hold short of Runway 15.  Taxiway E6 never had any construction work going on; nor any barricades with red lights placed on it; we were never in any danger of impacting any object. The remaining taxi into the ramp was uneventful.  Later the First Officer realized that he rushed into making the call to me that I missed Taxiway E7 and that he did not want to see company traffic behind us go around; especially in thunderstorms around the airport.




Synopsis: A B757-200 landed at ZGSZ with clearance to exit at Taxiway E7; but because of rain; a non functional window heat and being rushed; exited at the closed Taxiway E6 then were give additional instructions.
Date: 201707
Local time of day: 1201-1800
Location: ZZZ.ARTCC, US
Flight conditions: VMC
Weather elements / visibility: 100
Light: Daylight
Aircraft: Military
Operator: Personal
Operating under: Part 91
Flight plan: None
Mission: Personal
Flight phase: Cruise
Airspace: Class E ZZZ
ATC / advisory: Center ZZZ
Reporter organization: Personal
Reporter function: Single Pilot; Pilot Flying
Reporter qualification: Flight Crew Commercial
Human factors: Situational Awareness; Communication Breakdown
Anomaly: Conflict Airborne Conflict
Detector: Person Flight Crew
When detected: In-flight
Result: General None Reported / Taken
Contributing factors: Airspace Structure; Procedure
Primary problem: Procedure

Narrative: In cruise flight at 10;500 ft at about 240 kts GS; contacted Center to request flight following and was given a squawk. Within 5 minutes was told leaving sector and to squawk VFR; and try to contact [the next controlling agency] if desired. About 1 minute later while looking up the frequency for next possible controller; I looked up and was shocked to see a regional airliner crossing immediately overhead; passing from west to east. I had not changed altitude; speed or heading.I've never passed that close to another aircraft without being in formation with them. I can't imagine the controller was unaware of how close we passed; and I feel certain the airliner must have had TCAS activated by the encounter. The encounter really shook me for several minutes; which later turned to anger; as I never would have expected to be that close to another aircraft; especially a passenger aircraft if either of us were in contact with ATC. Perhaps the airliner had received an advisory and had me in sight; but I doubt it as [my aircraft] is camouflaged and very difficult to see in flight.I plan to call ATC to ask about the incident; and hope I will learn that the situation was in fact under control. Regardless; I feel strongly that I should have been advised before being dismissed from the freq.; if just out of courtesy.

Callback: The reporter stated that he was on a return trip from an air show when he encountered an airliner passed about 500 ft overhead. The reporter stated that he was in cruise at about 10;500 ft; and just released by ATC to another sector. While changing frequency on the radio to communicate with the next sector; an airliner passed overhead without warning from ATC. The Reporter stated that he feels the controller should have warn him of the airliner passing over him. The reporter also stated that it startled him quite a bit. The reported stated that he has not contacted ATC about the incident.



Synopsis: The pilot of a vintage military aircraft reported that while in cruise an airliner crossed overhead without warning.
Date: 201910
Aircraft: B757 Undifferentiated or Other Model
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Flight phase: Cruise
Airspace: Class A ZZZ
Reporter organization: Air Carrier
Reporter function: Captain; Pilot Flying
Reporter qualification: Flight Crew Instrument; Flight Crew Multiengine; Flight Crew Air Transport Pilot (ATP)
Human factors: Fatigue; Situational Awareness
Anomaly: Deviation / Discrepancy - Procedural FAR; Deviation / Discrepancy - Procedural Published Material / Policy; Inflight Event / Encounter Other / Unknown
Detector: Person Flight Crew
When detected: In-flight
Result: Flight Crew Became Reoriented
Contributing factors: Company Policy; Human Factors; Staffing; Aircraft
Primary problem: Company Policy

Narrative: Aircraft had a maintenance issue; the APU generator kept tripping off; and company finally decided to switch aircraft. We finally departed close to XA:00; about 1.5 hours before our duty CCO ran out. During the pre-departure brief we talked about the late hour and fatigue being a threat. Once we were in cruise flight we both felt very tired and talked about how we wished we had an IRO (International Relief Officer) so that we could get a break and some sleep. About 3-4 hours into the flight I accidentally nodded off. I am not sure how long I was asleep; but it was probably not more than 5-10 minutes. When I woke up; I noticed the First Officer had accidentally fallen asleep as well. Both pilots had fallen asleep at the controls! These late departures unaugmented are bad enough; but when you have a delay that lasts several hours; they are downright dangerous. Even if you feel OK at departure; you can 'crash' a few hours into the flight. I had taken a short nap about 5 hours before check-in; but was still very tired after take-off. Thankfully; nothing bad happened; but the potential for a dangerous situation was there.




Synopsis: B757 Captain reported that flight delays and fatigue caused him and the First Officer to fall asleep during flight.
Date: 201203
Local time of day: 1801-2400
Location: ZZZ.Airport, US
Flight conditions: VMC
Aircraft: MD-83
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Landing
ATC / advisory: Tower ZZZ
Aircraft component: Main Gear
Component problem: Failed
Reporter organization: Air Carrier
Reporter function: Pilot Not Flying; First Officer
Reporter qualification: Flight Crew Air Transport Pilot (ATP)
Second reporter function: Pilot Flying; Captain
Anomaly: Aircraft Equipment Problem Critical
Detector: Person Flight Crew
When detected: Other Landing roll
Result: Flight Crew Took Evasive Action
Contributing factors: Aircraft
Primary problem: Aircraft

Narrative: Normal flare and landing for the conditions. During touchdown autospoilers deployed then failed. As we slowed down there was a violent vibration. The Captain indicated that it felt like we had blown a tire on landing. I advised the Tower. We came to a complete stop straight ahead and I advised the Flight Attendants of the situation and told them to 'Standby'. The Tower said they saw smoke and we requested emergency services to come and inspect. We then advised the Tower that we were disabled on the runway. We consulted the QRH for blown tire/gear abnormalities but nothing suited the situation. Emergency services advised us the left main gear had rotated perpendicular to the aircraft. All checklists and procedures were completed. No passengers; crew or ground personal reported any injuries.


Second narrative: We kept the aircraft on the centerline of the runway until almost full stop. We had a slight left quartering headwind at a steady 24 KTS. Proper techniques and speeds were applied for this landing condition.


Synopsis: An MD-83 flight crew experienced a failed left main landing gear on the landing roll; disabling the aircraft on the runway.
Date: 201408
Local time of day: 1201-1800
Location: MDW.Airport, IL
Flight conditions: VMC
Light: Daylight
Aircraft: B737-700
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Flight phase: Initial Approach
Airspace: Class C MDW
ATC / advisory: Tower MDW
Second aircraft: B737 Undifferentiated or Other Model
Reporter organization: Air Carrier
Reporter function: Captain; Pilot Flying
Second reporter function: First Officer; Pilot Not Flying
Anomaly: Deviation - Speed All Types; Deviation / Discrepancy - Procedural Published Material / Policy; Inflight Event / Encounter Unstabilized Approach; Inflight Event / Encounter Wake Vortex Encounter
Detector: Person Flight Crew
When detected: In-flight
Result: General None Reported / Taken
Contributing factors: Procedure; Environment - Non Weather Related
Primary problem: Ambiguous

Narrative: Close in behind [B737] and encountered a fairly good wake. Powered out and then was high on path and oversped flaps by two knots. Did S-turn and selected [flaps] 40 just under 1;000 FT AGL.  Stable at 500 FT but still should have just gone around!


Second narrative: I was the pilot not flying on an arrival to [Runway] 4R into MDW. We were cleared the visual approach behind another aircraft. We were about four miles in trail when the aircraft ahead slowed rather quickly and we closed into about 2.5 to 3 miles behind him. The Captain tried to slow our aircraft as quickly as he could by disconnecting the autopilot and pitching up a bit and calling for more flaps. I deployed the flaps to 30 when we were below the flap maneuvering speed. I called out to watch the airspeed; however; the Captain oversped the flaps 30 speed by about two to three knots for about two seconds. He slowed the aircraft to below flaps 40 speed and called for them at that time which was slightly below 1;000 FT AGL. He was completely stabilized before reaching 500 FT AGL and landed in the touchdown zone on speed.Situational awareness is key here; to anticipate the aircraft in front of you slowing at a specific time and being prepared and configured to do the same.


Synopsis: B737-700 Captain reported encountering wake turbulence on arrival to MDW in trail of a B737 that resulted in a minor flap overspeed and an unstablized approach.
Date: 201401
Local time of day: 1801-2400
Location: ORD.Airport, IL
Light: Night
Aircraft: Challenger 300
Operator: Corporate
Operating under: Part 91
Flight plan: IFR
Mission: Ferry / Re-Positioning
Flight phase: Taxi
ATC / advisory: Tower ORD
Aircraft component: Safety Instrumentation & Information
Component problem: Design
Reporter organization: Corporate
Reporter function: Captain
Reporter qualification: Flight Crew Air Transport Pilot (ATP); Flight Crew Multiengine; Flight Crew Instrument; Flight Crew Flight Instructor
Human factors: Communication Breakdown; Distraction; Human-Machine Interface; Situational Awareness
Anomaly: ATC Issue All Types; Aircraft Equipment Problem Less Severe; Deviation / Discrepancy - Procedural Clearance; Ground Event / Encounter Other / Unknown
Detector: Person Flight Crew
When detected: Taxi
Contributing factors: Aircraft; Human Factors
Primary problem: Human Factors

Narrative: Occurrence 1) upon landing at ORD ATC's instructions blocked/missed because of RAAS [Runway Alerting and Advisory System] warning for an aircraft on short final behind us. Occurrence 2) ATC had us taxi on a runway not being used. Missed ATC exit instructions because of RAAS broadcasting in our ears. Two separate occurrences in under a minute at the busiest airport in the US. Potentially dangerous situations because of nuisance RAAS calls. RAAS should have a mute button or a way for the pilot to override it.




Synopsis: A CL30 Captain railed against the intrusive nature of RAAS warnings when taxiing on busy airports. Believes flight crew control of warning volume is an acceptable alternative.
Date: 201408
Location: ZZZ.ARTCC, US
Aircraft: B737-300
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: MCP
Component problem: Failed; Malfunctioning
Reporter organization: Air Carrier
Reporter function: First Officer; Pilot Not Flying
Anomaly: Aircraft Equipment Problem Less Severe
Detector: Person Flight Crew
When detected: In-flight
Result: Air Traffic Control Issued New Clearance; Flight Crew Diverted; Flight Crew Overcame Equipment Problem
Contributing factors: Aircraft
Primary problem: Aircraft

Narrative: Cruising at FL350; we had a MCP lock up. We lost the autopilot; both flight directors; and the altitude alert was going off every few seconds. At this point; we decided to exit RVSM airspace and ATC gave us a descent to FL290. We then notified Dispatch. The Captain then gave me the airplane and ran the MCP procedure to no avail. The Captain then took the airplane and; while waiting on a response from Dispatch and listening to the altitude alert going off every few seconds and still avoiding thunderstorms; I then offered to run the procedure. I ran the procedure and we got the MCP back. The MCP was working for quite some time. I think around this time; Dispatch got back to us and told us to go to ZZZ. As we began our descent into ZZZ; the MCP locked up again on us. Now with no flight directors; autopilot; and the altitude alert going off again every few seconds and the ensuing night approach; I offered to run the procedure again thinking we could get the MCP back long enough to land in ZZZ as the MCP worked for some time after we got it back the first time. With all the distractions of not having an autopilot or flight directors; and the altitude alert going off every few seconds; the Captain agreed and I ran it again.  We got the MCP back and landed uneventfully. We made a logbook writeup; changed airplanes; and continued to our scheduled destination.




Synopsis: B737-300 First Officer experiences an MCP failure at FL350; losing both autopilots; the flight directors and the altitude alerting system and descends out of RVSM airspace. The first reset attempt by the Captain is not successful but the second attempt by the First Officer is. Dispatch is contacted and replies with diversion instructions as the MCP fails again. The MCP is reset again and functions to landing.
Date: 201209
Local time of day: 1801-2400
Location: OJC.Airport, KS
Flight conditions: VMC
Weather elements / visibility: 5
Light: Night
Aircraft: Skyhawk 172/Cutlass 172
Operator: Personal
Operating under: Part 91
Flight plan: None
Mission: Training
Flight phase: Taxi
ATC / advisory: CTAF OJC
Reporter organization: Personal
Reporter function: Instructor
Reporter qualification: Flight Crew Flight Instructor; Flight Crew Air Transport Pilot (ATP); Flight Crew Instrument; Flight Crew Multiengine
Human factors: Confusion
Anomaly: No Specific Anomaly Occurred All Types
Detector: Person Flight Crew
When detected: Taxi
Result: General None Reported / Taken
Contributing factors: Airport; Human Factors
Primary problem: Airport

Narrative: Johnson County Executive Airport needs a serious revamp of airport markings and runway hold position signage.  AT NIGHT you CANNOT see their ground taxiway and runway markings.  No reflective component is added to the taxiway marking paint.  There is VERY LOW CONTRAST between runway markings and pavement.  Areas have NON AIM STANDARD hold bars not authorized by FAA.  EACH RUNWAY intersection should have a standard ICAO runway hold sign (red with white numbers).  Perhaps they should also paint red runway hold markers at the hold bars.  In any event the yellow lead lines and taxiway markings (especially on the southwest turnoffs of runway 18) need to be repainted with black contrast bars and/or reflective yellow paint --- it is VERY difficult to figure out taxiway at night.  This is a safety of flight issue that should be addressed with Johnson County airport operator.




Synopsis: C172 instructor reports OJC taxiway markings and signage are inadequate and in need of refurbishment with reflective paint.
Date: 202201
Local time of day: 1201-1800
Location: ZZZ.ARTCC, US
Flight conditions: VMC
Weather elements / visibility: 10
Light: Daylight
Aircraft: Beechjet 400
Operator: Air Taxi
Operating under: Part 91
Flight plan: IFR
Mission: Ferry / Re-Positioning
Flight phase: Initial Approach
Airspace: Class E ZZZ
ATC / advisory: TRACON ZZZ
Aircraft component: Trailing Edge Flap
Component problem: Malfunctioning
Reporter organization: Corporate
Reporter function: Captain
Reporter qualification: Flight Crew Air Transport Pilot (ATP); Flight Crew Flight Instructor; Flight Crew Instrument; Flight Crew Multiengine
Human factors: Troubleshooting
Anomaly: Aircraft Equipment Problem Critical; Deviation / Discrepancy - Procedural Published Material / Policy
Detector: Person Flight Crew
When detected: In-flight
Result: Air Traffic Control Provided Assistance; Flight Crew Diverted; Flight Crew Landed in Emergency Condition; Flight Crew Requested ATC Assistance / Clarification; General Flight Cancelled / Delayed; General Maintenance Action
Contributing factors: Aircraft
Primary problem: Aircraft

Narrative: Flight to ZZZ. Upon reaching the ZZZ1 location; I called for full flaps. Speed check was called and flaps didn't move to 30 degrees. Flaps got stuck in the exact position as with the previous de-ice check; and called for a recycle of flaps. Flaps didn't move at all. They were plainly stuck. We called for missed in order to assess the situation. We recycled the flaps a couple of more times with no position changes. We opted to divert to ZZZ2 and cycle the flaps a couple of time without success. We made a video of the problem. While enroute to ZZZ2; ATC assigned priority handling on our behalf. We landed safely without any other incidents in ZZZ2. While taxing out and clear of runway; I called for after landing checklist. When moving the flap handle to 0 degrees the flaps retracted properly!Upon landing ATC/ZZZ2/Ground informed that there was no need to file a report.




Synopsis: Beechjet 400 Captain reported trailing edge flaps failed to extend completely and remained locked. The flight crew elected to divert.
Date: 202007
Local time of day: 0601-1200
Location: PHL.Airport, PA
Flight conditions: VMC
Light: Daylight
Aircraft: EMB ERJ 145 ER/LR
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Takeoff / Launch
Airspace: Class B ZZZ
Aircraft component: Nose Gear
Component problem: Malfunctioning
Reporter organization: Air Carrier
Reporter function: Captain; Pilot Flying
Reporter qualification: Flight Crew Air Transport Pilot (ATP); Flight Crew Multiengine; Flight Crew Instrument
Anomaly: Aircraft Equipment Problem Critical; Deviation / Discrepancy - Procedural Published Material / Policy; Ground Event / Encounter Other / Unknown
Detector: Person Flight Crew
When detected: In-flight
Result: Air Traffic Control Provided Assistance; Flight Crew Landed in Emergency Condition; Flight Crew Returned To Departure Airport; General Flight Cancelled / Delayed; General Maintenance Action
Contributing factors: Aircraft; Procedure
Primary problem: Aircraft

Narrative: On takeoff roll after 80 kts. received a batt 1 off bus master caution after hitting a hard bump on the runway. We continued the roll out and take off. After gear up received a landing gear lever a/g fail master caution. Followed by a eng 1;2 thrust reverser disagree. The thrust lever interlocks started clicking in rapid succession and continued until landing configuration. We asked to remain in the terminal area while we ran the QRH. After running the QRH we advised ATC and setup for a extended downwind for runway 27L because there was concern we may have had degraded braking; no spoilers; and no reversers. We made a flaps 45 landing and on landing the nose strut fully compressed putting the aircraft at an unusually low nose down pitch. Upon reaching the gate maintenance informed us of a fully compressed nose wheel strut.We detected the chain of events on takeoff rollout just after reaching 80 kts.Unsure of the root cause.We ran the QRH and then advised ATC and completed landing and returned to the gate without incident.




Synopsis: Captain reported caution lights at 80 kts and striking something on runway; resulting in a return to the departure airport.
Date: 201501
Local time of day: 1201-1800
Location: AFW.Airport, TX
Light: Dusk
Aircraft: Small Aircraft
Operating under: Part 91
Flight phase: Landing
Airspace: Class D AFW
ATC / advisory: Tower AFW
Second aircraft: Light Transport; Low Wing; 2 Turbojet Eng
Reporter organization: Government
Reporter function: Instructor; Local
Reporter qualification: Air Traffic Control Fully Certified
Human factors: Situational Awareness; Distraction; Communication Breakdown; Training / Qualification
Anomaly: ATC Issue All Types; Conflict Ground Conflict; Less Severe; Deviation / Discrepancy - Procedural Clearance; Deviation / Discrepancy - Procedural Published Material / Policy
Detector: Person Air Traffic Control
When detected: In-flight
Contributing factors: Human Factors; Procedure
Primary problem: Procedure

Narrative: Training on local was in progress with 3 aircraft in left traffic Runway (RWY) 34L. A mix of several IFR/VFR arrivals landing and departing RWY 34R. Helicopter in left traffic taxiway Papa. Helicopters departing taxiway Alpha at Bell and the FBO. Ground Control (GC) also taxiing aircraft out on taxiway Alpha. Coordination for use of Alpha was accomplished between Local Control (LC) and GC. Trainee cleared Aircraft Y for takeoff RWY 34R. Aircraft X was on short final RWY 34R. I asked the trainee if she cleared Aircraft X to land 34R in hopes that he would be slow enough and not land past where Aircraft Y would start departure roll on the other runway. She said he was; this was incorrect. As it developed Aircraft X passed over the displaced threshold as Aircraft Y started departure role; Aircraft Y was beyond the departure end as Aircraft X started powering back up making a touch and go not a full stop. I'm not sure if this fits the definition of a simultaneous operation since Aircraft X never passed Aircraft Y but I wanted to be sure.Send Aircraft X around.




Synopsis: AFW instructor reports of a loss of separation due to not sending an aircraft around after Developmental clears a jet for takeoff.