elihoole/asrs-aviation-reports huggingface dataset:
Date: 201202
Local time of day: 1801-2400
Location: ZZZ.Airport, US
Light: Night
Aircraft: B757-200
Operator: Air Carrier
Operating under: Part 121
Mission: Passenger
Flight phase: Parked
Aircraft component: Fan Blade
Reporter organization: Air Carrier
Reporter function: Technician
Human factors: Other / Unknown
Anomaly: Aircraft Equipment Problem Critical; Deviation / Discrepancy - Procedural Published Material / Policy; Ground Event / Encounter FOD
Detector: Person Maintenance
When detected: Routine Inspection
Result: Aircraft Aircraft Damaged; General Maintenance Action
Contributing factors: Human Factors
Primary problem: Human Factors

Narrative: I am filing this report for visibility. A B757-200 aircraft arrived February 2012. A midnight shift Mechanic was in the process of doing a service check and he saw damage to three fan blades in #1 engine and also some damage to the fan exit case and fan exit guide vanes. Upon further investigation; an 8-inch file was found laying up against the fan exit guide vanes. The fan blades were replaced and the other damage was either repaired or deferred.




Synopsis: A Maintenance Technician reports that a midnight shift Technician found an 8-inch file laying up against the fan exit guide vanes of #1 engine during a service check on a B757-200 aircraft after noticing damage to three fan blades; the fan exit case; and fan exit guide vanes.
Date: 201811
Local time of day: 1801-2400
Location: HOU.Airport, TX
Light: Night
Aircraft: Commercial Fixed Wing
Operator: Air Carrier
Operating under: Part 121
Mission: Passenger
Flight phase: Climb
Airspace: Class D HOU
ATC / advisory: Center ZHU
Reporter organization: Air Carrier
Reporter function: Captain; Pilot Flying
Reporter qualification: Flight Crew Multiengine; Flight Crew Air Transport Pilot (ATP); Flight Crew Instrument
Human factors: Workload; Time Pressure; Situational Awareness; Communication Breakdown; Distraction
Anomaly: ATC Issue All Types; Deviation - Track / Heading All Types; Deviation / Discrepancy - Procedural Clearance; Inflight Event / Encounter Weather / Turbulence
Detector: Person Flight Crew
When detected: In-flight
Result: Air Traffic Control Provided Assistance; Flight Crew Requested ATC Assistance / Clarification
Contributing factors: Weather; Human Factors
Primary problem: Weather

Narrative: Houston Center was busy handling traffic holding for SAT and AUS; and was consequently slow to take a handoff from Departure. They then held us low and on a vector towards thunderstorms. After we asked; unsuccessfully; several times for a climb and/or a turn to avoid the weather; I came on the radio and advised Center that we needed to deviate now and asked if they preferred us to go left or right. They directed us to deviate left. I did not have to invoke my emergency authority as a Captain to deviate from our clearance; but this is as close as I've come. It seemed to me that they were snowed under by organizing all the holds and allowed that task to interfere with keeping traffic clear of thunderstorms. Having to work multiple frequencies and handling extra traffic puts a burden on understaffed Controllers in the best of conditions; I feel that in this case the extra task loading caused by deteriorating weather interfered with their ability to prioritize those tasks.




Synopsis: Air carrier pilot reported the need to deviate for weather while ATC was too busy to initially respond.
Date: 202103
Local time of day: 1201-1800
Location: CLT.Airport, NC
Aircraft: Commercial Fixed Wing
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Initial Approach
Airspace: Class B CLT
ATC / advisory: TRACON CLT
Reporter qualification: Flight Crew Air Transport Pilot (ATP); Flight Crew Instrument; Flight Crew Multiengine
Human factors: Confusion; Distraction; Situational Awareness
Anomaly: ATC Issue All Types; Aircraft Equipment Problem Less Severe; Deviation - Track / Heading All Types; Deviation / Discrepancy - Procedural Clearance
Detector: Person Flight Crew
When detected: In-flight
Result: General None Reported / Taken
Contributing factors: ATC Equipment / Nav Facility / Buildings; Aircraft; Airport; Human Factors
Primary problem: ATC Equipment / Nav Facility / Buildings

Narrative: On a vector to final; about 20 NM south of CLT; I observed the flight mode change from HDG to LNAV; then about 10 seconds later the flight director commanded a turn in the wrong direction. We were expecting all left turns to final; so when I saw the airplane starting to bank to the right; I immediately pressed the TCS button and leveled the wings.The first time that I saw this happen recently; I dismissed it as a fluke. But this has now happened to me 3 times at the same airport on different approaches. I would estimate this is happening on about 15% of all approaches to this airport now. It starts with a vector to the intermediate approach course; arming the LNAV mode; and shortly after switching modes the computer steers the airplane across the approach course; over-corrects back in the opposite direction; and then chases the CDI to a normal alignment.This error in navigation; even though semi-random in frequency; is of such concern that I have been briefing the risk of TCAS activations and NTZ [No Transgression Zone] incursions that could be caused by this computer glitch. At this airport; it is fair to assume that there is always traffic on the simultaneous parallel course. Today; I briefed this possibility with the pilot flying while at cruise; and his reaction when it happened; although not as fast as mine; was understandable. He thought the turn was at first a subtle deviation in the direction of the final course.




Synopsis: Air carrier pilot reported that the flight director commanded a turn in the wrong direction during approach to CLT airport.  Reporter advised; 'this has now happened to me 3 times at the same airport on different approaches.'
Date: 201210
Local time of day: 1201-1800
Location: PCT.TRACON, VA
Flight conditions: VMC
Light: Daylight
Aircraft: Regional Jet 200 ER/LR (CRJ200)
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Flight phase: Initial Approach
ATC / advisory: TRACON PCT
Second aircraft: Any Unknown or Unlisted Aircraft Manufacturer
Reporter organization: Air Carrier
Reporter function: Pilot Not Flying; First Officer
Human factors: Situational Awareness
Anomaly: Conflict Airborne Conflict; Deviation - Altitude Excursion From Assigned Altitude
Detector: Automation Aircraft RA; Automation Aircraft TA; Person Flight Crew
When detected: In-flight
Result: Air Traffic Control Issued New Clearance; Flight Crew Took Evasive Action
Contributing factors: Procedure; Airspace Structure; Human Factors
Primary problem: Ambiguous

Narrative: On the TRUPS ONE RNAV arrival into DCA; between RLLLL and LACKE at 6;000 feet we noticed traffic at our 12 o'clock; less than five miles ahead; roughly around 300 to 400 feet above us on the TCAS.  We confronted ATC and asked if they had traffic in front of us; the controller simply replied; 'Yes; there is traffic in front of you.' At this time we received a TCAS alert followed by an audible warning to monitor vertical speed.  We then complied with the RA and descended to avoid the traffic.  We notified ATC and were instructed to continue our descent to 4;000 feet.  In our descent we saw the traffic which appeared to be a light single engine aircraft.  We then continued on the arrival and landed in DCA uneventfully.  This event occurred due to the lack of assistance from ATC.  They could have simply given us a heading to avoid the traffic but instead gave us an ignorant response.




Synopsis: CRJ200 First Officer reports a TCAS RA during the TRUPS 1 arrival to DCA at 6;000 feet.  ATC does not seem concerned and issues a descent clearance only after a descent is initiated by the crew in compliance with the RA.
Date: 202106
Local time of day: 0601-1200
Location: DFW.Airport, TX
Aircraft: Commercial Fixed Wing
Operator: Air Carrier
Operating under: Part 121
Mission: Passenger
Flight phase: Taxi
ATC / advisory: Ground DFW
Reporter organization: Air Carrier
Reporter function: Captain; Pilot Flying
Reporter qualification: Flight Crew Instrument; Flight Crew Air Transport Pilot (ATP); Flight Crew Multiengine
Human factors: Confusion; Communication Breakdown; Situational Awareness
Anomaly: ATC Issue All Types; Deviation / Discrepancy - Procedural Clearance; Ground Incursion Taxiway
Detector: Person Air Traffic Control
When detected: Taxi
Result: Flight Crew Requested ATC Assistance / Clarification
Contributing factors: Human Factors
Primary problem: Human Factors

Narrative: Taxiing out from spot. Ground controller stated 'After the heavy join Lima Zulu bridge to 18L'.  As trained; the FO (First Officer) read back the clearance and stated the clearance to the Captain. As the Captain; I stated the clearance back to the FO. As we proceeded to Lima taxiway the Ground Controller stated ' Aircraft X where are you going?'  The FO stated you ' said join Lima...' upon to which I said to the FO that's what the Controller said.  After being felt like we made a mistake. The FO and myself noticed this Controller made a few more clearance errors that needed to be corrected. The FO and I (Captain) discussed the event later on. Suggestions from our side that might have caused the event is that:1) The Controller might have been tired at the end of their shift. 2) Controller had grown complacent and had expectation bias of what Company operated aircraft doing what they 'normally' do.       From the crew side of the event; we should have questioned the clearance since it was an abnormal clearance.  Bring back pre- COVID staffing to ATC so proper rest can be had for ATC personnel.




Synopsis: Air Carrier flight crew reported incorrect taxi clearance was issued by ATC and cited possible staffing issues at the controlling facility as a contributing factor.
Date: 201910
Local time of day: 1801-2400
Location: 50R.Airport, TX
Flight conditions: VMC
Weather elements / visibility: 10
Light: Night
Aircraft: Cessna Aircraft Undifferentiated or Other Model
Operator: Personal
Operating under: Part 91
Flight plan: None
Mission: Personal
Flight phase: Takeoff / Launch
ATC / advisory: CTAF 50R
Reporter organization: Personal
Reporter function: Pilot Flying; Single Pilot
Reporter qualification: Flight Crew Private
Anomaly: Aircraft Equipment Problem Less Severe; Ground Event / Encounter Person / Animal / Bird
Detector: Person Flight Crew
When detected: In-flight
Result: Flight Crew Rejected Takeoff; General Maintenance Action
Contributing factors: Airport; Environment - Non Weather Related
Primary problem: Environment - Non Weather Related

Narrative: I was taking off in a Cessna 172 at night at 50R. I was making three takeoffs and landings at night in order to be able to fly passengers at night. I flew once around the pattern; landed; and taxied back to the beginning of the runway. I looked down the runway; and it was clear. I started my normal takeoff roll and reached 50 kts. I was just about to rotate when a herd of five deer jumped onto the runway from the left side. The dear ran in front of the airplane; and the airplane struck one of the dear. There was no action I could have taken to avoid hitting the dear; as the plane was moving too fast to bring it to a full stop in time; and the herd was dispersed across the entire runway. I immediately aborted the takeoff by pulling the power to idle and applying full brakes. Control of the aircraft was never fully lost. I then proceeded to taxi back to the FBO and shut off the airplane. Upon examination; the right landing gear strut had struck the dear. The aluminum casing for the strut was damaged and morphed; although the interior structural component of the strut appeared undamaged. The brake also did not seem to be affected while taxiing. The deer was found dead on the runway. I contacted the nearest approach control and notified them of the incident. The presence of wildlife on the airstrip caused the problem. Moving forward; preventative measures should be taken at 50R to prevent wildlife form entering the field.




Synopsis: Cessna pilot reported a deer strike that resulted in an aborted takeoff and damage to the aircraft.
Date: 201407
Local time of day: 0001-0600
Location: PHL.Airport, PA
Light: Night
Aircraft: Medium Large Transport
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Final Approach
Airspace: Class B PHL
ATC / advisory: Tower PHL
Second aircraft: Medium Large Transport
Reporter organization: Government
Reporter function: Local
Reporter qualification: Air Traffic Control Fully Certified
Human factors: Training / Qualification
Anomaly: ATC Issue All Types; Conflict Airborne Conflict; Deviation / Discrepancy - Procedural Published Material / Policy
Detector: Person Air Traffic Control
When detected: In-flight
Result: Air Traffic Control Issued Advisory / Alert; Flight Crew Returned To Clearance
Contributing factors: Procedure; Human Factors
Primary problem: Procedure

Narrative: During my over night shift we were on a Runway 27 operation. I got a call from the Controller in the TRACON to coordinate a [Runway] 9R arrival which I approved. The Controller in the TRACON worked Aircraft Y in first for Runway 27R. I cleared Aircraft Y to land and noticed the TRACON Controller turn Aircraft X on final for Runway 9R. The Aircraft X was showing 280 KTS as a ground speed and was coming up to the runway fast as Aircraft Y was rolling out on the runway. The TRACON Controller did not switch the Aircraft X to me until he was on a 3 mile final for Runway 9R. When Aircraft X checked in I told him to continue and that traffic was rolling out on Runway 27L. The Aircraft X pilot then came back and said he was going to do S turns so he could descend and lose air speed. A couple seconds later the Aircraft X pilot said to me he does not think he will be able to land. I told Aircraft X to go-around. Shortly after Aircraft X was given instructions to go-around an alert on the ASDE-X went off saying to send Aircraft X around. At this time Aircraft Y was at taxi speed and I gave him instructions to exit the runway. I then went back to Aircraft X and cleared him for a visual approach to Runway 27L and cleared him to land on Runway 27L. After the incident I called down to the Supervisor to report the ASDE-X alert as required. No loss of separation occurred.The TRACON Controller [and] I did not follow proper opposite direction approach procedures. When I was given Aircraft X I should have sent him around right away instead of letting it go as far as it did. I believe our facility should have opposite direction approach procedures in the Local West and Local East SOP. I looked today and there is nothing in the Local Control section saying that the Tower has to call the TRACON to tell them that the landing aircraft is over the threshold but further back in the SOP it is written. I believe since this pertains to Local Control that the procedures should be clearly written in the Local Control East/West sections of the SOP.




Synopsis: PHL Tower Controller reports of situation being an opposite direction arrival that caused the ASDE-X to alarm because the LOA procedure was not followed by the TRACON or the Tower controllers.
Date: 201504
Local time of day: 1201-1800
Location: ZDV.ARTCC, CO
Flight conditions: IMC
Weather elements / visibility: Icing; Turbulence
Aircraft: Widebody Transport
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Cargo / Freight / Delivery
Flight phase: Cruise
Airspace: Class A ZDV
ATC / advisory: Center ZDV
Reporter organization: Air Carrier
Reporter function: Captain; Pilot Flying
Reporter qualification: Flight Crew Air Transport Pilot (ATP)
Second reporter function: First Officer; Pilot Not Flying
Anomaly: ATC Issue All Types; Deviation - Altitude Excursion From Assigned Altitude; Deviation - Speed All Types; Deviation / Discrepancy - Procedural Clearance; Inflight Event / Encounter Weather / Turbulence
Detector: Person Flight Crew
When detected: In-flight
Result: Flight Crew Took Evasive Action
Contributing factors: Weather
Primary problem: Weather

Narrative: We were just south of ALS (Alamosa) VOR at FL340 in level cruise flight; IMC; with moderate icing and moderate turbulence.  We started to see the airspeed start to bleed off from cruise mach. After setting max cruise power and still unable to maintain speed (at this point we had bled off about 10-15 knots of speed) I told the First Officer to notify Center that we would like to descend to FL320.  Because of the convective storm we were flying through; and radios were completely garbled; and we were unable to communicate.  I elected to start to descend to FL320 without ATC clearance after losing another 15 knots and within 20 knots of the lower foot.  At FL 330 we were able to talk to ATC and they gave us clearance to continue our descent to FL320.Possible mountain wave activity


Second narrative: Our airspeed dropped by over 40 knots indicated; putting us close to a possible aerodynamic stall. Even with max power; the airplane was unable to maintain or increase airspeed.


Synopsis: Air Carrier flight crew reported they were unable to maintain speed and altitude when they encountered mountain wave activity at FL340 in the vicinity of Alamosa VOR.
Date: 201403
Local time of day: 0601-1200
Location: ATL.Airport, GA
Flight conditions: VMC
Light: Dawn
Aircraft: B737-700
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Flight phase: Initial Approach
Airspace: Class B ATL
ATC / advisory: Tower ATL
Aircraft component: MCP
Component problem: Improperly Operated
Reporter organization: Air Carrier
Reporter function: First Officer; Pilot Flying
Reporter qualification: Flight Crew Air Transport Pilot (ATP)
Human factors: Situational Awareness; Fatigue
Anomaly: Deviation - Altitude Excursion From Assigned Altitude; Deviation - Altitude Crossing Restriction Not Met; Deviation / Discrepancy - Procedural Clearance; Deviation / Discrepancy - Procedural Published Material / Policy; Inflight Event / Encounter CFTT / CFIT
Detector: Person Flight Crew
When detected: In-flight
Result: Flight Crew Became Reoriented
Contributing factors: Human Factors
Primary problem: Human Factors

Narrative: During the ILS to 26L; for whatever reason I reset the Alt Select prior to capturing the glideslope and began following a false slope below the FAF. The Captain quickly caught my mistake and I disconnected the autopilot; leveled off and re-intercepted the proper glide path. I didn't realize how tired I was on this red eye until I made such a mistake. Although we had visual contact with airport at all times it was still a breach of procedure. We landed without incident. I followed the fatigue mitigation procedures including caffeine 30 minutes prior to landing but fatigue played a key role in my mistake.




Synopsis: B737-700 First Officer reports selecting a lower altitude on the MCP prior to the FAF and glideslope intercept resulting in descent below the glidepath. The Captain takes note and the reporter takes corrective action. Fatigue was cited as the main factor involved.
Date: 201702
Local time of day: 1201-1800
Location: ZZZ.Airport, US
Flight conditions: VMC
Aircraft: EMB ERJ 145 ER/LR
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Takeoff / Launch
Airspace: Class D ZZZ
ATC / advisory: Tower ZZZ
Aircraft component: Hydraulic Main System
Component problem: Failed
Reporter organization: Air Carrier
Reporter function: First Officer; Pilot Flying
Reporter qualification: Flight Crew Air Transport Pilot (ATP)
Second reporter function: Captain; Pilot Not Flying
Anomaly: Aircraft Equipment Problem Less Severe
Detector: Person Flight Crew
When detected: In-flight
Result: Flight Crew Returned To Departure Airport; Flight Crew Overcame Equipment Problem; General Maintenance Action
Contributing factors: Aircraft
Primary problem: Aircraft

Narrative: After departing and selecting landing gear up; the gear failed to come up and a Hyd Sys 1 Fail caution message was presented on the EICAS. It was clear the gear did not fully retract. We then notified the Flight Attendant of the situation and that we would be returning to [departure airport]. We ran the appropiate checklists and were able to fully extend the gear manually and safely return.


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


Synopsis: EMB-145 flight crew reported returning to departure airport when the landing gear failed to retract following the loss of hydraulic system 1 shortly after takeoff.
Date: 201303
Local time of day: 0601-1200
Location: ZZZ.Airport, US
Flight conditions: VMC
Light: Daylight
Aircraft: Citation Excel (C560XL)
Operator: Fractional
Operating under: Part 91
Mission: Ferry / Re-Positioning
Flight phase: Climb
Airspace: Class C ZZZ
ATC / advisory: TRACON ZZZ
Aircraft component: Pressurization System
Component problem: Failed
Reporter organization: Air Carrier
Reporter function: Captain; Pilot Not Flying
Reporter qualification: Flight Crew Air Transport Pilot (ATP)
Anomaly: Aircraft Equipment Problem Critical
Detector: Person Flight Crew
Result: Air Traffic Control Provided Assistance; Flight Crew Landed As Precaution; Flight Crew Requested ATC Assistance / Clarification; Flight Crew Returned To Departure Airport
Contributing factors: Aircraft
Primary problem: Aircraft

Narrative: On initial climb-out the cabin was climbing at 4;000 FPM. We leveled off at 5;000 and had ATC put us in a holding pattern. We communicated with our company and decided that the airplane wasn't pressurizing; and returned to [the airport] without further incident.




Synopsis: C560XL cabin failed to pressurize; resulting in an uneventful return to the departure airport.
Date: 201809
Local time of day: 1201-1800
Location: S46.TRACON, WA
Flight conditions: VMC
Light: Daylight
Aircraft: Travelair 95
Operator: Personal
Operating under: Part 91
Flight plan: VFR
Mission: Personal
Flight phase: Initial Climb
Airspace: Class E S46
ATC / advisory: TRACON S46
Second aircraft: Any Unknown or Unlisted Aircraft Manufacturer
Reporter organization: Personal
Reporter function: Single Pilot
Reporter qualification: Flight Crew Multiengine; Flight Crew Private
Human factors: Situational Awareness
Anomaly: ATC Issue All Types; Conflict NMAC
Detector: Person Flight Crew
When detected: In-flight
Result: Flight Crew Took Evasive Action
Contributing factors: Human Factors
Primary problem: Human Factors

Narrative: We took off and we started our climb out and turned to depart to the east. I contacted Approach to get flight following; they responded unable. A minute or two later at we were at 2000 feet heading east when I saw another aircraft heading from the south to north on a colliding path. They were less than 500 feet away. I had to make a steep climbing right turn to avoid a collision. It appeared that they did not see us because they made no attempt to maneuver to avoid a collision. It sounded like the other aircraft was already talking to Approach. Approach wasn't able to give us flight following and did not warn the other aircraft about us; they didn't attempt to turn them to avoid the conflict. We were 1000 feet below the Class B airspace and only 2000 feet off the ground. I don't believe there was any violations on my part.




Synopsis: Beechcraft pilot reported a near midair collision during initial climb.