elihoole/asrs-aviation-reports huggingface dataset:
Date: 201811
Local time of day: 1801-2400
Location: ZZZ.ARTCC, US
Flight conditions: IMC
Light: Night
Aircraft: Super King Air 300
Operator: Air Carrier
Operating under: Part 135
Flight plan: IFR
Mission: Passenger
Flight phase: Cruise
Airspace: Class A ZZZ
ATC / advisory: Center ZZZ
Reporter organization: Air Carrier
Reporter function: First Officer; Pilot Not Flying
Reporter qualification: Flight Crew Instrument; Flight Crew Multiengine; Flight Crew Air Transport Pilot (ATP)
Anomaly: Aircraft Equipment Problem Less Severe; Flight Deck / Cabin / Aircraft Event Smoke / Fire / Fumes / Odor
Detector: Person Flight Crew
When detected: In-flight
Result: Flight Crew Diverted; Flight Crew Landed As Precaution
Contributing factors: Aircraft
Primary problem: Aircraft

Narrative: At cruise flight at FL260 there was a faint smoke smell. After querying with the PIC if it was just me; we confirmed that we both smelt it. Four passengers in the back also confirmed the smell and that it was from the back of the cabin. There were no indication of anything abnormal on any system; no warning or caution lights and no abnormalities in the pressurization or environmental systems. We ran memory items for electrical smoke and as the smell was from the back turned off the interior master switch. At this point we communicated with ATC our intent to divert due to a smoke smell and coordinated a diversion to [a nearby alternate]. The PIC was flying and I was Pilot Monitoring. I proceeded to pull and run the checklist for electrical smoke. There was never more than a fumes smell (prior to donning oxygen) and a slight haze in the aft cabin. In the descent we manually deployed the passenger oxygen. After getting configured and set up for the approach we landed uneventfully; stopped briefly on the runway and talked with [ground personnel] as they did a brief inspection prior to us taxiing to the ramp. With nothing more than a faint smell at this time we decided it would be safe to taxi to the ramp and shut down and deplane there. We talked with the [ground] personnel who checked over the plane and found nothing more than a faint smell at that time.




Synopsis: BE300 First Officer reported diverting to an alternate airport after noticing smoke odor in the aircraft.
Date: 201912
Location: ZZZ.Airport, US
Aircraft: Commercial Fixed Wing
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Taxi
Aircraft component: Cargo Door
Component problem: Improperly Operated
Reporter organization: Air Carrier
Reporter function: Ramp
Human factors: Communication Breakdown
Anomaly: Aircraft Equipment Problem Less Severe; Deviation / Discrepancy - Procedural Published Material / Policy
Detector: Person Ground Personnel
When detected: Aircraft In Service At Gate
Result: General Maintenance Action
Contributing factors: Company Policy; Procedure
Primary problem: Procedure

Narrative: Today I was working [on a] flight going to ZZZ. After finishing [up on] loading the bags; I went to close the cargo door which my Agent already [had done]. I asked the Captain to release the brake to get an on time departure to which he said no. I asked him why via headset; to which he replied [that] the door was showing open.I proceeded to the back and recycled the door. After the third time; I told the Captain to call Maintenance. [The] Captain's response was that Maintenance knows about it and was told that the Ramp may not know how to properly close the aircraft. I do these flights all day. The Supervisor came out to the gate and was able to close the door by a way that was not procedure; which was closing the vent door first [and] then the latch arm. I have attached the Company procedure to this report which indicates; latch arm closed and flush with aircraft door; then pull the vent close. This is a potential danger of a malfunction of the cargo door that could be catastrophic once aircraft is in the air.




Synopsis: Ground crew reported being unable to close a cargo door after several attempts and reported concerns about the procedure used by the Supervisor to close the door.
Date: 201405
Local time of day: 0601-1200
Location: ZZZ.ARTCC, US
Flight conditions: VMC
Weather elements / visibility: Turbulence
Light: Daylight
Aircraft: B737-300
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: First Officer
Human factors: Distraction; Physiological - Other; Time Pressure; Workload
Anomaly: Deviation - Altitude Excursion From Assigned Altitude; Deviation / Discrepancy - Procedural Clearance; Inflight Event / Encounter Loss Of Aircraft Control; Inflight Event / Encounter Weather / Turbulence
Detector: Person Flight Crew
When detected: In-flight
Result: Air Traffic Control Issued Advisory / Alert; Flight Crew Regained Aircraft Control; Flight Crew Returned To Clearance
Contributing factors: Weather
Primary problem: Weather

Narrative: At FL320 we encountered severe turbulence that caused loss of aircraft control. There no reports of turbulence in the area at the time. This resulted in an altitude deviation of approximately 600 FT. We informed ATC that we were descending to FL280. ATC asked if we were declaring an emergency and we informed them that we were not. ATC told us to maintain FL320 due to oncoming traffic. We regained control of the aircraft at approximately FL314 and climbed back to FL320. The turbulence was reported to ATC.




Synopsis: A B737-300 encountered severe turbulence. Unable to maintain altitude; the aircraft descended 600 FT before the pilots regained control and returned to FL320 for on coming traffic.
Date: 202105
Local time of day: 0601-1200
Location: ZZZ.Airport, US
Flight conditions: VMC
Weather elements / visibility: Clear
Light: Daylight
Aircraft: Sundowner 23
Operator: Personal
Operating under: Part 91
Flight plan: VFR
Mission: Training
Flight phase: Initial Approach
Airspace: Class D ZZZ
ATC / advisory: Tower ZZZ
Second aircraft: Any Unknown or Unlisted Aircraft Manufacturer
Reporter organization: FBO
Reporter function: Instructor; Pilot Flying
Reporter qualification: Flight Crew Flight Instructor; Flight Crew Commercial
Human factors: Workload; Situational Awareness
Anomaly: Conflict NMAC; Deviation - Track / Heading All Types; Deviation / Discrepancy - Procedural Published Material / Policy; Deviation / Discrepancy - Procedural Clearance
Detector: Person Flight Crew
When detected: In-flight
Result: Flight Crew Took Evasive Action
Contributing factors: Human Factors
Primary problem: Human Factors

Narrative: I was flying into ZZZ and was told enter left base for Runway XX. I acknowledged and had a student who was on their second flight and is nervous flying. I was trying to keep him calm and I got focused on landing Runway XY because ZZZ is always landing Runway XY. There was another plane in the right downwind for Runway XX and they had to go below me. With everything going on in and out of the plane at that time I was just going to the runway we always land on. I miss took Runway XX for Runway XY.




Synopsis: Sundowner Instructor reported an NMAC event during landing training.
Date: 201201
Local time of day: 1201-1800
Location: ZZZ.Airport, US
Light: Daylight
Aircraft: B737-300
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Taxi
ATC / advisory: Ground ZZZ
Aircraft component: Aileron
Component problem: Malfunctioning
Reporter organization: Air Carrier
Reporter function: Captain; Pilot Flying
Reporter qualification: Flight Crew Air Transport Pilot (ATP)
Human factors: Troubleshooting
Anomaly: Aircraft Equipment Problem Critical
Detector: Person Flight Crew
When detected: Taxi
Result: Flight Crew Returned To Gate; General Maintenance Action; General Flight Cancelled / Delayed
Contributing factors: Aircraft
Primary problem: Aircraft

Narrative: On taxi out; First Officer remarked that ailerons felt stiff and seemed to be binding as he conducted flight control check during his taxi flow. Captain conducted an aileron check; and he too thought that the ailerons felt abnormal. A 737 Check Airman conducting a line check on the flight also exercised the ailerons; and he too concurred that their movement did not feel normal. Yoke movement side to side was stiffer than normal; with a slight hitch at approximately the 3 degree position. Also; the yoke would not return to neutral position; stopping at same 3 degree position when released. Flight returned to gate. Dispatch and Maintenance were notified; Contract Maintenance was called out; problem could not be identified and resolved. Flight canceled and a heavy maintenance crew dispatched.




Synopsis: A B737 returned to the gate after the First Officer; Captain; and Check Airman determined that aileron flight control check was abnormal.
Date: 201910
Local time of day: 1201-1800
Aircraft: A330
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Initial Climb
Reporter organization: Air Carrier
Reporter function: Flight Attendant In Charge
Reporter qualification: Flight Attendant Current
Human factors: Physiological - Other
Second reporter function: Flight Attendant (On Duty)
Anomaly: Aircraft Equipment Problem Critical; 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 Crew; Person Flight Attendant; Person Passenger
When detected: In-flight
Result: Air Traffic Control Provided Assistance; Flight Crew Landed in Emergency Condition; Flight Crew Overcame Equipment Problem; Flight Crew Returned To Departure Airport; General Maintenance Action
Contributing factors: Aircraft
Primary problem: Aircraft

Narrative: Immediately upon rotation on take off out of ZZZ; intense fumes filled the cabin. Since it was safety related; I called the Captain under 10;000 feet.  He said he would get back with me shortly. When he contacted me; he stated we were returning to the gate and to do prepare the cabin for a normal routing landing back in ZZZ. The flight deck was on oxygen masks. Flight attendants passengers were having difficulty breathing from the intense fumes throughout the cabin. The oxygen masks should have been deployed to aid with the breathing difficulties we were having in the cabin. We were exposed to intoxicating fumes in the cabin and flight deck for approximately one hour. The oxygen masks should have been deployed in order to assist with breathing under these conditions.


Second narrative: On takeoff from ZZZ; heavy; dirty; greasy fumes were detected in cabin. Difficulty breathing; itchy sore throat; irritated eyes due to fumes. Captain  contacted all flight attendants saying that we were returning to ZZZ and to prepare for normal routine landing. Pilots were using oxygen mask. Flight attendants were using wet paper towels to cover nose and mouth in order to breath. This did not offer much protection from heavy toxic fumes. Passengers had cloths or hands over nose and mouth as well. Flight was met by paramedics. Crew was evaluated.  If pilots were on oxygen then flight attendants and passengers should also be on oxygen. From takeoff to arriving at gate back in ZZZ we were all exposed to heavy; dirty; greasy; acrid fumes for approximately 1 hour. That's a long time to breath these toxic fumes. Oxygen mask in cabin should have been deployed in my opinion.


Synopsis: A330 Flight Attendant crew reported to the pilots 'intense fumes' in cabin immediately after takeoff. Flight executed an uneventful return to departure airport.
Date: 201501
Local time of day: 1801-2400
Location: ZZZ.ARTCC, US
Flight conditions: VMC
Weather elements / visibility: CAVU; 10
Light: Night
Aircraft: Iroquois 212/214
Operator: Air Taxi
Operating under: Part 91
Flight plan: VFR
Mission: Ferry / Re-Positioning
Flight phase: Cruise
Airspace: Class G ZZZ
Second aircraft: Iroquois 212/214
Reporter organization: Air Taxi
Reporter function: Captain
Reporter qualification: Flight Crew Air Transport Pilot (ATP); Flight Crew Flight Instructor
Human factors: Communication Breakdown; Confusion; Situational Awareness
Anomaly: Conflict NMAC; Deviation / Discrepancy - Procedural FAR
Detector: Person Other Person
When detected: Other Post flight
Contributing factors: Human Factors
Primary problem: Human Factors

Narrative: While on a presumed non-revenue positioning flight with two BH-212s; after proper briefing and filing as a flight of two with Center; the two aircraft were operated within three rotor diameters for some photos. Two way radio communication was maintained at all times and no hazardous conditions were encountered.After the flight was complete; the PICs were advised that it was a revenue flight under part 135; making the formation flight a violation of FARs. No crew member was aware of this prior to the flight departure; Operator onsite manager failed to brief crews as to the status of the flight prior to departure; causing flight crews to believe they were on a non-revenue flight; and not subject to the for hire restrictions on formation flight; while carrying passengers.




Synopsis: Believing the flight was a non-revenue operation the pilots of two BH-212 helicopters departed as a flight of two and flew in formation for a period of time for photos.  They were later advised the flight was actually planned as a revenue flight thus making the formation flight a violation of FAR Part 135 restrictions.
Date: 201909
Local time of day: 1201-1800
Location: ZZZ.Airport, US
Flight conditions: VMC
Weather elements / visibility: 10
Light: Daylight
Aircraft: Citation Excel (C560XL)
Operator: Corporate
Operating under: Part 135
Flight plan: IFR
Mission: Passenger
Flight phase: Climb
Airspace: Class E ZZZ
ATC / advisory: TRACON ZZZ
Aircraft component: FMS/FMC
Component problem: Failed
Reporter organization: Corporate
Reporter function: Captain
Reporter qualification: Flight Crew Air Transport Pilot (ATP); Flight Crew Instrument; Flight Crew Multiengine
Human factors: Human-Machine Interface; Situational Awareness; Troubleshooting
Anomaly: Aircraft Equipment Problem Less Severe; Deviation - Altitude Excursion From Assigned Altitude; Deviation - Track / Heading All Types; Deviation / Discrepancy - Procedural Clearance; Deviation / Discrepancy - Procedural Published Material / Policy
Detector: Person Air Traffic Control; Person Flight Crew
When detected: In-flight
Result: Air Traffic Control Issued Advisory / Alert; Flight Crew Overcame Equipment Problem; Flight Crew Returned To Clearance
Contributing factors: Aircraft
Primary problem: Aircraft

Narrative: Upon climbout on the ZZZZZ departure; the aircraft's FMS dropped all data of the departure [and] the MFD went blank. The aircraft deviated from the published departure. There was never a terrain warning from the GPWS. Upon discovery of the deviation; I climbed the aircraft and corrected back onto the published departure as ATC was alerting us to climb and turn left on course. There was never a time where terrain was an issue. I corrected back to course as ATC contacted my aircraft.




Synopsis: C560XL Captain reported an FMS data drop and MFD failure; resulting in an altitude and heading deviation.
Date: 201304
Location: ZZZ.Tower, US
Flight conditions: VMC
Weather elements / visibility: 10
Light: Daylight
Aircraft: Beechcraft / Beech Aircraft Corp Undifferentiated or Other Model
Operator: Air Taxi
Operating under: Part 91
Flight plan: VFR
Mission: Cargo / Freight / Delivery
Flight phase: Climb
Airspace: Class D ZZZ; Class E ZZZ
ATC / advisory: Tower ZZZ
Aircraft component: Engine
Component problem: Malfunctioning
Reporter organization: Air Taxi
Reporter function: Captain; Pilot Flying; Single Pilot
Reporter qualification: Flight Crew Commercial; Flight Crew Instrument; Flight Crew Multiengine
Anomaly: Aircraft Equipment Problem Critical
Detector: Person Flight Crew
When detected: In-flight
Result: Aircraft Equipment Problem Dissipated; Flight Crew Returned To Departure Airport; General Declared Emergency
Contributing factors: Aircraft
Primary problem: Aircraft

Narrative: I was on climb out from the airport when; suddenly; the right engine began running rough. I immediately took action to recover the engine. The engine [stopped developing power]; so I put the mixture forward and turned the boost pump on. At that time I called the Tower and declared an Emergency. I then proceeded to turn the carb heat on and was going to attempt to restart the engine. Applying carb heat was sufficient to recover the engine and it started running rough again. While descending the engine began to run smoother. Upon landing; the engine was running and I terminated the emergency. I taxied in and had a Mechanic look at the engine.




Synopsis: A Beech 18 pilot declared and emergency and returned to the departure airport when the engine began to run rough and then quit developing power.  During the descent; upon applying carbuetor heat; the engine recovered.
Date: 201308
Location: LAX.Airport, CA
Flight conditions: VMC
Aircraft: B737 Undifferentiated or Other Model
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Descent
Aircraft component: MCP
Component problem: Improperly Operated
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: Deviation - Altitude Crossing Restriction Not Met; Deviation - Altitude Overshoot; Deviation / Discrepancy - Procedural Clearance; Deviation / Discrepancy - Procedural Published Material / Policy
Detector: Person Flight Crew
When detected: In-flight
Result: Flight Crew Returned To Clearance; Flight Crew Became Reoriented
Contributing factors: Human Factors; Procedure
Primary problem: Human Factors

Narrative: On the River Arrival; ATC wanted us to slow from 250 KTS to 210 KTS. The FP used Level Change to slow down as sometimes VNAV does not slow down quickly. The VNAV was not reengaged and we got low on the arrival.


Second narrative: On descent into LAX; ATC asked that we slow from high speed to 250 KTS. VNAV was doing a poor job of slowing the aircraft in a timely fashion. I selected level change and 250 KTS to speed the slowing. I announced that level change had been selected and that I would re-engage VNAV once we were on profile at 250 KTS. Additional approach duties ensued and I failed to re engage VNAV prior to next crossing restriction on the arrival. We descended below the crossing altitude at the next fix by 500-600 FT.


Synopsis: B737 flight crew reports getting low on the RIIVR 2 arrival into LAX when asked to slow. The MCP is switched from VNAV to level change and 250 set in the speed window to slow more rapidly and VNAV is not re-selected in a timely manor.
Date: 201911
Location: ZZZ.Airport, US
Aircraft: B737 Undifferentiated or Other Model
Operator: Air Carrier
Operating under: Part 121
Mission: Passenger
Flight phase: Parked
Aircraft component: Cargo Equipment
Component problem: Design
Reporter organization: Air Carrier
Reporter function: Ramp
Anomaly: Aircraft Equipment Problem Less Severe; Ground Event / Encounter Other / Unknown
Detector: Person Ground Personnel
Contributing factors: Aircraft
Primary problem: Aircraft

Narrative: Almost daily B737 aircraft arrive in ZZZ and we are unable to fully open the Forward cargo door as the baggage has slid on the door. ZZZ has a short runway and aircraft land with max brakes and reverse thrust. This causes the bags to fly forward into the cargo nets. Most often we find the cargo nets are secure and anchored but stretched over the door. Some bags break through the nets. This has happened for years now. Some occasions we are forced to go through the floor into the cargo hold which is a 2-3 hour job. We (the stations) have submitted numerous reports. No solution has been established to date. 3 employees have been injured attempting to open the door.I would suggest installing more anchor points to secure bags from shifting. Certainly would not [be] shifting weight during flight.




Synopsis: Ground Support personnel report that on B737 aircraft; cargo breaks through netting surrounding cargo door preventing it from being opened.
Date: 202003
Location: ORD.Airport, IL
Weather elements / visibility: Rain
Aircraft: Commercial Fixed Wing
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Taxi
Reporter organization: Air Carrier
Reporter function: Pilot Flying; Captain
Reporter qualification: Flight Crew Air Transport Pilot (ATP)
Human factors: Situational Awareness; Confusion
Anomaly: Conflict Ground Conflict; Less Severe
Detector: Person Flight Crew
When detected: Taxi
Result: Flight Crew Became Reoriented
Contributing factors: Airport
Primary problem: Airport

Narrative: Taxiing in last night; we were cleared in to the gate from the Southport on the Bravo line. It was snowing; but 34 degrees; so just wet; no snow sticking to the surface. Once we crossed the Alpha taxiway into the Southport; it was impossible to see the Bravo line. Neither my FO nor I could see the yellow taxi line. I stopped the taxi while we navigated where the line was and a de-ice truck drove by on our right hand side.  These taxi lines need to be repainted. This is a huge safety hazard as it could cause an aircraft accident.




Synopsis: Air carrier Captain reported ORD taxiway Bravo line should be repainted.