elihoole/asrs-aviation-reports huggingface dataset:
Date: 202107
Local time of day: 0601-1200
Location: ZZZ.TRACON, US
Flight conditions: VMC
Weather elements / visibility: 10
Light: Daylight
Aircraft: Small Transport; Low Wing; 2 Turbojet Eng
Operator: Corporate
Operating under: Part 135
Flight plan: IFR
Mission: Passenger
Flight phase: Initial Climb
Airspace: Class C ZZZ
ATC / advisory: TRACON ZZZ
Second aircraft: Small Aircraft; Low Wing; 1 Eng; Fixed Gear
Reporter organization: Corporate
Reporter function: Captain; Pilot Flying
Reporter qualification: Flight Crew Air Transport Pilot (ATP); Flight Crew Instrument; Flight Crew Multiengine
Human factors: Communication Breakdown; Distraction; Time Pressure; Troubleshooting; Workload
Anomaly: Conflict NMAC; Deviation - Altitude Crossing Restriction Not Met; Deviation - Altitude Overshoot; Deviation / Discrepancy - Procedural Published Material / Policy; Deviation / Discrepancy - Procedural Clearance
Detector: Automation Aircraft TA; Person Flight Crew
When detected: In-flight
Result: Flight Crew Took Evasive Action
Contributing factors: Human Factors; Environment - Non Weather Related
Primary problem: Human Factors

Narrative: Departing Runway XX from ZZZ. Issued climb via SID to 20;000 ft. Briefed approach with crew. In the turn near ZZZZZ became aware of visual target approaching left to right. ATC was asking target about altitude which led crew to believe he wasn't where he was expected to be. Target was now 300 ft. above and appeared to have until now been in a descent. Traffic alert sounded in cockpit. Quick review of terrain on departure plate showed rising terrain 13;000 ft. and TAWS showed red to the left. Unable to transmit to ATC due to conversation between target and ATC. Elected to climb to avoid terrain and target. Disconnected autopilot for climb and preparation for potential evasive action. Climbed above published 'at or below' crossing restriction. Believe we were within 3 miles of crossing when we topped the altitude. Crossing restriction missed by crew due to distraction with traffic alert and eyes outside for see and avoid operations. Upon review after the fact; target on arrival should have been at 10;000 ft. and our level off at 9;000 ft. would have kept us below target. We did not have that information at the time of the incident which is why we believed the target was descending and our climb would have avoided the conflict.




Synopsis: Captain reported taking evasive action to avoid a NMAC while on a SID resulting in a missed crossing restriction.
Date: 201204
Local time of day: 1801-2400
Location: DEN.Airport, CO
Flight conditions: VMC
Light: Night
Aircraft: B737-700
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Flight phase: Climb
Airspace: Class E ZDV
ATC / advisory: TRACON D01
Reporter organization: Air Carrier
Reporter function: Captain; Pilot Flying
Reporter qualification: Flight Crew Air Transport Pilot (ATP)
Human factors: Human-Machine Interface; Situational Awareness
Anomaly: Aircraft Equipment Problem Less Severe; Deviation / Discrepancy - Procedural Published Material / Policy; Inflight Event / Encounter Other / Unknown
Detector: Person Flight Crew
When detected: In-flight
Result: Flight Crew Took Evasive Action
Contributing factors: Human Factors; Aircraft
Primary problem: Ambiguous

Narrative: During climb; I was the pilot flying and after receiving a climb clearance and dialing the new altitude in the Altitude Preselect window; I failed to notice VNAV had disengaged and Vertical Speed had engaged. As I noticed the airspeed low and was disengaging the autopilot and auto throttles; the Airspeed Low Aural Warning sounded briefly as I was advancing power and lowering the nose of the aircraft. Airspeed recovered quickly and the flight was completed without further event. All ATC clearances were adhered to. Aircraft did not stall. Airspeed quickly recovered after lowering the nose of the aircraft. In retrospect; I have seen the VNAV disengage numerous times on Company aircraft. Monitoring the FMA closer would have prevented this from occurring.




Synopsis: A B737-700 Captain reported a near-stall incident in climb when the aircraft dropped out of VNAV into Vertical Speed mode. Reporter stated this is not an uncommon occurrence.
Date: 201811
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: Ramp
Human factors: Situational Awareness
Second reporter function: Ramp
Anomaly: Deviation / Discrepancy - Procedural Published Material / Policy; Flight Deck / Cabin / Aircraft Event Illness / Injury; Ground Event / Encounter Other / Unknown
Detector: Person Ground Personnel
When detected: Pre-flight
Result: General Physical Injury / Incapacitation; General Police / Security Involved
Contributing factors: Human Factors; Procedure
Primary problem: Human Factors

Narrative: I was assigned to assist a flight bound for ZZZZ. While loading the 3rd pallet in succession; I noticed that a catering truck was blocking my agent from backing up to the right pallet. It was then I told the agent to go around with pallet; not noticing that I forgot to put the locks up. It was during the turning maneuver; the pallet fell halfway off the dolly and unto the ground. It was then; everyone nearby saw the incident and came over to help. One person; had a tug holding the pallet from falling further and another person was using a belt loader to push the pallet back on. I had disconnected the tug from the dolly for another person to use to hold the pallet as well. It was then the Captain and copilot came down from the cockpit and was talking to me about the contents of the pallet. He asked me if it was dangerous goods; but I was not sure. It was then I checked the scanner for the contents of pallet. When I returned to talk to the Captain; I noticed the tongue of the dolly swung towards me and I yelled Look Out. Someone had used a tug to abruptly push the pallet back on the dolly and in the process; the tongue narrowly missed me; another employee; and the copilot. Unfortunately; the Captain fell on his back when the tongue hit the back of this feet. I manage to hold the Captain by his hand; while he was going down to help break his fall. I then helped the Captain up to his feet and asked he was alright. After that; all other personnel such as management and airport police showed up.


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


Synopsis: Two ramp employees reported a company Captain was injured on the ramp due to contact with ground equipment.
Date: 202012
Local time of day: 1201-1800
Location: ZZZ.Airport, US
Flight conditions: VMC
Light: Daylight
Aircraft: B737-800
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Landing; Final Approach
Airspace: Class B ZZZ
ATC / advisory: TRACON ZZZ; Tower ZZZ
Reporter organization: Air Carrier
Reporter function: Pilot Not Flying; Captain
Reporter qualification: Flight Crew Instrument; Flight Crew Multiengine; Flight Crew Air Transport Pilot (ATP)
Anomaly: ATC Issue All Types; Ground Event / Encounter Person / Animal / Bird; Ground Event / Encounter Fuel Issue
Detector: Person Flight Crew
When detected: In-flight
Result: Air Traffic Control Provided Assistance; Air Traffic Control Issued New Clearance; Flight Crew Executed Go Around / Missed Approach; Flight Crew Requested ATC Assistance / Clarification
Contributing factors: Procedure; Airport
Primary problem: Ambiguous

Narrative: Great weather; normal fuel burn. Entering terminal area we were vectored around then low and slow which created more fuel burn in terminal area. Did go-around for XXL due to an animal on runway. Aircraft in front of us did same. Declared minimum fuel on go-around in order to expedite landing since fuel now was an issue with extra fuel burn and not much to play. Controller was going to extend us downwind behind an arriving aircraft which would have added more time and fuel so I elected to [request] an immediate turn to the FAF for XXC. I didn't want XXL because of animal issue and another possible go-around. Controller vectored preceding aircraft off their approach and cleared us for visual XXC. Landed uneventfully with 3.9 fuel.....2.10 left tank and 1.8 right tank. Reserve Fuel on Flight Plan was 3.78.Cause: Dispatched with normal arrival fuel with very good weather. Controller vectored us low and slow which increased fuel burn. Suggestions: Next time I will not accept so many vectors and low and slow increasing fuel burn when I do not have extra fuel to play.




Synopsis: B737-800 Captain reported a low fuel situation developed following a go-around to avoid an animal on the runway.
Date: 201902
Local time of day: 1201-1800
Location: ZZZ.Airport, US
Flight conditions: VMC
Weather elements / visibility: Rain
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: Pilot Flying; Captain
Reporter qualification: Flight Crew Multiengine; Flight Crew Air Transport Pilot (ATP); Flight Crew Instrument
Human factors: Communication Breakdown
Second reporter function: First Officer; Pilot Not Flying
Anomaly: Deviation / Discrepancy - Procedural Published Material / Policy; Deviation / Discrepancy - Procedural Weight And Balance; Deviation / Discrepancy - Procedural Hazardous Material Violation
Detector: Person Flight Crew
When detected: Pre-flight
Result: General Work Refused
Contributing factors: Human Factors; Procedure
Primary problem: Procedure

Narrative: After F/O (First Officer) finished the walk around he said he had taken a picture of something that was being loaded onto the aircraft and asked if I had ever seen this before. It looked like a small trash can on a small pallet; wrapped in plastic. He said it was labeled 'cryogenic medical supplies'. Preliminary DG (Dangerous Goods) report had said no DG on this flight. I went down to the ramp to see what this was. There were 3 of these containers each was marked 'cryogenic'. Dispatcher was called. He talked to Load Planner; neither had any record of DG to be loaded. Called [Station] Operations; they called back and said there was no paperwork on these containers; therefore; they were being removed from the aircraft. I went downstairs to the ramp; talked to the Ramp Supervisor and saw that they had been removed. F/O should be commended for his diligence. If he hadn't taken that picture I would have never known.


Second narrative: During the exterior aircraft inspection I noticed some strange cargo that appeared to be 3 barrels of medical equipment with dry ice. I took a photo of it and showed it to the Captain. At that moment we also got an ACARS message that said No Dangerous Goods. The CA (Captain) called and [Station] Operations. They said no Hazmat planned. The CA went out on the ramp and saw that the possible Hazmat cargo was loaded. The CA then called Operations again about the cargo; after a few minutes they said the cargo in question was removed from the aircraft. The rest of the flight was normal.


Synopsis: B737 flight crew reported undocumented Hazmat cargo loaded on aircraft with no flight crew notification.
Date: 201712
Local time of day: 1801-2400
Light: Night
Aircraft: B737-800
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Cruise
Airspace: Class A ZZZ
ATC / advisory: Center ZZZ
Aircraft component: FMS/FMC
Component problem: Malfunctioning
Reporter organization: Air Carrier
Reporter function: Captain; Pilot Flying
Reporter qualification: Flight Crew Air Transport Pilot (ATP)
Human factors: Distraction; Human-Machine Interface; Troubleshooting
Anomaly: Aircraft Equipment Problem Critical
Detector: Person Flight Crew
When detected: In-flight
Result: Flight Crew Overcame Equipment Problem
Contributing factors: Aircraft; Human Factors
Primary problem: Aircraft

Narrative: Dual FMC failure while at cruise for about 30 seconds. LNAV; VNAV; Autothrottle disengaged; FMC's went blank then returned without the option to select the FMC mode. Everything returned before we could even select a checklist. Reengaged all modes and they worked properly for the rest of the flight. Dispatch and Maintenance were both notified.




Synopsis: B737 Captain reported temporary dual FMC failure.
Date: 201209
Local time of day: 1801-2400
Location: ZZZ.ARTCC, US
Aircraft: B727-200
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Flight phase: Cruise
Airspace: Class A ZZZ
ATC / advisory: Center ZZZ
Aircraft component: Turbine Engine
Component problem: Malfunctioning
Reporter organization: Air Carrier
Reporter function: Captain
Reporter qualification: Flight Crew Air Transport Pilot (ATP)
Anomaly: Aircraft Equipment Problem Critical
When detected: In-flight
Result: Flight Crew Inflight Shutdown; Flight Crew Returned To Departure Airport; General Declared Emergency; General Maintenance Action
Contributing factors: Aircraft; Weather
Primary problem: Aircraft

Narrative: During cruise flight enroute; we heard and felt a vibration in the number two throttle lever with associated airframe vibration. In accordance with the QRH; we reduced the number two throttle to idle. Shortly after reaching idle; the engine did an uncommanded acceleration to 92% N2 RPM and remained there. All engine parameters remained within limits.We declared an emergency and; based on an ATC weather report of heavy rain and low ceilings with moderate turbulence below 8;000 in the immediate area; elected to return to our departure airport where the weather was VFR. We shutdown the Number Two Engine prior to landing. Oil pressure was normal prior to shutdown and windmilling oil pressure was observed after shutdown. We conducted a visual approach to a one engine inoperative landing and taxied to the gate. Post flight inspection of Number Two Engine showed severe damage to several stator blades.




Synopsis: A B727-200 flight crew shut down their Number Two Engine due to vibration and returned to their departure airport. Maintenance discovered significant damage to the engine's stator vanes.
Date: 201401
Local time of day: 1201-1800
Location: ZZZ.Airport, US
Flight conditions: VMC
Weather elements / visibility: 10
Light: Daylight
Aircraft: Cessna 150
Operator: FBO
Operating under: Part 91
Flight plan: None
Mission: Training
Flight phase: Cruise
Airspace: Class E ZZZ
ATC / advisory: TRACON ZZZ
Aircraft component: Reciprocating Engine Assembly
Component problem: Failed
Reporter organization: FBO
Reporter function: Instructor; Pilot Flying
Reporter qualification: Flight Crew Commercial; Flight Crew Flight Instructor
Anomaly: Aircraft Equipment Problem Critical; Deviation / Discrepancy - Procedural Published Material / Policy
Detector: 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: Conducting a training flight with student; aircraft was airworthy and up to date on maintenance. All licenses are current. Pre-flight and engine run-up check OK. Performed practice in west practice area for approximately 1 hour at an altitude in accordance with FAR 91.119. Engine roughness enroute from west practice area back to home base airport 2;000 RPM at full throttle. All systems operating normal; loss of engine power was only indication. 0 FPM climb; level 2;000 MSL; 80 knots IAS. Carburetor heat ON; engine roughness followed by engine failure. Engine Failure Emergency Checklist procedures followed; restart of engine unsuccessful. In communication with Approach; declared emergency; squawked 7770; instead of 7700. Aircraft secured for landing; fuel valve OFF; mixture full lean; throttle closed; [and] ignition OFF. Landed in cornfield with no damage to aircraft; persons; or property.




Synopsis: C150 instructor pilot experiences engine failure at 2;000 FT and lands safely in a corn field.
Date: 201701
Local time of day: 0601-1200
Location: ZZZ.Airport, US
Flight conditions: VMC
Light: Daylight
Aircraft: B767-300 and 300 ER
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Cargo / Freight / Delivery
Flight phase: Climb
Airspace: Class A ZZZ
ATC / advisory: Center ZZZ
Aircraft component: Turbine Engine
Component problem: Malfunctioning
Reporter organization: Air Carrier
Reporter function: Captain; Pilot Flying
Reporter qualification: Flight Crew Air Transport Pilot (ATP)
Second reporter function: First Officer; Pilot Not Flying
Anomaly: Aircraft Equipment Problem Critical; Deviation / Discrepancy - Procedural Weight And Balance
Detector: Person Flight Crew
When detected: In-flight
Result: Flight Crew Inflight Shutdown; Flight Crew Landed As Precaution; Flight Crew Returned To Departure Airport; General Maintenance Action
Contributing factors: Aircraft
Primary problem: Aircraft

Narrative: During climb we had EICAS message Lt oil filter. QRH procedure was complied with resulting in an inflight shutdown of the left engine. After EICAS msg ATC clearance obtained for intermediate level off to deal with the problem. QRH procedure was complied with. After throttle was slowly retarded and oil filter msg remained. Engine failure/shutdown procedure was accomplished. We contacted flight control and informed them of our problem and intentions of returning back to ZZZ. They agreed and Amended Release to Read (ARTR) was obtained. We considered burning down to max landing weight but after dumping center fuel (approx. 24;000 pounds) we determined it would be an unacceptably long time to reach that weight. Best course of action was an overweight landing. Flight control assisted in working on landing performance numbers. Uneventful approach and landing was accomplished with a landing weight of 349;400 pounds. Unassisted taxi back to ramp.


Second narrative: After landing; maintenance showed us a photo of the metal shavings that had been collected by a magnet in the left engine oil system. Therefore; the aircraft's warning system worked as it should. In other words; the problem was not just a light or sensor or indicator.


Synopsis: B767-300 flight crew reported returning to departure airport after receiving a L OIL FILTER EICAS message which led to an inflight shutdown.
Date: 202012
Local time of day: 1201-1800
Location: ZZZ.Airport, US
Flight conditions: VMC
Weather elements / visibility: Haze / Smoke; 10
Light: Daylight
Aircraft: Cessna Aircraft Undifferentiated or Other Model
Operator: Personal
Operating under: Part 91
Flight plan: None
Mission: Personal
Flight phase: Cruise
Airspace: Class E ZZZ
Aircraft component: Fuel System
Component problem: Improperly Operated
Reporter organization: Personal
Reporter function: Pilot Flying; Single Pilot
Reporter qualification: Flight Crew Instrument; Flight Crew Private
Human factors: Training / Qualification; Situational Awareness
Anomaly: Aircraft Equipment Problem Critical; Deviation / Discrepancy - Procedural Published Material / Policy; Inflight Event / Encounter Fuel Issue
Result: Flight Crew Inflight Shutdown; Flight Crew Landed in Emergency Condition
Contributing factors: Aircraft; Human Factors
Primary problem: Human Factors

Narrative: To keep current; I try to fly at least one hour a month. I confirmed that there was 15 gallons in each tank which would allow for 3 hours for an anticipated flight of less than 2. I did 8 landings at 3 airports and was on my last 10 mile leg to home base. About 1.5 hours. Because of failure to change the fuel selector to both; the engine died during low level cruise. I [selected and checked] carburetor heat; mags and gas but the engine did not start for unknown reasons. I landed in a farm field with no injuries; property damage and no damage to the airplane as determined by the club mechanic.  Lack of experience in type. This the only plane that requires leaving the fuel on right only that I have flown. I was interrupted during the preflight; I should have stated over again. I should practice emergency procedures more often.




Synopsis: Cessna pilot reported landing in a field following an engine failure related to fuel mismanagement.
Date: 201309
Local time of day: 0601-1200
Location: ZZZ.Airport, US
Flight conditions: VMC
Weather elements / visibility: 10
Light: Daylight
Aircraft: Cessna 170
Operator: Personal
Operating under: Part 91
Flight plan: None
Mission: Personal
Flight phase: Takeoff / Launch
Airspace: Class G ZZZ
Reporter organization: Personal
Reporter function: Instructor
Reporter qualification: Flight Crew Instrument; Flight Crew Multiengine; Flight Crew Flight Instructor; Flight Crew Flight Engineer; Flight Crew Air Transport Pilot (ATP); Flight Crew Commercial
Human factors: Human-Machine Interface
Anomaly: Inflight Event / Encounter Loss Of Aircraft Control
Detector: Person Flight Crew
When detected: In-flight
Result: Aircraft Aircraft Damaged; Flight Crew Regained Aircraft Control; Flight Crew Rejected Takeoff
Contributing factors: Human Factors; Aircraft
Primary problem: Ambiguous

Narrative: I was flying as pilot in command in right seat. An acquaintance; who is a commercial pilot; was flying the aircraft from the left seat. He made me take off and made left traffic for further touch and goes. A good landing (3 point) was then made; flaps were reduced to 10 degrees and take off power applied. The aircraft was straight and on centerline. At approximately 40 MPH IAS; the nose began coming around to the right. The tail wheel was still on the runway. I took control; applied full aft elevator and full left rudder; but the aircraft ground looped to the right; tipping and hitting the left wingtip and left elevator on the grass before returning to an upright position. I secured the aircraft and we exited the aircraft. Upon inspection; we determined the aircraft could be safely started and taxied off the runway. I taxied the aircraft to a maintenance facility on the field. Current weather was approximately 1;500 FT scattered clouds with no clouds above. Wind was calm; visibility was plus 10 miles; and runway was dry.




Synopsis: C170 Instructor reports a ground loop by the pilot flying during a touch and go. The instructor takes control but is unable to prevent the left wing tip and horizontal stabilizer from contacting the ground.
Date: 201212
Weather elements / visibility: Turbulence
Light: Night
Aircraft: B737-800
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Cruise
Airspace: Class A ZZZ
ATC / advisory: Center ZZZ
Aircraft component: Altitude Hold/Capture
Component problem: Malfunctioning
Reporter organization: Air Carrier
Reporter function: Pilot Flying
Human factors: Human-Machine Interface; Workload; Situational Awareness
Anomaly: Aircraft Equipment Problem Critical; Deviation - Altitude Excursion From Assigned Altitude; 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; Flight Crew Returned To Clearance; Flight Crew Took Evasive Action
Contributing factors: Aircraft
Primary problem: Aircraft

Narrative: In turbulence; the PITCH mode of the autopilot dropped out of VNAV path and reverted to CWS Pitch; and the plane immediately started diving at what must have been about 4;000 FPM. I grabbed the yoke; disconnected the autopilot and stopped the descent at a loss of about 300 FT. Later in the flight; the  same thing happened on descent but there was no altitude deviation.Suggestions for avoiding recurrence: Keep the autopilots up.




Synopsis: A B737-800 autopilot twice transitioned from VNAV Path to CWS Pitch without command and the during the first event at FL360 began a dive loosing 300 FT before recovery was affected.