elihoole/asrs-aviation-reports huggingface dataset:
Date: 202002
Local time of day: 1801-2400
Location: ZZZ.Airport, US
Flight conditions: VMC
Aircraft: A320
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Initial Approach
Reporter organization: Air Carrier
Reporter function: First Officer; Pilot Not Flying
Reporter qualification: Flight Crew Instrument; Flight Crew Air Transport Pilot (ATP); Flight Crew Multiengine
Anomaly: Aircraft Equipment Problem Less Severe; Deviation / Discrepancy - Procedural Published Material / Policy; Flight Deck / Cabin / Aircraft Event Smoke / Fire / Fumes / Odor
Detector: Person Flight Attendant; Person Flight Crew
When detected: In-flight
Result: Flight Crew Landed As Precaution; General Maintenance Action
Contributing factors: Aircraft
Primary problem: Aircraft

Narrative: Find the source and stop the leaks. On descent into ZZZ; base to final; we had an extremely strong odor of engine oil in the cockpit. It smelled like sour dirty socks. It was so intense; almost 'thick' if you will. We donned our masks; turned off the packs; opened the ram air valve; and landed as we were approaching the final approach fix. No passenger reported any smell. The aft Flight Attendant reported a short faint smell.




Synopsis: A320 First Officer reported a strong odor of engine oil in the cockpit during initial approach and continued to landing at destination.
Date: 201412
Local time of day: 1201-1800
Location: ZZZ.Airport, US
Flight conditions: VMC
Light: Daylight
Aircraft: TBM 700/TBM 850
Operator: Personal
Operating under: Part 91
Flight plan: IFR
Mission: Personal
Flight phase: Final Approach
Airspace: Class E ZZZ
ATC / advisory: TRACON ZZZ
Reporter organization: Personal
Reporter function: Captain; Single Pilot
Reporter qualification: Flight Crew Instrument; Flight Crew Private
Human factors: Situational Awareness
Anomaly: ATC Issue All Types; Conflict Airborne Conflict
Detector: Automation Aircraft TA
Result: Air Traffic Control Issued Advisory / Alert; Air Traffic Control Issued New Clearance; Flight Crew Took Evasive Action
Contributing factors: Airspace Structure; Human Factors
Primary problem: Human Factors

Narrative: On the ILS 29R maybe about 1 mile from the FAF we observed a traffic conflict 2 miles out 12 o'clock same altitude on TCAD. We were on the radio with socal approach. We were looking for the traffic didn't see it visually. As the traffic alert sounded I initiated a climb. A few seconds later socal called with the conflict and asked for a rapid descent. I pushed the plane over into rapid descent following ATC instructions. We passed the traffic same altitude with 1/4 mile horizontal separation. I should have initiated the conflict resolution and climb and at the same time break into the busy frequency announce the climb for TA resolution. Following the ATC instructions actually made the situation much more dangerous.




Synopsis: TBM pilot experiences an airborne conflict at 1600 feet approaching the FAF for the ILS. TCAD had indicated the traffic and the reporter had started an evasive climb at the time TRACON/ATC called for a descent. The climb is reversed resulting passing co-altitude with a quarter mile separation.
Date: 201808
Local time of day: 0601-1200
Location: ZZZZ.Airport, FO
Light: Daylight
Aircraft: B737-800
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Taxi
ATC / advisory: Tower ZZZZ
Aircraft component: Pax Seat
Component problem: Malfunctioning
Reporter organization: Air Carrier
Reporter function: First Officer; Pilot Not Flying
Reporter qualification: Flight Crew Multiengine; Flight Crew Instrument; Flight Crew Air Transport Pilot (ATP)
Human factors: Communication Breakdown; Situational Awareness
Second reporter function: Pilot Flying; Captain
Anomaly: Aircraft Equipment Problem Less Severe; Deviation / Discrepancy - Procedural Published Material / Policy; Flight Deck / Cabin / Aircraft Event Smoke / Fire / Fumes / Odor
Detector: Person Flight Attendant
When detected: Taxi
Result: General Maintenance Action
Contributing factors: Aircraft
Primary problem: Aircraft

Narrative: While arriving [at the gate]; Number 3 FA (Flight Attendant) called and conveyed that there's smoke and fire at row 18; left side and that he is taking the extinguisher to it. I informed the Captain and he expedited our parking as I tried to contact the Tower for ARFF assistance. The Tower frequency was congested and after a few tries I got through. Tower called ARFF and after shutdown the Captain went to the back and by that time the smoke had already dissipated.Smoke had actually originated from under row 18; right side. By the time we parked passengers sitting nearby apparently had poured water onto the electronics box that was smoking. We deplaned normally and upon inspection by Maintenance and ARFF; it was concluded that no other components of the plane were affected. A seat power box was removed and had a strong electronic burning odor.


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


Synopsis: B737-800 flight crew reported that a Flight Attendant reported a fire under a passenger seat in the cabin.
Date: 201201
Local time of day: 1801-2400
Location: ZZZ.ARTCC, US
Light: Night
Aircraft: Dash 8-400
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Climb
Airspace: Class E ZZZ
ATC / advisory: Center ZZZ
Aircraft component: Exterior Pax/Crew Door
Component problem: Malfunctioning
Reporter organization: Air Carrier
Reporter function: Pilot Flying; First Officer
Reporter qualification: Flight Crew Commercial
Human factors: Distraction; Situational Awareness; Troubleshooting
Second reporter function: Captain; Pilot Not Flying
Anomaly: Aircraft Equipment Problem Less Severe
Detector: Person Flight Crew; Person Flight Attendant; Person Passenger
When detected: In-flight
Result: Flight Crew Returned To Departure Airport; Flight Crew Landed As Precaution; General Release Refused / Aircraft Not Accepted; General Maintenance Action
Contributing factors: Aircraft
Primary problem: Aircraft

Narrative: We made the decision to return to the departure airport. As we passed through 10;000 FT the Captain and I heard a loud hissing and vibrating sound that seemed to be coming from the cockpit escape hatch. The sound lasted only a few seconds and we promptly called by the Flight Attendants asking if they had heard the sound as well and how the passengers were doing. They told us that some of the forward passengers had heard noise and that it seemed to come from the Main Cabin door. At this point we had begun a descent back to 10;000 FT and slowed to 200 KTS. During the descent we checked the pressurization several times and it seemed to be holding the correct pressure. As the power was decreased for the descent and to slow down; we heard the noise again and could hear the packs surging as they adjusted for the new power setting. We referenced the QRH for the problem; but there was not a corresponding checklist. The Captain then called Maintenance and informed them of the situation and then called Dispatch through [a commercial radio service]. The Captain and Dispatch collectively decided that returning to the departure airport was the best course of action. No emergency was declared [but] Tower had chosen to dispatch the fire and rescue trucks as an additional precaution. We landed the aircraft without incident and returned to gate where the aircraft could be further inspected.


Second narrative: We did not suspect any structural damage or safety issues and thus did not declare an emergency; however the Tower out of precaution rolled the trucks (there was an emergency aircraft landing about 5 minutes after us). Swapped airplanes and arrived in our planned destination later that night.


Synopsis: A Q400 main cabin door developed a loud hissing noise and vibration at about 10;000 FT so the crew returned to the departure airport as a precaution although pressurization remained normal.
Date: 201808
Local time of day: 0601-1200
Location: ZZZ.ARTCC, US
Flight conditions: VMC
Weather elements / visibility: Windshear
Light: Daylight
Aircraft: Regional Jet 900 (CRJ900)
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Climb
Airspace: Class A ZZZ
ATC / advisory: Center ZZZ
Aircraft component: Hydraulic Main System
Component problem: Malfunctioning
Reporter organization: Air Carrier
Reporter function: Pilot Flying; First Officer
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 Less Severe; Inflight Event / Encounter Weather / Turbulence
Detector: Person Flight Crew
When detected: In-flight
Result: Air Traffic Control Provided Assistance; Flight Crew Landed in Emergency Condition; Flight Crew Returned To Departure Airport; Flight Crew Requested ATC Assistance / Clarification
Contributing factors: Aircraft; Weather
Primary problem: Aircraft

Narrative: During ATC assigned level off at FL320 we received Hyd 3 Lo Press and IB Ground Splrs cautions. Also displayed were several status messages regarding electrical ties. Captain took control of the aircraft and the radios and called for the Hyd 3 Lo Press QRH. Ran the QRH which only asked for 3b pump on and monitoring of system with sufficient pressure. No further action but we noticed Gen 2 was not operating properly. We [advised ATC] over being down to one generator and back up Hyd 3 pump. We started to return to ZZZ as quickly and safely as possible. We were faced with the added challenge of wind shear reported on 2 mile final as storms moved through the terminal area. On short final we got two instances of positive wind shear followed by a good landing.


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


Synopsis: CRJ-900 flight crew reported the loss of a hydraulic system and a generator resulted in a return to the departure airport.
Date: 201903
Local time of day: 0001-0600
Location: ZZZ.Airport, US
Aircraft: A330
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Taxi
ATC / advisory: Ramp 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 Smoke / Fire / Fumes / Odor; Flight Deck / Cabin / Aircraft Event Illness / Injury
Detector: Person Flight Attendant
When detected: Taxi
Result: Flight Crew Returned To Gate; General Maintenance Action; General Flight Cancelled / Delayed
Contributing factors: Aircraft
Primary problem: Aircraft

Narrative: There were issues with the APU and the batteries on the aircraft. We had already boarded and deplaned once before due to not having any power on the aircraft; no lighting; etc. We re-boarded the plane as soon as the batteries were charged and we had cabin lighting back. We finished boarding; closed the door and started the safety video. As we were starting the pushback and the safety video was still playing; several of us started smelling a strong chemical burning smell fill the cabin. Also a haze was in the cabin. We immediately contacted the flight deck. The smell and haze was throughout the entire aircraft. The Captain decided to stop pushback and return to the gate and instructed the flight attendants to perform an emergency deplaning as soon as the jetway was attached. The Captain as well as the flight attendants made several announcements instructing passengers off the aircraft. Once all passengers had deplaned; we deplaned onto the jetway. The fire department and mechanics immediately boarded the aircraft. The flight attendants then asked to be seen by the paramedics; due to eye and throat irritation. We were all dizzy and feeling nauseated. We did not wish to be taken to the emergency room.




Synopsis: A330 Flight Attendant reported notifying the Captain of burning smell in the cabin during pushback for departure.
Date: 202011
Aircraft: Commercial Fixed Wing
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Other unknown
Reporter organization: Air Carrier
Reporter function: Flight Attendant (On Duty)
Reporter qualification: Flight Attendant Current
Human factors: Workload; Communication Breakdown; Physiological - Other
Anomaly: Deviation / Discrepancy - Procedural Published Material / Policy; Flight Deck / Cabin / Aircraft Event Passenger Misconduct
Detector: Person Flight Attendant
When detected: Other unknown

Narrative: Passenger A had to be told several times to please wear his mask.  The last time I asked him; he was playing with his cell phone; was NOT chewing anything and shook an empty chip bag at me; telling me twice that he was eating.  Well; he was not.  I learned later he had connected that day from ZZZ; a hot zone.  I guess Passenger A felt that he was exempt from wearing a mask on board.




Synopsis: Flight Attendant reported a passenger would not comply with face mask policy.
Date: 201512
Local time of day: 0601-1200
Location: VGT.Airport, NV
Flight conditions: VMC
Light: Daylight
Aircraft: Small Aircraft
Operator: Personal
Operating under: Part 91
Flight plan: IFR
Mission: Personal
Flight phase: Initial Climb
Airspace: Class E L30
ATC / advisory: TRACON L30
Reporter organization: Personal
Reporter function: Single Pilot; Pilot Flying
Reporter qualification: Flight Crew Flight Instructor; Flight Crew Instrument; Flight Crew Commercial
Human factors: Confusion; Situational Awareness; Communication Breakdown
Anomaly: ATC Issue All Types; Deviation - Track / Heading All Types; Deviation / Discrepancy - Procedural Published Material / Policy; Deviation / Discrepancy - Procedural Clearance
Detector: Person Air Traffic Control
When detected: In-flight
Result: Air Traffic Control Issued New Clearance
Contributing factors: Procedure; Airspace Structure
Primary problem: Ambiguous

Narrative: On the VMC day; there was confusion over the SID; the verbal clearance received was the NOTWN4. The clearance showing in the ATC computer was RTTRN2 per Flightaware.com (discovered later). I noted that the RTTRN2 SID was not approved for the assigned runway. There was some confusion between LAS TRACON and VGT Tower as the release was delayed to the point that I told the Tower I was considering cancelling the IFR clearance and departing VFR west under the Bravo. They then said that the release was about ready; I waited. As soon as I departed 30L and contacted departure I received an urgent (ATC voice tension) turn 090 and expedited climb to 7;000 which was my initial altitude assigned. I was just beginning my turn to a track of 313 to RUZCO and continued the climb to 7;000 as vectored. One misjudgment on my part was that I was depending on the GPS route to RUZCO and had not set the 313 radial off LAS and the moving map display was set to a larger than optimal range so the track was not very visible. My suggestion would be to change the NOTWN4 for a straight out departure to intercept the 313 off LAS. RTTRN2 should remain unchanged unless the airspace NE of VGT could be utilized for the SID from R7; 12R and 12L.

Callback: The initial problem was a departure clearance issued not appropriate for the runway. Once that was worked out; and the departure initiated; the departure (TRACON) Controller modified the turn off the expected radial; possibly to avoid airspace or traffic for LAS.



Synopsis: A general aviation pilot reported ATC issues prior to release; and then after takeoff from North Las Vegas airport.
Date: 201502
Local time of day: 0601-1200
Location: ZZZ.Airport, US
Light: Daylight
Aircraft: HS 125 Series
Operator: Fractional
Operating under: Part 91
Flight plan: IFR
Mission: Ferry / Re-Positioning
Flight phase: Parked
ATC / advisory: Ramp ZZZ
Aircraft component: Wing Attachment
Component problem: Malfunctioning
Reporter organization: Fractional
Reporter function: Captain; Pilot Flying
Reporter qualification: Flight Crew Air Transport Pilot (ATP)
Human factors: Situational Awareness; Communication Breakdown; Troubleshooting
Anomaly: Aircraft Equipment Problem Less Severe; Deviation / Discrepancy - Procedural Published Material / Policy
Detector: Person Flight Crew
When detected: Pre-flight
Result: Flight Crew Took Evasive Action; General Maintenance Action; General Flight Cancelled / Delayed
Contributing factors: Aircraft; Procedure; Company Policy
Primary problem: Aircraft

Narrative: We airlined to an airport to pick up an airplane for a reposition for a PAX [passenger] trip. On prefight readily apparent was corrosion on the majority of the screws on top of the wing; dozens if not hundreds. I have never seen corrosion this bad. On many of the screws the corrosion extended past the screw heads. After sending Maintenance Control pictures and discussing it with them I decided to have the plane evaluated for safety and regulatory compliance reasons. The next day I received a call from my Chief Pilot saying that this had turned into a big issue since this was done right before a pax trip. Not that that should matter; but it is also false. He said that I should expect to receive a request for a written report. He had seen the pictures and agreed it was horrendous. I don't know how to interpret this in any fashion other than blatant intimidation to not write up discrepancies.




Synopsis: An HS-125-800 Captain found and reported multiple corroded screws on his aircraft upper wing surface. His Chief pilot was unhappy with the Captain because his action affected the aircraft's availability.
Date: 201903
Local time of day: 0601-1200
Location: ZZZ.Airport, US
Flight conditions: VMC
Aircraft: B737 Undifferentiated or Other Model
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Climb
Aircraft component: Fuel Tank
Component problem: Malfunctioning
Reporter organization: Air Carrier
Reporter function: Pilot Flying; Captain
Reporter qualification: Flight Crew Multiengine; Flight Crew Instrument; Flight Crew Air Transport Pilot (ATP)
Second reporter function: First Officer; Pilot Not Flying
Anomaly: Aircraft Equipment Problem Less Severe; Flight Deck / Cabin / Aircraft Event Smoke / Fire / Fumes / Odor; Flight Deck / Cabin / Aircraft Event Illness / Injury
Detector: Person Flight Crew; Person Flight Attendant
When detected: In-flight
Result: Air Traffic Control Provided Assistance; Flight Crew Landed in Emergency Condition; Flight Crew Diverted
Contributing factors: Aircraft
Primary problem: Aircraft

Narrative: During climbout of ZZZ; Flight Attendant (FA) called and said there was a fuel odor in the cabin. Shortly after that the FAs called and said a passenger had gotten sick. At that point we [notified ATC]; informed ATC that we wanted to divert to ZZZ1. We called ZZZ1 station OPS and informed them that we were diverting to ZZZ1. On approach the FAs informed us that the smell had diminished. Approach and landing (overweight) was uneventful. Emergency equipment met the aircraft as we taxied clear of [runway]. The Emergency Crew Captain wanted to deplane while the aircraft was still on the taxiway. We asked them to walk around the plane and if they saw any leak we would deplane on the taxiway. They saw no leaks so we taxied to gate and waited for marshallers to arrive to marshal us to the gate. After parking at the gate; Maintenance informed us that there was a fuel leak from the center fuel tank.


Second narrative: [Report narrative contained no additional information]


Synopsis: B737 flight crew reported fuel odor in cabin and resulting passenger illness.
Date: 202003
Aircraft: A321
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Flight phase: Takeoff / Launch
Airspace: Class B ZZZ
ATC / advisory: Tower ZZZ
Aircraft component: Pneumatic System
Component problem: Malfunctioning
Reporter organization: Air Carrier
Reporter function: Pilot Flying; Captain
Reporter qualification: Flight Crew Multiengine; Flight Crew Air Transport Pilot (ATP); Flight Crew Instrument
Human factors: Workload
Second reporter function: First Officer; Pilot Not Flying
Anomaly: Deviation / Discrepancy - Procedural Published Material / Policy; 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 Landed in Emergency Condition; Flight Crew Requested ATC Assistance / Clarification; Flight Crew Returned To Departure Airport; Flight Crew Overcame Equipment Problem; General Maintenance Action
Contributing factors: Aircraft
Primary problem: Aircraft

Narrative: On departure my First Officer and I both noticed an acrid dirty sock smell. [We advised ATC]. We donned our O2 masks and executed a return to field. I transferred the controls to the First Officer; he worked the radios and flew while I ran as much of the checklist as possible prior to landing. I was unable to complete the diagnostic portion due to our proximity to the airport and needed to prepare for landing. We were fully configured 80 ft. low but due to the [situation] we elected to continue. Upon landing we removed our o2 masks noticed the smell remained. I shut the packs off and opened our windows. All in all I was fairly pleased with our performance in such a compressed time table. General observations. Communicating through the o2 mask is more difficult than anticipated. ATC obviously asks their required questions. If we have our interphone selected to facilitate coms between us; it makes it impossible to hear ATC. If we use the interphone in PTT mode it makes communication between us more difficult. The fumes were isolated to the flight deck. Suggestions: The QRH guidance for SOF event is complicated. With tons of great information for diagnosing a problem. The issue in our case was the compressed timeframe of this event. It would perhaps be wise to design a separate checklist for SOF on departure. That isolates the most important systems; and most probable failure points. Then defers to the longer checklist with time permitting. Obviously landing an airplane experiencing SOF is a higher priority than fighting the fumes. In our 11 minutes of flight time it was impossible to run the entire checklist; as well as the standard procedures; and execute a return to field. This necessitated prioritization of tasks and load shedding. In retrospect I should have completed the remaining checklist after landing. However isolating the packs and opening the windows cleared the smell. So we merely returned to gate.


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


Synopsis: A321 flight crew reported that a fumes event on takeoff resulted in a return to the departure airport.