elihoole/asrs-aviation-reports huggingface dataset:
Date: 201906
Local time of day: 0001-0600
Location: ZZZ.Airport, US
Aircraft: EMB ERJ 145 ER/LR
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Cruise
Aircraft component: Air Conditioning and Pressurization Pack
Component problem: Malfunctioning
Reporter organization: Air Carrier
Reporter function: Flight Attendant In Charge
Human factors: Situational Awareness; Troubleshooting; Communication Breakdown
Anomaly: Aircraft Equipment Problem Less Severe; Flight Deck / Cabin / Aircraft Event Smoke / Fire / Fumes / Odor
Detector: Person Flight Attendant; Person Flight Crew
When detected: In-flight
Result: Air Traffic Control Provided Assistance; Aircraft Equipment Problem Dissipated; Flight Crew Landed in Emergency Condition; Flight Crew Diverted; General Maintenance Action
Contributing factors: Aircraft
Primary problem: Aircraft

Narrative: At approximately XA:07 a bump was felt/heard by passengers. At XA:08 the passenger in XC got my attention and told me there was smoke filling the cabin. I investigated and noticed white smoke filling the cabin accompanied by the smell of burnt rubber. I told the CA and he asked me if I noticed a change. The smoke and smell both dissipated. He asked me to inform him if there were any changes. I returned to row 9 at approximately XA:11 to check on the passengers. I asked the passengers in rows 8 and 9 to let me know if they noticed any changes. I then returned to the galley to stow things away in the galley and prepare for landing. XA:20 the CA [Captain] informs me that we were continuing on to [destination] and that it was the closest airport and that he [notified ATC] to get emergency vehicles following us. I asked him if I needed to prepare the cabin for an emergency landing. He replied no; that won't be necessary; he is expecting a normal landing. He just wanted emergency vehicles following us just in case; so at the CA's direction I did not do the 12 steps to prepare the cabin for emergency landing. However after the CA made his PA to the passengers to inform them of our landing plans I followed with my own pa to reassure them and to prepare for a possible emergency landing. The CA called and asked to check in the area of row 9 after we landed to see if I noticed anything abnormal. XA:39 we landed safely in [destination] and I checked from the exit row to row 9 to look for anything unusual and I didn't find anything. The CA called to get my point of view report. I made a PA to the passengers letting them know that they may see emergency vehicles outside checking for abnormalities and that we were parked away from the gates for safety reasons. I told them if nothing was found we would continue on to the gates and get them on their way. About a minute later we were heading to the gates and deplaned without a problem. None of the passengers complained of any pain or discomfort and continued on their way after deplaning. According to the mechanic a PAC blew and that was the source of smoke and smell.




Synopsis: EMB-145 Flight Attendant reported Captain notification of smoke in the passenger cabin during flight.
Date: 201710
Local time of day: 1201-1800
Location: ZZZ.Airport, US
Flight conditions: IMC
Light: Daylight
Aircraft: Cessna 402/402C/B379 Businessliner/Utiliner
Operator: Air Taxi
Operating under: Part 135
Flight plan: IFR
Mission: Passenger
Flight phase: Initial Approach
Airspace: Class B ZZZ
ATC / advisory: TRACON ZZZ
Aircraft component: Instrument and Control Panels
Component problem: Malfunctioning
Reporter organization: Air Taxi
Reporter function: Single Pilot
Reporter qualification: Flight Crew Air Transport Pilot (ATP)
Anomaly: Aircraft Equipment Problem Critical; Flight Deck / Cabin / Aircraft Event Smoke / Fire / Fumes / Odor
Detector: Person Flight Crew
When detected: In-flight
Result: Air Traffic Control Provided Assistance; Aircraft Aircraft Damaged; Flight Crew Requested ATC Assistance / Clarification; Flight Crew Landed in Emergency Condition; Flight Crew Diverted; General Evacuated
Contributing factors: Aircraft
Primary problem: Aircraft

Narrative: At the time of the incident; I was at 5;000 ft on a downwind being vectored by Approach. I began setting up the ILS and reading the approach plate. I rolled the Captain overhead light switch on. The light did not turn on. I rolled it back thinking I had turned it the wrong way. No light came on. I rolled the Co-Pilot's overhead light on and began reading the approach plate. I began to smell a burning odor. I looked into the beam of the light and saw smoke coming into the cabin. I could not see where it was coming from. I performed Electrical Fire In-flight flow and turned off (gang-bar) the master switch row. The plane was completely dark. I looked up and saw a glow followed by fire flickering in the overhead panel by the Captain's roller switch. It appeared to be getting worse.I powered the master battery on; one radio and a transponder. I declared...'fire in flight' to Approach. I initiated a decent into [divert field] per their recommendation and vector. The fire burned for a minute and extinguished by itself when we were on final. I performed a short field landing and then a ground evacuation through the main cabin door onto the runway. Fire/Rescue and Airport Operations met us immediately and the aircraft was examined by the thermal imaging camera for several minutes after.




Synopsis: C402 pilot reported a fire in the overhead electrical panel that extinguished on final approach to a divert field.
Date: 202101
Local time of day: 0001-0600
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: Troubleshooting; Situational Awareness; Physiological - Other; Workload; Communication Breakdown
Anomaly: Deviation / Discrepancy - Procedural Published Material / Policy; Flight Deck / Cabin / Aircraft Event Passenger Misconduct
Detector: Person Flight Attendant
When detected: Pre-flight
Result: General None Reported / Taken
Contributing factors: Company Policy; Human Factors; Environment - Non Weather Related
Primary problem: Human Factors

Narrative: Saw Passenger X sitting in the gate house wearing a mesh mask. I pointed it out to the gate agent and he stated it's approved; because it covers her nose and mouth. But I stated; no; because it's see through and mesh. Masks have to be made of solid material.So thinking the gate agent would say something to her about the mask Passenger X boards the plane and takes her seat wearing her mesh mask. FWD Flight Attendant (FA) sees this and questions it and then calls me for a reference. I stated to her; I don't think it's an approved mask for flying; let me find it in the manual before going to Passenger X. While I'm trying to find it; FWD FA sends a message to the gate agent about Passenger X wearing this mesh mask.  FWD FA also informs the Captain as well. After searching under COVID section; I find it and inform FWD FA and the Captain that it's not approved and that I'll inform her that her mask is not compliant. I approach Passenger X about her mesh mask and also show her in manual that it's not compliant. Passenger X makes a statement that she's been allowed to wear it on her flights. I then read the mask compliance portion in the manual verbatim. She makes a little fuss about it and then states 'Fine; hand me a mask.' I tell her 'Thank you.' I head back up to the FWD part of the cabin; galley area to inform FWD FA and Captain we're good. Passenger X switched out her mask for one of our mask. Also show them both in the manual where it's located if there's ever any other issues that arise in the future. They can both reference. Also state to the gate agent that Passenger X mask is not approved.




Synopsis: Flight Attendant reported a passenger was required to remove a mesh face mask; while the Gate Agent did not agree; and use a company supplied mask before departure.
Date: 202005
Local time of day: 1201-1800
Location: ZZZ.Airport, US
Flight conditions: VMC
Weather elements / visibility: 10
Light: Daylight
Aircraft: SR22
Operator: Personal
Operating under: Part 91
Flight plan: None
Mission: Training
Flight phase: Taxi
Aircraft component: Nose Gear
Component problem: Failed
Reporter organization: Personal
Reporter function: Instructor; Pilot Not Flying
Reporter qualification: Flight Crew Multiengine; Flight Crew Flight Instructor; Flight Crew Commercial; Flight Crew Instrument
Anomaly: Aircraft Equipment Problem Critical
Result: Aircraft Aircraft Damaged; Flight Crew Took Evasive Action; General Flight Cancelled / Delayed; General Maintenance Action
Contributing factors: Aircraft
Primary problem: Aircraft

Narrative: After landing; during taxi to ramp in movement area; the airplane's front landing gear failed and collapsed resulting in the propeller striking the ground.  The mechanic on site indicated that the top of the front gear strut is prone to failing and sheering off.  He also said that inspection of the strut and specifically the top portion should be inspected as part of a normal annual inspection because stress cracks can occur over time in the part.  He suggested that failure in the top part of the front gear strut was responsible for the collapsed gear.  I am not qualified to determine the accuracy of the mechanic's diagnosis however it seemed plausible.




Synopsis: SR 22 pilot reported on taxi; the nose gear collapsed; damaging the aircraft.
Date: 201909
Local time of day: 0001-0600
Location: ZZZ.Airport, US
Flight conditions: VMC
Light: Night
Aircraft: Gulfstream V / G500 / G550
Operator: Fractional
Operating under: Part 91
Flight plan: IFR
Mission: Passenger
Flight phase: Initial Approach
Aircraft component: Gear Down Lock
Component problem: Malfunctioning
Reporter organization: Fractional
Reporter function: Captain; Pilot Not Flying
Reporter qualification: Flight Crew Air Transport Pilot (ATP)
Anomaly: Aircraft Equipment Problem Critical
Detector: Person Flight Crew
When detected: In-flight
Result: Air Traffic Control Provided Assistance; Flight Crew Executed Go Around / Missed Approach; Flight Crew Requested ATC Assistance / Clarification; Flight Crew Landed in Emergency Condition; General Flight Cancelled / Delayed; General Maintenance Action
Contributing factors: Aircraft
Primary problem: Aircraft

Narrative: When landing gear was extended the nose gear did not show a green light. A go-around was made and aircraft was vectored away from the airport while crew accomplished checklists related to gear failure to extend. An emergency gear extension was performed; and nose gear still did not show green. Other indications that the nose gear was not down and locked were present; including a report by the control tower that the nose gear appeared to be down but not locked. [We advised ATC]; and aircraft was landed successfully. After landing the gear was pinned; and aircraft was towed to the FBO.




Synopsis: Gulfstream 550 Captain reported nose gear did not indicate down and locked; causing a go-around and a precautionary landing.
Date: 202004
Local time of day: 1801-2400
Location: ZZZ.ARTCC, US
Aircraft: Any Unknown or Unlisted Aircraft Manufacturer
Operating under: Part 91
Flight plan: IFR
Mission: Training
Flight phase: Cruise
Airspace: Class E ZZZ
ATC / advisory: Center ZZZ
Second aircraft: Any Unknown or Unlisted Aircraft Manufacturer
Reporter organization: Government
Reporter function: Enroute
Reporter qualification: Air Traffic Control Fully Certified
Human factors: Workload; Distraction
Anomaly: ATC Issue All Types; Conflict Airborne Conflict; Deviation - Track / Heading All Types; Deviation / Discrepancy - Procedural Clearance
Detector: Person Air Traffic Control
When detected: In-flight
Result: Air Traffic Control Provided Assistance
Contributing factors: Procedure; Staffing; Human Factors; Environment - Non Weather Related
Primary problem: Human Factors

Narrative: During COVID-19 operations; I was very busy with sectors combined and a lot of aircraft in the ZZZ area with a large map range.  I just took the sectors over from the previous Controller and asked him to sit on my D Side to help me.  Aircraft X was a departure [out] of ZZZ1 and was level at 15;000 north out of ZZZ Approach airspace and Aircraft Y was a departure out of ZZZ to the west of Aircraft X climbing to 10;000. I originally climbed Aircraft Y to 14;000 under Aircraft X and I was very busy with sectors combined and a lot of aircraft in the ZZZ area with a large map range.  I observed that Aircraft Y was out in front of Aircraft X and climbed Aircraft Y with a turn on course to ZZZ2 to 17;000 due to other crossing traffic from the west. Aircraft Y was faster and wouldn't be an issue to climb. I continued to work the sector and noticed that the turn to ZZZ2 was [going to] bring the Aircraft together. I turned Aircraft X to zzz2 to help parallel the Aircraft and requested to Aircraft Y to report leaving 16;000 for standard separation. I believe I had 5 miles and 1;000 feet at the closest point.Smaller scale map would have helped viewing the traffic.




Synopsis: Center Controller reported that while working through COVID-19 Operations; they became very busy working combined sectors resulting in an airborne conflict.
Date: 202005
Local time of day: 0601-1200
Location: ZZZ.Airport, US
Weather elements / visibility: 10
Light: Daylight
Aircraft: Skylane 182/RG Turbo Skylane/RG
Operator: Personal
Operating under: Part 91
Flight plan: VFR
Mission: Training
Flight phase: Landing
ATC / advisory: Tower ZZZ
Reporter organization: Personal
Reporter function: Pilot Flying; Single Pilot
Reporter qualification: Air Traffic Control Fully Certified; Flight Crew Private
Human factors: Training / Qualification
Anomaly: Ground Event / Encounter Loss Of Aircraft Control
Detector: Person Flight Crew
When detected: Other landing roll
Result: Flight Crew Regained Aircraft Control
Contributing factors: Human Factors
Primary problem: Human Factors

Narrative: The situation took place as I touched down onto the runway. Directly after I touched down the aircraft sharply turned to the left; making it feel as though I had little control with the rudders in order to straighten out. The aircraft went off the side of the runway slightly; before correcting it back. I had initially believed I had a flat tire; because of the little control I was feeling with the rudder pedals. After having the aircraft inspected that did not seem to be the issue. I believe that I either accidentally partially pressed on the left brake instead of only rudder; or that my passenger may have accidentally stepped on the rudder while bracing for landing. This scenario seems most likely to me; as a sharp turn while landing would make it hard to regain control of the aircraft at the speed of landing roll. In order to prevent a recurrence; I would need to feel positively confident on my coordination while landing; and diligence on keeping clear of the brakes. Another thing I can do is to reiterate to my passenger before landing to keep hands and feet clear of the controls and pedals.




Synopsis: C182 pilot reported loss of directional control after landing that was probably related to the passenger depressing a rudder unintentionally.
Date: 201506
Local time of day: 1801-2400
Location: ZAU.ARTCC, IL
Flight conditions: IMC
Light: Daylight
Aircraft: EMB ERJ 145 ER/LR
Operator: Air Carrier
Flight plan: IFR
Mission: Passenger
Flight phase: Cruise
Airspace: Class A ZAU
ATC / advisory: Center ZAU
Aircraft component: Pitot/Static Ice System
Component problem: Malfunctioning
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: Aircraft Equipment Problem Less Severe; Inflight Event / Encounter Weather / Turbulence
Detector: Person Flight Crew
When detected: In-flight
Result: Flight Crew Overcame Equipment Problem
Contributing factors: Aircraft; Weather
Primary problem: Aircraft

Narrative: While working our way around thunderstorms that were near Chicago; we had pitot 2 freeze over in flight. We had no EICAS message indicating that we had a failure of the pitot heat. We had a CASS message indicating that there was a split in the airspeed. As we increased and decreased speed; the First Officer's indicated speed remained steady as the Captain and standby indicated speed matched. As we descended the First Officer showed a decrease in speed as we descended. We had a slight variation in altitude reading between the Captain and First Officer altimeter. As we descended below FL270 the ice apparently melted as the speed decreased to zero; followed by an increase to match the Captain and standby indicated speeds.The aircraft was never in a UAS as we controlled the plane by reference to the Captain and standby instruments.


Second narrative: While circumnavigating line of thunderstorms that passed through ORD area; we encountered high altitude icing accumulation (non ice detector detected) in IMC; causing pitot tube 2 to freeze and show incorrect information. At FL350; the PFD2 IAS comparison flag illuminated followed by gradual changes in PFD2 IAS conducive to altimeter type readings; (ie. no airspeed change with large power changes; and reduction of speed when descending). The indicator caused us to follow the QRH procedure which led us to inform ATC of the indication error and descend out of RVSM. Since the PFD 1 speed and ISIS (Integrated Standby Instrument System) indicated appropriately; the situation was nominal; as we were using data from pitot 1 and the CA/PF side. As in this incident the pitot 2 was the only frozen/failed tube; it resumed normal operation after descent into VMC and altitudes of approximately FL280-FL220 with additional increases of both SAT and TAT.


Synopsis: EMB-145LR flight crew reported pitot tube 2 iced up and showed incorrect information. Indications returned to normal when the flight descended into warmer temperatures.
Date: 202008
Local time of day: 1201-1800
Location: ZZZ.Tower, US
Flight conditions: VMC
Light: Daylight
Aircraft: EMB ERJ 170/175 ER/LR
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Final Approach; Initial Approach
Airspace: Class B ZZZ
ATC / advisory: Tower ZZZ
Reporter organization: Air Carrier
Reporter function: Captain; Pilot Not Flying
Reporter qualification: Flight Crew Multiengine; Flight Crew Air Transport Pilot (ATP); Flight Crew Instrument
Human factors: Situational Awareness; Confusion; Time Pressure
Anomaly: Deviation / Discrepancy - Procedural Published Material / Policy; Inflight Event / Encounter CFTT / CFIT; Inflight Event / Encounter Weather / Turbulence
Detector: Automation Aircraft Terrain Warning
When detected: In-flight
Result: Flight Crew Became Reoriented; Flight Crew Took Evasive Action; Flight Crew FLC complied w / Automation / Advisory
Contributing factors: Human Factors; Weather
Primary problem: Human Factors

Narrative: Our flight was going to ZZZ and prior to takeoff and en-route we were aware of the prevailing weather in ZZZ. The ATIS was showing 330@6 Vis 3/4; HZ; 003 OVC; 18/13; 3008 and using ILS RWY XXR. We briefed as normal and terrain was a mentioned as a threat and I had brought up my terrain map to help mitigate the threat. During decent ZZZ switched runways to the XY's due to VMC conditions east of the field allowing for visual approaches. We were following aircraft and were told to reduce speed. As we kept descending ZZZ1 came into view and I had mistakenly took this as ZZZ and called the field in site; ZZZ1 is more north of the terrain and at this point not a concern. We were cleared for the visual approach at this time and I realized that I had identified ZZZ1 instead of ZZZ as it came into view from under the marine layer. The Pilot Flying was still following the RNAV approach and was going from ZZZZZ to ZZZZZ1 but was hand flying and was still in a descent. We were handed off to tower and were cleared to land but wanted us to square our base to final for traffic ahead. I programed a straight in final in the FMS and the Pilot Flying started the turn but was still in a descent. I had noticed the Pilot Flying was getting low and then was immediately followed by a GRD PROX message. I instructed the Pilot Flying to level off which he did and then landed without incident. I had all terrain in site during the approach to landing. The cause of this event was due to the Pilot Flying not aware of the close proximity of the terrain as he kept a descent while squaring the base to final. Be fully aware and briefed of all possible threats including terrain in any phase of flight. Be ready to possibly take control of the aircraft or execute a go-around and in extreme situations climb-out of a CFIT situation.




Synopsis: Airline pilot reported receiving a Terrain Warning after preparing to land initially at the wrong airport.
Date: 201902
Local time of day: 1801-2400
Location: ZZZ.Airport, US
Light: Night
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: Takeoff / Launch
Airspace: Class B ZZZ
ATC / advisory: Tower ZZZ
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
Detector: Person Flight Attendant; Person Flight Crew; Person Passenger
When detected: In-flight
Result: Flight Crew Landed As Precaution; Flight Crew Returned To Departure Airport; General Maintenance Action
Contributing factors: Aircraft
Primary problem: Aircraft

Narrative: Late in the takeoff roll; experienced a few short minor shudders and slight lateral pull on nose. Very short in duration. Both pilots checked all engine indications which were all normal. After normal takeoff flight attendants quickly reported a burning rubber odor in cabin and said a passenger reported sparks coming out of left engine. [We] coordinated with ATC and returned for a precautionary landing. Fire crew checked aircraft on runway; everything appeared normal. Normal engine indications for entire flight; no warning or caution lights of any kind. Reported all to Maintenance with logbook entry.Unknown [cause] at this time; event reported to Maintenance.


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


Synopsis: MD-80 flight crew reported returning to departure airport after noting anomalies on the takeoff roll and receiving a report from a passenger of sparks from the left engine.