elihoole/asrs-aviation-reports huggingface dataset:
Date: 201909
Local time of day: 0601-1200
Location: ZZZ.ARTCC, US
Flight conditions: Mixed
Weather elements / visibility: Thunderstorm
Aircraft: Citation Excel (C560XL)
Flight plan: IFR
Mission: Passenger
Flight phase: Cruise
Airspace: Class A ZZZ
Reporter function: Pilot Flying; Captain
Human factors: Communication Breakdown; Confusion; Situational Awareness; Time Pressure; Workload
Anomaly: ATC Issue All Types; Deviation / Discrepancy - Procedural Published Material / Policy; Inflight Event / Encounter Fuel Issue; Inflight Event / Encounter Weather / Turbulence
Detector: Person Flight Crew
When detected: In-flight
Result: Air Traffic Control Issued New Clearance; Flight Crew Diverted; Flight Crew Requested ATC Assistance / Clarification
Contributing factors: Weather; Human Factors; Procedure
Primary problem: Weather

Narrative: While enroute to ZZZ; a line of storms formed completely shutting down the arrival into the area. We were issued holding as published at ZZZZZ; FL410; then 390; then 400. In conferring with passengers about our limited options; we decided the best decision was to divert to ZZZ1; where the passengers could catch a train [to their destination]. ATC  was informed and we were given a substantial vector to the south. We still had plenty of fuel so we weren't concerned and figured we needed to get to less busy airspace in order to descend. Eventually; we were given direct ZZZ1 from ATC and started a left turn to the north to comply. It turns out; that even though we informed them we were diverting to '[city]; [state]; [phonetic identifier]' - a Controller entered [same city]; [different state] - [different phonetic identifier] and was taking us there. The controllers just told us to stop our turn and gave us a little bit more routing into ZZZ1 and there weren't any traffic issues that I know of - but ATC wasn't expecting us to do that. It ended up not being a big deal; but wasted a lot of time and could have resulted in us having to divert again due to depleted fuel reserves and weather moving in to ZZZ1. We dropped off 4 of our 6 passengers at ZZZ1; and after taking on fuel and a weather/ATC delay on departure we proceeded to ZZZ2 where the remaining passengers needed to go.When given the significant routing to the south; we were suspicious but didn't want to speak up because many other aircraft were holding and diverting; and the frequency was very busy. Very odd routes like that are semi normal in [this area's] airspace anyway.




Synopsis: C-560XL flight crew reported being incorrectly re-routed by ATC.
Date: 201909
Local time of day: 0601-1200
Location: CZQX.ARTCC, NF
Flight conditions: VMC
Aircraft: B787 Dreamliner Undifferentiated or Other Model
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Cruise
ATC / advisory: Center CZQX
Reporter organization: Air Carrier
Reporter function: Captain; Pilot Flying
Reporter qualification: Flight Crew Air Transport Pilot (ATP); Flight Crew Multiengine; Flight Crew Instrument
Human factors: Communication Breakdown; Confusion
Anomaly: ATC Issue All Types
Detector: Person Air Traffic Control; Person Flight Crew
When detected: In-flight
Result: Air Traffic Control Provided Assistance; Flight Crew Requested ATC Assistance / Clarification
Contributing factors: ATC Equipment / Nav Facility / Buildings
Primary problem: ATC Equipment / Nav Facility / Buildings

Narrative: We were at FL320 and requested a climb to FL360 via CPDLC with Gander Oceanic which Gander approved and we accepted via CPDLC and we climbed to FL360 and reported maintaining FL360 automatically via CPDLC. During the climb; Gander sent us a message via CPDLC to 'check selected Flight level. Cleared flight level is different.' When level at FL360 we contacted Gander Oceanic via HF to query them about their prior message to us and they said they didn't know why; that message was sent to us in error. There was [an aircraft] behind us 2 miles at FL370. We were offset R2 and they were offset R1. No RA . We continued on to EWR uneventfully.




Synopsis: B787 Captain reported receiving an erroneous CPDLC message from ATC regarding assigned flight level.
Date: 201506
Local time of day: 0601-1200
Location: ATL.Airport, GA
Aircraft: Regional Jet 200 ER/LR (CRJ200)
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Flight phase: Descent
Airspace: Class B ATL
ATC / advisory: TRACON A80
Second aircraft: B717 (Formerly MD-95)
Reporter organization: Air Carrier
Reporter function: First Officer; Pilot Not Flying
Reporter qualification: Flight Crew Air Transport Pilot (ATP)
Anomaly: Inflight Event / Encounter Wake Vortex Encounter
Detector: Person Flight Crew
When detected: In-flight
Result: Flight Crew Took Evasive Action
Contributing factors: Environment - Non Weather Related; Procedure
Primary problem: Environment - Non Weather Related

Narrative: Descending thru 10;000 FT MSL we encountered wake turbulence resulting in a 10 degree left bank. The pilot flying (PF) disconnected the autopilot and returned the aircraft to its original position. The rate of roll seemed somewhat abrupt. We shallowed our descent rate after in order to stay above the B717's flight path. In response to my query ATC advised we were 8 miles in trail of a B717. The flight continued uninterrupted and we did not encounter further wake.




Synopsis: CRJ-200 First Officer reported encountering wake turbulence in descent through 10;000 FT in trail of a B717 on arrival to ATL.
Date: 201701
Local time of day: 1201-1800
Location: ZZZ.Airport, US
Aircraft: A319
Operator: Air Carrier
Operating under: Part 121
Mission: Passenger
Flight phase: Taxi
Aircraft component: Air Conditioning Distribution System
Reporter organization: Air Carrier
Reporter function: Pilot Flying; Captain
Reporter qualification: Flight Crew Air Transport Pilot (ATP)
Second reporter function: Flight Attendant (On Duty)
Anomaly: Flight Deck / Cabin / Aircraft Event Illness / Injury; Flight Deck / Cabin / Aircraft Event Smoke / Fire / Fumes / Odor
Detector: Automation Aircraft Other Automation; Person Flight Attendant
When detected: Taxi
Result: Aircraft Equipment Problem Dissipated; General Maintenance Action
Contributing factors: Aircraft; Human Factors
Primary problem: Aircraft

Narrative: After clearing runway; #2 FA called Flight Deck almost same time; ECAM message Aft Cargo Smoke warning; I stopped aircraft to answer FA; and asked for ECAM actions; FA reported 'haze' in cabin and odd smell. I selected the #2 Pack off; while FO started reading ECAM; ECAM instantly cleared; I asked TWR if there was any sort of smoke coming from aft section of aircraft; and he confirmed NO; he asked [another] flight if they saw any; and also said no. I elected to taxi to the gate; as all warnings were gone. After Flight #2 FA said she had a headache the entire flight; I contacted MX Control; filed a quick Fumes report and wrote up the MX items in AC MX logbook; when I deplaned I found the #3 FA in a wheel chair in the gate area; I asked if she was ok; and she said she didn't feel well; I requested the gate agent call EMS for the two FAs. The number one did not wish to be evaluated.We need a COMPANY FUME EVENT procedure that incorporates the FA's and lets them know to let us know when something is going on.


Second narrative: Upon landing and taxi in; smoke filled the cabin. C flight attendant yelled there is smoke and strong burning smell in the cabin. We immediately called the captain and the A flight attendant. Passengers turned on air vents. Captain explained when he turned on air system the engine oil came into the air vent creating this haze. Also; a cabin sensor light came on as we were told by the captain. We were in back galley in jumpseats and immediately felt ill; excruciating headache; coughing; dizzy; scratchy throat and felt very disoriented. After arriving to the gate; we opened the 2L door with captain's approval to help ventilate as I explained I was ill. Then myself and C flight attendant were rushed to the emergency room at the Hospital.


Synopsis: A319 flight attendants and flight crew reported smoke in the cabin after landing. Two of the flight attendants felt nausea and went to the hospital to be checked out.
Date: 201909
Local time of day: 1201-1800
Location: ZZZ.Airport, US
Flight conditions: VMC
Aircraft: B777 Undifferentiated or Other Model
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Parked
Aircraft component: Oxygen System/Crew
Component problem: Improperly Operated
Reporter organization: Air Carrier
Reporter function: Captain; Pilot Not Flying
Reporter qualification: Flight Crew Instrument; Flight Crew Air Transport Pilot (ATP); Flight Crew Multiengine
Human factors: Troubleshooting
Anomaly: Aircraft Equipment Problem Less Severe; Deviation / Discrepancy - Procedural Maintenance; Deviation / Discrepancy - Procedural Published Material / Policy
Detector: Person Flight Crew
When detected: Aircraft In Service At Gate; Pre-flight
Result: General Maintenance Action
Contributing factors: Procedure
Primary problem: Procedure

Narrative: On the preflight of the Captain oxygen mask; my technique is to preflight the mask as per the flight manual and then remove the mask out of the storage compartment to then clean and sanitize the mask with wipes. On today's flight; when I pulled out the Captain O2 mask; I found a solid white film attached to and covering the entire lens of the smoke goggle portion of the mask with giant letters on the film saying to remove the protective film from the lens prior to installation. To examine the mask further; I was not able to fully extend the mask out as the O2 line was tangled and wrapped in and around the expansion rubber bands/straps making it impossible to don the mask if needed. As I was trying to figure out the mask; the oxygen was still continuous flowing trying to inflate the rubber band straps and would not shut off and the rubber bands would not expand so as to be able to put the mask on. Maintenance history showed the mask was replaced the day before and that 2 flights had been flown with the mask in this condition. We made a maintenance write-up and called in the discrepancy to Maintenance. When the mechanic arrived; he too was in disbelief as to what he was seeing. He corrected the 3 issues of the mask. The person who replaced the mask the day before and left the mask in this condition could have seriously impacted the safety of the crew; passengers and plane if there had been a need for the mask for smoke issues; pressurization issues; etc.; and that the Captain would not have been able to don and use the oxygen mask in a timely manner. Our SOP's do not require the removal of the mask from the storage compartment on preflight and [therefore] the 2 prior Captains would not have known the condition of the mask unless taken out of the storage compartment.




Synopsis: B777 Captain reported finding O2 mask in an inoperable condition during preflight.
Date: 201211
Local time of day: 0001-0600
Location: ZZZ.Airport, US
Flight conditions: VMC
Weather elements / visibility: 10
Light: Daylight
Aircraft: Bonanza 35
Operator: Personal
Operating under: Part 91
Mission: Training
Flight phase: Landing
ATC / advisory: Tower ZZZ
Aircraft component: Landing Gear
Component problem: Failed
Reporter organization: Personal
Reporter function: Single Pilot; Pilot Flying
Reporter qualification: Flight Crew Multiengine; Flight Crew Instrument; Flight Crew Private
Human factors: Other / Unknown
Second reporter function: Pilot Not Flying; Instructor
Anomaly: Aircraft Equipment Problem Critical; Ground Event / Encounter Ground Strike - Aircraft
Detector: Person Flight Crew
When detected: In-flight
Result: Aircraft Aircraft Damaged
Contributing factors: Aircraft
Primary problem: Aircraft

Narrative: I sat in the left seat to receive elective dual from a CFI. We were cleared to land on an extended left base following a regional jet. On the extended base I verbally completed the landing checklist. After turning final and I verbalized the Landing Checklist a second time reconfirming the position of each control and the green gear indicator light. The approach was normal; after I began the flare; I heard a dragging noise. When I saw the prop strike; I secured the engine. Tower asked if we needed assistance. The instructor answered that the aircraft was disabled on the runway. There were no injuries.


Second narrative: I sat right seat to give dual to a pilot in his BE35. We were cleared to land on an extended left base behind a commercial airliner. During the extended left base I heard him audibly accomplish the Landing Checklist. He again called out the check items on final. I also visually confirmed the gear down indicator light on about 1 mile final. However; upon flare we heard a dragging noise which turned out to be the main landing gear doors on the runway. Eventually the nose settled in; striking the propeller. We indicated to the Tower the aircraft was disabled on the runway and then vacated the airplane. There were no fuel or oil leaks. The landing was a very smooth and on the mains; it should not have caused the gear to collapse.

Second callback: Post flight revealed that the gear handle was indeed down but the main gear had collapsed on top of the inner gear doors which were closed with the wheels sandwiched between the runway and the doors. The nose gear was retracted and the gear doors were closed. Squabbling between the FAA and the insurance company has delayed inspection and repair of the aircraft; so a cause has not been determined.

Synopsis: BE35 pilot with an instructor aboard reports an apparent gear collapse during landing. The gear had been confirmed down with a green light by both pilots prior to the collapse.
Date: 202008
Local time of day: 1201-1800
Location: ZZZ.Airport, US
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
Aircraft component: APU
Component problem: Malfunctioning
Reporter organization: Air Carrier
Reporter function: Captain; Pilot Flying
Reporter qualification: Flight Crew Air Transport Pilot (ATP); Flight Crew Instrument; Flight Crew Multiengine
Anomaly: Flight Deck / Cabin / Aircraft Event Smoke / Fire / Fumes / Odor
Detector: Person Flight Attendant
When detected: In-flight
Result: Flight Crew Overcame Equipment Problem; General Maintenance Action
Contributing factors: Aircraft
Primary problem: Aircraft

Narrative: During descent to ZZZ strong odor entered the cabin mostly when thrust at idle. Clearing during taxing to gate. Made AML entry; Maintenance found oil leak in APU and said that's what caused the odor. APU was not running during descent though? When accepting the aircraft one of the flight attendants who had been through an odor event before had noticed the residual from the previous flight and had her self removed; no others including myself felt it was that abnormal. Knowing that smell now I would be more aware and think I would refuse it until the source is known.Listen more closely to the concerns of all crew members even if they are the only one.




Synopsis: A319 Captain reported a fumes event during initial approach descent.
Date: 201911
Local time of day: 0601-1200
Location: ZZZ.Airport, US
Flight conditions: VMC
Weather elements / visibility: 5
Light: Daylight
Aircraft: A300
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Parked
ATC / advisory: Ground ZZZ
Aircraft component: Turbine Engine Thrust Reverser
Component problem: Malfunctioning
Reporter organization: Air Carrier
Reporter function: Pilot Flying; Captain
Reporter qualification: Flight Crew Air Transport Pilot (ATP)
Human factors: Confusion; Other / Unknown
Anomaly: Aircraft Equipment Problem Critical
Detector: Automation Aircraft Other Automation; Person Flight Crew; Person Maintenance
When detected: Routine Inspection; Aircraft In Service At Gate
Result: Aircraft Aircraft Damaged; General Maintenance Action
Contributing factors: Aircraft
Primary problem: Aircraft

Narrative: We had a normal landing; roll out and exited the runway uneventfully. Taxiing to [ramp]; we got an ECAM ATS off. ECAM directed us to reset. We attempted one reset and it would not reset. Moments later we taxied and parked uneventfully. Upon shut down and completion of checklist I filled out the logbook for the ATS failure. After exiting Aircraft I found the mechanic doing his walk around and informed him of the ATS write up along with an enroute write up of the First Officer's SGU failure. This is when he told me he found something else and led us to the number 2 engine reverser. The reverser was only partially stowed and the reverser cowling was distorted and wrinkled. I was shocked and the mechanic indicated to me that he has seen it before but was rare. The mechanic went straight to the logbook to enter what he had found. Out of curiosity I went back to the cockpit to look and see if the amber reverser not stowed on num 2 was illuminated and sure enough it was. Not sure why we did not get a reverser not stowed ECAM. Maybe because of the ATS failure ECAM?




Synopsis: A300 Captain reported that a reverser did not properly stow after landing; resulting in cowl damage and an ECAM warning.
Date: 202008
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: Flight Attendant (On Duty)
Reporter qualification: Flight Attendant Current
Human factors: Situational Awareness; Communication Breakdown; Workload
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: Passenger in X6; Mr. A; did not want to comply with mask policy and refused to stop his conversation on his phone when we [were] getting ready for pushback. He got very loud and ornery with me. I went to inform the Captain about the situation and the passenger's behavior and the Captain turned me and said 'what do you want me to do about it.' I was shocked at his response. I figured he was not going to give any support to the situation so I just turned and walked out of the flight deck. Another crew member told me that Mr. A gave him attitude also. At this point I felt that the Captain was not going to give us any support to the situation so I briefed the rest of the flight attendants to not address Mr. A. about wearing his mask so that we would not have a bad situation happen inflight. I put the face mask policy on Mr. A's console and left the situation alone after that. Mr. A. did not wear his mask at all during the flight.




Synopsis: Flight Attendant reported passenger refused to comply with the face mask policy.
Date: 201412
Location: ZBAA.Airport, FO
Flight conditions: IMC
Aircraft: B747-400
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Flight phase: Final Approach
Aircraft component: FMS/FMC
Component problem: Design
Reporter organization: Air Carrier
Reporter function: Captain
Reporter qualification: Flight Crew Air Transport Pilot (ATP)
Human factors: Human-Machine Interface; Distraction; Confusion; Communication Breakdown; Situational Awareness; Workload
Anomaly: ATC Issue All Types; Aircraft Equipment Problem Critical
Detector: Person Flight Crew
When detected: In-flight
Result: Air Traffic Control Issued New Clearance; Flight Crew Requested ATC Assistance / Clarification
Contributing factors: Chart Or Publication; Airport; Aircraft; Human Factors; Procedure
Primary problem: Human Factors

Narrative: The labels of the STARS in the FMC for PEK (ZBAA) have NO relation to the names of the STARS in the Jeppesen (JEPP) book. PEK approach issues STARS by the labels in the Jepp book. ZBAA approach issues clearance for a STAR only a minute or so from the fix which begins the STAR. There are 72 STARS in the FMC. If the STAR loaded by the crew as a best guess before contacting approach control isn't the STAR issued by approach; there is no time to fiddle around with each of the labeled STARs in the FMC trying to match the depiction with the named STAR in the clearance and the JEPP book. We took a best guess at the STAR we thought we would be issued and approach issued a different STAR. I said we were unable to accept the issued STAR.




Synopsis: A B747 Captain reported that ZBAA STAR identifiers in the FMS database utilized different nomenclature than that of the associated STAR arrival chart. The inability to quickly determine; program and activate their cleared arrival caused the reporter to declare the flight unable to comply with the clearance.
Date: 202110
Local time of day: 0601-1200
Location: ZZZ.TRACON, US
Flight conditions: Mixed
Aircraft: Regional Jet 200 ER/LR (CRJ200)
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Descent
Airspace: Class E ZZZ
Second aircraft: UAV: Unpiloted Aerial Vehicle
Reporter organization: Air Carrier
Reporter function: Captain
Reporter qualification: Flight Crew Air Transport Pilot (ATP); Flight Crew Instrument; Flight Crew Multiengine
Human factors: Distraction; Situational Awareness
Anomaly: Airspace Violation All Types; Conflict NMAC; Deviation / Discrepancy - Procedural Unauthorized Flight Operations (UAS); Deviation / Discrepancy - Procedural Published Material / Policy; Deviation / Discrepancy - Procedural Clearance
Detector: Person Flight Crew
When detected: In-flight
Result: Air Traffic Control Provided Assistance; Flight Crew Requested ATC Assistance / Clarification; General Police / Security Involved
Contributing factors: Environment - Non Weather Related; Human Factors
Primary problem: Environment - Non Weather Related

Narrative: While descending on the ZZZZZ Arrival into ZZZ about halfway between ZZZZZ1 and ZZZZZ2; we were descending through 12;400 ft. for 12;000 ft.; and we had what looked like a drone pass off our left side about 200 ft. or so away. We did not have to do any evasive maneuvers. It appeared to be black and silver and cylindrical with what appeared to be the little drone rotors.  It was right around the tops of the cloud layer. We reported it to ATC about 15 seconds later. A little while after reporting it ATC asked us what gate we were planning on. We told them [gate] XX. After landing and taxiing to the gate; [authorities] met us in the jetway and asked us about what we saw. I repeated the events just as I have written here to him.What appeared to be a drone was just above the cloud layer near our flight path on the ZZZZZ Arrival in to ZZZ. Drones should not be near commercial aircraft.




Synopsis: CRJ200 Captain reported a near miss with a UAS while on descent to a Class B airport and reported to ATC.