elihoole/asrs-aviation-reports huggingface dataset:
Date: 202008
Location: ZZZ.Airport, US
Aircraft: Commercial Fixed Wing
Operator: Air Carrier
Operating under: Part 121
Flight phase: Parked
Reporter organization: Air Carrier
Reporter function: Ramp
Anomaly: Ground Event / Encounter Other / Unknown
Detector: Person Ground Personnel
When detected: Aircraft In Service At Gate
Result: General None Reported / Taken
Contributing factors: Equipment / Tooling
Primary problem: Equipment / Tooling

Narrative: Jetbridges and portable Ground Power Units used do not include a proper 'Ground Power Cord Support Device' or strap that is to be utilized on aircraft when connecting ground power. This can be a serious hazard for ramp personnel and can cause damage if the cord ever becomes disconnected while in use. This has been brought up many times in local safety meetings with nobody taking responsibility to correct.




Synopsis: Air carrier ramp employee reported a possible safety issue regarding portable ground power units that were not equipped with the proper power cord support device.
Date: 201701
Local time of day: 1801-2400
Location: ZZZ.Airport, US
Aircraft: PA-28 Cherokee/Archer/Dakota/Pillan/Warrior
Operator: Personal
Operating under: Part 91
Mission: Training
Flight phase: Landing
Airspace: Class D ZZZ
Reporter organization: Government
Reporter function: Local
Reporter qualification: Air Traffic Control Fully Certified
Human factors: Time Pressure; Situational Awareness; Distraction; Confusion
Anomaly: Conflict Ground Conflict; Less Severe; Deviation / Discrepancy - Procedural Clearance; Ground Incursion Runway
Detector: Person Air Traffic Control
When detected: In-flight
Result: Air Traffic Control Issued New Clearance; Air Traffic Control Separated Traffic
Contributing factors: Aircraft; Procedure; Human Factors
Primary problem: Human Factors

Narrative: I was working Local South and I had Aircraft X doing stop and goes. Aircraft X was just about ready to touch down when I saw Aircraft Y with a lot of speed approaching the runway on B5. I tried to send Aircraft X around but it was too late. Once Aircraft X landed and was under control I told him to make a full stop and the traffic crossing in front of him wasn't supposed to that. He complied.These Aircraft Y Type that go out are never ready. This flight school is concerned with money and not safety. We need someone to help us get control of this.




Synopsis: Local Controller reported seeing an aircraft taxiing fast towards the runway. Local attempted to send arrival traffic around; but it landed. Reporter advised landing traffic that the other aircraft was not supposed to enter the runway.
Date: 202112
Local time of day: 0601-1200
Location: ZMA.ARTCC, FL
Flight conditions: VMC
Aircraft: Commercial Fixed Wing
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Cruise
Airspace: Class A ZMA
ATC / advisory: Center ZMA
Aircraft component: Air/Ground Communication
Component problem: Malfunctioning
Reporter organization: Air Carrier
Reporter function: Captain; Pilot Not Flying
Reporter qualification: Flight Crew Air Transport Pilot (ATP); Flight Crew Multiengine; Flight Crew Instrument
Human factors: Communication Breakdown; Distraction
Anomaly: ATC Issue All Types; Aircraft Equipment Problem Less Severe
Detector: Person Flight Crew
When detected: In-flight
Result: Air Traffic Control Provided Assistance; Flight Crew Overcame Equipment Problem
Contributing factors: Aircraft; Environment - Non Weather Related; Human Factors; ATC Equipment / Nav Facility / Buildings
Primary problem: Ambiguous

Narrative: Shortly after checking on with ZMA; Miami Center we began getting comm interference on 126.52.  The voice appeared to be a recording outlining information / disinformation about the COVID-19 vaccine (it may have been a live reading; but the cadence made it seem like a recording).  We notified Center; who in-turn seemed to boost their output power which momentarily helped. Within minutes the recording was again dominating the frequency. Comms were barely readable; frequency changes had to be read back multiple times by several aircraft. The interference signal seemed to be strongest as we passed 30 NM east of TPA on Q118 heading north.  Once we were switched to ZJX; JAX Center we had no more problems.




Synopsis: Air carrier Captain reported hearing non-aviation information on a ZMA 126.52 frequency interfering with regular communications.
Date: 202007
Local time of day: 0601-1200
Location: ZZZ.TRACON, US
Flight conditions: VMC
Aircraft: Commercial Fixed Wing
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Descent
Airspace: Class E ZZZ
ATC / advisory: TRACON ZZZ
Reporter organization: Air Carrier
Reporter function: Captain; Pilot Not Flying
Reporter qualification: Flight Crew Air Transport Pilot (ATP); Flight Crew Instrument; Flight Crew Multiengine
Human factors: Communication Breakdown
Anomaly: Deviation - Speed All Types; Deviation / Discrepancy - Procedural FAR; Deviation / Discrepancy - Procedural Published Material / Policy
Detector: Person Flight Crew
When detected: In-flight
Result: Flight Crew Returned To Clearance
Contributing factors: Procedure; Company Policy; Environment - Non Weather Related; Human Factors
Primary problem: Company Policy

Narrative: First Officer was flying and distracted.  While reviewing approach plate; I looked up to see that the First Officer was rapidly descending for 6;000 feet; and was already at approximately 9;000 feet and still at 300 knots.  I immediately instructed the First Officer to turn off the autopilot; and immediately slow the aircraft to 250 knots by raising the nose of the aircraft.  Once the aircraft slowed to 250; the First Officer continued the descent.First Officer is extremely inexperienced in jets; and due to COVID-19; has extreme lack of proficiency.  Making sure new pilots in new aircraft receive more training in this time when flying becomes very infrequent.




Synopsis: Captain reported experiencing a speed deviation below 10;000 feet and stated First Officer's lack of flying contributed to the event.
Date: 201912
Local time of day: 1801-2400
Location: ZZZ.Airport, US
Flight conditions: VMC
Light: Night
Aircraft: Skyhawk 172/Cutlass 172
Operator: FBO
Operating under: Part 91
Flight plan: None
Mission: Training
Flight phase: Takeoff / Launch
Airspace: Class D ZZZ
ATC / advisory: Tower ZZZ
Aircraft component: Engine
Component problem: Malfunctioning
Reporter organization: FBO
Reporter function: Instructor; Pilot Not Flying; Pilot Flying
Reporter qualification: Flight Crew Flight Instructor
Anomaly: Aircraft Equipment Problem Critical
Detector: Person Flight Crew
When detected: In-flight
Result: Air Traffic Control Issued New Clearance; Flight Crew Returned To Departure Airport
Contributing factors: Aircraft
Primary problem: Aircraft

Narrative: After being cleared to takeoff on Runway XXL at ZZZ; the student and I verified that the airspeed was alive and the engine instruments are in the green. Everything was going as plan during the takeoff role and during rotation as well. Then at 300 feet. I felt a reduction of power I thought the student reduced power accidentally my reaction was to push the throttle full forward but it was already full forward. Then right after the was strong vibrations from the engine after that I complete control of the aircraft and I told ATC I would like to land back on Runway XXL due to partial power loss. Then ATC canceled IFR and cleared me to land on XXL. After I landed I went back to the FBO.




Synopsis: C172 flight instructor reported engine problems on takeoff that resulted in a return to the departure airport.
Date: 201207
Local time of day: 1801-2400
Location: ZZZ.Airport, US
Light: Night
Aircraft: Regional Jet 200 ER/LR (CRJ200)
Operator: Air Carrier
Operating under: Part 91
Flight plan: IFR
Mission: Ferry / Re-Positioning
Flight phase: Taxi
ATC / advisory: Tower ZZZ
Reporter organization: Air Carrier
Reporter function: Captain; Pilot Flying
Reporter qualification: Flight Crew Air Transport Pilot (ATP)
Human factors: Confusion; Situational Awareness
Anomaly: Deviation / Discrepancy - Procedural Clearance; Ground Incursion Runway
Detector: Person Air Traffic Control
When detected: Taxi
Result: Air Traffic Control Issued Advisory / Alert; Flight Crew Became Reoriented
Contributing factors: Human Factors
Primary problem: Human Factors

Narrative: Upon landing on Runway XXR; we were given taxi instructions to the maintenance hangar via E; U; V; C; cross Runway XXL. As we reached Taxiway V on U; I saw the red and white XXL-YYR sign to my right and made a right hand turn and inadvertently crossed onto Runway ZZ-WW before I realized I had made a wrong turn. The Tower called us on our mistake and re-cleared us around the north side of the airport to the hangar.It was a difficult day due to weather; maintenance; a ferry flight and a diversion before getting to [destination]. After the diversion; it was a quick easy flight to our destination. Once on the ground it felt like we were finally 'done;' just a short taxi to the hangar. Upon making the turn onto Taxiway U; I saw the XXL-YYR sign and I needed to cross it; looking right past the Runway ZZ-WW signs and rolling onto that runway. Thankfully Runway ZZ-WW was not in use at the time. Looking back; what I did made no sense; that route is way out of the way. I was concerned about crossing that runway not where to cross it. I need to double check the airport diagram and ask myself is this right? After landing; I let my guard down; we were 'DONE;' 'It's easy from here.' I need to make sure we're not done until we're parked and off the plane.




Synopsis: CRJ-200 flight crew; given taxi clearance that included a runway crossing; inadvertently crossed the wrong runway.
Date: 201207
Local time of day: 1801-2400
Location: ZZZ.Airport, US
Light: Night
Aircraft: A330
Operator: Air Carrier
Operating under: Part 121
Mission: Passenger
Flight phase: Parked
ATC / advisory: Ramp ZZZ
Aircraft component: Fuselage
Reporter organization: Air Carrier
Reporter function: Technician
Reporter qualification: Maintenance Airframe; Maintenance Powerplant
Human factors: Time Pressure; Communication Breakdown; Confusion
Anomaly: Aircraft Equipment Problem Less Severe; Deviation / Discrepancy - Procedural Published Material / Policy
Detector: Person Maintenance
When detected: Aircraft In Service At Gate
Result: General Maintenance Action; General Flight Cancelled / Delayed
Contributing factors: Aircraft; Chart Or Publication; Company Policy; Human Factors; MEL; Procedure
Primary problem: MEL

Narrative: A CDL [(Configuration Deviation List)] was applied on an A330 aircraft on the 3-Left (3L) Door Sill plate (CDL-51-021) which we did in accordance with (I/A/W) the CDL Manual. Maintenance Control however insisted per the CDL; that the aircraft be pressurized as part of the CDL. The CDL Manual does not require that to be done and the aircraft took an additional 30 minute delay as a result. The aircraft was on a gate in ZZZ; scheduled for an evening departure. Personnel involved were myself; another Mechanic; the Lead Mechanic; and the 'A' Concourse Supervisor. In reviewing the CDL; we saw no requirement that the aircraft be pressurized as a result of applying this CDL and that this action be documented on an Engineering Report as directed by Maintenance Control. It was our feeling that we were accomplishing a special procedure that Maintenance Control had decided [needed] to be done and not one that the CDL Manual specified. My opinion is that the event occurred as a result of Maintenance Control adding a Special Procedure to the application of a CDL that was not specified and not needed to legally dispatch the aircraft. We disputed the requirement of pressurizing the aircraft after the CDL was applied; and documented this action on a company Engineering Report; but performed this as Maintenance Control insisted it was required for the CDL. We were at the end of our work shift and were focused on getting the airplane out. [Issues involve] Maintenance Control communicating directly with the mechanics about the work to be accomplished and the requirements of a specified CDL and no unnecessary actions being performed.




Synopsis: A Line Mechanic reports that an A330 aircraft was delayed 30 minutes while Maintenance was required to perform an aircraft pressurization check to satisfy a Maintenance Controller's CDL deferral of a damaged Sill plate at Cabin Door 3-Left (3-L). Mechanic noted the CDL did not specify a pressurization check requirement for dispatch.
Date: 201911
Local time of day: 0001-0600
Location: LGA.Airport, NY
Flight conditions: IMC
Aircraft: Commercial Fixed Wing
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Taxi
ATC / advisory: Ground LGA
Reporter organization: Air Carrier
Reporter function: First Officer
Reporter qualification: Flight Crew Air Transport Pilot (ATP)
Human factors: Situational Awareness; Distraction; Communication Breakdown; Confusion
Anomaly: ATC Issue All Types; Deviation / Discrepancy - Procedural Published Material / Policy; Deviation / Discrepancy - Procedural Clearance
Detector: Person Flight Crew
When detected: Taxi
Contributing factors: Airport; Company Policy; Procedure
Primary problem: Company Policy

Narrative: Maintain situational awareness. Rewrite the company information clearly and concisely. Amongst other things there were references to a central terminal which I still cannot find on the Jeppesen Chart. Determine why 'spot' 9A; 9B and 9D are half a mile from 'spot' 9 and in between 'spot' 20 and 23? Create a national standard of being handed off to Ramp Control from Ground and not flipping back and forth between multiple frequencies. Direct all arriving aircraft to a holding lane until their ramp entry can be coordinated. It's nice to say 'stop and figure it out' and in a safety situation; absolutely. However; anyone who has flown into our busiest airports knows that they all have differing tribal knowledge and with as short of a taxi as we had they want you out of their way and fast.




Synopsis: Air carrier First Officer reported confusing taxi and parking information and non-standard communication procedures at LGA airport.
Date: 201909
Local time of day: 0601-1200
Location: SDL.Airport, AZ
Flight conditions: VMC
Light: Daylight
Aircraft: PA-44 Seminole/Turbo Seminole
Operator: Personal
Operating under: Part 91
Flight plan: None
Mission: Training
Flight phase: Climb
Airspace: Class D P50
ATC / advisory: TRACON P50
Second aircraft: Aerobatic
Reporter organization: Personal
Reporter function: Single Pilot
Reporter qualification: Flight Crew Multiengine; Flight Crew Commercial; Flight Crew Flight Instructor; Flight Crew Instrument
Human factors: Situational Awareness; Communication Breakdown
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: While climbing out and making radio calls on the appropriate practice area frequency; noticed an aerobatic aircraft doing aerobatics and taking up a large amount of space both vertical and horizontal in an area that is well known to be congested with training aircraft. Aerobatic aircraft was making no radio calls and intentions were unknown; but they were moving in a direction that would have them crossing to our right; well above us. I began to turn to the left to avoid getting any closer given the type of maneuvers they were performing and the lack of any indication/communication as to what they would be doing. While making my turn away from the flightpath of the aerobatic aircraft; it quickly changed its direction of flight towards us; and began to descend rapidly; resulting in me needing to go from what was a no threat slow turn away into an evasive action steep turn.I believe the issue could have been avoided entirely [if] radio communication was present and intentions were stated prior to performing any maneuver involving a rapid descent/ascent and/or change in direction especially given the nature of the practice area being discussed. Furthermore as soon as identifying the plane as an aerobatic I should have already been diverting my path well clear of any area they could possibly end up in as I had not appropriately anticipated how quickly separation could deteriorate.




Synopsis: PA-44 pilot reported a Near Mid Air Collision with an aerobatic aircraft.
Date: 202104
Local time of day: 1201-1800
Location: ORD.Airport, IL
Light: Daylight
Aircraft: Commercial Fixed Wing
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Climb
Airspace: Class E ZAU
ATC / advisory: Center ZAU
Reporter organization: Air Carrier
Reporter function: Captain; Pilot Flying
Reporter qualification: Flight Crew Air Transport Pilot (ATP); Flight Crew Instrument; Flight Crew Multiengine
Human factors: Communication Breakdown
Anomaly: Deviation - Track / Heading All Types; Deviation / Discrepancy - Procedural Clearance
Detector: Person Flight Crew
When detected: In-flight
Result: Air Traffic Control Issued New Clearance; Flight Crew Returned To Clearance
Contributing factors: Airspace Structure; Chart Or Publication
Primary problem: Chart Or Publication

Narrative: During climb portion of flight we were given direct EMMLY at approximately 14;000 feet. We both went direct EMILY in the FMS. Just before roll out ATC calls and said what is your heading. Upon that call FO (First Officer) gave heading and I pulled up the release. ATC then gave us correct heading toward EMMLY and we entered EMMLY into the FMS and not EMILY and continued to ZZZ. ATC was quick to see the heading change so no major deviation occurred. [Identified by] ATC initially then crew. [Caused by] inadequate spelling cross check by myself of the route entered into FMS by FO. When we read through the route EMILY was read when spelling was EMMLY. [We] corrected the waypoint spelling and proceeded on course. Waypoints should not be so closely spelled to eliminate possibility of mistakes. Always triple check spelling when route not entered by yourself.




Synopsis: Regional Jet Captain reported similar sounding fixes EMMLY instead of EMILY; resulted in a turn off course.
Date: 201402
Local time of day: 0601-1200
Location: ZNY.ARTCC, NY
Flight conditions: VMC
Aircraft: MD-11
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Cargo / Freight / Delivery
Flight phase: Cruise
Airspace: Class A ZNY
ATC / advisory: Center ZNY
Reporter organization: Air Carrier
Reporter function: First Officer; Pilot Flying
Reporter qualification: Flight Crew Air Transport Pilot (ATP)
Human factors: Confusion; Training / Qualification
Anomaly: ATC Issue All Types; Deviation - Track / Heading All Types; Deviation / Discrepancy - Procedural Clearance
Detector: Person Air Traffic Control
When detected: In-flight
Result: Air Traffic Control Issued New Clearance; Flight Crew Became Reoriented; Flight Crew Returned To Clearance
Contributing factors: Human Factors
Primary problem: Human Factors

Narrative: Preflight was normal.  Captain sent away for DCL.  When we received and it said 'Cleared Route Clearance' we were unaware that this was actually a change to our route.  As we departed Newark; we were advised to fly direct BUSKY.  We asked for that to be spelled phonetically and the Controller said it 'was on our Flight Plan.' We told him after SBJ we showed V3 MAISY.  He advised us that we were cleared Direct BUSKY Direct PTW Direct... and that our old routing was incorrect.  We complied with the clearance.  Our DCL said Cleared Route Clearance; and we were unaware that this was actually a revision to our filed clearance.  Upon Landing we contacted Newark Tower via phone and became aware of our mistake. 1.  I do not think that 'Cleared Route Clearance' is significant enough wording to advise you that your route has changed.  It is too close to 'Cleared as Filed' and does not contain the old PDC wording 'Notice Route Change'   2. There has been no hands on training with DCL Clearances.  This has been my second exposure to DCL and first route change.  I have just had training in December with no mention that I recall of DCL procedures.  It has all been through word of mouth with captains and looking at the printouts provided with the release; which evidently wasn't enough to make me aware of the significance of 'Cleared Route Clearance.'  Subsequently I felt I was inadequately prepared to back up the Captain with the DCL Procedure. Hands on training with DCL Clearances during formal training events; to include a route change; and a lesson to highlight the significance of the wording on DCL Clearances and subsequent actions that must be accomplished.




Synopsis: Air carrier First Officer using DCL for the first time receives a clearance starting with 'Cleared Route Clearance' and assumes this means cleared as filed; which is not the case.
Date: 202106
Local time of day: 0001-0600
Location: SAN.Airport, CA
Flight conditions: VMC
Light: Daylight
Aircraft: Light Transport; Low Wing; 2 Turbojet Eng
Operator: Air Carrier
Operating under: Part 121
Mission: Passenger
Flight phase: Takeoff / Launch
ATC / advisory: Ramp SAN
Second aircraft: Any Unknown or Unlisted Aircraft Manufacturer
Reporter organization: Air Carrier
Reporter function: First Officer; Pilot Not Flying
Reporter qualification: Flight Crew Air Transport Pilot (ATP); Flight Crew Instrument; Flight Crew Multiengine
Human factors: Communication Breakdown; Distraction; Situational Awareness
Anomaly: ATC Issue All Types; Conflict Ground Conflict; Less Severe; Deviation / Discrepancy - Procedural Published Material / Policy; Ground Incursion Runway
Detector: Person Flight Crew
When detected: Other On Runway
Result: Air Traffic Control Issued New Clearance
Contributing factors: Human Factors; Procedure; Staffing
Primary problem: Human Factors

Narrative: We were instructed to line up and wait while the aircraft that just landed rolled out and exited the runway. While we were in position; Tower became busy talking to other aircraft on frequency. The next radio call for us was to exit the runway at C2. While exiting; a cleared to land aircraft was heard asking 'is that an airplane on the runway?' Tower instructed them to not overfly us; that we were exiting the runway. They were never instructed to go-around; instead to offset. We observed them offsetting slightly as to not fly directly over the top of us as they continued to land.Tower becoming busy and possibly forgetting about us on the runway; and the landing aircraft not executing a go-around when they became aware of us in position on the runway; both contributed to the near miss. Query ATC when any delay in position.




Synopsis: Air carrier flight crew reported near miss on runway due to incorrect ATC clearance at SNA airport.