elihoole/asrs-aviation-reports huggingface dataset:
Date: 201504
Local time of day: 1201-1800
Location: ZMP.ARTCC, MN
Aircraft: Regional Jet 700 ER/LR (CRJ700)
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Descent
Reporter organization: Air Carrier
Reporter function: Captain; Pilot Flying
Reporter qualification: Flight Crew Air Transport Pilot (ATP)
Human factors: Communication Breakdown
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
Contributing factors: Human Factors
Primary problem: Human Factors

Narrative: FL280...We had been filed to MSP via the BAE.EAU9 (EAU CLAIRE). The controller in a mumbling voice cleared us to what we believed he had said as 'descend via the Eau Claire arrival'.  We dialed in the lowest of the published arrival of 11;000.  A few minutes later we were told to contact the next controller on 134.3.  After checking in he verified that we had been cleared to descend via KKILR 1. We responded we were on the Eau Claire.  He mentioned this was happening a lot; and that we were now cleared to descend via the KKILR 1.  We attempted to load the arrival and our route had no transition to the Killer.  He cleared us to CMAAC.Obviously due to the second controllers remark that this happens frequently there appears to be confusion with similar sounding arrivals. Reviewing the arrivals; when we had been given the KKILR; there were no transition on the previous arrival to complete this without being specifically [cleared] direct to a new fix.




Synopsis: CRJ-700 Captain reported misunderstanding the descend via clearance issued by ATC on arrival into MSP. Controller reportedly stated there was a history of misunderstanding the subject arrivals (the EAU CLAIRE and the KKILR).
Date: 201603
Location: BUR.Airport, CA
Weather elements / visibility: Haze / Smoke; 10
Light: Daylight
Aircraft: Gulfstream IV / G350 / G450
Operator: Air Taxi
Operating under: Part 135
Flight plan: IFR
Mission: Passenger
Flight phase: Initial Approach
Airspace: Class C BUR
ATC / advisory: TRACON SCT
Second aircraft: UAV - Unpiloted Aerial Vehicle
Reporter organization: Corporate
Reporter function: First Officer; Pilot Flying
Reporter qualification: Flight Crew Air Transport Pilot (ATP)
Anomaly: Conflict NMAC
Detector: Person Flight Attendant
When detected: In-flight
Result: General None Reported / Taken
Contributing factors: Human Factors
Primary problem: Human Factors

Narrative: We were being vectored to the ILS Runway 8 at Burbank (BUR) just outside of BUDDE intersection at 3;000 feet when the flight attendant (who was sitting in the jump seat) described what she believes was a drone fly past us. The flight attendant estimated the object was at our exact altitude and about half a wingspan off to the left of our aircraft.Neither the captain nor I ever saw it. We continued for an uneventful landing on Runway 8.




Synopsis: GIV First Officer is informed by the Flight Attendant in the jumpseat that they had just missed a drone at 3000 feet during vectors to Runway 8 at BUR. The flight crew never saw the UAV and no evasive action was taken.
Date: 201906
Local time of day: 0601-1200
Location: A11.TRACON, AK
Aircraft: Commercial Fixed Wing
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Initial Climb
Airspace: Class C ANC
ATC / advisory: TRACON A11
Reporter organization: Government
Reporter function: Departure
Reporter qualification: Air Traffic Control Fully Certified
Human factors: Confusion; Situational Awareness
Anomaly: Deviation - Track / Heading All Types; Deviation / Discrepancy - Procedural Published Material / Policy; Inflight Event / Encounter CFTT / CFIT
Detector: Person Air Traffic Control
When detected: Taxi
Result: Air Traffic Control Issued Advisory / Alert; Air Traffic Control Issued New Clearance
Contributing factors: Airspace Structure; Chart Or Publication
Primary problem: Chart Or Publication

Narrative: Aircraft X assigned the KNIK2 SID began left turn at 4.3 DME at 2;300 MSL and the system immediately responded with a low altitude notification. I issued a low altitude alert with an immediate climb and left turn. The aircraft responded in the affirmative and advised terrain in sight. At the TED 057 radial 7.3 DME; Aircraft X entered a lower MVA. I advised the aircraft of the MVA change and issued a normal rate of climb. I believe adding a 'do not penetrate' DME arc about the TED VOR; and incorporating into a new KNIK3 SID; would solve a lot of the issues with our SID. The wording in the notes does not seem to be properly interpreted by the auto pilots; and is being misread or unnoticed by the PICs. A graphically depicted DME arc about the TED DME should be easier for the Flight Director to digest; while providing a visual queue to the PIC that an important restriction exists. I also suggest terrain depictions to be overlaid onto the plate in order to convey the importance of the restrictions by clearly displaying the proximity of the topographical challenge.




Synopsis: A11 TRACON controller reported air carrier on KNIK2 SID entered higher MVA resulting in low altitude alert.
Date: 201907
Local time of day: 1201-1800
Location: ZZZ.Airport, US
Flight conditions: VMC
Light: Daylight
Aircraft: Commercial Fixed Wing
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Cruise
Airspace: Class B ZZZ
ATC / advisory: Center ZZZ
Aircraft component: Gear Extend/Retract Mechanism
Component problem: Malfunctioning
Reporter organization: Air Carrier
Reporter function: Captain
Reporter qualification: Flight Crew Instrument; Flight Crew Multiengine; Flight Crew Air Transport Pilot (ATP)
Human factors: Situational Awareness
Anomaly: Aircraft Equipment Problem Less Severe; Flight Deck / Cabin / Aircraft Event Passenger Misconduct
Detector: Person Flight Crew
When detected: In-flight
Result: Flight Crew Returned To Departure Airport; General Flight Cancelled / Delayed
Contributing factors: Aircraft
Primary problem: Aircraft

Narrative: During flight XXXX from ZZZ to ZZZ1; we had a landing gear malfunction on takeoff. Upon reaching a safe altitude we began troubleshooting. The Flight Attendant called us to ask if she could get up because a passenger had pressed the attendant call button. I told her to remain seated because we were troubleshooting a problem. I then made a brief announcement to passengers that the Flight Attendant would remain seated until we reached a higher altitude. Shortly thereafter; I received a call from the cabin; but it was from a passenger that had picked up the cabin phone. They told me that the Flight Attendant wasn't getting out of her seat when they pressed the call button and that they heard a thumping sound from the airplane. I told the passenger to hang up the phone. I then made a PA to the passengers telling them to remain seated with their seat belts fastened and that we were troubleshooting a problem that was causing the thumping sound and not to be alarmed. I also advised them to listen to the Flight Attendants directions while we prepare for an air return to the ZZZ airport. After landing; I was on the phone with Maintenance and overheard the passenger exchanging words with the Flight Attendant. The Flight Attendant told me that she did not want 3 particular passengers to continue to ZZZ1 with us due to their actions in the cabin; so I asked the Gate Agent to have them rebooked.




Synopsis: Captain reported that on takeoff there was a landing gear malfunction; upon returning to the airport a few passengers were not allowed to continue on the flight.
Date: 201905
Location: ORD.Airport, IL
Flight conditions: IMC
Aircraft: Commercial Fixed Wing
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Final Approach
ATC / advisory: Tower ORD
Reporter organization: Air Carrier
Reporter function: Captain
Reporter qualification: Flight Crew Multiengine; Flight Crew Instrument; Flight Crew Air Transport Pilot (ATP)
Human factors: Communication Breakdown
Anomaly: ATC Issue All Types; Deviation / Discrepancy - Procedural Other / Unknown
Detector: Person Flight Crew
When detected: In-flight
Result: General None Reported / Taken
Contributing factors: ATC Equipment / Nav Facility / Buildings; Procedure
Primary problem: ATC Equipment / Nav Facility / Buildings

Narrative: ORD ATC is using the PRM monitor frequency for routine ground operations communication. This makes it very difficult to hear and understand the primary Tower frequency communication.




Synopsis: Air carrier Captain reported the ILS PRM monitor frequency at ORD is being used for routine ground operations communication; which makes it difficult to hear and understand the primary Tower frequency.
Date: 201505
Local time of day: 1201-1800
Location: ZZZ.Airport, US
Flight conditions: VMC
Light: Daylight
Aircraft: PA-31 Navajo/Chieftan/Mojave/T1040
Operator: Corporate
Operating under: Part 91
Flight plan: DVFR
Mission: Passenger
Flight phase: Descent
Airspace: Class D ZZZ
ATC / advisory: Tower ZZZ
Aircraft component: Engine
Component problem: Malfunctioning
Reporter organization: Corporate
Reporter function: Pilot Flying; Single Pilot
Reporter qualification: Flight Crew Commercial; Flight Crew Multiengine; Flight Crew Instrument
Human factors: Distraction; Workload; Situational Awareness; Troubleshooting
Anomaly: Aircraft Equipment Problem Critical
Detector: Person Flight Crew
When detected: In-flight
Result: Flight Crew Inflight Shutdown; Flight Crew Landed in Emergency Condition; Flight Crew Took Evasive Action
Contributing factors: Aircraft
Primary problem: Aircraft

Narrative: Left engine had been running a little rough throughout the flight. As we descended the engine started to lose power; and upon leveling off at 1;000 feet AGL there was a large drop in EGT and Manifold pressure - but the propeller was still spinning. I tried troubleshooting - switching tanks; boost pumps on; etc. but nothing gave the engine more power. We were losing altitude while approaching the shoreline; so I elected to feather the engine - lest we lose any additional altitude. I wanted to get all aircraft separated from myself; and because I felt that at that time and altitude - that was the correct thing to do.




Synopsis: A PA-31 left engine after lost power and when troubleshooting did not recover it the pilot feathered the engine while level at 1;000 feet preparing to land.
Date: 201812
Local time of day: 1801-2400
Location: ZZZ.Airport, US
Flight conditions: IMC
Aircraft: Airbus Industrie Undifferentiated or Other Model
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Taxi
Second aircraft: Boeing Company Undifferentiated or Other Model
Reporter organization: Air Carrier
Reporter function: Captain; Pilot Flying
Reporter qualification: Flight Crew Multiengine; Flight Crew Instrument; Flight Crew Air Transport Pilot (ATP)
Human factors: Situational Awareness; Communication Breakdown
Second reporter function: Pilot Flying; First Officer
Anomaly: Aircraft Equipment Problem Critical; Conflict Ground Conflict; Critical; Deviation / Discrepancy - Procedural Published Material / Policy; Ground Event / Encounter Aircraft
Detector: Person Maintenance
When detected: In-flight
Result: Aircraft Aircraft Damaged; Flight Crew Returned To Gate; General Flight Cancelled / Delayed
Contributing factors: Human Factors
Primary problem: Human Factors

Narrative: During aircraft pushback while awaiting clearance to start it felt as if the aircraft slid a little as if trying to turn on a painted line. Maintenance stopped the pushback and informed us over the intercom that our right wingtip had just made contact with the aircraft that had been parked behind us. After the pushback crew inspected the situation we were tugged back into the original parking spot.


Second narrative: During cockpit preflight; the airplane shook violently for approx. 3-5 seconds. I exited the airplane to figure out what happened. Upon reaching the tail; it was apparent the ground crew had pushed an Airbus RH wing into our RH elevator and horizontal stab. The 767 elevator sustained damage.


Synopsis: Airbus Captain and B767 First Officer reported that during pushback; ground crew pushed one air carrier aircraft into the other; both aircraft sustained damage.
Date: 201909
Location: LLLL.ARTCC, FO
Aircraft: B777 Undifferentiated or Other Model
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Flight phase: Climb
ATC / advisory: Center LLLL
Aircraft component: GPS & Other Satellite Navigation
Component problem: Malfunctioning
Reporter organization: Air Carrier
Reporter function: Captain
Reporter qualification: Flight Crew Air Transport Pilot (ATP); Flight Crew Multiengine; Flight Crew Instrument
Human factors: Situational Awareness
Anomaly: Aircraft Equipment Problem Less Severe
Detector: Person Flight Crew
When detected: In-flight
Result: General None Reported / Taken
Contributing factors: Aircraft; Procedure; Environment - Non Weather Related; Airspace Structure
Primary problem: Aircraft

Narrative: Departing TLV on two separate occasions; our GPS was jammed. The airplane reverted to INERTIAL updating. We also received the ADS-B EICAS/checklist message as well as the ADS-B STATUS message. Upon exiting the TLV FIR; everything returned to normal.




Synopsis: B-777 Captain reported experiencing GPS jamming multiple times during departure from Tel Aviv airport.
Date: 201807
Local time of day: 0601-1200
Location: ZZZ.Airport, US
Flight conditions: VMC
Light: Daylight
Aircraft: Any Unknown or Unlisted Aircraft Manufacturer
Operating under: Part 91
Flight phase: Parked
Airspace: Class E ZZZ
ATC / advisory: CTAF ZZZ
Second aircraft: Cessna Aircraft Undifferentiated or Other Model
Reporter function: Single Pilot
Reporter qualification: Flight Crew Instrument; Flight Crew Private
Human factors: Communication Breakdown; Time Pressure
Anomaly: Conflict Ground Conflict; Critical; Deviation / Discrepancy - Procedural Published Material / Policy; Ground Event / Encounter Other / Unknown; Inflight Event / Encounter Other / Unknown
Detector: Person Flight Crew
When detected: Other eye witness
Result: General None Reported / Taken
Contributing factors: Airspace Structure; Human Factors
Primary problem: Human Factors

Narrative: I had just landed south and taxied off the runway. I had noticed someone at the hold short line when I landed on runway XX. When I taxied off it looked like someone was doing their run-up near runway XY. There was one radio call that said that someone was taxiing onto XX however as I heard this I saw the other Cessna taxi onto XY. I simply keyed the mike to say 'umm; that's XY' - I should have been more forceful and told the plane on runway XX to return to the taxiway. Turns out the guy started rolling on XY and he was NORDO (No Radio). 5500 ft long runway made it impossible for him to see the other side of the field.Could have been a very close call. I should have said even more. I realized that a major accident could have taken place (two planes taking off in opposite directions); but I'm still unsure what I should have said...Seems like commercial operations in class E should not be able to work NORDO. Just because you legally can in that airspace doesn't mean you should. Furthermore; everyone that day was a Cessna. It did me no good to trouble shoot the position of these planes since they were just referring to themselves as 'Cessna taking active runway XX'The departing pilot from XY eventually turned his radio on and apologized. He took off over the conflicting traffic (that was on the runway first for the record). They saw the plane coming right at them so they stopped.




Synopsis: GA pilot reported observing two aircraft begin to takeoff from opposite ends of a runway at a non-towered field.
Date: 202101
Local time of day: 0601-1200
Aircraft: Commercial Fixed Wing
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Cruise
Reporter organization: Air Carrier
Reporter function: Flight Attendant (On Duty)
Reporter qualification: Flight Attendant Current
Human factors: Situational Awareness; Workload; Physiological - Other
Anomaly: Deviation / Discrepancy - Procedural Published Material / Policy; Flight Deck / Cabin / Aircraft Event Passenger Misconduct
Detector: Person Flight Attendant
When detected: In-flight
Result: General None Reported / Taken
Contributing factors: Environment - Non Weather Related; Human Factors
Primary problem: Human Factors

Narrative: A passenger in XX2 informed us that passenger in YY3 would not keep her mask on. Passenger stated she kept taking her mask off once the flight attendants passed by. When I walked by her the face mask was off and I asked her to put the mask on and she did. Flight Attendant B also had to ask her to put her mask back on.




Synopsis: Flight Attendant reported a passenger was not complaint with face mask policy.
Date: 202111
Local time of day: 0601-1200
Location: ZZZ.ARTCC, US
Flight conditions: VMC
Light: Daylight
Aircraft: Citationjet (C525/C526) - CJ I / II / III / IV
Operator: Corporate
Operating under: Part 91
Flight plan: IFR
Mission: Passenger
Flight phase: Cruise; Descent
Airspace: Class A ZZZ
ATC / advisory: Center ZZZ
Aircraft component: Powerplant Lubrication System
Component problem: Malfunctioning
Reporter organization: Corporate
Reporter function: First Officer; Pilot Flying
Reporter qualification: Flight Crew Air Transport Pilot (ATP); Flight Crew Instrument; Flight Crew Multiengine
Human factors: Troubleshooting; Time Pressure
Second reporter function: First Officer; Pilot Not Flying
Anomaly: Aircraft Equipment Problem Critical; Deviation / Discrepancy - Procedural Published Material / Policy
Detector: Automation Aircraft Other Automation; Person Flight Crew
When detected: In-flight
Result: Air Traffic Control Provided Assistance; Flight Crew Requested ATC Assistance / Clarification; Flight Crew Landed in Emergency Condition; Flight Crew Inflight Shutdown; General Flight Cancelled / Delayed; General Maintenance Action
Contributing factors: Aircraft
Primary problem: Aircraft

Narrative: Engine 1 failed during the descent to ZZZ. We complied with the QRH for engine low oil pressure and completed an inflight engine shutdown. We received priority with ATC and requested to divert to ZZZ1. The Pilot Not Flying completed all QRH procedures and Pilot Flying handled the radios and aircraft control. The descent; approach; and landing were uneventful; and the aircraft was met on the ground by Airport ARFF (Airport Rescue and Firefighting) crews. After ARFF completed an aircraft walk around; we proceeded to FBO for passenger unloading.


Second narrative: During cruise we got a Master Warning/Caution for oil pressure left side. Oil pressure was low; in the red. Other annunciations came on as engine was failing. We descended at low power setting. We ran the checklist and decided to shut down and secure the left engine. We requested priority handing and diverted to ZZZ1. We performed a single engine approach checklist and flew the ILS [Runway] XXL approach and landed. After getting checked out by ARFF (Airport Rescue and Firefighting) we taxied to the FBO.


Synopsis: C525 flight crew reported loss of oil pressure on #1 engine and elected to perform an inflight shut down and diverted to the nearest suitable airport.
Date: 201903
Local time of day: 0601-1200
Location: ZZZ.Airport, US
Light: Daylight
Aircraft: Commercial Fixed Wing
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Parked
Reporter organization: Air Carrier
Reporter function: First Officer; Pilot Not Flying
Reporter qualification: Flight Crew Instrument; Flight Crew Air Transport Pilot (ATP); Flight Crew Multiengine
Human factors: Confusion; Situational Awareness
Anomaly: Deviation / Discrepancy - Procedural Security; Deviation / Discrepancy - Procedural Published Material / Policy
Detector: Person Flight Crew
When detected: Pre-flight
Contributing factors: Company Policy; Procedure; Manuals; Human Factors; Environment - Non Weather Related
Primary problem: Company Policy

Narrative: We had an FAA Maintenance Inspector jumpseating. When he took our credentials; he photographed them with his personal phone. I asked him about that and he said it is just easier and our licenses are the property of the government. My concern is with operational security and privacy issues. The Captain and I had never seen this before; nor had our additional jumpseater. I brought up my concerns with the inspector. The flight was routine and uneventful. I called the union on the way home and they asked me to submit a report on my concerns over these issues.




Synopsis: Air carrier First Officer reported that an FAA Maintenance Inspector photographed the pilots' credentials with his personal mobile phone.
Date: 201308
Local time of day: 1201-1800
Location: ZSPD.Airport, FO
Flight conditions: VMC
Aircraft: MD-11
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Flight phase: Initial Approach
ATC / advisory: Tower ZSPD
Aircraft component: FMS/FMC
Component problem: Improperly Operated
Reporter organization: Air Carrier
Reporter function: First Officer
Reporter qualification: Flight Crew Air Transport Pilot (ATP)
Human factors: Confusion; Human-Machine Interface
Anomaly: Deviation - Track / Heading All Types; Deviation / Discrepancy - Procedural Clearance; Deviation / Discrepancy - Procedural Published Material / Policy
Detector: Person Air Traffic Control; Person Flight Crew
When detected: In-flight
Result: Air Traffic Control Issued Advisory / Alert; Air Traffic Control Issued New Clearance; Flight Crew Became Reoriented; Flight Crew Returned To Clearance
Contributing factors: Aircraft; Procedure; Human Factors; Chart Or Publication
Primary problem: Human Factors

Narrative: During approach planning to ZSPD; the pilot flying loaded the DUM21F to Runway 34 in the secondary flight plan and the DUM23F to Runway 34 in the primary flight plan. After commencing the approach; we were given 35R and I activated the secondary flight plan as directed by the pilot flying. When performing the Approach checklist; I quickly realized that the Localizer identifier was incorrect and manually tuned the localizer for Runway 35R. The pilot flying transitioned visually; making a slight left turn to intercept the localizer to Runway 35R. Moments later; ATC gave us a 10 degree heading change for localizer intercept; though we had already initiated the turn. An uneventful landing was performed.Having two separate arrivals; the DUM21F and the DUM23F; to Runway 34 is confusing and excessive. The transitions need to be better annotated on the Commercial Chart plate. In addition; earlier assignment for the approach by ATC would allow earlier detection of the incorrect localizer frequency during the Approach checklist. As a crew; we detected the incorrect localizer and runway setup; but an earlier detection would have precluded ATC's query and subsequent intercept vector. The arrivals with multiple transitions to the same runways can be simplified or more clearly displayed. I am not sure if this is a chart manufacture shortcoming or a ZSPD issue.

Callback: When asked about the relationship of the multiple arrivals it was discovered that both of the arrivals the Captain had programmed into the primary and secondary routes reporter were associated with Runway 34. When either was activated doing so would autotune the ILS for the same runway; the only difference would be the last waypoint on the line selected STAR. In order to autotune the Runway 35R ILS they would have had to line select specific arrivals associated with that runway. Those arrivals would be any of the following: DUM21G; CUM23G; PIN21G; PIN23G.



Synopsis: The flight crew of an MD-11; inbound to ZSPD; line selected the wrong RNAV STAR associated with their final assigned runway. Doing so autotuned the incorrect ILS frequency and a short lived track deviation resulted.