elihoole/asrs-aviation-reports huggingface dataset:
Date: 202101
Local time of day: 1801-2400
Location: ZZZ.ARTCC, US
Flight conditions: IMC
Weather elements / visibility: Turbulence
Aircraft: B757 Undifferentiated or Other Model
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
Reporter organization: Air Carrier
Reporter function: Captain
Reporter qualification: Flight Crew Air Transport Pilot (ATP); Flight Crew Instrument; Flight Crew Multiengine
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: Flight Crew Regained Aircraft Control
Contributing factors: Weather
Primary problem: Weather

Narrative: ATC advised of SIGMET R with reports of moderate turbulence. As we approached the forecast area of turbulence we slowed to turbulence penetration speed of .78 MACH at FL360. After a few minutes of mostly moderate turbulence with significant mountain wave turbulence... we abruptly encountered approximately 10 seconds of severe turbulence resulting in simultaneous 5 to 10 degrees roll variations; +/-10 knots airspeed variations; 5 degrees pitch variations and over 1000 fpm down resulting in approximately 100 ft. below altitude. Autopilot recover aircraft to level flight. No injuries or damage noted. Reported to ATC. A few minutes following our PIREP; another aircraft report severe turbulence. Clear Air Turbulence associated with mountain wave.Suggest better forecasting. Uber conservative routing around forecast turbulence.




Synopsis: Air carrier Captain reported they encountered severe turbulence associated with mountain wave which caused roll variations and altitude and airspeed deviations.
Date: 202012
Local time of day: 1201-1800
Location: ZZZ.Airport, US
Flight conditions: VMC
Weather elements / visibility: Clear; 10
Light: Daylight
Aircraft: Cessna 170
Operator: Personal
Operating under: Part 91
Flight plan: VFR
Mission: Personal
Flight phase: Landing
Airspace: Class E ZZZ
ATC / advisory: CTAF ZZZ
Reporter organization: Personal
Reporter function: Single Pilot
Reporter qualification: Flight Crew Private
Anomaly: Ground Event / Encounter Loss Of Aircraft Control; Ground Excursion Runway
Detector: Person Flight Crew
When detected: Other Landing
Result: Aircraft Aircraft Damaged
Contributing factors: Procedure
Primary problem: Procedure

Narrative: After landing; ground loop off the active runway. No injuries.




Synopsis: Pilot reported ground looping the aircraft after landing with no injuries.
Date: 202111
Local time of day: 1201-1800
Location: ZZZ.ARTCC, US
Aircraft: Cessna Stationair/Turbo Stationair 7/8
Flight plan: IFR
Flight phase: Descent
Airspace: Class E ZZZ
ATC / advisory: Center ZZZ
Reporter organization: Government
Reporter function: Enroute
Reporter qualification: Air Traffic Control Fully Certified
Human factors: Distraction; Situational Awareness; Time Pressure
Anomaly: ATC Issue All Types; Deviation - Altitude Excursion From Assigned Altitude; Deviation / Discrepancy - Procedural Clearance; Inflight Event / Encounter CFTT / CFIT; Inflight Event / Encounter Weather / Turbulence
Detector: Person Air Traffic Control
When detected: In-flight
Result: Air Traffic Control Issued New Clearance; Air Traffic Control Provided Assistance
Contributing factors: Human Factors
Primary problem: Human Factors

Narrative: I was working a session with plenty of weather deviations with the cargo arrival push of the evening. Instructed Aircraft X on initial call to depart ZZZZZ intersection on a heading of 290 degrees to clear a mountainous terrain south of their position. Minutes later; I observed Aircraft X overflying the mountainside terrain below a MVA of 5;700 at 4;500 feet. I immediately advise Aircraft X to turn northbound on a heading of 310 to clear the terrain and the aircraft proceeded clear of the terrain without further incident.The RX/RXX sector was aware of the weather complexity in my sector; but was not giving me the traffic in an orderly and properly spaced manner. I asked the CIC to assist me with coordinating other sectors the departure headings due to the weather deviations; but the RX/ RXX sector was not asked to help me out with the situation by providing sufficient spacing.Also; Aircraft X did not comply with my initial instructions and due to the constant workload; I did not see this situation developing.




Synopsis: Center Controller reported an aircraft flew below the MVA by 1;300 feet near mountain side terrain.
Date: 201308
Local time of day: 0601-1200
Location: ZZZ.Airport, US
Flight conditions: VMC
Light: Daylight
Aircraft: B757 Undifferentiated or Other Model
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: Powerplant Lubrication System
Reporter organization: Air Carrier
Reporter function: Pilot Flying; First Officer
Human factors: Training / Qualification; Workload
Anomaly: Aircraft Equipment Problem Critical; Flight Deck / Cabin / Aircraft Event Smoke / Fire / Fumes / Odor
Detector: Person Flight Crew
When detected: In-flight
Result: Flight Crew Returned To Departure Airport; Flight Crew FLC complied w / Automation / Advisory; Flight Crew Landed in Emergency Condition; General Declared Emergency
Contributing factors: Aircraft
Primary problem: Aircraft

Narrative: I was the First Officer; the pilot flying. During climbout passing through approximately 14;000 MSL I noticed that the left engine oil temperature was high; in the caution range; approximately 164 degrees. I had the Captain look at the Engine Oil Temperature QRH. The checklist guides you to turn off the Autothrottle Arm switch; then retard the thrust lever of the affected engine with confirmation of the of the other pilot. The oil temperature reduced below the caution range. The QRH also guides you to make plans to land at the nearest suitable airport. By the time we were finished with the checklist we were climbing through 27;000 FT when the cockpit filled with smoke. Following the memory items for cockpit smoke we donned our oxygen masks and established crew communication. The Captain declared an emergency and requested to return to the departure airport. To stabilize the situation I engaged the autopilot. Then we selected the left engine bleed to OFF to see if it would clear the smoke and it worked. The smoke cleared quickly. Center vectored us for an ILS approach to the runway. The Captain requested landing performance information from Dispatch. For some reason we received a message from Dispatch stating that performance numbers had been sent but we didn't receive them. The Captain looked up the performance in his iPad. After a normal landing we taxied to the gate and deplaned the passengers.




Synopsis: A B757 oil temperature rose during climb after takeoff and after smoke entered the aircraft the Captain declared an emergency; completed the QRH and returned to the departure airport.
Date: 202112
Local time of day: 1201-1800
Location: ZZZ.Tower, US
Flight conditions: VMC
Weather elements / visibility: 10
Light: Daylight
Aircraft: Small Aircraft; Low Wing; 1 Eng; Retractable Gear
Operator: Personal
Operating under: Part 91
Flight plan: VFR
Mission: Personal
Flight phase: Descent
Airspace: Class E ZZZ
ATC / advisory: Tower ZZZ
Aircraft component: Cowling
Component problem: Failed
Reporter organization: Personal
Reporter function: Captain; Instructor; Pilot Flying
Reporter qualification: Flight Crew Commercial; Flight Crew Flight Instructor; Flight Crew Instrument; Flight Crew Multiengine
Human factors: Time Pressure; Workload
Anomaly: Aircraft Equipment Problem Critical
Detector: Person Flight Crew
When detected: In-flight
Result: Aircraft Aircraft Damaged
Contributing factors: Aircraft
Primary problem: Aircraft

Narrative: Descending through 3000 ft. MSL; 140 KIAS; engine cowling was torn off; took out the temperature probe and tore a hole in the windshield. Priority landing was given to Runway XX at ZZZ. Pilot was NOT injured; cowling fell over Reservoir.




Synopsis: Single Engine Pilot reported the engine cowling was torn off the aircraft while in descent.
Date: 201409
Local time of day: 1801-2400
Location: ZZZ.ARTCC, US
Flight conditions: IMC
Light: Night
Aircraft: B737-700
Operator: Air Carrier
Operating under: Part 121
Flight phase: Cruise
Airspace: Class A ZZZ
ATC / advisory: Center ZZZ
Aircraft component: Turbine Engine
Component problem: Malfunctioning
Reporter organization: Air Carrier
Reporter function: First Officer; Pilot Flying
Anomaly: Aircraft Equipment Problem Less Severe; Inflight Event / Encounter Weather / Turbulence
Detector: Person Flight Crew
When detected: In-flight
Result: Aircraft Equipment Problem Dissipated
Contributing factors: Aircraft; Weather
Primary problem: Aircraft

Narrative: We were on our last leg of our day and I was the flying pilot. We started to paint a little weather up ahead on our route but at 41;000 feet; we were pretty much on top of most of weather and the radar was depicting very little returns. Being at night in a moonless environment; it was hard to tell or avoid all the weather. We started to encounter moderate turbulence and entered IMC. The outside temp was -61 C and; per the AOM limitations; didn't require any engine ice protection. With the bumps though; the Captain elected to turn the ignition switches to CONT. We were IMC conditions and light to occasional moderate for two to three minutes when we felt the shudder and vibration and heard two muffled bangs. I noticed the number two N1 indication started to spool from cruise thrust of 90 to about 76% to 75%. I immediately announced I think we had an engine failure and the Captain took control of the thrust levers. All other indications stayed normal and never deviated from their normal cruise indications. The Captain vocalized it probably was a compressor stall and prepared for the checklist memory items. After about 10 to 15 seconds; the N1 spooled back up to normal cruise thrust and all secondary indications remained normal. We continued to monitor the indications closely and continued the flight. We landed uneventfully and all engine indications remained normal through the remainder of the flight.




Synopsis: B737 First Officer experiences a compressor stall at FL410 while flying in IMC and light turbulence at -61 degrees C. The engine anti-ice was off but continuous ignition was selected. The engine recovered by itself and the flight continued to its destination.
Date: 201502
Local time of day: 1201-1800
Location: CDC.Airport, UT
Flight conditions: VMC
Weather elements / visibility: 10
Light: Daylight
Aircraft: Skyhawk 172/Cutlass 172
Operator: Personal
Operating under: Part 91
Flight plan: None
Mission: Personal
Flight phase: Takeoff / Launch
Airspace: Class E CDC
ATC / advisory: CTAF CDC
Reporter organization: Personal
Reporter function: Pilot Flying; Single Pilot
Reporter qualification: Flight Crew Private
Human factors: Situational Awareness
Anomaly: Conflict Ground Conflict; Less Severe; Deviation / Discrepancy - Procedural Clearance; Deviation / Discrepancy - Procedural Published Material / Policy; Ground Incursion Runway
Detector: Person Flight Crew
When detected: In-flight
Result: General None Reported / Taken
Contributing factors: Human Factors
Primary problem: Human Factors

Narrative: CDC has many helicopters training in the area.  I landed for fuel on runway 02; taxied to the east side of the airport for self-serve fuel.  I refueled and the immediately adjacent runway - 26 - was favorable for my intended direction of travel; and to the best of my recollection it was favored by light winds from the NW.  I also was considering the training helicopter activity on the ramp and the 26 departure put me on the runway quickly; allowing me to expedite my departure from the busy training environment.  I heard other aircraft inbound; but they were a comfortable distance out.  I saw no traffic creating a conflict for a 26 departure.  I announced a 26 departure.  As I was climbing out; I noticed a R44 helicopter at the west end of 26; blades turning; sitting on the ground.  It was not close call.  I routinely have closer interactions using the taxiway at my home airport with training helicopters in the pattern.  The R44 was on the ground at the time and I had substantial altitude.  A minute or so later; I heard the R44 pilot announce a movement.  Knowing then that the pilot was on CTAF; I asked the pilot why he had not said something on the radio when I announced I was using 26.  He replied the runway was closed.  He was correct; and when he said that; I in fact recalled the NOTAM.  Nothing on the AWOS or on the ground prior to 26 entry indicated closure.  The runway was in fine condition from what I could see.  I do not agree that a runway being NOTAMed closed suggests that one then shouldn't use the radio to tell someone where you are at or better; point out the closure.  Factors affecting my decision making include not rechecking NOTAMs prior to takeoff and wanting to quickly leave the training environment and continue my x-country flight.  Also; distance or possibly runway crown prevented me from seeing the R44 at the opposite end prior to takeoff.




Synopsis: C172 unknowingly departed from closed Runway 26 at CDC causing some concern to a helicopter training crew.
Date: 201503
Local time of day: 1201-1800
Location: ZZZ.Airport, US
Aircraft: EMB ERJ 170/175 ER/LR
Operator: Air Carrier
Operating under: Part 121
Mission: Passenger
Flight phase: Initial Climb
Airspace: Class E ZZZ
ATC / advisory: TRACON ZZZ
Aircraft component: Turbine Engine
Component problem: Failed
Reporter organization: Air Carrier
Reporter function: Flight Attendant In Charge; Flight Attendant (On Duty)
Anomaly: Aircraft Equipment Problem Critical; Flight Deck / Cabin / Aircraft Event Other / Unknown
Detector: Person Flight Attendant; Person Flight Crew
When detected: In-flight
Result: Flight Crew Diverted; Flight Crew Landed in Emergency Condition; General Declared Emergency
Contributing factors: Aircraft
Primary problem: Aircraft

Narrative: 2-3 minutes after takeoff we experienced a loud bang and a shudder from the airplane. Flight Attendant (FA) B called me and stated she had heard a loud noise which I confirmed I had also heard.  I immediately called the flight deck to see if they had also heard it.  The captain answered and stated 'we have an engine failure; we are turning back; you have about 10 minutes and I will call back with special instructions.'  I called FA B up to brief her and locked my LAV.  The passengers were beginning to ask questions as they had obviously all heard the noise and we briefed them that we would be turning back and to return all seats and tray tables to their upright positions and to make sure seatbelts were fastened.  The captain called back to ask if we could look out at the engine and see if we saw smoke or anything unusual.  We looked and did not.  He then said he would call back which he did shortly and said that the engine was now in idle and appeared to be functioning for the time but we would still be returning.  He did not expect us to have to evacuate now that he was more aware of what was going on.He said he would make an announcement to the passengers and did so stating that we would be returning due to an engine failure and that he did not anticipate us having to evacuate and it should be a normal landing but we would be met by fire trucks.  We did our final preparations and compliance checks for landing and each took our jump seats.  The captain called back one final time stating we would be landing in 5 minutes and if we were ready.  We stated that we were and that everyone was seated.  Upon touchdown the captain came on the PA and commanded 'standby; standby' which we followed with instructing everyone to 'stay seated'.  The fire marshal checked our engine and we were cleared to taxi in without incident to our gate where we deplaned.




Synopsis: An EMB-175 Flight Attendant describes an engine failure on departure from her perspective; and the ensuing return to the departure airport.
Date: 201207
Local time of day: 1201-1800
Location: LAX.Airport, CA
Aircraft: Regional Jet 900 (CRJ900)
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Flight phase: Climb
Airspace: Class E ZLA
ATC / advisory: Center ZLA
Second aircraft: B737 Undifferentiated or Other Model
Reporter organization: Government
Reporter function: Enroute
Reporter qualification: Air Traffic Control Fully Certified
Human factors: Communication Breakdown; Confusion
Anomaly: ATC Issue All Types; Airspace Violation All Types
Detector: Person Air Traffic Control
When detected: In-flight
Result: General None Reported / Taken
Contributing factors: Human Factors
Primary problem: Human Factors

Narrative: I was working Sector 21 and I just took RADAR on a B737 climbing to 15;000 FT and a CRJ9 checked on climbing to 15;000 FT. I thought it was the B737 checking on and I climbed him to FL230. The CRJ9; which was in a different sector and I didn't have RADAR on; took the clearance and climbed. I never caught the wrong call sign. I would recommend listening to the full read back until moving on to the next thing.




Synopsis: ZLA Controller confused two different Air Carrier callsigns and issued a climb clearance to the incorrect aircraft. The incorrect read back was missed by the Controller.
Date: 201603
Local time of day: 1801-2400
Location: COS.TRACON, CO
Light: Daylight
Aircraft: Small Transport
Operator: FBO
Operating under: Part 91
Mission: Skydiving
Flight phase: Climb
Airspace: Class E COS
ATC / advisory: TRACON COS
Second aircraft: Small Aircraft; Low Wing; 1 Eng; Retractable Gear
Reporter organization: Government
Reporter function: Approach
Reporter qualification: Air Traffic Control Fully Certified
Human factors: Distraction; Situational Awareness; Time Pressure; Communication Breakdown
Anomaly: Conflict Airborne Conflict; Deviation / Discrepancy - Procedural Clearance; Deviation / Discrepancy - Procedural FAR; Deviation / Discrepancy - Procedural Published Material / Policy
Detector: Person Air Traffic Control
When detected: In-flight
Result: Air Traffic Control Issued Advisory / Alert
Contributing factors: Procedure; Human Factors
Primary problem: Human Factors

Narrative: Aircraft X is a jump plane that operates at Area X. They operate there knowing it is a bad location and does not want to sign an LOA with us because 'no matter what we have to provide services'. Area X is under multiple routes that IFR aircraft have to use to go enroute or just to land at COS. Also Area X is in the middle of a practice area that all VFR aircraft want to operate in. In this particular situation Aircraft Y was in the way of the descent of Aircraft X. The controller issued traffic to both; but both did not get each other in sight. So the controller stopped the descent of the Aircraft X. The response is 'blocked' try again 'blocked.' These are not one time offenses. This pilot always does this. Either blatantly ignores instructions or casually say blocked to pretend that they didn't hear it. I've recommended that they hold jumpers because they have jets underneath them. Their response is 'we are jumping in 1 minute'. What do I do? Kill myself trying to move everyone out of the way for them? Putting all the other aircraft in dangerous situations or proximity because they don't want to wait 2 minutes to let the aircraft pass? Luckily yelling on frequency and being unprofessional seemed to stop them. But of course that opens me up to other problems. Get NTSB on it; or something. We can't change the airspace because of one aircraft. I know parachute operations is a big topic; but there has to be some sort of control before it becomes a tombstone policy.




Synopsis: COS Approach Controller reported about a skydiving operation and the problems they are having with the pilot not doing what ATC is asking them to do.
Date: 201502
Local time of day: 0601-1200
Location: CMH.TRACON, OH
Flight conditions: VMC
Light: Dawn
Aircraft: Medium Large Transport; Low Wing; 2 Turbojet Eng
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Climb
Airspace: Class E ZID
ATC / advisory: TRACON CMH
Reporter organization: Air Carrier
Reporter function: Pilot Flying; First Officer
Reporter qualification: Flight Crew Air Transport Pilot (ATP)
Human factors: Communication Breakdown; Confusion; Workload
Anomaly: ATC Issue All Types; Deviation - Altitude Excursion From Assigned Altitude; Deviation / Discrepancy - Procedural Clearance
Detector: Person Air Traffic Control
When detected: In-flight
Result: Air Traffic Control Issued Advisory / Alert; Air Traffic Control Issued New Clearance; Flight Crew Became Reoriented; Flight Crew Returned To Clearance
Contributing factors: Procedure; Human Factors
Primary problem: Human Factors

Narrative: Took off out of CMH on runway 28R and on our initial climb to 10;000 feet. We were switched to Departure and checked in climbing to 10;000 feet and were informed to climb and maintain 15;000 feet passing through 11;500 feet ATC told us to maintain 10;000 feet we then stated we were told to climb and maintain 15;000 feet ATC came back and said we weren't. I then stopped the climb and started back to 10;000 feet and we were given a frequency change and then told to climb and maintain FL230.




Synopsis: An air carrier crew departed CMH and thought were cleared to 15;000 feet by departure; but when they called Center they were notified 10;000 feet was their climb limit. So; they started descending down to 10;000 feet only to be cleared to FL230.
Date: 201307
Location: ZZZ.ARTCC, US
Flight conditions: VMC
Light: Night
Aircraft: B757-200
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Flight phase: Climb
Airspace: Class E ZZZ
ATC / advisory: Center ZZZ
Aircraft component: Fuselage Panel
Component problem: Failed
Reporter organization: Air Carrier
Reporter function: First Officer; Pilot Not Flying
Reporter qualification: Flight Crew Air Transport Pilot (ATP)
Human factors: Situational Awareness
Anomaly: Aircraft Equipment Problem Critical; Deviation / Discrepancy - Procedural Published Material / Policy; Ground Event / Encounter Ground Strike - Aircraft
Detector: Person Flight Crew
When detected: In-flight
Result: Aircraft Aircraft Damaged; Flight Crew Returned To Departure Airport
Contributing factors: Aircraft; Human Factors
Primary problem: Human Factors

Narrative: After normal takeoff during climb through about 11;000 we heard and felt a pressurization bump. Cabin altitude was climbing and approaching 10;000. We leveled near 14;000 MSL; and then executed a descent back to 10;000 MSL. [We] received Cabin Altitude alert while leveling at 10;000. Complied with QRH; contacted Operations and decided to return to our departure airport. On post flight I noted a ruptured panel and scrape on underside of rear fuselage.I think I missed the damage on preflight. I think the damage on post flight was probably more evident than the preflight due to panel that may have ruptured during flight hanging down/not flush.




Synopsis: Following a return to their departure airport due to the failure of the aircraft to pressurize the flight crew of a B757-200 discovered scrapes and a blown out panel on the aft lower fuselage.