elihoole/asrs-aviation-reports huggingface dataset:
Date: 201306
Local time of day: 1201-1800
Location: ZOA.ARTCC, CA
Flight conditions: VMC
Light: Daylight
Aircraft: A321
Operator: Air Carrier
Operating under: Part 121
Flight phase: Cruise
Airspace: Class A ZOA
ATC / advisory: Center ZOA
Second aircraft: Airbus Industrie Undifferentiated or Other Model
Reporter organization: Air Carrier
Reporter function: Pilot Flying; Captain
Reporter qualification: Flight Crew Air Transport Pilot (ATP)
Anomaly: Inflight Event / Encounter Wake Vortex Encounter
Detector: Person Flight Crew
When detected: In-flight
Result: General None Reported / Taken
Contributing factors: Environment - Non Weather Related
Primary problem: Environment - Non Weather Related

Narrative: Overhead BTY VOR en route to LOMIA Intersection we encountered wake turbulence at FL340 causing the aircraft to roll 10 to 15 degrees of bank to the right. Encounter was momentary with no loss of control or clearance deviation. ATC advised the only aircraft to transit the area recently was a company Airbus that was 15 miles ahead of us also at FL340. We all presume this was the aircraft's wake we encountered. The ride conditions were smooth; both prior to and after the encounter. I don't know what atmospheric condition held the vortices level at FL340 for the two to two and a half minutes between us and the preceding aircraft. Although the wind was on our tail so there would have been no lateral displacement of the vortices.




Synopsis: A321 pilot reported wake vortex encounter at FL340 from preceding Airbus that was two to two and one half minutes ahead.
Date: 201601
Local time of day: 1201-1800
Location: JAX.TRACON, FL
Flight conditions: VMC
Light: Daylight
Aircraft: Military Transport
Operator: Military
Operating under: Part 91
Flight plan: VFR
Mission: Tactical
Flight phase: Cruise
Airspace: Class E JAX
ATC / advisory: TRACON JAX
Second aircraft: Any Unknown or Unlisted Aircraft Manufacturer
Reporter organization: Government
Reporter function: Approach
Reporter qualification: Air Traffic Control Fully Certified
Human factors: Communication Breakdown; Situational Awareness
Anomaly: ATC Issue All Types; Conflict NMAC; Deviation - Track / Heading All Types; Deviation / Discrepancy - Procedural Clearance
Detector: Person Flight Crew
When detected: In-flight
Result: Flight Crew Requested ATC Assistance / Clarification; Flight Crew Returned To Clearance; Flight Crew Took Evasive Action
Contributing factors: Human Factors; Procedure
Primary problem: Procedure

Narrative: Aircraft X was under radar advisories. Aircraft X was issued VFR traffic at his altitude south bound; and told their current heading they would go behind the traffic. I then told them if they turned 15 degrees to the right that they would definitely go behind. Aircraft X acknowledged with looking for traffic. I was then up for break; and during the relief briefing Aircraft X told me that traffic had come within 20 feet of him. That is when I noticed Aircraft X had turned left and reversed course back around into the traffic. I then reported the event to the OM.I should have re issued the traffic again to make sure they saw them and/or given a control instruction instead of a suggested heading.




Synopsis: JAX TRACON Controller reported of issuing a turn to an aircraft to the right to go behind traffic. During the relief briefing; pilot reported the traffic came within 20 feet of the aircraft. Reporter said aircraft turned left instead of right.
Date: 202003
Location: ZZZ.Airport, US
Aircraft: Commercial Fixed Wing
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Parked
ATC / advisory: Ramp ZZZ
Aircraft component: Aircraft Furnishing
Component problem: Improperly Operated
Reporter organization: Air Carrier
Reporter function: Flight Attendant (On Duty)
Reporter qualification: Flight Attendant Current
Human factors: Communication Breakdown; Other / Unknown; Troubleshooting
Anomaly: Aircraft Equipment Problem Less Severe; Deviation / Discrepancy - Procedural Published Material / Policy
Detector: Person Flight Attendant
When detected: Aircraft In Service At Gate
Result: General None Reported / Taken
Contributing factors: Company Policy; Environment - Non Weather Related; Aircraft
Primary problem: Company Policy

Narrative: When we did our safety checks on first flight out of ZZZ; we found no disinfectant wipes. I requested them immediately and none ever came. We had approximately 10 alcohol wipes for the whole flight to ZZZ1; [a] 3 hour 30 minute flight. When we arrived to ZZZ1; we were on same airplane back to ZZZ. When cleaners came on I asked them if they had any disinfectant wipes or alcohol wipes; they said no. I asked if they had disinfectant spray; they said no. The cleaners came on the airplane with a vacuum cleaner and garbage bags. They did not clean the bathrooms nor fill up the empty tissue boxes.




Synopsis: Flight Attendant reported lack of disinfectant wipes and cleaning agents on the round trip flight.
Date: 201504
Location: P50.TRACON, AZ
Flight conditions: VMC
Light: Daylight
Aircraft: Aerobatic
Operator: Personal
Operating under: Part 91
Mission: Training
Flight phase: Cruise
Airspace: Class E P50
Reporter organization: Personal
Reporter function: Instructor; Pilot Not Flying
Reporter qualification: Flight Crew Flight Instructor
Human factors: Situational Awareness
Anomaly: ATC Issue All Types; Conflict Airborne Conflict
Detector: Automation Aircraft Other Automation; Person Flight Crew
When detected: In-flight
Result: Flight Crew Took Evasive Action
Contributing factors: Human Factors; Procedure
Primary problem: Procedure

Narrative: While performing an upset [recovery] flight in training area alpha I had a traffic conflict with a Caravan at 7000 feet. We started spin training at 7;500 feet and while the student was performing a spin maneuver we had a TCAD alert; I immediately instructed the student to recover. At the same time [another] Grob who was also maneuvering in the area alerted me to traffic. Passing 7;000 feet I noticed the traffic and immediately started an extreme dive to avoid the traffic at which point I noticed the Caravan pilot started to maneuver away from me. TCAD alert was 0.3 at same altitude. The alpha aerobatic area was opened with TRACON that morning.I believe when we open an aerobatic box that TRACON should not route traffic right through it.




Synopsis: Aerobatic instructor reported Cessna Caravan traffic was routed through his training area resulting in a conflict.
Date: 201307
Local time of day: 1201-1800
Location: ZZZ.Airport, US
Flight conditions: VMC
Weather elements / visibility: 10
Light: Daylight
Aircraft: Mustang (P51)
Operator: Personal
Operating under: Part 91
Flight plan: None
Mission: Personal
Flight phase: Cruise
Airspace: Class C ZZZ
ATC / advisory: Tower ZZZ
Aircraft component: Oil Line
Component problem: Malfunctioning
Reporter organization: Personal
Reporter function: Single Pilot
Reporter qualification: Flight Crew Air Transport Pilot (ATP); Flight Crew Instrument; Flight Crew Multiengine
Anomaly: Aircraft Equipment Problem Critical; Ground Event / Encounter Other / Unknown; Ground Excursion Runway
Detector: Person Flight Crew
When detected: In-flight
Result: Flight Crew Landed in Emergency Condition; General Declared Emergency
Contributing factors: Aircraft
Primary problem: Aircraft

Narrative: Aircraft developed a major oil leak [that] covered the windshield; [causing] no forward visibility. [I] declared an emergency with the Tower; landed; and departed the runway in the grass to the left of the runway. [There was] no damage to the plane or airport or pilot. [I] talked to the FAA FSDO who advised to remove the plane from the grass and give him a call as to what caused the oil leak.




Synopsis: After observing a significant oil leak; the pilot of a P51 landed in an emergency condition and exited the runway surface. There was no reported damage or injury.
Date: 201306
Local time of day: 1801-2400
Location: ZZZ.Airport, US
Light: Night
Aircraft: A319
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Takeoff / Launch
ATC / advisory: Tower ZZZ
Aircraft component: Air Conditioning Distribution System
Component problem: Malfunctioning
Reporter organization: Air Carrier
Reporter function: Flight Attendant (On Duty)
Reporter qualification: Flight Attendant Current
Human factors: Communication Breakdown; Confusion; Situational Awareness; Troubleshooting
Anomaly: Aircraft Equipment Problem Critical
Detector: Person Flight Attendant
When detected: In-flight
Result: Aircraft Equipment Problem Dissipated
Contributing factors: Aircraft; Human Factors
Primary problem: Aircraft

Narrative: We began our takeoff roll and found it strange that our exit light placards and signs never came on or illuminated for our takeoff. Once airborne at cruise the cabin lost all electrical power and went to black. Our phones were inoperative; (Flight Attendant Panels) FAPs were inoperative and forward as well as aft galleys were making audible clicking and chirping noises. Aircraft temperature was impossible to control; many hot and cold spots and intermittent electrical smells. There was no contact from the cockpit whatsoever during the event and communication was completely unavailable. I had a new lead flight attendant so I ran to the front to assist. I began to write a note to slide under the cockpit door; preparing to bang on door or even use emergency cockpit access procedures. Yet; just as we were beginning to initiate this; the lights came on all to full bright locked and phones still down and FAP began resetting. We finally made contact with flight deck and flight continued on with no further incident.




Synopsis: As they began the takeoff roll the flight attendants aboard an A319 began to notice numerous electrical lighting and galley power anomalies that went unattended by the cockpit crew. As quickly as the events started they ended and reset before the cockpit could be alerted.
Date: 202011
Aircraft: No Aircraft
Reporter organization: Air Carrier
Reporter function: Captain
Reporter qualification: Flight Crew Instrument; Flight Crew Air Transport Pilot (ATP); Flight Crew Multiengine
Human factors: Communication Breakdown; Time Pressure
Anomaly: Deviation / Discrepancy - Procedural Other / Unknown; Flight Deck / Cabin / Aircraft Event Other / Unknown
Detector: Person Flight Crew
When detected: Pre-flight
Result: General Work Refused
Contributing factors: Human Factors; Environment - Non Weather Related; Company Policy
Primary problem: Company Policy

Narrative: I contacted First Officer X to notify him of my desire to wear masks on the flight deck. The FO replied that he did not want to wear a mask in the cockpit. As per policy we both agreed to contact the Union. The Union notified me that they would contact me. They called me to give me the option to remove myself from the trip either with or without pay. I was informed that I could be removed from the trip by using my vacation time thereby retaining my pay. The other option was to be removed from the trip without pay and suffer no other adverse consequences. Although I did not believe that the offers to remove myself from the trip were fair; I felt compelled to drop the trip because of my desire to protect myself from potentially being exposed to COVID-19 on the flight deck. The practice of offering crew members the option of taking vacation time is not sustainable. Considering the variables of the extended time COVID-19 may be affecting operations as well as personal choice to refuse mask wearing; one's vacation time could potentially be quickly exhausted. The company mandates pilots that masks be worn in all public places upon reporting to work to include the employee bus; the terminal; and the cabin to protect ourselves and others. This leads me to question why; when COVID-19 cases among pilots are growing; there is no direction strongly encouraging the wearing of masks even when it is not currently FAA directed.




Synopsis: Air carrier Captain reported the First Officer did not want to wear a mask in the cockpit. The Captain decided due to concerns about exposure to COVID-19; to take the only option given of dropping the trip.
Date: 201206
Local time of day: 1801-2400
Location: ZZZ.Airport, US
Flight conditions: IMC
Light: Night
Aircraft: B737-300
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: Pressurization System
Component problem: Failed
Reporter organization: Air Carrier
Reporter function: First Officer
Anomaly: Aircraft Equipment Problem Critical
Detector: Automation Aircraft Other Automation; Person Flight Crew
When detected: In-flight
Result: General Maintenance Action
Contributing factors: Aircraft
Primary problem: Aircraft

Narrative: Cabin Altitude Warning horn sounded at 37;000 FT. We performed the memory items; ran the appropriate checklists; and performed an emergency descent to 12;000 FT.




Synopsis: A B737-300 First Officer describes an emergency descent when the cabin altitude warning horn sounds at 37;000 FT.
Date: 201812
Local time of day: 1201-1800
Location: CLT.Airport, NC
Flight conditions: IMC
Light: Dusk
Aircraft: Regional Jet 200 ER/LR (CRJ200)
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Taxi
ATC / advisory: Ground CLT
Reporter organization: Air Carrier
Reporter function: Captain; Pilot Flying
Reporter qualification: Flight Crew Multiengine; Flight Crew Air Transport Pilot (ATP); Flight Crew Instrument
Human factors: Distraction; Troubleshooting; Confusion; Communication Breakdown; Training / Qualification
Anomaly: Deviation / Discrepancy - Procedural Published Material / Policy; Flight Deck / Cabin / Aircraft Event Other / Unknown
Detector: Person Flight Crew
When detected: Taxi
Contributing factors: Human Factors; Company Policy; Procedure
Primary problem: Human Factors

Narrative: This was a line check. We had 6 MELs total. [One MEL] was added by me when I discovered the 1B pump would not pressurize the system. This set us back. After everything was signed off; we ran remaining checklists. We then pushed back off the gate. Even though it was previously briefed; the Check Airman was pretty sure the 1B pump switch should be on. I pulled up the MEL again which stated it should be off. We begin taxi on one engine. Temperature is 6 degrees Celsius. The First Officer asks if I want the cowl heat on. Expecting to start the left engine shortly; I stated no and the reason why.Crossing Runway 5 on Golf; I gave the command for delayed engine start. I was greeted with a bleed misconfiguration caution message. The cause of which was the cowl heat being on; not sure why. The Check Airman stated that cowl heat needed to be on. I replied I can't start the left engine with the cowl heat on.After the left engine was idling and the Delayed Start Checklist was complete; we moved onto the Before T/O Checklist. Cowl heat was on. Wings Anti/Ice was off. The temperature was 6 degrees. We were configured according to the weather conditions and the Dispatch Monitor. The Check Airman then informs me we must takeoff with wings and cowls on. I respond by noting the ATIS is indicating 6 degrees and that SAT is 6 degrees. The ceiling is 400 Overcast.At this point; I believe I am in compliance with POH limitations. My First Officer then proceeds to send for new numbers with wings and cowls operating. The check airman told her to do this. I did not. After about three minutes; I elected to takeoff with wings and cowls operating to prevent any further drama.I have never seen this happen before. With weather conditions according to POH. We were within limitations to depart cowls only.




Synopsis: Air carrier Captain reported poor CRM on the flight deck leading to confusion during the taxi-out and preparation for takeoff.
Date: 201906
Local time of day: 1801-2400
Location: ZSE.ARTCC, WA
Light: Daylight
Aircraft: Small Transport
Operator: Air Taxi
Operating under: Part 135
Flight plan: IFR
Mission: Passenger
Flight phase: Climb
Airspace: Class E ZSE
ATC / advisory: Center ZSE
Reporter organization: Government
Reporter function: Trainee; Enroute
Reporter qualification: Air Traffic Control Developmental
Human factors: Distraction; Situational Awareness; Training / Qualification
Anomaly: ATC Issue All Types; Deviation / Discrepancy - Procedural Published Material / Policy; Inflight Event / Encounter CFTT / CFIT
Detector: Person Air Traffic Control
When detected: In-flight
Result: Air Traffic Control Issued New Clearance
Contributing factors: Airspace Structure; Human Factors; Procedure
Primary problem: Human Factors

Narrative: I am currently a Radar Sector trainee training on sectors. Aircraft X departed runway heading of 340 degrees. We do have approval for vectors below the MIA (Minimum IFR Altitude) at 800 feet on that side of the airport. I was thinking about the sequence into the airport with him and another aircraft behind him. I cleared him direct to a VOR 200 feet below the MIA. I realized what I had done after and learned from my mistake. I recommend as a trainee slowing down just a little to think through every possible situation before I issue clearances.




Synopsis: Developmental Controller reported issuing a direct routing to departure below the Minimum IFR Altitude.
Date: 202111
Local time of day: 1201-1800
Location: DFW.Airport, TX
Aircraft: B737-800
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Climb
Airspace: Class B DFW
ATC / advisory: Tower DFW
Second aircraft: Commercial Fixed Wing
Reporter organization: Air Carrier
Reporter function: Captain; Pilot Flying
Reporter qualification: Flight Crew Air Transport Pilot (ATP)
Human factors: Communication Breakdown; Situational Awareness
Anomaly: Conflict Airborne Conflict; Deviation - Track / Heading All Types; Deviation / Discrepancy - Procedural Clearance; Inflight Event / Encounter Wake Vortex Encounter
Detector: Person Flight Crew; Person Air Traffic Control
When detected: In-flight
Result: Air Traffic Control Issued New Clearance; Flight Crew Became Reoriented; Flight Crew Returned To Clearance
Contributing factors: Procedure; Human Factors; Environment - Non Weather Related
Primary problem: Human Factors

Narrative: After takeoff encountered wake turbulence from the previous departure. To avoid further wake turbulence I climbed on runway heading. I tried; after climbing to what I thought was an altitude above the wake of previous plane; to get back on track but encountered wake turbulence again. At this time we finished the clean up and noticed we were off track to the right of the RNAV track. As we started to return to the track received a call from ATC to come left to a heading of 090. After further vectors we were informed to give ATC a call. After calling was informed we had a loss of separation with a departure from the west side. We did not receive any RA or TA advisories or indications. Loss of situational awareness with relation to the RNAV departure track as we were trying to avoid the wake turbulence. Lack of communication with ATC as to what we were experiencing.  Greater separation on takeoff; however communication with ATC could have prevented this situation and maybe an early turn to be on the left side of the wake turbulence.




Synopsis: B737-800 Captain reported a track deviation occurred on departure from DFW during a wake turbulence avoidance maneuver.
Date: 202110
Location: CKB.TRACON, WV
Flight conditions: Marginal
Weather elements / visibility: 10
Aircraft: Skyhawk 172/Cutlass 172
Operator: Personal
Operating under: Part 91
Flight plan: IFR
Mission: Personal
Flight phase: Cruise
Airspace: Class E CKB
Second aircraft: UAV: Unpiloted Aerial Vehicle
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; Distraction; Training / Qualification
Anomaly: Airspace Violation All Types; Conflict NMAC; Deviation / Discrepancy - Procedural FAR; Deviation / Discrepancy - Procedural Published Material / Policy; Deviation / Discrepancy - Procedural Unauthorized Flight Operations (UAS)
Detector: Person Flight Crew
When detected: In-flight
Result: Air Traffic Control Issued Advisory / Alert; Flight Crew Requested ATC Assistance / Clarification
Contributing factors: Environment - Non Weather Related; Human Factors; Weather
Primary problem: Ambiguous

Narrative: I wish to report unauthorized drone use. I was flying IFR; in IMC in and out of clouds near Weston; West Virginia; approximately 20 nm SW of Clarksburg West Virginia. My aircraft; a Cessna 172; was at 7;000 ft. enroute to ZZZ. Conditions of flight were: I was mostly above a broken layer; going in and out of cloud occasionally. I observed a drone pass approximately 300 ft. beneath me. Size is a guess; but I think it was less than two feet in diameter; with a blue light on top. The light could have been sun glare though. I reported the sighting to ATC; Clarksburg Approach they; of course; could do little as they weren't painting a primary target. They did warn other aircraft in the vicinity. I also am convinced that the drone had to be penetrating IMC as I was; it was more likely at the lower altitude because the broken layer was thicker below me. An in flight collision with such a craft would be catastrophic to a C-172; or any aircraft for that matter.




Synopsis: General aviation pilot reported a near miss with a UAS in IMC conditions on an IFR flight plan and advised ATC.
Date: 201706
Local time of day: 1801-2400
Location: ZZZ.Airport, US
Flight conditions: VMC
Weather elements / visibility: 30
Light: Daylight
Aircraft: CH650
Operator: Personal
Operating under: Part 91
Flight plan: None
Mission: Personal
Flight phase: Landing
ATC / advisory: CTAF ZZZ
Reporter organization: Personal
Reporter function: Pilot Flying; Single Pilot
Reporter qualification: Flight Crew Private
Human factors: Situational Awareness; Training / Qualification
Anomaly: Aircraft Equipment Problem Critical; Deviation - Speed All Types; Ground Event / Encounter Ground Strike - Aircraft
Detector: Person Flight Crew
When detected: In-flight
Result: Aircraft Aircraft Damaged
Contributing factors: Human Factors
Primary problem: Human Factors

Narrative: Zenith CH-650 kit-built aircraft in Phase I flight testing. Approach was on typical numbers for speed and altitude until final landing phase when speed was approximately 10 kts too fast. Resulted in bounce and collapsed nose gear. Landing resulted in minor aircraft damage. No damage to persons or facilities other than scrapes on runway. No collateral damage. Landing with no other aircraft in pattern or waiting for takeoff; but runway was closed for approximately 20 minutes. Arriving and departing aircraft used adjacent grass runway. I will take voluntary remedial training with instructor and highly qualified many thousands hours experienced observer pilot for tips and recommendations. Engine will be checked by qualified; factory authorized; mechanic.




Synopsis: Zenith CH650 pilot reported the aircraft sustained minor damage following a bounced landing and collapsed nose gear.