elihoole/asrs-aviation-reports huggingface dataset:
Date: 201906
Local time of day: 1201-1800
Location: ZZZ.Airport, US
Weather elements / visibility: Rain
Light: Daylight
Aircraft: A319
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Descent
Airspace: Class B ZZZ
ATC / advisory: TRACON ZZZ; Tower ZZZ
Reporter organization: Air Carrier
Reporter function: First Officer; Pilot Flying
Reporter qualification: Flight Crew Air Transport Pilot (ATP); Flight Crew Instrument; Flight Crew Multiengine
Human factors: Situational Awareness
Anomaly: Flight Deck / Cabin / Aircraft Event Smoke / Fire / Fumes / Odor
Detector: Person Flight Crew
When detected: In-flight
Result: Air Traffic Control Provided Assistance; Flight Crew Landed in Emergency Condition; Flight Crew Requested ATC Assistance / Clarification; General Maintenance Action
Contributing factors: Aircraft
Primary problem: Aircraft

Narrative: I was PF (Pilot Flying) started descent in ZZZ; Captain asked me if I smelled a dirty sock smell. I said that I did. Although it wasn't real strong at first. Captain called the FAs to ask them if they smelled anything. I was on ATC; so I didn't hear conversation with FAs. Things were starting to get busy as we were on the arrival. We donned our Oxygen masks when we thought that the odor had become more noticeable. Captain was running QRH and sending ACARS messages to Company Maintenance and Dispatch Dispatcher. [Notified ATC]. We made a normal approach and landed; taxied up but short of our gate. Then finally we were marshaled into the gate after a long wait. With the information the Dispatcher had (fumes dirty socks smell) we should have been allowed to proceed straight to the gate. The Captain and I both opened our windows in the rain to get fresh air into the aircraft as the smell was very strong by this point.Cause: I believe it was oil aerosol from the engine into the packs.




Synopsis: A319 First Officer reported a 'dirty socks' smell in cockpit which steadily intensified and resulting into an uneventful landing.
Date: 202104
Local time of day: 1201-1800
Location: MYR.Airport, SC
Aircraft: Commercial Fixed Wing
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Taxi
ATC / advisory: Tower MYR
Reporter organization: Air Carrier
Reporter function: Captain; Check Pilot
Reporter qualification: Flight Crew Multiengine; Flight Crew Instrument; Flight Crew Air Transport Pilot (ATP)
Human factors: Distraction; Confusion; Troubleshooting; Situational Awareness
Anomaly: ATC Issue All Types; Deviation / Discrepancy - Procedural Clearance; Deviation / Discrepancy - Procedural Published Material / Policy; Ground Event / Encounter Ground Equipment Issue; No Specific Anomaly Occurred Unwanted Situation
Detector: Person Flight Crew
When detected: Taxi
Result: Air Traffic Control Provided Assistance; Flight Crew Requested ATC Assistance / Clarification
Contributing factors: Airport; Human Factors
Primary problem: Airport

Narrative: MYR Ground instructed us to taxi from the ramp to Runway 18 via Z; hold short Runway 18.  At the ramp exit; we were positioned exactly on Z but the taxiway signage indicated Taxiway A4.  I stopped the plane; set the brake and told Ground that I thought we were holding short Taxiway Z; but the ground sign said A4.  Ground reported that the taxiway diagrams have been changed Z; but the ground signage still says A4.  We proceeded as directed without further incident. The taxiway diagram does not match the ground signage.  The signs should change at the same time as the taxi diagram or a NOTAM should be issued describing the discrepancy.




Synopsis: Air carrier Captain reported the taxiway diagram at MYR airport does not match the ground signage.
Date: 202108
Local time of day: 1201-1800
Location: ZZZ.Airport, US
Flight conditions: VMC
Light: Daylight
Aircraft: Lancair IV/IVP
Operator: Personal
Operating under: Part 91
Flight plan: IFR
Mission: Personal
Flight phase: Landing
Airspace: Class C ZZZ
ATC / advisory: Tower ZZZ
Aircraft component: Nose Gear
Component problem: Malfunctioning
Reporter organization: Personal
Reporter function: Flight Engineer / Second Officer; Single Pilot
Reporter qualification: Flight Crew Multiengine; Flight Crew Instrument; Flight Crew Flight Instructor; Flight Crew Air Transport Pilot (ATP); Other A&P
Anomaly: Aircraft Equipment Problem Critical; Ground Event / Encounter Ground Strike - Aircraft
Detector: Person Flight Crew
When detected: Other Landing
Result: Aircraft Aircraft Damaged; General Maintenance Action; General Flight Cancelled / Delayed
Contributing factors: Aircraft
Primary problem: Aircraft

Narrative: Normal approach and landing at ZZZ. Normal touchdown. Shortly after the nose wheel touched down the nose gear collapsed into the wheel well. The prop contacted the runway and we slid to a stop on the runway surface. There were no injuries; no leaking fluids. damage appears confined to prop and engine.




Synopsis: Pilot reported nose landing gear collapse on landing with no injuries. Pilot reported damage was limited to the nose landing gear and propeller.
Date: 201507
Local time of day: 0601-1200
Weather elements / visibility: 10
Light: Daylight
Aircraft: Helicopter
Operator: Corporate
Operating under: Part 137
Flight plan: None
Flight phase: Cruise
Airspace: Special Use RESTRICTED
Aircraft component: GPS & Other Satellite Navigation
Component problem: Malfunctioning
Reporter organization: Corporate
Reporter function: Pilot Flying; Single Pilot
Reporter qualification: Flight Crew Commercial; Flight Crew Flight Instructor; Flight Crew Instrument; Flight Crew Multiengine
Human factors: Situational Awareness
Anomaly: Aircraft Equipment Problem Less Severe; Airspace Violation All Types; Deviation / Discrepancy - Procedural FAR
Detector: Person Flight Crew
When detected: In-flight
Result: Flight Crew Exited Penetrated Airspace; Flight Crew Overcame Equipment Problem
Contributing factors: Human Factors; Aircraft
Primary problem: Ambiguous

Narrative: While circumnavigating a Restricted area my portable GPS yoke mounted unit malfunctioned and locked up. After trying to get it unlocked and usable to no avail; I rebooted the unit. When the unit came back on it indicated that I had inadvertently entered into the edge of the Restricted area. I immediately made a turn and exited out of the area. I feel that an additional backup unit online in the aircraft would have prevented this.




Synopsis: A helicopter pilot reported the yoke mount GPS malfunctioned resulting in restricted airspace entry.
Date: 201707
Local time of day: 0601-1200
Location: BGR.Airport, ME
Flight conditions: VMC
Light: Daylight
Aircraft: Small Transport
Operator: Fractional
Operating under: Part 91
Flight plan: IFR
Mission: Passenger
Flight phase: Taxi
ATC / advisory: Tower BGR
Aircraft component: Compass (HSI/ETC)
Component problem: Malfunctioning
Reporter organization: Fractional
Reporter function: Captain; Pilot Not Flying
Reporter qualification: Flight Crew Air Transport Pilot (ATP)
Human factors: Confusion
Anomaly: Aircraft Equipment Problem Less Severe; Deviation / Discrepancy - Procedural Published Material / Policy; Ground Event / Encounter Other / Unknown
Detector: Automation Aircraft Other Automation; Person Flight Crew
When detected: Taxi
Result: Flight Crew Overcame Equipment Problem
Contributing factors: Airport
Primary problem: Airport

Narrative: While on Taxiway M; holding short of Rwy 15 at BGR; the compass deviation increased to over 60 degrees; apparently due to a high capacity underground power line. We had HSI1 and HSI2 Caution messages. The Cautions went out when we were cleared to 'line up to wait' on the runway; however the heading was still 089 degrees while lined up on runway 15. As the weather was VFR; we elected to takeoff and continue the flight; navigating via pilotage.Recommend the airport authority provide signs to warn crews of potential compass deviations and avoid holding for any length of time on Taxiway M. Also; add a comment about this phenomenon in the airfield notes.




Synopsis: Small transport aircraft Captain reported experiencing a drastic compass heading deviation allegedly caused by underground power lines on Taxiway M at BGR.
Date: 201504
Local time of day: 1801-2400
Location: ZZZ.Airport, US
Light: Night
Aircraft: Regional Jet 900 (CRJ900)
Operator: Air Carrier
Operating under: Part 121
Flight phase: Parked
Aircraft component: Hydraulic System Pump
Component problem: Malfunctioning
Reporter organization: Air Carrier
Reporter function: Technician
Reporter qualification: Maintenance Airframe; Maintenance Powerplant
Human factors: Communication Breakdown; Situational Awareness; Training / Qualification
Anomaly: Aircraft Equipment Problem Critical; Deviation / Discrepancy - Procedural Published Material / Policy
Detector: Person Flight Crew
When detected: In-flight
Result: General None Reported / Taken
Contributing factors: Human Factors; Manuals
Primary problem: Human Factors

Narrative: Was sent to do this job with another co-worker to do MEL on Engine Driven Pump (EDP). I'm still on bye back. We installed a flying kit for engine driven pump. However; we misread one step and forgot to install a nut into a spline shaft. This lead to oil splitting from engine driven pump. Training not adequate.




Synopsis: A Line Aircraft Maintenance Technician (AMT) was informed that oil had leaked from an Engine Driven Pump (EDP) on a CRJ-900 aircraft after he and another Technician had installed a flying kit as part of an MEL deferral for a # 2 Engine EDP. They had misread one step and forgot to install a nut onto the spline shaft.
Date: 201505
Location: CYYC.Airport, AB
Flight conditions: VMC
Aircraft: B737 Undifferentiated or Other Model
Operator: Air Carrier
Mission: Passenger
Flight phase: Taxi
ATC / advisory: Ramp CYYC
Aircraft component: Turbine Engine
Component problem: Malfunctioning
Reporter organization: Air Carrier
Reporter function: Pilot Not Flying; Captain
Reporter qualification: Flight Crew Air Transport Pilot (ATP)
Anomaly: Aircraft Equipment Problem Less Severe; Ground Event / Encounter Other / Unknown
Detector: Person Ground Personnel
When detected: Taxi
Result: Flight Crew Returned To Gate; General Maintenance Action
Contributing factors: Aircraft
Primary problem: Aircraft

Narrative: During pushback starting engines the number 2 engine began dumping a large amount of fuel upon initial start selection prior to fuel lever being selected to idle; according to the push crew.  I asked the push crew a 2nd time if we were still dumping fuel which the crew indicated that we were so I asked the First Officer (FO) to stop the start of the number 2 engine.  A wide path of fuel was then noted on the ramp on the right side of the aircraft.  Ramp control was advised of a possible fuel spill and then we notified operations of the situation and advised we needed to return to the gate to have the engine checked out by maintenance and Maintenance Control was notified.Maintenance Control advised the flight crew via cell phone that an engine run would be required to clear the problem and verified that we were willing to comply.  After review with Maintenance Control and the [Operations Manual] of the requirements and ACARS printout we successfully completed the engine run.  The logbook was signed off by local technicians after which the flight continued without further issue.




Synopsis: A B737 Captain is informed by the ground crew during engine start that the right engine is leaking significant amounts of fuel. This occurred prior to the fuel lever being selected to idle. The start is terminated and the aircraft returned to the gate for maintenance.
Date: 202006
Local time of day: 1201-1800
Location: BJC.Airport, CO
Flight conditions: VMC
Weather elements / visibility: 10
Light: Daylight
Aircraft: Citation I/SP (C501)
Operator: Corporate
Operating under: Part 91
Flight plan: None
Mission: Personal
Flight phase: Landing
ATC / advisory: Tower BJC
Reporter organization: Corporate
Reporter function: Pilot Flying; Captain; Single Pilot
Reporter qualification: Flight Crew Glider; Flight Crew Flight Instructor; Flight Crew Air Transport Pilot (ATP); Flight Crew Instrument; Flight Crew Sea; Flight Crew Rotorcraft; Flight Crew Multiengine
Human factors: Communication Breakdown; Training / Qualification; Confusion; Situational Awareness
Anomaly: ATC Issue All Types; Deviation / Discrepancy - Procedural Clearance; Deviation / Discrepancy - Procedural Landing Without Clearance; Deviation / Discrepancy - Procedural Published Material / Policy; Ground Incursion Runway
Contributing factors: Human Factors; Procedure
Primary problem: Human Factors

Narrative: While conducting takeoffs and landings for currency; I taxied to RWY 12R and held for take off. I was issued takeoff clearance from RWY 12L with right closed traffic for 'the option' to RWY 12R and asked if that was acceptable. I did a stop and go (or touch and go) landing on RWY 12R; with R traffic after takeoff. I flew R traffic to RWY 12L with a go around issued by tower. I conducted the go around and used R traffic with a landing on RWY 12L. I taxied back for another pattern and was told urgently by ATC (Air Traffic Control) to pull into run up area at end of runway. In order to taxi into run up area I had to maneuver by several persons standing outside by a light Grumman aircraft with my exhaust pointed in their direction; with which I was very uncomfortable. But there appeared to be some urgency on the part of ATC; like a fire or incapacitation.I was directed by radio to call ATC on a landline by clearance frequency and they told to call a number for the tower for a 'deviation'. I indicated I was uncomfortable with two jet engines running in the midst of all these light aircraft and that if they needed to talk to me immediately I would taxi back to my hanger; otherwise I wanted one more trip around the traffic pattern. I was cleared for takeoff and conducted a RH pattern for landing on 12L. I taxied back normally to my hanger and talked to the tower on a land line. He indicated I had landed on 12R when cleared for 12L. I asked to get a copy of the tower tapes; he indicated I could not.I feel it is fortunate that there were apparently not injuries from the jet blast to the persons operating around and outside of their aircraft at the run up area.




Synopsis: Pilot flying C-501 aircraft reported deviation from landing clearance.
Date: 202201
Local time of day: 0601-1200
Location: ZZZ.Airport, US
Aircraft: Regional Jet 900 (CRJ900)
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Taxi
ATC / advisory: Ramp ZZZ
Second aircraft: Commercial Fixed Wing
Reporter organization: Air Carrier
Reporter function: Pilot Flying; Captain
Reporter qualification: Flight Crew Air Transport Pilot (ATP); Flight Crew Multiengine; Flight Crew Instrument
Human factors: Other / Unknown; Communication Breakdown; Situational Awareness; Workload; Troubleshooting
Anomaly: Conflict Ground Conflict; Critical; Deviation / Discrepancy - Procedural Published Material / Policy; Ground Event / Encounter Aircraft
Detector: Person Ground Personnel
When detected: Taxi
Result: Aircraft Aircraft Damaged; General Flight Cancelled / Delayed; General Maintenance Action
Contributing factors: Human Factors
Primary problem: Human Factors

Narrative: After a normal flight and landing at ZZZ we were taxing into Gate XX at ZZZ Terminal XX. We were cleared in to the gate area by Ramp Control; there were rampers waiting for us as we arrived. At Gate XX; the gate next to our assigned gate; another aircraft was waiting on push back; there was another ramp crew with that aircraft also. The marshallers started to wave us in; I lined up on the center line at Gate XX and began to taxi in. A few ft. short of the stop line the lead gave us a very sudden stop. I stopped the aircraft and set the parking brake. Within a few minutes it became clear we had collided with the aircraft at Gate XY. We deplaned the passengers normally via the jet bridge.Seems like it was a case of the ramp crew just not paying attention.




Synopsis: CRJ 900 Captain reported a ground collision; while parking; with another aircraft at an adjacent gate. The Captain states the ground crew was not paying attention while they were signaling the aircraft into the gate.
Date: 201907
Local time of day: 0601-1200
Location: DFW.Airport, TX
Aircraft: Commercial Fixed Wing
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Landing
Airspace: Class B DFW
Reporter organization: Air Carrier
Reporter function: Pilot Flying
Human factors: Confusion; Situational Awareness
Anomaly: ATC Issue All Types; Deviation / Discrepancy - Procedural Published Material / Policy
Detector: Person Flight Crew
When detected: In-flight
Result: General None Reported / Taken
Contributing factors: Procedure
Primary problem: Procedure

Narrative: All day long; DFW operated with a tailwind. The wind was from 330 degrees to 050 degrees all day long. Generally from 5 to 8 knots. DFW continued to operate with a south flow. Much of the time; the ATIS reported the wind as calm even though the flags were standing out smartly. That the airport would operate all day in this condition is amazing to me. I was always taught that airplanes took off and landed into the wind. In the interest of safety; we should at least try to operate into the wind. In the interest of economics also. Faster landing speeds; hotter brakes; maximum power required for takeoff; etc. Who would be responsible if an aircraft rolled off the end?




Synopsis: Air carrier pilot questioned why DFW operated all day with a 5-8 knot tailwind against the stated interests of safety and economics.
Date: 201508
Local time of day: 0601-1200
Location: SCT.TRACON, CA
Flight conditions: VMC
Weather elements / visibility: 10
Light: Daylight
Aircraft: Small Aircraft; Low Wing; 1 Eng; Retractable Gear
Operator: Personal
Operating under: Part 91
Flight plan: IFR
Mission: Personal
Flight phase: Cruise
Airspace: Class E SCT
ATC / advisory: TRACON SCT
Reporter organization: Personal
Reporter function: Single Pilot
Reporter qualification: Flight Crew Private; Flight Crew Instrument
Human factors: Confusion; Situational Awareness; Communication Breakdown
Anomaly: ATC Issue All Types; Deviation - Track / Heading All Types; Deviation / Discrepancy - Procedural Clearance; Deviation / Discrepancy - Procedural Published Material / Policy
Detector: Person Air Traffic Control
When detected: In-flight
Result: Air Traffic Control Provided Assistance; Flight Crew Requested ATC Assistance / Clarification; Flight Crew Returned To Clearance
Contributing factors: Human Factors; Procedure
Primary problem: Human Factors

Narrative: An IFR flight from Monterey Regional Airport (KMRY) to Redlands Airport (REI) was filed as follows: KMRY SNS V137 GMN LHS V459 DARTS V186 PDZ WEEDD KREI. Clearance Delivery at KMRY amended this as follows: TORO 6 Departure SERFR AVE V137 GMN then as filed. Later in the flight; Bakersfield Approach had an amendment to the clearance as follows: Present position GMN LHS V459 V186 PDZ KREI. Note the specific deletion of DARTS which is the intersection or fix which connects the two airways. Upon reaching DARTS I continued on V459 waiting for the controller to state 'join V186'. (The reason for this presumption is based on the flight several days earlier from KREI to KMRY the flight plan had been amended; again; by SOCAL APP to delete DARTS intersection. Prior to arriving at DARTS on that earlier flight; the approach controller said 'join V459' after passing PURMS intersection on V186.) After passing DARTS; the controller inquired as to when I was going to continue on my flight plan. I replied that since DARTS had been specifically deleted; I was waiting on him. This was stated in a calm and respectful manner. He said to continue on the flight plan and was easily accomplished without penetrating the LAX Class B airspace and did not cause any conflicts.I am filing this because of the ambiguity of the amended clearance to delete the intersection which would have avoided the misunderstanding in the first place. Controllers are always free to spontaneously say 'join Vxxx' at any time during a flight. Prior to moving to California; I cannot remember receiving a clearance that avoided listing the requested intersection that joined two airways. However; in the future I will simply ask ATC if I can join the other airway when I am in reasonable distance to it.




Synopsis: The pilot was confused by the ambiguity of an amended clearance which deleted the intersection at the junction of two airways.
Date: 202003
Location: LTAA.ARTCC, FO
Aircraft: B777 Undifferentiated or Other Model
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Cruise
ATC / advisory: Center LTAA
Reporter organization: Air Carrier
Reporter function: Captain; Check Pilot
Reporter qualification: Flight Crew Air Transport Pilot (ATP); Flight Crew Multiengine; Flight Crew Instrument
Human factors: Distraction; Workload; Situational Awareness
Anomaly: Aircraft Equipment Problem Less Severe; Deviation - Track / Heading All Types; Deviation / Discrepancy - Procedural Published Material / Policy; Inflight Event / Encounter Other / Unknown
Detector: Person Flight Crew
When detected: In-flight
Result: Flight Crew FLC complied w / Automation / Advisory
Contributing factors: Airspace Structure; Aircraft; ATC Equipment / Nav Facility / Buildings; Human Factors
Primary problem: Ambiguous

Narrative: Upon crossing into the Ankara FIR after crossing TOMBI intersection; our GPS was jammed intermittently for about 5 minutes. All SOP complied with.




Synopsis: B777 Line check Captain reported suspected GPS jamming during cruise.
Date: 201812
Local time of day: 0001-0600
Location: MSP.Airport, MN
Aircraft: Commercial Fixed Wing
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Taxi
ATC / advisory: Tower MSP
Second aircraft: Bombardier/Canadair Undifferentiated or Other Model
Reporter organization: Government
Reporter function: Local
Reporter qualification: Air Traffic Control Fully Certified
Human factors: Situational Awareness
Anomaly: ATC Issue All Types; Conflict Ground Conflict; Critical; Deviation / Discrepancy - Procedural Clearance; Ground Incursion Runway
Detector: Person Air Traffic Control
When detected: Taxi
Result: Air Traffic Control Separated Traffic
Contributing factors: Human Factors
Primary problem: Human Factors

Narrative: I was working the Local Control South position. I observed Aircraft X on Runway 22 approaching Runway 12R/30L. Due to the aircraft's taxi speed I concluded the Aircraft X would be unable to stop without causing a runway incursion. At the same time Aircraft Y was approximately on a half mile final to Runway 12R. I told Aircraft Y to go around. I then observed Aircraft X cross Runway 12R on Runway 22 and turn onto taxiway Whiskey. Wigwag lights and retractable barriers installed at the intersection of 12R/30L and Runway 4/22.




Synopsis: MSP Tower Controller observed a fast taxing aircraft and sent the aircraft on final around.