elihoole/asrs-aviation-reports huggingface dataset:
Date: 201210
Local time of day: 0601-1200
Location: ZZZ.Airport, US
Flight conditions: VMC
Weather elements / visibility: 50
Light: Daylight
Aircraft: Cessna 210 Centurion / Turbo Centurion 210C; 210D
Operator: Personal
Operating under: Part 91
Flight plan: VFR
Mission: Personal
Flight phase: Cruise
Airspace: Class C ZZZ
ATC / advisory: TRACON ZZZ
Aircraft component: Gear Extend/Retract Mechanism
Component problem: Failed
Reporter organization: Personal
Reporter function: Single Pilot; Pilot Flying
Reporter qualification: Flight Crew Instrument; Flight Crew Private
Human factors: Human-Machine Interface
Anomaly: Aircraft Equipment Problem Less Severe
Detector: Person Flight Crew
When detected: In-flight
Result: Flight Crew Overcame Equipment Problem; General Maintenance Action
Contributing factors: Aircraft; Human Factors
Primary problem: Aircraft

Narrative: Electric/hydraulic landing gear motor failed and gear did not extend and lock. Executed emergency procedures to extend gear with manual hand pump and initially could not get gear down either. Checked hydraulic fluid reservoir and it was full. [I] asked Flight Service to notify destination airport of possible emergency gear up landing. After contact with Approach Control and explaining the situation; I tried the manual pump again and it did work; extended the gear and made an uneventful landing.




Synopsis: C210 pilot reports failure of the landing gear motor en route and initial difficulties with the manual pump. Eventually hand pumping results in a down and safe indication and a normal landing ensues at destination airport.
Date: 201807
Local time of day: 1201-1800
Location: ZZZ.Airport, US
Weather elements / visibility: Clear; 10
Light: Daylight
Aircraft: PA-28 Cherokee/Archer/Dakota/Pillan/Warrior
Operator: FBO
Operating under: Part 91
Flight plan: VFR
Mission: Personal
Flight phase: Cruise
Airspace: Class E ZZZ
Aircraft component: Powerplant Fuel System
Component problem: Failed
Reporter organization: FBO
Reporter function: Instructor; Pilot Flying
Reporter qualification: Flight Crew Commercial; Flight Crew Flight Instructor
Human factors: Situational Awareness
Anomaly: Aircraft Equipment Problem Critical; Inflight Event / Encounter Fuel Issue
Detector: Person Flight Crew
When detected: In-flight
Result: Flight Crew Landed in Emergency Condition; Flight Crew Diverted; Flight Crew Inflight Shutdown
Contributing factors: Aircraft
Primary problem: Aircraft

Narrative: I was enroute to ZZZ as a diversion due to an aircraft having landed gear up which consequently closed the runway at ZZZ1. Approximately 10 NM south southeast from ZZZ1 and 1 mile due east from the town; I was switching fuel tanks from the right fuel tank to the left fuel tank at the completion of that action the aircraft sputtered and the engine instrument displayed '0' Fuel Pressure which caused my aircraft's engine to cease operation thus requiring me to perform an emergency descent and off airport landing. With limited time to conduct the engine failure checklist; I troubleshot the situation by cycling the throttle and fuel pump switch which did not cure the situation. It was at this point in the event; that I opted to put the aircraft into a field which at the time seemed the safest course of action. The aircraft impacted the ground softly on the landing gear and rolled to a stop approximately 100 yards south of [the] road. The aircraft came to a stop with no visible damage. I secured that aircraft; exited and contacted emergency services to report my situation and to notify Approach Control that I was on the ground safe and was in no further need of aid. This event was a PART 91 operation.




Synopsis: PA28 flight instructor reported the engine lost fuel pressure and shut down in cruise; resulting in an off-field landing.
Date: 201908
Local time of day: 0601-1200
Location: ZKC.ARTCC, KS
Weather elements / visibility: Turbulence
Aircraft: Any Unknown or Unlisted Aircraft Manufacturer
Flight plan: IFR
Flight phase: Cruise
Airspace: Class E ZKC
ATC / advisory: Center ZKC
Aircraft component: Cockpit Window
Component problem: Failed
Reporter organization: Government
Reporter function: Enroute
Reporter qualification: Air Traffic Control Fully Certified
Human factors: Time Pressure; Communication Breakdown; Distraction; Situational Awareness; Workload
Anomaly: ATC Issue All Types; Aircraft Equipment Problem Less Severe; Deviation / Discrepancy - Procedural Other / Unknown; Inflight Event / Encounter Weather / Turbulence
Detector: Person Air Traffic Control
When detected: In-flight
Result: Air Traffic Control Issued New Clearance; Aircraft Aircraft Damaged; Flight Crew Diverted; Flight Crew Requested ATC Assistance / Clarification
Contributing factors: Staffing; Human Factors; Company Policy; Aircraft
Primary problem: Staffing

Narrative: The whole area was busy and as usual with not enough people to work the sectors as needed. I had just come back from a break and was told to work the d-side (Radar Assist) on a high altitude sector. I helped out there for a few minutes before I was told to go work the d-side on a different sector due to an emergency. I plugged in and right away heard the pilot say that his back window was broken out and he wanted to land at ICT. He stated that he was not in an emergency situation and did not need equipment on the ground. Since he was turning to ICT; we started the hand off to Approach. I called Approach and told them that 'his back window was broken out; pilot stated that he was not in an emergency situation and did not need equipment on the ground but we were treating him as an emergency. Let us know when he is one the ground.' Shortly after that the pilots' communications were transferred to Approach. A few minutes later I was told to go work the d-side on another sector. It was not until two days later that I learned that the pilot had flown into turbulence and that caused the broken window. I was sent to a sector to help with an emergency and that's what I did. There was no time to call the radar controller for a sector briefing before coordination needed to be done on the aircraft.Our low sectors are routinely run too busy. There are 9 VHF frequency and 9 UHF frequencies to manage. Pilots are always stepping on each other. It's a lot of airspace to work and a lot of advance low altitude traffic to work. These sectors should be split out a lot more that they are. Due to low staffing numbers we are forced to work busy sectors without help and in this case; work two of the most complex sectors combined up.




Synopsis: ZKC Controller reported they did not properly coordinate a priority aircraft due to not receiving a sector briefing.
Date: 201202
Local time of day: 1801-2400
Location: ZZZ.ARTCC, US
Aircraft: MD-82
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Flight phase: Cruise
Airspace: Class A ZZZ
ATC / advisory: Center ZZZ
Second aircraft: Cessna Citation Sovereign (C680)
Reporter organization: Government
Reporter function: Enroute
Reporter qualification: Air Traffic Control Fully Certified
Human factors: Communication Breakdown; Confusion; Situational Awareness
Anomaly: ATC Issue All Types; Conflict Airborne Conflict
Detector: Automation Aircraft RA
Result: Air Traffic Control Issued New Clearance
Contributing factors: Human Factors
Primary problem: Human Factors

Narrative: The R-Side controller climbed a C680 to FL310 to go underneath a MD82. There was a NXXX also on frequency that had been leveled at FL310 for arrival traffic. The R-Side climbed NYXX to FL370 but meant to climb NXXX. I did not hear the clearance to be wrong. An MD82 and NYXX responded to a TCAS and the R-Side responded.




Synopsis: Enroute Controller described a loss of separation event when the R-Side Controller issued an altitude assignment to the wrong aircraft; similar call signs were in play.
Date: 201706
Local time of day: 1801-2400
Location: CLT.Airport, NC
Flight conditions: VMC
Light: Night
Aircraft: Regional Jet 200 ER/LR (CRJ200)
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Initial Climb
Airspace: Class B CLT
ATC / advisory: Tower CLT
Second aircraft: A320
Reporter organization: Air Carrier
Reporter function: First Officer; Pilot Not Flying
Reporter qualification: Flight Crew Air Transport Pilot (ATP)
Anomaly: Inflight Event / Encounter Wake Vortex Encounter
Detector: Person Flight Crew
When detected: In-flight
Result: General None Reported / Taken
Contributing factors: Environment - Non Weather Related; Procedure
Primary problem: Ambiguous

Narrative: Rotated off of Runway 18L at Charlotte International Airport behind an Airbus 320. Just after rotation I called positive rate and the pilot flying called gear up. As I was selecting the gear up we experienced wake turbulence that caused the stick shaker to activate for just a second. We continued the climb out and the flight as normal.




Synopsis: CRJ-200 First Officer reported encountering wake turbulence shortly after takeoff from CLT in trail of an A320.
Date: 201508
Local time of day: 0001-0600
Location: ZZZ.ARTCC, US
Flight conditions: VMC
Weather elements / visibility: 50
Light: Night
Aircraft: B767-300 and 300 ER
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
Aircraft component: Powerplant Lubrication System
Component problem: Malfunctioning
Reporter organization: Air Carrier
Reporter function: Captain; Pilot Flying
Reporter qualification: Flight Crew Air Transport Pilot (ATP)
Human factors: Situational Awareness
Second reporter function: Pilot Not Flying; First Officer
Anomaly: Aircraft Equipment Problem Less Severe
Detector: Person Flight Crew
When detected: In-flight
Result: Flight Crew Landed As Precaution; Flight Crew Diverted; General Maintenance Action
Contributing factors: Aircraft
Primary problem: Aircraft

Narrative: During cruise flight at FL360. Crew noticed right engine oil quantity displayed 0; and right engine oil pressure turned yellow and displayed 20 PSI. Reduced thrust was applied to the right engine. Appropriate checklist and Aircraft Operating Manual (AOM) procedures reviewed. Dispatch and Maintenance were notified via SAT comm. We decided it was best to divert. ATC was notified and we diverted to ZZZ. The aircraft landed without further incident. After landing the right engine was shutdown on taxi in the ramp.


Second narrative: [Report Narrative Contained No Additional Information.]


Synopsis: The Boeing 767 crew diverted to a nearby airport after noticing low oil pressure and quantity.
Date: 201412
Local time of day: 0601-1200
Location: CLT.Airport, NC
Flight conditions: Marginal
Light: Daylight
Aircraft: Regional Jet 200 ER/LR (CRJ200)
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Initial Climb
Airspace: Class B CLT
ATC / advisory: Tower CLT
Second aircraft: A320
Reporter organization: Air Carrier
Reporter function: First Officer; Pilot Flying
Reporter qualification: Flight Crew Air Transport Pilot (ATP)
Anomaly: Inflight Event / Encounter Wake Vortex Encounter
Detector: Person Flight Crew
When detected: In-flight
Result: Flight Crew Took Evasive Action
Contributing factors: Environment - Non Weather Related; Procedure
Primary problem: Procedure

Narrative: Departing out of CLT were cleared for takeoff behind an A320. I anticipated that ATC would keep us adequately separated from any potential wake turbulence. As we began our climb and acceleration through 1;000 feet AGL I could see the probability of flying through that aircraft's wake. I called for continuous ignition then just before we were about to retract the flaps we got into it pretty hard. Counter control required full aileron deflection and some additional rudder. The stick shaker activated as well. The stick shaker activation was due to the turbulent air deflecting the AOA vanes and not due to an excessive angle of attack. Airspeed throughout the maneuver was approximately 190KIAS. To avoid this in the future I think Charlotte tower should give the following aircraft an upwind vector; or turn the leading aircraft downwind and earlier; or hold the following aircraft until separation is sufficient. Based on the CRJ's long takeoff roll it is inevitable that following a larger aircraft will cause the climbing flight path to intersect with the flight path of the leading aircraft. The most likely cause was ATC clearing us for takeoff before there was adequate separation.




Synopsis: CRJ-200 First Officer reported encountering wake turbulence on departure from CLT in trail of an A320 that resulted in uncommanded roll and stick shaker. Reporter suggested increased separation on takeoff.
Date: 202112
Local time of day: 1201-1800
Location: ZZZ.ARTCC, US
Flight conditions: VMC
Light: Daylight
Aircraft: A300
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
Aircraft component: Powerplant Lubrication System
Component problem: Malfunctioning
Reporter organization: Air Carrier
Reporter function: Dispatcher
Reporter qualification: Dispatch Dispatcher
Human factors: Troubleshooting
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 As Precaution; Flight Crew Requested ATC Assistance / Clarification; General Flight Cancelled / Delayed; General Maintenance Action
Contributing factors: Aircraft
Primary problem: Aircraft

Narrative: Flight was about 35 miles Southwest of ZZZ and got a high oil temperature warning on number 1 engine. Crew followed QRH procedures and diverted to ZZZ. Crew throttled back number 1 engine but did not shut it down. Crew requested priority handling but did not request Crash; Fire and Rescue. Flight landed uneventfully and taxied to gate. Maintenance will be evaluating.




Synopsis: Dispatcher reported flight crew had an engine oil temperature high indication and the flight crew elected to divert and make a precautionary landing.
Date: 201811
Local time of day: 1801-2400
Aircraft: Challenger 650
Operator: Air Carrier
Operating under: Part 121
Flight phase: Taxi
Reporter organization: Air Carrier
Reporter function: Ramp
Human factors: Training / Qualification; Communication Breakdown
Anomaly: Deviation / Discrepancy - Procedural Published Material / Policy; Deviation / Discrepancy - Procedural Maintenance; Ground Event / Encounter Other / Unknown
Detector: Person Ground Personnel
When detected: Taxi
Contributing factors: Company Policy; Human Factors; Procedure
Primary problem: Human Factors

Narrative: I was dispatched to tow in Aircraft X that taxied in I got into tug and proceeded to Aircraft X in the taxi lane. I contacted the mechanics on board the aircraft via the radio asked for brakes to be set engines and hydraulics off. Mechanic confirmed brakes set engines and hydraulics off. I set the brake on the tug so I could rotate the seat to face the aircraft so I could capture and tow the aircraft into the hanger area to park him. As I turned the seat I saw the aircraft coming at me the aircraft jumped the cradle; hit the for control arms and stopped I then got out of the tug mechanics got out of the aircraft I again asked them if the brakes was set or if he lost brake pressure the mechanic told me he never set the brake handle he was just putting his feet on the brake pedals which is not SOP they are to set the brake handle.




Synopsis: Ground crew reported Maintenance crew member claimed to have set brakes prior to tug; did not and allowed the plane to roll into tug.
Date: 201503
Local time of day: 1201-1800
Location: ZLA.ARTCC, CA
Flight conditions: VMC
Light: Daylight
Aircraft: Challenger 300
Operator: Corporate
Operating under: Part 91
Flight plan: IFR
Mission: Personal
Flight phase: Descent
Airspace: Class A ZLA
ATC / advisory: Center ZLA
Reporter organization: Corporate
Reporter function: Pilot Flying; Captain
Reporter qualification: Flight Crew Multiengine; Flight Crew Instrument; Flight Crew Air Transport Pilot (ATP)
Second reporter function: First Officer
Anomaly: Conflict Airborne Conflict; Deviation - Altitude Overshoot; Deviation / Discrepancy - Procedural Hazardous Material Violation; Deviation / Discrepancy - Procedural Published Material / Policy; Deviation / Discrepancy - Procedural Clearance
Detector: Automation Aircraft Other Automation; Automation Aircraft RA; Automation Aircraft TA; Person Flight Crew
When detected: In-flight
Result: Flight Crew Took Evasive Action; Flight Crew FLC complied w / Automation / Advisory
Contributing factors: Human Factors; Procedure
Primary problem: Procedure

Narrative: ATC gave us a descent to FL340 while in a left hand turn from a heading of 170 to 330.  At roughly FL355; we received a TA on an aircraft left of our nose that we did not see and was not yet called out by ATC.  We queried ATC about the TA traffic and as ATC gave us information; we received an RA of 'adjust vertical speed'.  As Pilot Flying; I followed the RA commands in the cockpit and reduced our rate of descent and then visually acquired the traffic.  Once we received the 'clear of conflict' audio; I lowered the flight deck angle in order to continue descent while maintaining visual of the traffic.  I received an alert that I was 300 feet below our pre-selected altitude and quickly arrested the descent and climbed back to FL340.  Our cockpit indication was that we descended to FL335 at the low point before recovering back to FL340.  ATC contacted us and gave us the phone number to call.  After landing; we contacted ATC and they informed us that there was a 'loss of separation' of 800 feet and 3 nautical miles.  ATC's threshold is 1000 feet and 5 nautical miles.  We discussed the events that took place in the cockpit.  I informed ATC of our failure to level off at the assigned altitude after reacting to the RA and that both pilots were scanning outside the cockpit to gain a visual on the traffic.  We recognized our deficiency in maintaining an outside and inside scan throughout this evolution.  In the near term; we will brief our team and review the Pilot Flying and Pilot Monitoring duties and responsibilities when searching for traffic; reacting to RA's and when we are within 1000 feet of planned level off.


Second narrative: The secondary narrative contained no additional information.


Synopsis: While in a descent; cleared to FL330; the flight crew of a CL30 responded as directed to a TCAS TA followed shortly by an RA. Upon completion of the avoidance maneuver they continued their descent while monitoring the traffic visually. While doing so they inadvertently descended approximately 500 feet below their cleared altitude.
Date: 202004
Local time of day: 0001-0600
Flight conditions: VMC
Light: Night
Aircraft: Bombardier/Canadair Undifferentiated or Other Model
Operator: Corporate
Operating under: Part 91
Flight plan: VFR
Mission: Ferry / Re-Positioning
Flight phase: Final Approach
Reporter organization: Corporate
Reporter function: First Officer; Pilot Flying
Reporter qualification: Flight Crew Multiengine; Flight Crew Instrument; Flight Crew Air Transport Pilot (ATP)
Human factors: Situational Awareness
Second reporter function: Pilot Not Flying; Captain
Anomaly: Deviation - Altitude Overshoot; Ground Event / Encounter Ground Strike - Aircraft; Inflight Event / Encounter CFTT / CFIT
Detector: Person Flight Crew
When detected: In-flight
Result: Aircraft Aircraft Damaged
Contributing factors: Human Factors; Environment - Non Weather Related
Primary problem: Human Factors

Narrative: I was performing a repositioning flight. It was a clear moonless night. I was the Pilot Flying from the right seat. Before departure I briefed the Pilot Monitoring that I would be doing an RNAV approach because of the lack of visual guidance at this airport. I intercepted the final approach at the FAF and tracked it inbound; keeping the VPATH indicator perfectly centered. At approximately 400 ft. AGL I transitioned the visual keeping the GPS VPATH centered and just before touchdown at approximately 75 ft. AGL I heard a sound resembling the sound I have heard when I hit a bird. The Pilot Monitoring and I discussed the obvious - that we had contacted treetops. After a very normal landing and taxi to the FBO we discovered minor damage.


Second narrative: We receive the landing information and cancelled our radar coverage with Approach. There was no natural lighting (moonlight) to use and [the] runway does not have a VASI. We proceeded with care to landing point. At about 250 ft. and 1;000 ft. from the runway with good visibility of the runway we hit the top of a tree. The aircraft did not change attitude and the landing was uneventful. After a post flight I found small marks on the leading edge and grounded the aircraft till further inspection could be made.


Synopsis: Flight crew of a corporate jet reported hitting a tree top on a night visual approach.
Date: 202001
Location: ZZZ.Airport, CA
Aircraft: A320
Operator: Air Carrier
Operating under: Part 121
Flight phase: Takeoff / Launch
Aircraft component: Rudder Pedal
Component problem: Improperly Operated
Reporter organization: Air Carrier
Reporter function: Captain; Pilot Not Flying
Reporter qualification: Flight Crew Air Transport Pilot (ATP); Flight Crew Instrument; Flight Crew Multiengine
Anomaly: Flight Deck / Cabin / Aircraft Event Other / Unknown
Detector: Person Flight Crew
When detected: In-flight
Result: Flight Crew Overcame Equipment Problem
Contributing factors: Aircraft
Primary problem: Aircraft

Narrative: During the takeoff roll; a loose can of unopened Coca-Cola Zero rolled from behind the Captain's rudder pedals and stopped between the Captain's left foot and the left rudder pedal.  Since I was the Pilot Monitoring; I was able to remove the object and the takeoff was continued.  Had I been the Pilot Flying; this event would have resulted in a rejected takeoff. This object was not from our crew and was lost/loose at some time prior to us beginning our pre-flight duties for this flight. This event would have been a much greater threat to safe operations had anything else irregular happened during the takeoff roll.




Synopsis: A320 Captain reported that during the takeoff roll an unopened beverage can rolled from behind the rudder pedals and between his left foot and the rudder pedal. The Captain; who was the pilot monitoring; removed the can and the takeoff continued safely.