elihoole/asrs-aviation-reports huggingface dataset:
Date: 201905
Location: ZZZ.Airport, US
Aircraft: B737-800
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Initial Climb
Airspace: Class B ZZZ
ATC / advisory: TRACON ZZZ
Reporter organization: Air Carrier
Reporter function: Flight Attendant (On Duty)
Human factors: Physiological - Other
Anomaly: Deviation / Discrepancy - Procedural Published Material / Policy; Flight Deck / Cabin / Aircraft Event Illness / Injury; Flight Deck / Cabin / Aircraft Event Smoke / Fire / Fumes / Odor
Detector: Person Flight Crew; Person Flight Attendant
When detected: In-flight
Result: Air Traffic Control Provided Assistance; Flight Crew Returned To Departure Airport; General Maintenance Action
Contributing factors: Aircraft
Primary problem: Aircraft

Narrative: After takeoff; the #1 [Flight Attendant] and I started smelling something foul. The # 2 [Flight Attendant] called the #1 [Flight Attendant] to see if all crew was smelling the same thing and the cockpit pitched in saying they were smelling something pungent as well. At first; the pilots wanted to continue on but when the smell kept coming back; they decided to head back to ZZZ. The #4 [Flight Attendant] felt nauseous and threw up; the #1 [Flight Attendant] had a headache; [and] the flight crew had a headache along with itchy and dry eyes. I felt nauseous and had a severe headache with heat flashes. As a team; we decided to go to the ER to check ourselves out.




Synopsis: B737-800 Flight Attendant reported persistent foul fumes during climb causing health issues. Flight crew executed a return to departure airport.
Date: 201506
Local time of day: 1801-2400
Location: ZZZ.Airport, US
Aircraft: B737 Undifferentiated or Other Model
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Taxi
Reporter organization: Air Carrier
Reporter function: Captain; Pilot Flying
Reporter qualification: Flight Crew Air Transport Pilot (ATP)
Human factors: Fatigue
Anomaly: Deviation / Discrepancy - Procedural Published Material / Policy
Detector: Person Flight Crew
When detected: Taxi
Result: Flight Crew Became Reoriented
Contributing factors: Human Factors
Primary problem: Human Factors

Narrative: This trip started with an ANF for ZZZ to ZZZ1. The flight was delayed due to late inbound aircraft by approximately 1+ hours. An 11 hour day layover was reduced to XA:06. The hotel cleaning crew was talking loudly outside my door; off and on; until approximately noon. A late afternoon departure to ZZZ2 was delayed 3 hours due to weather. The next segment was scheduled ZZZ2 ZZZ3; approximately 4 hour flight. After the ANF; poor rest; scheduled short day layover; scheduled late night 2 leg flying the next night and adverse weather due to thunderstorms; I was fatigued. Upon arrival at the gate; my fatigue was verified by my failure to shut down the engine once the parking brake was set and APU established on the airplane. My overall parking flow was missed as I realized; during the parking checklist; I had missed other switches (IRS to off; for example). Running the checklist corrected my errors.




Synopsis: Captain reported omitting or deviating from several post flight SOP procedures due to feeling fatigued.
Date: 201902
Local time of day: 1201-1800
Location: ZOA.ARTCC, CA
Flight conditions: VMC
Weather elements / visibility: 10
Light: Daylight
Aircraft: Skylane 182/RG Turbo Skylane/RG
Operator: Personal
Operating under: Part 91
Flight plan: VFR
Mission: Personal
Flight phase: Cruise
Airspace: Class E ZOA
ATC / advisory: Center ZOA
Second aircraft: Light Transport; Low Wing; 2 Turbojet Eng
Reporter organization: Personal
Reporter function: Pilot Flying; Single Pilot
Reporter qualification: Flight Crew Private
Anomaly: Conflict NMAC; Deviation / Discrepancy - Procedural Published Material / Policy
Detector: Person Flight Crew; Person Air Traffic Control
When detected: In-flight
Result: Air Traffic Control Issued Advisory / Alert; Flight Crew Took Evasive Action
Contributing factors: Airspace Structure; Human Factors
Primary problem: Human Factors

Narrative: Returning at 3;500 cruise altitude heading direct to CCR (Concord; CA) between 120 and 130 knots. Using Flight Following with Oakland Center (Freq 127.8). Executive type; twin engine jet was approaching head on at same flight level. Its landing gear was retracted. Oakland Center warned of traffic at 12 o'clock. Approaching jet was on radar; but not identified. Jet did not change course or attitude. Given closing speeds and the fact the jet remained wings level; I determined safest course of evasive action was to force my plane into a steep dive to avoid head on collision. Estimate jet passed directly overhead at approximately 300 feet.




Synopsis: C182 pilot reported an NMAC with a small jet in Oakland Center Class E airspace.
Date: 201905
Local time of day: 0001-0600
Location: ZZZZ.Airport, FO
Aircraft: Cessna Citation Sovereign (C680)
Flight phase: Other Non-Flight
Aircraft component: Oxygen System/Pax
Component problem: Malfunctioning
Reporter function: Pilot Flying; Captain
Reporter qualification: Flight Crew Instrument; Flight Crew Air Transport Pilot (ATP); Flight Crew Multiengine
Human factors: Situational Awareness
Anomaly: Aircraft Equipment Problem Less Severe; Deviation / Discrepancy - Procedural Maintenance; Deviation / Discrepancy - Procedural Published Material / Policy
Detector: Person Flight Crew
When detected: Pre-flight
Result: General Maintenance Action
Contributing factors: Human Factors; Procedure
Primary problem: Human Factors

Narrative: Picked up [the aircraft]. Had a few write-ups for Maintenance including oxygen level low. I wrote it up and it was serviced to the max level. Then 2 days later (they were working other maintenance issues) we went to go fly it and the oxygen was low again. Wrote it up again. The mechanic discovered 7 of the 10 passenger masks were not attached properly.Reporting this event in the hopes that this type of discovery won't happen again. This could have had a very bad outcome.




Synopsis: CE-680 Captain reported maintenance found 7 of 10 passenger oxygen masks were not attached properly; causing a loss of oxygen pressure.
Date: 202111
Local time of day: 1801-2400
Location: ZZZ.Airport, US
Aircraft: A320
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Parked
Aircraft component: Air Conditioning and Pressurization Pack
Component problem: Malfunctioning
Reporter organization: Air Carrier
Reporter function: Pilot Flying
Reporter qualification: Flight Crew Multiengine; Flight Crew Air Transport Pilot (ATP); Flight Crew Instrument
Anomaly: Aircraft Equipment Problem Less Severe; Flight Deck / Cabin / Aircraft Event Smoke / Fire / Fumes / Odor
Detector: Person Flight Crew
When detected: Aircraft In Service At Gate
Result: General None Reported / Taken
Contributing factors: Aircraft
Primary problem: Aircraft

Narrative: Had another fumes event. 3rd one in 2 months.  The plane had a history of fumes events. Was last written up on Date1 or Date2. It would be nice if the FAA; Airbus; and our company got together and figured a way to reduce these.




Synopsis: A320 pilot reported multiple fumes events on assigned aircraft. Reporter suggested there needs to be collaboration between the FAA; aircraft manufacturer; and air carrier to remedy frequent fume events.
Date: 202101
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: Pilot Flying; Captain
Reporter qualification: Flight Crew Instrument; Flight Crew Multiengine; Flight Crew Air Transport Pilot (ATP)
Human factors: Other / Unknown; Physiological - Other
Anomaly: Deviation / Discrepancy - Procedural Published Material / Policy
Detector: Person Flight Crew
When detected: In-flight
Result: General None Reported / Taken
Contributing factors: Environment - Non Weather Related; Human Factors
Primary problem: Human Factors

Narrative: With about 4 hours to go before landing; I had just emerged from the crew rest bunk when Lead Flight Attendant asked me if I could have the flight deck crew wear a face mask when a Flight Attendant was in the cockpit in flight. I told her no for the safety of flight reasons. I did not add anything further.I personally was not going to wear a face mask in the cockpit since I would be in the cockpit for the rest of the flight. I am required by the FAA on my medical 'Must wear corrective lenses; possess glasses for near/intermediate vision.' Since my glasses fog up every time I wear any type of face mask I know that wearing a mask at my flight deck seat is a safety of flight issue. About two hours later when the Lead came to in to give us a restroom break we; First Officer and I; offered her an N95 mask to wear for her safety and set it on the pedestal for her. She did not put it on and chose to wear what appeared to be a non-N95 certified black cloth mask.




Synopsis: Air Carrier Captain reported telling the Lead Flight Attendant that he would not be wearing a face mask in the flight deck due to safety of flight reason as his glasses fog up when wearing a face mask.
Date: 202008
Local time of day: 0601-1200
Location: ZZZ.ARTCC, US
Flight conditions: VMC
Aircraft: MD-11
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Cargo / Freight / Delivery
Flight phase: Cruise
ATC / advisory: Center ZZZ
Aircraft component: Hydraulic System
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: Aircraft Equipment Problem Less Severe
Detector: Automation Aircraft Other Automation
When detected: In-flight
Result: Air Traffic Control Issued New Clearance; Air Traffic Control Provided Assistance; Flight Crew Landed in Emergency Condition; Flight Crew Requested ATC Assistance / Clarification
Contributing factors: Aircraft
Primary problem: Aircraft

Narrative: 15 Minutes into cruise; received a HYD (Hydraulic) 1 OFF alert. Referenced QRH and reviewed HYD 1 FAIL and HYD 1&3 FAIL as contingency. ACARS OPSCTL (Ops Control) message to [dispatch and maintenance control]. Alerted them to limited NWS (Nose Wheel Steering) and possibility of no brakes; worst case. Dispatch coordinated with ATC and ATC [gave us priority assistance]. Received additional and expected QTY LO (Quantity Low) alerts during configuration. Landed uneventfully. CFR (Crash Fire Rescue) followed us to gate XXX. Debriefed CFR. AML entry included '[Priority Assistance Requested]'System malfunction. Hydraulic Leak.




Synopsis: MD-11 flight crew reported hydraulic system failure inflight.
Date: 201707
Local time of day: 1801-2400
Location: ZZZ.Airport, US
Aircraft: Regional Jet 200 ER/LR (CRJ200)
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Cruise
Airspace: Class A ZZZ
ATC / advisory: Center ZZZ
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
Detector: Person Flight Crew
When detected: In-flight
Result: Flight Crew Diverted; Flight Crew Inflight Shutdown
Contributing factors: Aircraft
Primary problem: Aircraft

Narrative: We were at 27;000 ft in cruise when the right engine oil pressure began to fluctuate. As we began to watch it the pressure started to slowly go down. The FO (First Officer) was flying and flew the aircraft the entire time to landing. I ran the QRH for engine oil fluctuations then descend to 21;000 ft and then 17;000 ft the pressure continued to go down which lead me to the shutdown the engine because the pressure now was below 25 psi as I followed the QRH. [We advised ATC] and we proceeded to ZZZ into an uneventful single engine landing.




Synopsis: CRJ200 Captain reported a loss of engine oil pressure at cruise altitude; an inflight shutdown; and successful diversion.
Date: 201807
Local time of day: 1201-1800
Location: OSH.Airport, WI
Flight conditions: VMC
Light: Daylight
Aircraft: Amateur/Home Built/Experimental
Operator: Personal
Operating under: Part 91
Flight plan: None
Mission: Personal
Flight phase: Final Approach
Second aircraft: PA-28 Cherokee/Archer/Dakota/Pillan/Warrior
Reporter organization: Personal
Reporter function: Pilot Flying
Reporter qualification: Flight Crew Instrument; Flight Crew Multiengine; Flight Crew Private
Human factors: Distraction; Time Pressure
Anomaly: ATC Issue All Types; Conflict NMAC; Deviation / Discrepancy - Procedural Landing Without Clearance; Deviation / Discrepancy - Procedural Published Material / Policy
Detector: Person Flight Crew
When detected: In-flight
Result: General None Reported / Taken
Contributing factors: Human Factors; Environment - Non Weather Related; Procedure
Primary problem: Ambiguous

Narrative: Flying the Fisk approach into the Kosh airshow. Established at 85-90 Kias and 1800 msl; a PA-28 passed me closely to my right; overtaking me and cutting in front of me. In the confusion that ensued in avoiding collision; I overflew the fisk controllers and my passenger said he believed the 'wing rock' was for us. I was already too far from fisk for them to see my wing rock. I proceeded to runway 36L and upon reaching short final and commitment to land I did not get a clearance specifically for a dot. Going around was deemed far more dangerous than just landing and vacating the runway due to the incredible traffic density and my good traffic separation at the time. The discipline by pilots during the arrival was poor at best.




Synopsis: GA pilot distracted by near mid air collision; landed without clearance.
Date: 202012
Aircraft: Commercial Fixed Wing
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Taxi
Reporter organization: Air Carrier
Reporter function: Captain; Pilot Flying
Reporter qualification: Flight Crew Instrument; Flight Crew Air Transport Pilot (ATP); Flight Crew Multiengine
Human factors: Situational Awareness; Communication Breakdown; Physiological - Other
Anomaly: Deviation / Discrepancy - Procedural Published Material / Policy; Flight Deck / Cabin / Aircraft Event Passenger Misconduct
Detector: Person Flight Attendant; Person Flight Crew
When detected: Other push back
Result: General Flight Cancelled / Delayed
Contributing factors: Environment - Non Weather Related; Human Factors
Primary problem: Human Factors

Narrative: During pushback a Flight Attendant called and informed me that a passenger was refusing to wear their face mask.  I asked if she wished to have the passenger removed for non-compliance to which she responded in the affirmative.  I had the push crew pull us backed to the gate and requested a Supervisor from operations.  Arriving at the gate; the Flight Attendant informed me that she made four attempts to have the customer replace his mask over his nose to which he refused or was otherwise non-compliant.  The Gate Agent boarded the plane and was unable to get the customer to wear the mask appropriately so he was removed.




Synopsis: Air Carrier Captain reported a passenger would not comply with face mask policy and was removed from the flight.
Date: 201402
Local time of day: 0001-0600
Location: L30.TRACON, NV
Aircraft: Beechjet 400
Flight plan: IFR
Flight phase: Initial Climb
ATC / advisory: TRACON L30
Reporter organization: Government
Reporter function: Departure
Reporter qualification: Air Traffic Control Fully Certified
Human factors: Situational Awareness; Other / Unknown
Anomaly: ATC Issue All Types; Deviation / Discrepancy - Procedural Published Material / Policy; Inflight Event / Encounter CFTT / CFIT
Detector: Person Air Traffic Control
Result: Air Traffic Control Issued New Clearance; Air Traffic Control Issued Advisory / Alert; Flight Crew Returned To Clearance
Contributing factors: Human Factors
Primary problem: Human Factors

Narrative: I was relieving the Developmental and Instructor on DAG. During the briefing; a BE400 reports on frequency; the Developmental advises the pilot to contact Departure on 133.95 which is the correct and published departure control frequency. I took the sector; signed-on; and started to adjust my RADAR scope when the BE400 asks for the departure frequency again. I displayed the aircraft because it wasn't on my tag and had only a limited data block; told the MEAD Controller that I still had him on frequency and requested control. I then climbed the BE400 to 19;000 FT and turned him to heading 100 away from NATCF's [Nellis] airspace. I then noticed how low he was and advised the pilot to climb immediately for terrain. I then RADAR identified him; turned him back on course; and advised him to contact ZLA. The pilot did not appear to comply with the published HOOVR3 minimum obstacle climb rate of 328 FT per NM to 5;000 FT. I recommend the Departure frequencies be highlighted and clarified on all Las Vegas DP's; because this wrong frequency issue happens frequently even with U.S. registered aircraft; yet alone foreign ones.




Synopsis: L30 Departure Controller reports noticing a departing BE400 well below the required altitude for terrain separation and the HOOVR3 SID restrictions. The foreign pilot had trouble switching to the correct departure control frequency.
Date: 201211
Local time of day: 1801-2400
Location: NCT.TRACON, CA
Flight conditions: IMC
Weather elements / visibility: 5
Light: Night
Aircraft: B737-300
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Initial Approach
Airspace: Class C OAK
ATC / advisory: TRACON NCT
Reporter organization: Air Carrier
Reporter function: Captain
Reporter qualification: Flight Crew Air Transport Pilot (ATP)
Human factors: Communication Breakdown; Confusion
Anomaly: Deviation - Altitude Excursion From Assigned Altitude; Deviation - Track / Heading All Types; Deviation / Discrepancy - Procedural Clearance
Detector: Person Air Traffic Control
Result: Air Traffic Control Issued New Clearance
Contributing factors: Human Factors; Procedure
Primary problem: Human Factors

Narrative: On approach to OAK Runway 11; [we] planned visual approach due to ATIS of 2;600 FT ceiling and 10 miles [visibility]. I briefed the ILS course; frequency; and touchdown zone elevation. I somehow failed to set the correct ILS frequency on my side First Officer had the correct frequency on his side. Weather was worse than planned. We were being vectored for the ILS to Runway 11. Somewhere near ALCAT we were cleared for the approach. The aircraft flew past the LOC course due to the frequency error. We were vectored back toward the course but again failed to intercept. ATC canceled our approach clearance and gave us a heading toward the field with a climb to 3;000 FT. Approaching 2;500 FT they called traffic out above us and gave us urgent instruction to descend to 1;800 FT. We complied and saw the traffic on TCAS (no RA occurred). After we crossed the field at 1;800 FT; we were given a climb and RADAR vectors to an uneventful ILS to Runway 11.




Synopsis: OAK Air Carrier arrival for Runway 11 selected an incorrect localizer frequency resulting in a failed intercept requiring additional ATC vectors and an eventual go around event.
Date: 201202
Local time of day: 1201-1800
Location: ZDC.ARTCC, VA
Aircraft: MD-82
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Cruise
Airspace: Class A ZDC
ATC / advisory: Center ZDC
Second aircraft: Cessna Citation Mustang (C510)
Reporter organization: Government
Reporter function: Enroute
Reporter qualification: Air Traffic Control Fully Certified
Human factors: Training / Qualification; Situational Awareness; Human-Machine Interface
Anomaly: ATC Issue All Types; Conflict Airborne Conflict
Detector: Person Air Traffic Control
When detected: In-flight
Result: Air Traffic Control Issued New Clearance
Contributing factors: Airspace Structure; Human Factors
Primary problem: Ambiguous

Narrative: A MD82 was heading westbound; a C510 was heading northbound. The C510 needed a descent due to his arrival airport. I descended him and realized that I had crossing traffic. I immediately turned the MD82 30 degrees right and turned the C510 right to a 070 heading. Then I told the C510 no delay in his descent and to report leaving FL330 for traffic. I called the traffic to him. ZDC has just gone through a complete area change. I am in a new area with 8 new sectors that I have never been certified on before. I believe that because of the limited time and knowledge on the sector my traffic scan is not as good as it usually is. I moved from an area where we had very little crossing traffic. We should have never moved out of the original configuration. In my current area I see no benefit to these changes. The change has only complicated the combining of sectors and is requiring more personnel to work the area. They told us we were moving to 6 areas due to staffing and if this is true we are requiring more in this new configuration. Plus we put the flying public safety at risk by now having the majority of our personnel with limited knowledge on the sectors. At times you might be the only one in the area able to work a particular sector and if you have any questions there is no one around who can assist.




Synopsis: ZDC Controller reported an loss of separation; citing sector reconfiguration as contributory.
Date: 201906
Aircraft: Commercial Fixed Wing
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Other Post flight unload
Reporter organization: Air Carrier
Reporter function: Ramp
Human factors: Situational Awareness
Anomaly: Deviation / Discrepancy - Procedural Hazardous Material Violation; Deviation / Discrepancy - Procedural Published Material / Policy
Detector: Person Ground Personnel
When detected: Other Post flight unload
Result: General None Reported / Taken
Contributing factors: Procedure; Human Factors
Primary problem: Human Factors

Narrative: Bag arrived with battery not removed.




Synopsis: Ramp Agent reported smart bag arrived in cargo with lithium ion battery installed in violation of Hazmat air transport regulations.
Date: 201903
Local time of day: 0601-1200
Location: ZZZ.Airport, US
Flight conditions: VMC
Light: Night
Aircraft: Helicopter
Operator: Air Taxi
Operating under: Part 135
Flight plan: VFR
Mission: Passenger
Flight phase: Parked
Reporter organization: Air Taxi
Reporter function: Pilot Flying; Single Pilot
Reporter qualification: Flight Crew Flight Instructor; Flight Crew Commercial; Flight Crew Instrument
Human factors: Training / Qualification
Anomaly: Aircraft Equipment Problem Critical; Deviation / Discrepancy - Procedural Published Material / Policy; Deviation / Discrepancy - Procedural FAR; Deviation / Discrepancy - Procedural Maintenance
Detector: Person Flight Crew
When detected: Pre-flight
Contributing factors: Company Policy; Human Factors; Procedure
Primary problem: Human Factors

Narrative: A 300 hour maintenance inspection was completed on Company aircraft. During the preflight; a cotter pin was discovered to be missing from the right side pitch control linkage. I flew the aircraft during the time between the inspection and discovery and could possibly have flown it with the cotter pin missing.




Synopsis: Helicopter pilot reported cotter pin was found missing during pre-flight after 300 hour maintenance inspection was completed.