elihoole/asrs-aviation-reports huggingface dataset:
Date: 201711
Local time of day: 1201-1800
Location: ZZZ.Airport, US
Flight conditions: VMC
Light: Daylight
Aircraft: Light Sport Aircraft
Operator: FBO
Operating under: Part 91
Flight plan: None
Mission: Training
Flight phase: Cruise
ATC / advisory: TRACON ZZZ
Aircraft component: Engine
Component problem: Malfunctioning
Reporter organization: FBO
Reporter function: Instructor; Pilot Flying
Reporter qualification: Flight Crew Flight Instructor; Flight Crew Instrument; Flight Crew Multiengine; 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 Diverted; Flight Crew Landed in Emergency Condition
Contributing factors: Aircraft
Primary problem: Aircraft

Narrative: During flight instruction a noticeable engine roughness occurred. The flight was conducted under VFR and utilizing Flight Following. I immediately turned on carburetor heat to no avail and turned back toward ZZZ (airport of operations) that was about 17 nm distant.  By adjusting the throttle; rpm was kept at cruise setting and roughness stopped.  After approximate 8 miles of flight the roughness returned and would not subside.  I notified The Approach controller of the situation and asked for an expedited path to the closest airport. He cleared me direct ZZZ1 and asked [about] souls and fuel on board; with two souls and 3 hours fuel. He then switched me to ZZZ1 tower who cleared me to land.  The approach to runway was uneventful with the engine running rough but producing more than adequate power.  The landing was uneventful and taxied to the FBO without incident.




Synopsis: LSA pilot reported a loss of engine performance that led to a diversion and a successful landing.
Date: 202007
Aircraft: No Aircraft
Reporter organization: Air Carrier
Reporter function: Other / Unknown
Anomaly: No Specific Anomaly Occurred All Types
Detector: Person Other Person
Result: General None Reported / Taken
Contributing factors: Company Policy; Environment - Non Weather Related
Primary problem: Company Policy

Narrative: Since last week there is not enough alcohol gel available at office for employees (everyone has to bring it from home) to keep us safe. Also; there is no water bottles available for employee's hydration in every operation. We are working X type flights and since COVID-19 situation is getting worst we need to have safety tools like alcohol gels or liquid alcohol to sanitize the work areas to give a good customer service and provided customers a safety area.




Synopsis: Ground employee reported there is not enough alcohol gel available in the office for employees to use during the COVID-19 pandemic.
Date: 201506
Local time of day: 1801-2400
Location: ZZZ.Airport, US
Flight conditions: VMC
Light: Daylight
Aircraft: B737 Next Generation Undifferentiated
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Parked
Reporter organization: Air Carrier
Reporter function: Captain
Reporter qualification: Flight Crew Air Transport Pilot (ATP)
Human factors: Situational Awareness
Second reporter function: First Officer
Anomaly: Deviation / Discrepancy - Procedural Security; Deviation / Discrepancy - Procedural FAR; Flight Deck / Cabin / Aircraft Event Smoke / Fire / Fumes / Odor; Flight Deck / Cabin / Aircraft Event Passenger Misconduct; Ground Event / Encounter Other / Unknown
Detector: Person Ground Personnel
When detected: Aircraft In Service At Gate
Result: Flight Crew Took Evasive Action; General Police / Security Involved; General Maintenance Action; General Flight Cancelled / Delayed
Contributing factors: Human Factors
Primary problem: Human Factors

Narrative: The Agent came and told me that a Ramp Agent found a small checked duffle bag smoking as it was coming up the belt loader; and that he threw it on the ramp before it got into the cargo compartment. A Ramp Supervisor found stick matches in a bundle next to the striker strip in a baggie. The matches had apparently struck the striker strip and had started to burn. I called Dispatch and the Safety Officer was listening in. The Chief Pilot on Call was notified by the Dispatcher. The CSS had the Passenger who owned the bag come off the aircraft to discuss the matter and then the CSS let him return to his seat. The Agent notified the TSA Official and the Local Police. I had Maintenance come out and check the cargo compartment door frame and he found no damage. The Ramp Supervisor took the bag to an office to document it for his report. The Police then took custody of the bag and pulled the Passenger from the flight so that they could continue their investigation (I believe he was accommodated on the next XXX flight). I had more fuel put on the aircraft and the Dispatcher affirmed our departure to XXX. We departed without further complication. I failed to brief the Passengers in a timely manner due to the complexity of the situation. I believe we made three PA's but after the first 20 to 25 minutes after the departure time. The Ramp Agent saved our Company a lot of money; let alone the lives of 144 people.As far as the smoking bag; I am glad our Ramp Personnel are watching out for us. As for keeping our Passengers informed every 15 minutes; I will try to be more diligent.


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


Synopsis: A Ramp Agent loading bags in a B737 noticed smoke from a bag on a belt loader before it entered the Cargo Compartment; threw the bag on the ramp; and notified the Captain. The smoke's source was stick matches next to a striker pad ignited within a baggie.
Date: 201912
Local time of day: 0601-1200
Location: ZZZZ.ARTCC, FO
Flight conditions: VMC
Light: Daylight
Aircraft: B757-200
Operator: Air Carrier
Operating under: Part 91
Flight plan: IFR
Mission: Ferry / Re-Positioning
Flight phase: Climb
ATC / advisory: Center ZZZZ
Aircraft component: Pressurization System
Component problem: Malfunctioning
Reporter organization: Air Carrier
Reporter function: Check Pilot; Pilot Flying
Reporter qualification: Flight Crew Air Transport Pilot (ATP); Flight Crew Instrument; Flight Crew Multiengine
Anomaly: Aircraft Equipment Problem Critical; Inflight Event / Encounter Fuel Issue
Detector: Person Flight Crew
When detected: In-flight
Result: Flight Crew Returned To Departure Airport
Contributing factors: Aircraft
Primary problem: Aircraft

Narrative: We were ferrying [an] aircraft. We knew that this aircraft had previous issues with pressurization on other recent occasions. On climbout everything looked normal. Rate of climb was approximately 200 [and the] cabin differential looked normal. After crossing FL300; we received a CABIN ALT warning and EICAS message. We performed the memory items and asked for a descent to FL250 where the cabin was still at 15;000 so we continued the descent to FL230 where the cabin started to come back to 10;000 and stabilize.After the QRH was completed we wrote numerous messages to [the] Company asking for new fuel burn numbers at the lower altitude. We had a Mechanic on board [and] we asked him his opinion on everything or if he had a different way to look at things. He agreed with our assessments. While waiting; we checked the oxygen tables to make sure we had enough oxygen for our plan; in which we did. We had planned to wait to hear from [the] Company before making a decision. We then changed the step climb in the FMC in case the new numbers were okay to continue and we would not be able to step climb anymore; to which we received a message of insufficient fuel and showed us landing with 10.2 in ZZZ. At that time; we asked to return to ZZZZ and requested priority handling. We then made it back to ZZZZ with no further issues.




Synopsis: B757-200 pilot reported ferrying an aircraft where a previously known issue reappeared; resulting in a return to the departure airport.
Date: 201310
Local time of day: 1801-2400
Location: SCT.TRACON, CA
Aircraft: A320
Operator: Air Taxi
Operating under: Part 121
Flight plan: IFR
Flight phase: Initial Climb
ATC / advisory: TRACON SCT
Second aircraft: Regional Jet 900 (CRJ900)
Reporter organization: Government
Reporter function: Other / Unknown
Anomaly: ATC Issue All Types; Conflict Airborne Conflict; Deviation / Discrepancy - Procedural Published Material / Policy
Detector: Person Air Traffic Control
Result: General None Reported / Taken
Contributing factors: Human Factors
Primary problem: Human Factors

Narrative: I was working another sector when I saw this happen and I talked to the RADAR controller involved. I thought it was very very dangerous and I was shocked that it happened so that's why I'm filing a report. LAX Tower cleared an A320 routed south of the north complex runways for a departure into the Manhattan RADAR (MANR) Sector. MANR has control to turn this aircraft and climb them. About the same time maybe a 1/2 mile offset; a CRJ-900 routed north was coming off the south complex. These aircraft have to swap out. MANR was never advised about the CRJ-900 and even though the CRJ-900 was instructed to maintain visual separation; MANR had no idea who that aircraft was. Ninety Five percent of the time a departure off the north complex is immediately issued a south bound heading. In this case the controller waited wondering who this unknown target was (CRJ-900). Had MANR done the norm; and turned the A320 south; there not only would have been an ugly loss of separation but a potential MID-AIR collision. The CRJ-900 would have freaked out if the A320 had turned. Dangerous and Scary! Recommendation; training to LAX Tower on the proper use of Visual Separation; requirements to inform Departure Sector of aircraft using visual and stopped at lower altitude.




Synopsis: SCT Controller observed a conflict event involving two air carrier aircraft departing LAX; the north complex aircraft routed south and a south complex aircraft routed north.
Date: 201711
Local time of day: 1201-1800
Location: SAN.Airport, CA
Flight conditions: VMC
Light: Daylight
Aircraft: Falcon 2000
Operator: Corporate
Operating under: Part 91
Flight plan: IFR
Mission: Passenger
Flight phase: Initial Approach
Airspace: Class B SAN
ATC / advisory: TRACON SCT
Second aircraft: A320
Reporter organization: Corporate
Reporter function: Pilot Not Flying
Reporter qualification: Flight Crew Air Transport Pilot (ATP); Flight Crew Flight Instructor
Anomaly: Inflight Event / Encounter Wake Vortex Encounter
Detector: Person Flight Crew
When detected: In-flight
Result: Flight Crew Requested ATC Assistance / Clarification; Flight Crew Took Evasive Action
Contributing factors: Environment - Non Weather Related; Procedure
Primary problem: Ambiguous

Narrative: Descending via the LYNDI FOUR into SAN our aircraft encountered two wake upsets from [an] A320.  Aircraft bank angle was approximately 35 degrees.  After second event we queried ATC on our in trail distance and were told '5 miles behind A320.'  We adjusted VNAV descent to fly above published path to avoid further encounters in A320 wake.




Synopsis: Falcon 2000 pilot reported encountering wake turbulence 5 miles in trail of an A320 on approach into SAN.
Date: 202012
Local time of day: 1201-1800
Location: ZZZ.ARTCC, US
Aircraft: Small Transport
Operator: Personal
Operating under: Part 91
Flight plan: IFR
Mission: Personal
Flight phase: Cruise
Airspace: Class E ZZZ
ATC / advisory: Center ZZZ
Reporter organization: Government
Reporter function: Enroute
Reporter qualification: Air Traffic Control Developmental
Human factors: Confusion; Situational Awareness; Training / Qualification
Anomaly: ATC Issue All Types; Deviation / Discrepancy - Procedural Clearance; Inflight Event / Encounter CFTT / CFIT
Detector: Automation Air Traffic Control; Person Air Traffic Control
When detected: In-flight
Result: General None Reported / Taken
Contributing factors: Airspace Structure; Human Factors
Primary problem: Human Factors

Narrative: [Aircraft X] was on an IFR flight to ZZZ1 on [Airway1] at 9;000 ft. There was another aircraft on [Airway2] also landing ZZZ1 just handed off to me also at 9;000 ft. The adjacent sector asked me if I would like [Aircraft X] at a different altitude and I gave them 8;000 ft.; which they complied with. Upon further review that was below the Minimum Vectoring Altitude of 8;600 ft. and [Airway2]'s Minimum IFR Altitude of 8;400 ft. I should have been more aware of the Minimum IFR Altitudes along [Airway2].




Synopsis: A Center Developmental reported they issued a control instruction to an aircraft through another controller that placed it below the Minimum Vectoring Altitude and Minimum IFR Altitude.
Date: 201712
Local time of day: 0601-1200
Location: GEO.Airport, OH
Flight conditions: VMC
Weather elements / visibility: 10
Light: Daylight
Aircraft: Skyhawk 172/Cutlass 172
Operator: FBO
Operating under: Part 91
Flight plan: None
Mission: Training
Flight phase: Landing
Airspace: Class G GEO
ATC / advisory: CTAF GEO
Reporter organization: Personal
Reporter function: Observer
Reporter qualification: Flight Crew Instrument; Flight Crew Flight Instructor; Flight Crew Commercial
Human factors: Training / Qualification
Second reporter function: Single Pilot; Pilot Flying
Anomaly: Ground Event / Encounter Loss Of Aircraft Control; Ground Event / Encounter Object
Detector: Person Flight Crew; Person Observer
When detected: In-flight
Result: Flight Crew Regained Aircraft Control
Contributing factors: Human Factors
Primary problem: Human Factors

Narrative: Student on solo flight had slight loss of control after a bounced landing and went off the runway and struck a runway light.


Second narrative: Came in on final too high and too fast. Bounced on touchdown and veered off left of center and struck a runway light.


Synopsis: A Flight Instructor and student reported that the stundent lost control of the aircraft during landing.
Date: 201512
Local time of day: 1201-1800
Location: ZZZ.ARTCC, US
Flight conditions: IMC
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
ATC / advisory: Center ZZZ
Reporter organization: Air Carrier
Reporter function: Captain; Pilot Flying
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 Diverted; Flight Crew Landed As Precaution; Flight Crew Landed in Emergency Condition
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 [advised] 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 at [a nearby alternate]; and to follow the instructions of the crewmembers.We descended and landed normally; and we had Crash Fire Rescue (CFR) inspect the exterior of the aircraft. The CFR 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 CFR 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 CFR continuously standing by and monitoring.More effective aircraft maintenance and inspection procedures.




Synopsis: MD-80 Captain reported diverting to a nearby alternate airport when the cabin crew reported noticing heat on the walls and floor of the aircraft. After landing; Crash Fire and Rescue (CFR) reported heat signatures in the aft cargo compartment.
Date: 201205
Local time of day: 0601-1200
Location: ZZZ.ARTCC, US
Flight conditions: VMC
Light: Daylight
Aircraft: Learjet 45
Operator: Air Taxi
Operating under: Part 135
Flight plan: IFR
Mission: Passenger
Flight phase: Cruise
Airspace: Class A ZZZ
ATC / advisory: Center ZZZ
Aircraft component: Turbine Engine
Component problem: Malfunctioning
Reporter organization: Air Taxi
Reporter function: Captain
Reporter qualification: Flight Crew Air Transport Pilot (ATP)
Anomaly: Aircraft Equipment Problem Critical
Detector: Person Flight Crew
When detected: In-flight
Result: Flight Crew Diverted; General Declared Emergency
Contributing factors: Aircraft
Primary problem: Aircraft

Narrative: Declared emergency and landed after receiving 'L OIL PRESS LOW' red CAS message. Landed safely [at nearby airport] without incident.




Synopsis: A LR45 Captain reported receiving 'L OIL PRESS LOW' CAS message.  He declared an emergency and landed safely at a nearby airport.
Date: 202011
Local time of day: 1201-1800
Location: ZZZ.Airport, US
Flight conditions: VMC
Weather elements / visibility: 50
Light: Daylight
Aircraft: Skylane 182/RG Turbo Skylane/RG
Operator: Personal
Operating under: Part 91
Mission: Personal
Flight phase: Taxi
Airspace: Class G ZZZ
ATC / advisory: CTAF ZZZ
Second aircraft: Cessna 150
Reporter organization: Personal
Reporter function: Single Pilot
Reporter qualification: Flight Crew Commercial; Flight Crew Instrument
Human factors: Communication Breakdown; Situational Awareness; Training / Qualification
Anomaly: Conflict NMAC; Deviation / Discrepancy - Procedural FAR; Deviation / Discrepancy - Procedural Published Material / Policy
Detector: Person Observer
Result: Flight Crew Took Evasive Action
Contributing factors: Human Factors
Primary problem: Human Factors

Narrative: Our aircraft had just landed at ZZZ when a single-seat aerobatic biplane began to do low-level aerobatics (hammerheads and rolls) opposite normal traffic in the pattern. A Cessna 150 entered left downwind Runway XX; well spaced from the biplane; which was in a modified right downwind/base; when the biplane crossed the field and entered a midfield left crosswind-to-downwind behind the 150. The 150 continued downwind; turned base then final; when the biplane banked hard from downwind directly to final abeam the 150 and approximately 25 feet above. The 150 initiated a go-around and the biplane did the same; nearly colliding which each other. The 150 eventually landed on a second go-around while the biplane continued to execute high speed low passes over the runway at about 50 feet AGL. The problem likely arose because the biplane; which was NORDO; was engaged in a low level acrobatics display for a group of onlookers in the tiedown area and was not scanning for conflicting traffic. The 150 likely saw the biplane traffic near the airport; but the biplane's erratic behavior and rapid altitude and direction changes would have complicated efforts to maintain separation. The conflict could have been resolved if the biplane pilot refrained from low-level aerobatics in the vicinity of the traffic pattern; was visually scanning for traffic; and vacated the traffic pattern area when other traffic was inbound to land.




Synopsis: Pilot observer reported a near mid air collision between two airplanes in airport traffic pattern.
Date: 202011
Local time of day: 1201-1800
Location: ZZZ.Airport, US
Aircraft: No Aircraft
Reporter function: Captain
Reporter qualification: Flight Crew Instrument; Flight Crew Air Transport Pilot (ATP); Flight Crew Multiengine
Human factors: Physiological - Other; Confusion; Situational Awareness
Anomaly: Deviation / Discrepancy - Procedural Published Material / Policy; Deviation / Discrepancy - Procedural Security; Ground Event / Encounter Other / Unknown
Detector: Person Flight Crew
Contributing factors: Environment - Non Weather Related; Human Factors; Procedure
Primary problem: Environment - Non Weather Related

Narrative: Arriving at security at XA:00pm; we found all security check points and KCM [Known Crew Member] closed.  We were directed to security for airport employees in another terminal.  After setting off the alarm; I was instructed to start removing various articles of clothing.  With a line of airport employees behind me; I asked for a private search.  I was taken to yet another terminal and told to enter a room the size of an average walk in closest.  Two security personnel crammed in behind me.  There was poor ventilation and no possibility of distancing ourselves.  We all stood within a foot of each other.  I would suggest in this time of COVID; TSA like every other organization must adapt procedures and protocols to prevent the spread of COVID-19.  Utilizing KCM decreases the time and contact between security personnel and flight crews; two groups exposed to more human interaction than most.  Increasing the hours of KCM operation and relaxing constraints within the program to facilitate secure social distancing is a reasonable adaptation to help mitigate the spread of COVID among both essential workers and the public at large.




Synopsis: Air carrier Captain reported concerns with security checks in the terminal area that do not allow for proper social distancing.
Date: 201303
Local time of day: 1201-1800
Location: ZZZ.Airport, US
Aircraft: B737-300
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Flight phase: Initial Climb
Airspace: Class B ZZZ
ATC / advisory: TRACON ZZZ
Second aircraft: A319
Reporter organization: Government
Reporter function: Departure; Approach
Reporter qualification: Air Traffic Control Fully Certified
Human factors: Other / Unknown
Anomaly: ATC Issue All Types
Detector: Person Flight Crew
When detected: In-flight
Result: General None Reported / Taken
Contributing factors: Environment - Non Weather Related
Primary problem: Environment - Non Weather Related

Narrative: A B737 followed an A319 on departure and visual separation was applied by the Tower. Once on my frequency; the B737 pilot asked to deviate off course for wake turbulence. This happens often; and while pilot concurrence is needed; sometimes during major departure pushes this creates increased workload; but more importantly is a safety situation for the aircraft.




Synopsis: TRACON Controller voiced concern that; at times; aircraft departing with required wake separation request to deviate for wake avoidance; indicating that during heavy departure pushes this can be a separation problem.