elihoole/asrs-aviation-reports huggingface dataset:
Date: 201209
Local time of day: 0601-1200
Location: ZTL.ARTCC, GA
Aircraft: B737-800
Operator: Air Carrier
Operating under: Part 121
Mission: Passenger
Flight phase: Cruise
Airspace: Class A ZTL
ATC / advisory: Center ZTL
Second aircraft: B777 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; Inflight Event / Encounter Loss Of Aircraft Control
Detector: Person Flight Crew
When detected: In-flight
Result: Air Traffic Control Issued New Clearance; Flight Crew Regained Aircraft Control
Contributing factors: Environment - Non Weather Related
Primary problem: Environment - Non Weather Related

Narrative: At Cruise at FL330; 70 NM west of CALCO we experienced a rapid roll to the right not exceeding 30 degrees Angle Of Bank (AOB). [We] took control of aircraft putting airplane into Control Wheel Steering (CWS) and Control Wheel Position (CWP) to correct to level flight. No altitude loss. Asked ATC what type of aircraft we were following at FL330 and the spacing. They said it was a B777 at FL330 at 8 miles. Told them we had a partial upset. [ATC] told us to descend to FL290. No passengers were up and about. No injuries to any passengers or flight attendants; continued uneventfully.




Synopsis: B737-800 Captain reported a 'partial upset' at FL330 when he encountered the wake of a B777 8 miles ahead.
Date: 201205
Local time of day: 1201-1800
Location: ZMP.ARTCC, MN
Flight conditions: IMC
Weather elements / visibility: Cloudy
Light: Daylight
Aircraft: Cessna 210 Centurion / Turbo Centurion 210C; 210D
Operator: Personal
Flight plan: IFR
Flight phase: Initial Climb
ATC / advisory: Center ZMP
Reporter organization: Government
Reporter qualification: Air Traffic Control Fully Certified
Human factors: Situational Awareness
Anomaly: Conflict Airborne Conflict; Inflight Event / Encounter VFR In IMC
Detector: Person Air Traffic Control
When detected: In-flight
Result: Air Traffic Control Separated Traffic; Air Traffic Control Issued New Clearance
Contributing factors: Human Factors; Procedure
Primary problem: Human Factors

Narrative: Aircraft Y was inbound on the GPS 35 to the Mora (JMR) Airport and over to advisories.  Aircraft X called at JMR looking for his IFR clearance.  I did have a proposal for him.  I asked him if he was on the ground and he said no; that he had departed and he was 010.  I gave him his code and told him to maintain VFR.  He replied that he couldn't because he was in the clouds.  I told him that Aircraft Y was inbound to JMR about 10 miles out; inbound.  Aircraft X responded that he was in the clouds.  Aircraft X's code popped up on my scope about 3 miles South of JMR.  I suggested he turn to a 090 heading immediately.  I called Aircraft Y to see if he was monitoring the frequency and he responded.  I issued him a clearance to turn to a 270 heading and climb to 040 and I cancelled his approach clearance.  Aircraft Y complied and said that he had Aircraft X on TCAS.  They were about 2 1/2 miles apart; but they were altitude separated.  Aircraft X should not have departed in IFR conditions.




Synopsis: ZMP Controller described a loss of separation when an IFR aircraft departed non-towered airport without a release; conflicting with an IFR inbound.
Date: 201705
Local time of day: 1201-1800
Aircraft: Commercial Fixed Wing
Operator: Air Carrier
Operating under: Part 121
Mission: Passenger
Flight phase: Cruise
Reporter organization: Air Carrier
Reporter function: Flight Attendant (On Duty); Flight Attendant In Charge
Reporter qualification: Flight Attendant Current
Anomaly: Aircraft Equipment Problem Less Severe; Flight Deck / Cabin / Aircraft Event Illness / Injury
Detector: Person Passenger
When detected: In-flight

Narrative: I was in the first class galley working the flight attendant A position.  Flight attendant B; approached me and informed me that the passenger in 6A had detected a brown liquid on her tray table.  FA B immediately gave the passenger prewet wipes and the passenger proceeded to wipe of the liquid. Flight attendant B then proceeded back to inspect and also cleaned the soiled area with wet clothes.  Several minutes later after disposing of the clothes in the garbage can in the first class galley FA B noticed that she felt a burning sensation on her hands.  She immediately notified the Captain.  She then proceeded to wash and sanitize her hands.  At this point we realized the liquid on the tray table was not coffee or coke but some type of corrosive.  The Captain advised us to retrieve the soiled clothes from the garbage bin.  I proceeded to put on protective gloves and retrieved the soiled clothes; putting them into the hazmat bag from the Universal Precaution Kit (UPK) and then sealing that bag and placing that bag into a garbage bag and sealing that bag.  We relocated the bag away from the passengers until landing.  Upon landing Hazmat came on board and retrieved the bag.  The passenger in 6A had no issues with her hands burning but reported a slight and temporary itching which disappeared after she cleaned her hands.  She reported back to us that she felt fine and was not concerned.  We reported this information to the Captain.  Upon landing a maintenance crew member came on the aircraft and inspected the tray table and seat for any further fluid.  The passengers all deplaned without any further incident.  Flight attendant B reported that she also had no further irritation to her skin.

Callback: The reporter stated that a brown liquid substance was found on a tray table and when the passenger attempted to wipe it off using a wipe it burned her skin. The reporter also stated that another flight attendant attempted to assist the passenger clean up the substance when she too felt her skin burning. The reporter stated that the brown substance was from an unknown origin; suspect perhaps its from a leaking battery from a previous passenger or a cleaning solution used by Maintenance. The reporter stated she was sure the origin of the substance was not from the aircraft itself.



Synopsis: Flight Attendant reported that a passenger detected a brown liquid on her tray table that irritated skin when contact was made.
Date: 201510
Local time of day: 1801-2400
Location: ZZZ.Airport, US
Flight conditions: VMC
Light: Night
Aircraft: B747 Undifferentiated or Other Model
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Flight phase: Cruise
Airspace: Class A ZZZ
ATC / advisory: Center ZZZ
Reporter organization: Air Carrier
Reporter function: Captain; Pilot Not Flying
Reporter qualification: Flight Crew Air Transport Pilot (ATP)
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
Contributing factors: Aircraft
Primary problem: Aircraft

Narrative: We departed and upon level off at FL300 we noticed an EICAS 'FUEL IMBALANCE 1 and 4'. The entire crew looked at the fuel synoptic in disbelief because fuel is not burned out of 1 and 4 by system logic until tanks 1;2;3;4 are approximately even (about 30k pounds). We ran the fuel imbalance check list and tried to determine if we had a leak but totalizer and calculated fuel were about the same and no other factors indicated to us that we had a leak. We balanced the fuel between tanks 1 and 4 by closing #1 crossfeed. When the levels were within 800 pounds the balance was close enough and we opened crossfeed 1 again. Fuel balance remain good until late in the flight. FO became alarmed when we got to our next fix and we were down 1500#. I had a wait and see attitude and recommended we press on and maybe we would get the fuel score in line with the OFP. By the next fix we were down 2500# on the fuel score and the FO advocated and I agreed to contact [Maintenance]. [Maintenance] downloaded our data and told us there were no fuel error codes and that he recommends we continue our flight but keep a close watch on the fuel. A few fixes later we were 5500 to 6000# down on the fuel score so I told the FO that I felt we should divert and if he agreed; also wake the [relief pilots] up and prepare for the divert. We did NOT initially declare an emergency but when we started dumping fuel to get down under the max landing weight we got out of balance again between tanks 1 and 4 by about 5000#. I told the crew to terminate the dump and I [advised ATC] - mainly because I had no confidence in the fuel indicators and that we would most likely land overweight. We requested a lower altitude to burn fuel to lighten the weight and I pulled speed brakes to assist in the burn. Flight attendants were briefed and we did ask ATC to 'roll the equipment.' We landed 1.9 over max landing and the landing was uneventful.




Synopsis: B747 Captain reported diverting to an alternate after noting fuel quantity indication system anomalies.
Date: 201807
Local time of day: 1801-2400
Location: ZZZ.Airport, US
Flight conditions: VMC
Weather elements / visibility: 15
Light: Daylight
Aircraft: PA-28 Cherokee/Archer/Dakota/Pillan/Warrior
Operator: FBO
Operating under: Part 91
Flight plan: VFR
Mission: Training
Flight phase: Climb
Airspace: Class E ZZZ
ATC / advisory: CTAF ZZZ
Aircraft component: Engine
Component problem: Failed
Reporter organization: Personal
Reporter function: Pilot Flying; Single Pilot
Reporter qualification: Flight Crew Student
Human factors: Training / Qualification; Troubleshooting
Anomaly: Aircraft Equipment Problem Critical; Deviation / Discrepancy - Procedural Published Material / Policy
Detector: Person Flight Crew
When detected: In-flight
Result: Aircraft Aircraft Damaged; Flight Crew Landed in Emergency Condition; General Evacuated
Contributing factors: Aircraft
Primary problem: Aircraft

Narrative: Student pilot rented Aircraft X for a VFR solo cross country flight; operating under CFR Part 91. Before departure; a logbook endorsement was received from the pilot's CFI for the intended route of flight and a VFR flight plan was filed for this route indicating a cruising altitude of 3;000 and five hours of fuel onboard. Aircraft X departed ZZZ1; activated flight plan shortly after; climbed to FL030; and continued for pattern entry for ZZZ approx. 1 hour later. No traffic was observed in the pattern at ZZZ; and a touch and go was made on Rwy YY. On upwind; at an unknown altitude; the engine RPM went from 2800 to 500 in approx. one second. After pumping the throttle the engine restarted then quit again.A 180 degree turn was made back to ZZZ airport; Rwy YX; but not enough altitude was available to reach the field; and the airplane was landed into a nearby body of water. The fuel selector was on the Left tank from departure at ZZZ1; the electric boost pump was on; per the checklist. Upon landing; the pilot was able to get the attention of people on shore who came to the scene in a canoe.




Synopsis: Engine failed after touch and go; aircraft landed in a lake; no injuries indicated.
Date: 201511
Local time of day: 1201-1800
Location: ZZZ.Airport, US
Flight conditions: VMC
Aircraft: Widebody Transport
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Cargo / Freight / Delivery
Flight phase: Cruise
Airspace: Class A ZZZ
ATC / advisory: Center ZZZ
Aircraft component: Pneumatic System
Component problem: Malfunctioning
Reporter organization: Air Carrier
Reporter function: Pilot Flying; First Officer
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 Landed As Precaution; Flight Crew Diverted
Contributing factors: Aircraft
Primary problem: Aircraft

Narrative: Got a High Stage Bleed message.  Less than a minute later got a Manifold message.  Captain followed the QRH. We pulled the engine back to idle and left the bleed closed.  I continued to fly with the auto throttles off.  We were cruising at FL370. We requested lower to keep from bleeding off too much airspeed.  We were given FL290. Got weather for ZZZ and ZZZ1.  We had come through ice out of [the departure airport] so returning there was not an option as we had no wing anti ice.  We decided to continue to ZZZ1 after ATC informed us of rain in the vicinity of ZZZ.  The captain took over as Pilot Flying after completing the in range checklist.  Captain asked me to manipulate the flight control panel for him even though the Autopilot (AP) was engaged.  Since the autothrottles remained off this helped him better monitor the aircraft.  I think having me do the Flight Control Panel (FCP) was a smart move and kept us ahead of the aircraft.  Did an autoland; got checked out by [Airport Rescue and Fire Fighting] with no adverse heat signature on [the affected engine] then taxied to the gate.Manifold message.  Land at nearest suitable airport. We continued to ZZZ1 finding it the nearest suitable.Not sure about how to prevent it.  But; it would have been easier to shut the engine down than leave it running at idle.  Leaving it running at idle meant no auto throttles which increased our workload.




Synopsis: A First Officer reported diverting to nearest suitable airport after receiving High Stage Bleed and Manifold 3 messages.
Date: 201908
Local time of day: 0601-1200
Location: ZZZ.Airport, US
Flight conditions: VMC
Light: Daylight
Aircraft: Cessna 152
Operator: FBO
Operating under: Part 91
Flight plan: IFR
Mission: Training
Flight phase: Initial Climb
ATC / advisory: Center ZZZ
Aircraft component: Engine
Component problem: Failed
Reporter organization: FBO
Reporter function: Instructor; Pilot Flying
Reporter qualification: Flight Crew Commercial; Flight Crew Flight Instructor; Flight Crew Multiengine; Flight Crew Instrument
Human factors: Situational Awareness; Troubleshooting
Anomaly: Aircraft Equipment Problem Critical; Inflight Event / Encounter Other / Unknown
Detector: Person Flight Crew
When detected: In-flight
Result: Flight Crew Landed in Emergency Condition; Flight Crew Returned To Departure Airport; General Maintenance Action
Contributing factors: Aircraft; Equipment / Tooling
Primary problem: Aircraft

Narrative: Upon going around at ZZZ; on Runway XX; our Cessna 152 began to struggle to climb; combined with [an] rpm drop. Both student and I confirmed oil pressure and oil temp were in the green arc; 10 seconds later our oil pressure began to drop and oil temp began to rise. At the first indication of the changes in operating range; I pitched for best glide and [requested priority handling]. I turned 180 degrees back to ZZZ and let Center know of the situation and changed over to advisory and did the same. The motor began to shake itself apart and we glided back and made the runway safely. Upon inspection from Maintenance; the motor has suffered internal failure and will need a new motor.




Synopsis: C-152 Flight Instructor reported engine failure shortly after takeoff resulting in a turn back to departure airport.
Date: 201909
Local time of day: 0601-1200
Location: ZZZ.Airport, US
Aircraft: EMB ERJ 170/175 ER/LR
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Takeoff / Launch
Reporter organization: Air Carrier
Reporter function: Captain; Pilot Flying
Reporter qualification: Flight Crew Air Transport Pilot (ATP); Flight Crew Instrument; Flight Crew Multiengine
Human factors: Confusion; Situational Awareness
Second reporter function: Pilot Not Flying; First Officer
Anomaly: Flight Deck / Cabin / Aircraft Event Smoke / Fire / Fumes / Odor
Detector: Person Flight Crew
When detected: In-flight
Result: Air Traffic Control Provided Assistance; Flight Crew Returned To Departure Airport
Contributing factors: Aircraft
Primary problem: Aircraft

Narrative: On takeoff; I noticed an odor. After takeoff; the odor increased. We called the FAs and they smelled it as well and said that it was strong. It smelled like some type of burning smell. We [notified ATC] and returned to land at ZZZ. Paramedics met the aircraft at the gate as a precaution; but nobody requested any medical attention. The smoke/fire/fumes checklist does not perfectly fit the scenario. As I had dealt with fumes before; I knew that we would only be running a modified checklist. In the checklist; some of the 'yes/no questions' refer to smoke; but not fumes. In a case with invisible fumes or odor; these questions don't apply and it's difficult to tell if fumes have dissipated because the oxygen masks prevent identifying if a smell is still present. Post-flight discussion with maintenance personnel revealed that aircraft had a compressor wash completed prior to the flight.


Second narrative: On departure from ZZZ we noticed an odd burning smell with no identifiable source. We saw no smoke in the cabin. We confirmed with the cabin crew and decided to return to ZZZ. We [notified ATC] and returned to ZZZ after running an amended smoke fire fumes checklist. We landed in ZZZ without incident. Review the smoke fire fumes checklist for some ambiguity.


Synopsis: EMB-175 flight crew reported detecting a 'burning odor' on departure. After completing the QRH procedure; crew executed an uneventful return to departure airport.
Date: 202108
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: Parked
Aircraft component: Air Cycle Machine
Component problem: Malfunctioning
Reporter organization: Air Carrier
Reporter function: Flight Attendant (On Duty)
Reporter qualification: Flight Attendant Current
Anomaly: Aircraft Equipment Problem Less Severe; Deviation / Discrepancy - Procedural Published Material / Policy; Flight Deck / Cabin / Aircraft Event Smoke / Fire / Fumes / Odor
Detector: Person Flight Crew
When detected: Aircraft In Service At Gate
Result: General Flight Cancelled / Delayed
Contributing factors: Aircraft
Primary problem: Aircraft

Narrative: We had just started boarding when the Captain called to the back of the aircraft and asked if we smelled anything unusual.  I could smell an oil/chemical smell. We then deplaned the pax that had boarded and we got off the aircraft.




Synopsis: A319 Flight Attendant reported a fume event during boarding resulting in deplaning passengers.
Date: 201512
Local time of day: 1201-1800
Location: MRLB.Airport, FO
Flight conditions: VMC
Aircraft: Large Transport
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Initial Approach
Airspace: Class A MHTG
ATC / advisory: Center MHTG
Reporter organization: Air Carrier
Reporter function: Captain; Pilot Not Flying
Reporter qualification: Flight Crew Air Transport Pilot (ATP)
Human factors: Human-Machine Interface; Situational Awareness
Second reporter function: Pilot Flying; First Officer
Anomaly: Inflight Event / Encounter CFTT / CFIT; Inflight Event / Encounter Weather / Turbulence
Detector: Automation Aircraft Terrain Warning
When detected: In-flight
Result: Flight Crew Took Evasive Action
Contributing factors: Airspace Structure; Chart Or Publication; Airport; Weather
Primary problem: Airspace Structure

Narrative: On the COTAL NORTH arrival in VMC we requested and received approval to descend to 1;700ft and direct to COTAL on the ILS DME 07 in MRLB. We were experiencing light to moderate turbulence at altitude and we decided that a lower altitude would provide the passengers a better ride. We were following the coast line over the water and descending. About 20 miles to the North of the airport there is a peninsula that extends further out from the coast line. We were fully aware of it and we had out EGPWS selected. We discussed it and our decision was to fly further west of it. The GPWS was two steps ahead. This triggered the GPWS terrain warning. We then climbed and turned to the right leaving the auto pilot on. The system worked as designed.


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


Synopsis: Air carrier flight crew reported the GPWS sounded an alarm as it was descending for an approach.
Date: 201808
Local time of day: 0001-0600
Location: ZZZ.Airport, US
Aircraft: Commercial Fixed Wing
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Flight phase: Parked
Reporter organization: Air Carrier
Reporter function: First Officer
Reporter qualification: Flight Crew Instrument; Flight Crew Air Transport Pilot (ATP); Flight Crew Multiengine
Anomaly: Deviation / Discrepancy - Procedural Hazardous Material Violation; Deviation / Discrepancy - Procedural Published Material / Policy; Deviation / Discrepancy - Procedural FAR
Detector: Person Flight Crew
When detected: Pre-flight
Result: General Maintenance Action
Contributing factors: Procedure
Primary problem: Procedure

Narrative: During preflight inspection of the HAZMAT container; I was unable to verify the contents of a box because it was packed in such a way that none of the packing labels were visible. Upon telling the DG Agent; she called her manager. He showed up and agreed that the label should be visible. He then released the netting enough so that we could verify the contents; and re-secured the cargo. The HAZMAT package was incorrectly oriented so that labels could not be seen during preflight inspection. The package could have been correctly oriented so that HAZMAT labels were visible during the preflight inspection.




Synopsis: B767 First Officer reported HAZMAT container content labels were obscured due to improper loading. DG Agent reloaded container to permit proper preflight inspection.
Date: 201604
Local time of day: 1201-1800
Location: ZZZ.Airport, US
Light: Daylight
Aircraft: A321
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)
Anomaly: Aircraft Equipment Problem Less Severe; 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: Aircraft Equipment Problem Dissipated
Contributing factors: Aircraft
Primary problem: Aircraft

Narrative: Upon rolling down the runway for takeoff an extremely heavy fuel smell permeated the cabin in all areas. It was so bad that we flight attendants felt nauseous; light headed and 2 of the 4 of us nearly passed out. [It] stayed very heavy all the way through the 10;000 foot climb. After that it began to subside. The cockpit also told us that they had the very heavy smell also. I know this cannot be healthy and upon discussing this with other flight crew; this is not an isolated event. I personally filed every report I could think of along with an injury on duty. I had headaches for several days following this event and didn't feel right in the head.




Synopsis: A321 Flight Attendant reported a very strong fuel smell as the aircraft accelerates for takeoff. The odor was detected by the flight crew as well; but began to diminish passing through 10;000 feet. Other Flight Attendants detected the odor and some felt nausea but the flight continued to destination.