elihoole/asrs-aviation-reports huggingface dataset:
Date: 202007
Local time of day: 0601-1200
Location: ZZZ.Airport, US
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: Communication Breakdown; Other / Unknown
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 X row X was disappointed with the passenger in front of her because he had his mask down while drinking his coffee. We kindly explained to her that it's allowed.  Passenger X then started griping about the fact she wasn't allowed to move. we professionally explained to her that we are weight restricted in the front so we cannot accommodate that request at this time. She still was confused so we had the CS Supervisor on board talk with her. After we got in the air apparently the two gentlemen in row Y took their own seats and yet again Passenger X started right back up about why she cannot move and they can. Apparently the gate already moved the gentleman; so that they have their row.I was just cornered in my galley by Passenger X. She began raising her voice at me about our guests in front of her for not wearing their masks while eating and drinking. I told her all guests are allowed to have their masks down while eating or drinking. She began raising her voice more about her dying father and she doesn't wanna get exposed to COVID. I told her I'm monitoring the whole situation and they aren't doing anything wrong and apologized. She then told me I was no help and she wants my name. Furthermore; explained I cannot enforce it when they're really doing nothing wrong.Have more information at the gate regarding folks [being] allowed to eat or drink with their masks down.




Synopsis: Flight Attendant reported a passenger was upset with the airline's COVID-19 policies when observing other passengers removing their masks to eat and drink.
Date: 201307
Local time of day: 0001-0600
Location: IAH.Airport, TX
Flight conditions: VMC
Light: Daylight
Aircraft: EMB ERJ 145 ER/LR
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Initial Approach
Airspace: Class B IAH
ATC / advisory: Tower IAH
Reporter organization: Air Carrier
Reporter function: Pilot Flying; Captain
Reporter qualification: Flight Crew Air Transport Pilot (ATP)
Second reporter function: First Officer; Pilot Not Flying
Anomaly: Conflict Ground Conflict; Less Severe; Ground Incursion Runway
Detector: Person Flight Crew
When detected: In-flight
Result: Flight Crew Executed Go Around / Missed Approach
Contributing factors: Human Factors; Procedure
Primary problem: Ambiguous

Narrative: On approach to Runway 8R in IAH on glideslope. When we were [at] 1.3 NM from the threshold (per FMS range to runway reading) ground traffic (aircraft about to cross our runway) was on NE [at] CC taxiway; approaching Runway 8R at high speed. 0.9 NM from the threshold the ground traffic (crossing aircraft) was still on the runway surface area. The Captain (PF) immediately executed a go-around. Subsequently ATC issued a clearance to climb to 2;000 FT and turn to heading 360 for a downwind for Runway 8L.IAH Tower lost situational awareness of the ground traffic and us; as well as our respective distances to the 8R threshold area; thus causing this situation. Tower didn't advise either of us about the other. With the sun in our back the ground traffic would have had difficulty seeing approaching traffic.


Second narrative: [Report narrative contained no additional information]


Synopsis: EMB-145LR flight crew reported they executed a go-around when another aircraft taxied onto their runway when they were a mile out. Flight crew felt it was an ATC error.
Date: 202006
Location: ZZZ.Airport, US
Flight conditions: VMC
Light: Daylight
Aircraft: PA-28 Cherokee/Archer/Dakota/Pillan/Warrior
Operator: Other Flight School
Operating under: Part 91
Flight plan: None
Mission: Training
Flight phase: Initial Approach
Airspace: Class E ZZZ
ATC / advisory: TRACON ZZZ
Second aircraft: Any Unknown or Unlisted Aircraft Manufacturer
Reporter organization: Other Flight School
Reporter function: Instructor; Pilot Flying
Reporter qualification: Flight Crew Flight Instructor; Flight Crew Commercial; Flight Crew Multiengine; Flight Crew Instrument
Second reporter function: Pilot Not Flying; Trainee
Anomaly: Conflict NMAC
Detector: Person Air Traffic Control
When detected: In-flight
Result: Flight Crew Took Evasive Action
Contributing factors: Human Factors; Aircraft
Primary problem: Aircraft

Narrative: I was being vectored to ZZZZZ for the RNAV XX into ZZZ. We were 3;000 feet MSL when the other aircraft was on a course towards us. ATC alerted us to the traffic and was also shown on our traffic page. I immediately did a right descending turn to avoid the traffic collision. The traffic headed towards us did not divert or alter their course.


Second narrative: My instructor and I were getting vectors from ATC for a practice RNAV XX into ZZZ. We have a traffic page and my instructor was looking for traffic that was our altitude and coming direct to us. We turn right to give way and the plane turns toward us. My instructor grabbed the controls and put us in a steep spiral down after reporting to ATC that the traffic was headed right to us. We were told to maneuver as necessary.


Synopsis: Instructor and student pilots reported they experienced an NMAC that required evasive action.
Date: 201907
Local time of day: 1801-2400
Location: ZZZ.Airport, US
Flight conditions: Mixed
Weather elements / visibility: Rain; Thunderstorm
Light: Night
Aircraft: B737-700
Operator: Air Carrier
Operating under: Part 121
Mission: Passenger
Flight phase: Taxi
Airspace: Class C ZZZ
ATC / advisory: Ground ZZZ
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: Situational Awareness; Communication Breakdown; Distraction
Anomaly: Conflict Ground Conflict; Critical; Ground Event / Encounter Aircraft; Inflight Event / Encounter Weather / Turbulence
Detector: Person Flight Crew
When detected: Taxi
Result: Flight Crew Returned To Gate
Contributing factors: Procedure
Primary problem: Procedure

Narrative: Conditions at the time of the event were thunderstorms in the area; rain; and night time. Moments before the push with the jetway disconnected; the Ground Personnel gave me the motion of 'No Headsets'; which was understandable with the lighting in the area. I proceeded to open the cockpit window to have a quick briefing by yelling down to him. He told me they 'are going without headsets'. I said 'I understand; let's use standard signals; but let me give you some additional instructions.' I told him if during the pushback I flash you once with the taxi light; that means 'Stop the push'. If I flash you multiple times with the light; that means we have a problem and 'Pull us back into the gate '. After he had an understanding; I closed the window and we proceeded with the push.ZZZ is a 'No Call for Push' station; I gave them the brakes released signal when we were ready. I was only able to see the Wing Walker on my side (left) who I was relaying the signals. It was about a minute or two before we started moving and I remember saying to the First Officer 'There must be a Traffic Jam behind us.' We proceeded to push then we stopped for about five seconds and I was looking for the Ground Personnel in my visual range to give me the 'Set the Brakes' signal. That is when we felt the jolt to the aircraft. It felt different from a tow bar breaking because there was an obvious swaying motion in the aircraft. I said to the First Officer 'We just got hit!' Looking out the right window we both saw the other aircraft turn away to the right taxiing away.The First Officer was quick on the radio informing Ground Control of the collision and to mitigate the possibility if the other aircraft was unaware of possible damage. I flashed the Ground Crew multiple times with the taxi lights and they immediately towed us back to the gate. Station Ops was called to meet us; and then I started the call to Dispatch and the Operations Center




Synopsis: Flight crew reported that with severe weather; ramp crew could  not use headsets during pushback; resulting in confusion and a collision with another aircraft.
Date: 201906
Local time of day: 0601-1200
Location: EWR.Airport, NJ
Flight conditions: VMC
Light: Daylight
Aircraft: B757 Undifferentiated or Other Model
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Flight phase: Takeoff / Launch
Airspace: Class B EWR
ATC / advisory: Tower EWR
Aircraft component: Speed (Rate Sensing)
Component problem: Malfunctioning
Reporter organization: Air Carrier
Reporter function: First Officer; Pilot Flying
Reporter qualification: Flight Crew Air Transport Pilot (ATP); Flight Crew Multiengine; Flight Crew Instrument
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 None Reported / Taken
Contributing factors: Aircraft; Procedure; Human Factors; Company Policy
Primary problem: Aircraft

Narrative: Observed and wrote up a chronic First Officer speed tape presentation issue. During maintenance corrective action; it was observed that the FO's (First Officer) stall warning test failed. As this has been observed and written up previously; it seems that the speed tape presentation issue is linked to a failed stall warning functionality and that the aircraft most likely is operating without a functioning First Officer stall warning. The speed tape presentation; as written up; has been observed on every flight I have flown of Aircraft X for over 6 years. This is a chronic issue. Maintenance has previously cleared the problem using 27-XX-XX-XXX. Because this happens on every flight; is not erratic; and is connected to a chronically failed stick shaker warning on the FO side; I do not believe this corrective action is appropriate.




Synopsis: B757 First Officer reported an anomaly with the cockpit speed tape display on the Primary Flight Display.
Date: 201312
Local time of day: 1201-1800
Location: ZZZ.Airport, US
Flight conditions: VMC
Light: Daylight
Aircraft: Robinson R22
Operator: FBO
Operating under: Part 91
Flight plan: None
Mission: Training
Flight phase: Cruise
Airspace: Class D ZZZ
ATC / advisory: Tower ZZZ
Aircraft component: Door
Component problem: Improperly Operated
Reporter organization: FBO
Reporter function: Instructor
Reporter qualification: Flight Crew Instrument; Flight Crew Flight Instructor; Flight Crew Commercial
Human factors: Training / Qualification
Anomaly: Aircraft Equipment Problem Critical
Detector: Person Flight Crew
When detected: In-flight
Result: Flight Crew Landed in Emergency Condition; Flight Crew Overcame Equipment Problem
Contributing factors: Aircraft; Procedure
Primary problem: Procedure

Narrative: [In] cruise flight [I] heard loud metal against metal noise. Felt some vibrations in the ship and a yaw/roll to the right. Lowered collective; rolled off throttle; followed through with yaw to the right to clear a ridge. Contacted Tower stating I might have an emergency. Performed an auto[rotation] with power recovery in the desert area nowhere near roads; houses; or persons. Contacted Tower and advised we were on the ground. Helicopter was OK and both occupants alright. Tower asked if medical support was needed and I advised everyone was fine. Shut down; exited and started a walk-around. Noticed cowl door [on the] right side open. Performed preflight and flew back to the airport.




Synopsis: R22 pilot completed a successful autorotation after hearing a loud noise in-flight accompanied by right yaw. Right cowl door found open.
Date: 201812
Local time of day: 1201-1800
Location: ZZZ.Airport, US
Aircraft: No Aircraft
Reporter organization: Air Carrier
Reporter function: Other / Unknown
Anomaly: Deviation / Discrepancy - Procedural Hazardous Material Violation; Deviation / Discrepancy - Procedural Published Material / Policy
Detector: Person Ground Personnel
When detected: Pre-flight
Result: General Work Refused
Contributing factors: Human Factors
Primary problem: Human Factors

Narrative: While security screening of passengers baggage the TSA staff found 2 containers Easy Off Spray.




Synopsis: Cargo Personnel reported Hazmat cleaning solutions in passenger baggage.
Date: 201304
Local time of day: 1201-1800
Location: VUO.Airport, OR
Aircraft: Aerobatic
Flight phase: Final Approach
Airspace: Class E VUO
ATC / advisory: CTAF VUO
Second aircraft: Light Sport Aircraft
Reporter organization: Government
Reporter function: Local
Reporter qualification: Air Traffic Control Fully Certified
Human factors: Communication Breakdown; Confusion; Situational Awareness
Anomaly: ATC Issue All Types; Deviation / Discrepancy - Procedural Published Material / Policy
Detector: Person Air Traffic Control
Result: Air Traffic Control Issued Advisory / Alert
Contributing factors: Airport; Airspace Structure; Human Factors; Procedure
Primary problem: Human Factors

Narrative: A Pitts was on VUO CTAF frequency; broadcasting position reports normally; and responding to my advisories. Right after he announced turning left downwind for Runway 8; a Sonex called ready to depart Runway 26. I gave the Sonex the usual information; plus advised him of inbound traffic; thinking he would wait for opposite direction traffic to land. No response. I then told the Pitts to use caution for a possible departure. Right after the Pitts reported turning final for Runway 8; the Sonex announced he was departing Runway 26. I immediately advised the Pitts of traffic departing opposite direction. The Pitts executed a go-around; and the Sonex departed Runway 26. Open a Tower at VUO; from which we could have easily controlled the traffic and prevented this incident. Pilots at VUO are encouraged to match PDX flow; which was Runway 28 at the time. But it's an uncontrolled airport; and they're free to go either direction. My responsibility at the VUO advisory position is to advise the traffic at VUO of pertinent PDX traffic. It's the pilots' responsibility to separate themselves. The Pitts probably heard the other pilot say Runway 26; but the opposite direction situation was very dicey; so I wanted no doubt that he knew. By the way; our VUO procedures are a joke. ATC should not be on a CTAF frequency. It often confuses the pilots. If ATC is on frequency; pilots usually expect more than advisory service. Due to proximity to PDX; we need to control the traffic at VUO; and the only safe way to do that is with a Tower.




Synopsis: PDX Controller described an opposite direction take off from VUO; the reporter suggesting a Tower be opened at VUO to reduce these types of events.
Date: 202101
Local time of day: 0601-1200
Location: ZZZ.ARTCC, US
Flight conditions: VMC
Light: Daylight
Aircraft: Small Aircraft
Operator: Personal
Operating under: Part 91
Flight plan: IFR
Mission: Passenger
Flight phase: Cruise
Airspace: Class A ZZZ
ATC / advisory: Center ZZZ
Aircraft component: Air/Ground Communication
Component problem: Malfunctioning
Reporter organization: Personal
Reporter function: Single Pilot; Pilot Flying
Reporter qualification: Flight Crew Flight Instructor; Flight Crew Air Transport Pilot (ATP); Flight Crew Instrument; Flight Crew Multiengine
Human factors: Troubleshooting; Training / Qualification; Physiological - Other; Confusion; Communication Breakdown; Situational Awareness
Anomaly: ATC Issue All Types; Aircraft Equipment Problem Less Severe; Deviation / Discrepancy - Procedural Clearance; Deviation / Discrepancy - Procedural Published Material / Policy
Detector: Automation Air Traffic Control; Person Air Traffic Control
When detected: In-flight
Result: Air Traffic Control Issued Advisory / Alert; Flight Crew Became Reoriented
Contributing factors: Human Factors; Aircraft; Environment - Non Weather Related
Primary problem: Human Factors

Narrative: While enroute at FL280; I noticed the radio frequency was very quiet. Since COVID has impacted US aviation; frequency congestion has decreased significantly; which makes longer periods of radio silence a new sense of normalcy.  My last handoff to ZZZ Center was eight minutes prior at which I made positive radio contact on frequency XYZ.AB. I was using COM 1 as primary radio and monitoring XYX.B on COM 2 with the proper audio panel selections to hear both radios simultaneously. After time passed by and I realized I was not hearing anyone; I transmitted my N number on COM 1 to ZZZ Center and did not receive a response. I selected microphone to COM 2 and reached out to ZZZ Center on XYX.B; no response. I switched the microphone back to COM 1 and tried XYZ.AB again; no response. I switched the microphone back to COM 2 and announced; 'All stations on guard; radio check.' After the second attempt; ZZZ1 Center answered and gave me a new frequency; XXC.DY. A Controller replied 'Aircraft X; possible pilot deviation; I have a number for you; advise when ready to copy.' I was extremely shocked at the situation as I was unaware the radio issue had escalated to that extent. I continued my flight to ZZZZ and called as soon as practical after landing. I spoke with a Controller. Controller said NORDO is a common issue but mine was excessive. I have no deviations on my record and strive to maintain a clean record. Going forward; I will be more diligent in recognizing radio silence and will reach out more frequently if I assume the silent period is excessive.




Synopsis: GA pilot reported becoming NORDO enroute and thinking because of the COVID-19 pandemic the radio just had less communication traffic.
Date: 201602
Local time of day: 1201-1800
Location: ZZZ.Airport, US
Flight conditions: VMC
Weather elements / visibility: 60
Light: Daylight
Aircraft: Cessna 210 Centurion / Turbo Centurion 210C; 210D
Operator: Personal
Mission: Personal
Flight phase: Landing
ATC / advisory: Tower ZZZ
Aircraft component: Nose Gear
Component problem: Malfunctioning
Reporter organization: Personal
Reporter function: Pilot Flying; Single Pilot
Reporter qualification: Flight Crew Instrument; Flight Crew Multiengine; Flight Crew Commercial; Flight Crew Flight Instructor
Anomaly: Aircraft Equipment Problem Critical
Detector: Person Flight Crew
When detected: In-flight
Result: Aircraft Aircraft Damaged; Flight Crew Landed in Emergency Condition
Contributing factors: Aircraft
Primary problem: Aircraft

Narrative: When coming in to land I selected my gear down. With no green light [I] looked outside to see my nose gear was not extended. I recycled the gear a few more times with no success. I reverted to the Emergency Gear Extension checklist; and after multiple attempts that was unsuccessful. I then did a soft landing to make sure that my main gears were locked in the down position then performed a hard bounce landing to see if the gear would shake free. The attempt was unsuccessful. I had decided that all my options had been exhausted so I proceeded on a landing without a nose gear but both main gears. I performed 2 practice landings to get an idea of where I would need to land to make it across the intersecting runway. On the 3rd attempt I went through my emergency landing checklist and secured my cockpit; then came in and landed. After the aircraft came to a stop I got out of the aircraft to the left and waited on the grass for emergency crews to arrive.




Synopsis: Cessna 210T pilot reported landing with the nose gear retracted after all efforts to extend it failed.
Date: 202110
Local time of day: 0601-1200
Location: ZZZ.Airport, US
Aircraft: A320
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Parked
Airspace: Class B ZZZ
ATC / advisory: Ground ZZZ
Aircraft component: Air Conditioning and Pressurization Pack
Component problem: Malfunctioning
Reporter organization: Air Carrier
Reporter function: Pilot Flying; Captain
Reporter qualification: Flight Crew Air Transport Pilot (ATP); Flight Crew Instrument; Flight Crew Multiengine
Anomaly: Aircraft Equipment Problem Less Severe; Flight Deck / Cabin / Aircraft Event Smoke / Fire / Fumes / Odor
Detector: Person Flight Attendant
When detected: In-flight
Result: General Maintenance Action
Contributing factors: Aircraft
Primary problem: Aircraft

Narrative: After deplaning all customers; our flight attendants stated that they smelled musty fumes from the mid to aft cabin area (rows 14-21) during low altitude descent during approach and that the fumes remained until the engines were shut down at the gate. I did not smell any fumes. After obtaining pertinent information from the flight attendants; ZZZ maintenance was notified; and a discrepancy was entered into the aircraft logbook. As was previously stated; the fumes event was brought to our attention only after deplaning was completed and we did not smell fumes in the flight deck.




Synopsis: Air Carrier Captain reported being notified at arrival gate by flight attendant of a fume event.  Cabin fumes began during descent and lasted until engine shutdown at gate.