elihoole/asrs-aviation-reports huggingface dataset:
Date: 201704
Location: ZZZ.ARTCC, US
Aircraft: Widebody Transport
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Cruise
Airspace: Class A ZZZ
ATC / advisory: Center ZZZ
Reporter organization: Air Carrier
Reporter function: Flight Attendant In Charge
Reporter qualification: Flight Attendant Current
Human factors: Distraction
Anomaly: Flight Deck / Cabin / Aircraft Event Passenger Misconduct
Detector: Person Flight Attendant
When detected: In-flight
Result: General None Reported / Taken
Contributing factors: Company Policy; Human Factors
Primary problem: Human Factors

Narrative: During Inflight main cabin meal service Flight Attendant Y told me the passenger wanted the Purser. I approached them. Screens were down. Tried numerous times to reset. They asked for two seats together. I got them the last row aircraft left. Shortly; they were reported filming the crew! I asked them about it and they denied doing it. I asked them to stop as it's against company policy. We had no passenger misconduct sheets in our kits to tear off and hand them the bottom warning section. I also do not see them anywhere online. They interfered with our duties most of the flight.In the recent events being posted online we need clearer policy on how to handle these situations as they will become more common; especially as we shrink the cabins increasing the likely of more confrontations!




Synopsis: A Flight Attendant reported a passenger misconduct incident involving the unauthorized filming of the flight crew performing their duties.
Date: 201705
Local time of day: 1201-1800
Location: ZMP.ARTCC, MN
Light: Daylight
Aircraft: Medium Transport; Low Wing; 2 Turbojet Eng
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Climb
Airspace: Class A ZMP
ATC / advisory: Center ZMP
Second aircraft: Small Transport; Low Wing; 2 Turbojet Eng
Reporter organization: Government
Reporter function: Enroute
Reporter qualification: Air Traffic Control Fully Certified
Human factors: Communication Breakdown; Situational Awareness
Anomaly: ATC Issue All Types; Conflict Airborne Conflict; Deviation / Discrepancy - Procedural Published Material / Policy
Detector: Person Air Traffic Control
When detected: In-flight
Result: Air Traffic Control Issued New Clearance; Air Traffic Control Separated Traffic
Contributing factors: Human Factors; Procedure; Company Policy
Primary problem: Human Factors

Narrative: I was working at the sector and noticed an alert on my display on three aircraft coming from the adjacent Center. It indicated that Aircraft X; who was level at 35000 feet was in conflict with Aircraft Y and Aircraft Z both climbing to 35000 feet all coming from the same adjacent Center sector.  Their 'controller' ended up stopping both Aircraft Y and Aircraft Z at 33000 feet. The problem was Aircraft Z was behind Aircraft Y and 160 knots faster. I alerted the underlying Sector controllers to the large overtake. As soon as Aircraft Y came over; the underlying sector controller stopped Aircraft Y's climb at 31000 feet. If we had not noticed the overtake; separation would have been lost approximately 10 to 15 miles outside the other ARTCC airspace. Retrain Center controllers and hold them accountable for their mistakes.




Synopsis: ZMP Center Controller reported the adjacent Center was handing three aircraft off that were on conflicting headings and in an overtake situation.
Date: 202005
Local time of day: 0001-0600
Location: U90.TRACON, AZ
Flight conditions: VMC
Aircraft: Military
Operator: Military
Flight plan: IFR
Mission: Training
Flight phase: Initial Approach
Airspace: Class C TUS
ATC / advisory: TRACON U90
Reporter organization: Government
Reporter function: Approach
Reporter qualification: Air Traffic Control Fully Certified
Human factors: Distraction; Situational Awareness
Anomaly: ATC Issue All Types; Deviation - Track / Heading All Types; Deviation / Discrepancy - Procedural Clearance; 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: Procedure

Narrative: Aircraft X was an IFR overflight requesting a practice approach. I had a handful of other aircraft at the time but traffic volume was not a factor. While I had Aircraft X on a downwind heading I was also checking a full route clearance for another aircraft to ensure it was good. This resulted in a late turn to base. I realized I had an MVA (Minimum Vectoring Altitude) issue; so I climbed Aircraft X to 8;000 ft. After doing to the low altitude alarm went off; but because I had already issued a climb I did not issue a low altitude alert. Because there is terrain along the final approach course that requires precise altitude control and base turns; I should avoid getting caught up in other duties until I have turned aircraft base; especially for fast moving aircraft.




Synopsis: TRACON Controller reported they were late vectoring an aircraft from downwind to base leg and the aircraft flew below the Minimum Vectoring Altitude.
Date: 201307
Local time of day: 0601-1200
Location: ZAB.ARTCC, NM
Flight conditions: VMC
Light: Daylight
Aircraft: UAV - Unpiloted Aerial Vehicle
Operator: Government
Operating under: Part 91
Flight plan: IFR
Mission: Other national security
Flight phase: Cruise
Airspace: Class A ZAB
ATC / advisory: Center ZAB
Aircraft component: Altimeter
Component problem: Improperly Operated
Reporter organization: Government
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
Anomaly: Aircraft Equipment Problem Less Severe; Deviation - Altitude Undershoot; Deviation / Discrepancy - Procedural FAR; Deviation / Discrepancy - Procedural Published Material / Policy; Deviation / Discrepancy - Procedural Clearance
Detector: Person Air Traffic Control
When detected: In-flight
Result: Air Traffic Control Issued Advisory / Alert; Flight Crew Became Reoriented
Contributing factors: Human Factors; Aircraft
Primary problem: Human Factors

Narrative: When I was given command of the aircraft; it was below Class A airspace on a VFR flight plan at 15;000 MSL. The altimeter setting was set as appropriate for the airspace and altitude it was in. I decided to climb to FL190 and activate our IFR flight plan. After reaching FL190 I forgot to reset my altimeter setting to 29.92. The effect of this was that the aircraft was flying approximately 300 feet lower than indicated by my altimeter. I did not notice this until questioned about it by the Center Controller approximately 20 minutes after reaching FL190. I corrected my error and the aircraft resumed flight at the correct altitude.




Synopsis: A UAV pilot failed to reset the altimeter when the aircraft was climbed to FL190 from 15;000 MSL. ATC questioned the altitude readout and the error was corrected.
Date: 201401
Aircraft: A320
Operator: Air Carrier
Operating under: Part 121
Mission: Passenger
Flight phase: Parked
Aircraft component: Antiskid System
Component problem: Malfunctioning
Reporter organization: Air Carrier
Reporter qualification: Maintenance Airframe
Human factors: Other / Unknown; Situational Awareness; Training / Qualification
Anomaly: Aircraft Equipment Problem Critical; Deviation / Discrepancy - Procedural Maintenance; Deviation / Discrepancy - Procedural Published Material / Policy
Detector: Person Maintenance
When detected: Other pre installation
Result: General Maintenance Action
Contributing factors: Human Factors; Procedure
Primary problem: Human Factors

Narrative: [While working the] pre-installation inspection; we found the left-hand main landing gear harness misrouted. The wiring to anti-skid transducers was reversed. The inboard wheel harness was routed to the outboard and vice versa. Connector 7GV-B routed to inboard position and connector 9GV-B to outboard position. We had to correct wiring routing to the correct sides. There needs to be better quality control at the landing gear vendor or bring back the work in-house.


Second narrative: Before installing the new left-hand main landing gear; Inspection noticed the anti skid transducer wiring harnesses were reversed with harness connector 7GV-B routed to inboard position and 9GV-B routed to outboard position. We had to reroute the harnesses to the correct sides. The overhaul vendor quality assurance needs to be improved.


Synopsis: Maintenance personnel indentified improperly routed antiskid wiring harnessess during pre-installation checks following vendor overhaul of main landing gear assemblies
Date: 201412
Local time of day: 1201-1800
Location: C90.TRACON, IL
Weather elements / visibility: Icing
Aircraft: MD-83
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Initial Approach
ATC / advisory: TRACON C90
Reporter organization: Air Carrier
Reporter function: Captain
Reporter qualification: Flight Crew Air Transport Pilot (ATP)
Second reporter function: First Officer
Anomaly: Aircraft Equipment Problem Less Severe; Deviation - Altitude Excursion From Assigned Altitude; Deviation / Discrepancy - Procedural Clearance; Inflight Event / Encounter Weather / Turbulence
Detector: Person Flight Crew
When detected: In-flight
Result: Flight Crew Overcame Equipment Problem; Flight Crew Regained Aircraft Control; Flight Crew Returned To Clearance
Contributing factors: Aircraft; Procedure; Weather
Primary problem: Ambiguous

Narrative: Right downwind ORD 27R descending in heavy icing conditions. Aircraft encountered heavy ice in the descent between 8000 and 4000 ft. Engine and Wing anti-ice had been selected 'on' before entering icing conditions appoximately 5 minutes prior to event. Tail deice had not been activated at this point. Aircraft was level at 4000 ft and 250 kts.ATC issued us to slow to 210 kts and a 90 degree right turn to heading 180. The combination of flaps being extended; a 25 degree bank turn and ice on tail prevented the slow speed trim from keeping up with nose down tendencies. Aircraft started to sink rapidly in the turn.  Upon realization that the autopilot was not satisfactorily flying the airplane; the autopilot was disconnected as well as autothrottles. The aircraft was in a extreme out of trim nose down situation.Corrective inputs were applied and required aggressive correction to stop the sink. By the time the aircraft was recovered and climbing; we had lost 400 ft. The tail deice was applied and the autopilot was engaged for a normal ILS approach. In heavy icing conditions; the tail deice needs to be run more often.


Second narrative: [Report narrative contained no additional information].


Synopsis: MD-83 flight crew reported encountering tail ice on approach to ORD resulting in a 400 FT altitude deviation.
Date: 202001
Local time of day: 0601-1200
Aircraft: B737-800
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Cruise
Reporter organization: Air Carrier
Reporter function: Flight Attendant (On Duty)
Reporter qualification: Flight Attendant Current
Human factors: Physiological - Other
Anomaly: Aircraft Equipment Problem Less Severe; 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 Attendant
When detected: In-flight
Result: General None Reported / Taken
Contributing factors: Aircraft
Primary problem: Aircraft

Narrative: C FA (Flight Attendant) approached me when while the D and I were doing the entertainment tablet cart. He told me to follow him in the back galley and asked me if I smelled any gasoline type of smell. I told him I did. It smelled like some type of gas scent when turning on a burner and the gas doesn't produce a fire but a gasoline smell. We checked the lavatories or looked at any equipment to see if anything was producing a stronger scent but we could not find anything. C FA then proceeded to call the pilots and the pilots asked us to ask a deadheading Captain we had on board to see if there was anything unfamiliar to him. C FA handled the rest of the situation. This was a scary situation and granted we did not feel any medical effects but slight headaches but hopefully nothing too serious may come from this.




Synopsis: B737-800 Flight Attendant reported a fume event occurred during cruise and was unable to determine the source of the odor.
Date: 202104
Local time of day: 1801-2400
Location: ZZZ.ARTCC, US
Flight conditions: VMC
Light: Dusk
Aircraft: Hawker 4000
Operator: Air Taxi
Operating under: Part 135
Mission: Passenger
Flight phase: Climb
Airspace: Class A ZZZ
ATC / advisory: Center ZZZ
Aircraft component: Cockpit Window
Component problem: Failed
Reporter organization: Air Taxi
Reporter function: First Officer; Pilot Flying
Reporter qualification: Flight Crew Multiengine; Flight Crew Instrument; Flight Crew Air Transport Pilot (ATP)
Second reporter function: Pilot Not Flying; Captain
Anomaly: Aircraft Equipment Problem Critical; Deviation / Discrepancy - Procedural Clearance; Flight Deck / Cabin / Aircraft Event Other / Unknown
Detector: Person Flight Crew
When detected: In-flight
Result: Aircraft Aircraft Damaged; Flight Crew Diverted; Flight Crew Landed in Emergency Condition; Flight Crew Took Evasive Action
Contributing factors: Aircraft
Primary problem: Aircraft

Narrative: Departed ZZZ enroute to ZZZ2. As we were climbing through FL250; we heard a loud bang and noticed that the Right-Side B Panel Window was shattered. In less than 40 seconds; the window let go and we experienced an explosive decompression. Immediately began an emergency descent with intentions of diverting to ZZZ1. During the emergency descent; ATC was unable to hear our radio calls [requesting priority handling] until we reached a lower altitude when there was less wind noise in the flight deck. It was also hard to hear crew-to-crew communication. We were able to communicate with each other utilizing hand signals. Besides glass; the only known objects that departed through the window were: Oakley Conductor 8 sunglasses and case; Clarity Aloft Headset Case; 6 ft. charging cable for Apple products; aircraft cupholder; tinted sunshade visor; energy drink; plastic Fiji water bottle; and a can of Copenhagen Mint smokeless tobacco.


Second narrative: Approximately 15 minutes after departing ZZZ enroute to ZZZ1 while climbing through 25;000 ft.; we heard a loud pop and determined that part of the copilot side aft window had cracked. We slowed our climb rate and within 30 seconds the rest of the window gave way and we experienced an explosive decompression. We immediately executed an emergency descent. Crew was transmitting our intentions but with excessive wind noise; could not establish communication with ATC. After descending to [a] safe altitude and slowing [the] aircraft to minimize wind noise; we were able to establish communication with ATC and were issued a clearance to land on a visual approach to Runway XX at ZZZ1. We landed and taxied in with no further issues. Emergency and medical personnel were waiting when we arrived...


Synopsis: Hawker 4000 flight crew reported the cockpit window breaking away inflight resulted in an explosive decompression. The flight crew performed a successful diversion.
Date: 201704
Local time of day: 1201-1800
Location: ZZZ.Airport, US
Light: Daylight
Aircraft: B737 Undifferentiated or Other Model
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: Fuel Quantity-Pressure Indication
Component problem: Failed
Reporter organization: Air Carrier
Reporter function: Captain; Pilot Flying
Reporter qualification: Flight Crew Air Transport Pilot (ATP)
Human factors: Situational Awareness
Anomaly: Aircraft Equipment Problem Less Severe; Inflight Event / Encounter Fuel Issue
Detector: Person Flight Crew
When detected: In-flight
Result: Flight Crew Diverted; Flight Crew Landed As Precaution; General Maintenance Action
Contributing factors: Aircraft
Primary problem: Aircraft

Narrative: The incident occurred enroute at FL350. Left center tank fuel pump was MEL inop. We took off with 1800 pounds in center tank. After center tank drained; had approximately a 1700-pound fuel imbalance with right side heavier. We transferred fuel; and had both tanks stable at about 6500 pounds each. Right main fuel tank quantity indicator intermittently went to zero many times at cruise; then remained at zero. We wrote up discrepancy in the logbook; and were in process of sending Maintenance message describing condition when left main fuel tank quantity indicator began to intermittently show zero. While attempting to verify fuel on board in FMC; I noticed the FMC fuel onboard total drop from 10.3 to 4.3 in less than one minute. I verified FMC routing to eliminate a routing discrepancy causing the FMC fuel reading to possibly be erroneous. No discrepancy existed; and the total fuel on board number in the FMC continued to rapidly decrease. Without reliable main fuel tank quantity indicators; and with the FMC fuel quantity rapidly decreasing; I made the decision to initiate a rapid descent; and requested nearest suitable airport from ATC. My concern was a fuel leak; and I had no way of verifying fuel on board. No caution or warning; or low pressure lights illuminated. I flew aircraft; communicated with ATC; and communicated with the Flight Attendants and Passengers; while First Officer prepared landing data and communicated with Dispatch.  We performed an uneventful flaps 40 landing.I feel the main contributing factor in this situation is the aging condition of the 737-Classic series fleet. It is not uncommon to have multiple MELs on these aircraft for major components like fuel pumps and gauges.




Synopsis: B737 Captain reported a loss of fuel quantity indication at FL350 with the FMC showing decreasing fuel. Fearing a possible fuel leak the Captain elected to divert to a suitable alternate.
Date: 201512
Local time of day: 1201-1800
Location: ZZZ.ARTCC, US
Aircraft: MD-80 Series (DC-9-80) Undifferentiated or Other Model
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Cruise
Airspace: Class A ZZZ
Reporter organization: Air Carrier
Reporter function: Pilot Flying; Captain
Reporter qualification: Flight Crew Air Transport Pilot (ATP)
Anomaly: Flight Deck / Cabin / Aircraft Event Smoke / Fire / Fumes / Odor
Detector: Person Flight Attendant
When detected: In-flight
Result: Flight Crew Landed As Precaution; Flight Crew Diverted
Contributing factors: Aircraft
Primary problem: Aircraft

Narrative: During cruise flight; at FL330; the Flight Attendants called the Flight Deck and informed myself and the First Officer that there was a noticeable odor in the cabin; and the odor appeared to be getting stronger. The First Officer and I began reviewing the Cabin Fire/Smoke Checklist. The Lead Flight Attendant called the Flight Deck again and stated that the cabin lights had been turned off; and the odor had dissipated rapidly. The Cabin Crew suspected that there might be a problem with one of the ballasts. The odor never returned during the rest of the flight.After some time had passed; we were informed by the Cabin Crew that the aft left lavatory was very hot; and the walls and floor of the airplane in that area were too hot to even touch. They advised that they could feel the heat of the floor through their shoes. After receiving this information; I told the Flight Attendants to keep me advised of any changes; I transferred controls to the First Officer; and then I declared an emergency with ATC and asked for their help in finding a nearby suitable diversion airfield. I then made a PA to the passengers that we would be executing a landing in [a nearby airport]; and to follow the instructions of the crewmembers. We descended and landed normally; and we had [emergency services] inspect the exterior of the aircraft. The [emergency services] Captain advised me that through infrared he could see large heat signatures in the back of the aircraft; in particular; he advised that the bags in the aft cargo compartment appeared to be glowing. Once [emergency services] advised that the aircraft was cleared; and the Flight attendants reported that there were no adverse changes in the cabin; we proceeded to the north transient ramp and deplaned via the forward stairs; with [emergency services] continuously standing by and monitoring. More effective aircraft maintenance and inspection procedures.




Synopsis: MD-80 Captain reported diverting to an alternate after heat and odor were noticed in the cabin.
Date: 202010
Local time of day: 0001-0600
Location: ZZZ.Airport, US
Flight conditions: VMC
Light: Dawn
Aircraft: A319
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Taxi
Aircraft component: Tablet
Component problem: Malfunctioning
Reporter organization: Air Carrier
Reporter function: Flight Attendant (On Duty)
Reporter qualification: Flight Attendant Current
Human factors: Confusion; Situational Awareness
Second reporter function: Flight Attendant (On Duty)
Anomaly: Aircraft Equipment Problem Less Severe; Deviation / Discrepancy - Procedural FAR; Deviation / Discrepancy - Procedural Published Material / Policy; Flight Deck / Cabin / Aircraft Event Other / Unknown
Detector: Person Flight Attendant
When detected: In-flight; Taxi
Result: Flight Crew Overcame Equipment Problem; General Flight Cancelled / Delayed
Contributing factors: Equipment / Tooling
Primary problem: Equipment / Tooling

Narrative: We were taxiing to the runway. I opened my tablet to access the safety PA and it was not there. I notified the Captain that my PAs were not on my tablet. We were nearing take-off so I gave the safety PA by memory. After take-off; the #2; #4 and I realized we could not find our PAs or our manuals on our tablet. I spoke with the FO and he informed me that there was a systemwide outage of the Safety Manual.


Second narrative: Noticed after takeoff that my in flight manual was not downloading to my tablet.


Synopsis: Flight Attendants reported a system wide failure of the Safety Manual required them to recite safety announcements from memory.