elihoole/asrs-aviation-reports huggingface dataset:
Date: 202104
Local time of day: 0601-1200
Location: ZZZ.Airport, US
Flight conditions: VMC
Weather elements / visibility: 10
Light: Daylight
Aircraft: Skylane 182/RG Turbo Skylane/RG
Operator: Personal
Operating under: Part 91
Flight plan: VFR
Mission: Personal
Flight phase: Cruise
Airspace: Class E ZZZ
ATC / advisory: TRACON ZZZ
Aircraft component: Engine
Component problem: Failed
Reporter organization: Personal
Reporter function: Pilot Flying; Single Pilot
Reporter qualification: Flight Crew Private
Anomaly: Aircraft Equipment Problem Critical; Ground Event / Encounter Fuel Issue
Detector: Person Flight Crew
When detected: In-flight
Result: Air Traffic Control Provided Assistance; Flight Crew Requested ATC Assistance / Clarification; Flight Crew Overcame Equipment Problem
Contributing factors: Aircraft
Primary problem: Aircraft

Narrative: Approximately 30 nm north on the 340 radial from ZZZ at 3;000 feet MSL engine failure was experienced.  Approximately 3 minutes prior to engine failure fuel tank selector was moved from both to left tank to compensate for uneven fuel burn.  Before and at the time of engine failure aircraft was on flight following with ZZZ approach.  Immediately upon experiencing engine failure ZZZ Approach was contacted and requested priority handling.  At this time; aircraft pitched for best glide speed and made 180 degree turn to ZZZZ.  Emergency procedures were followed; aircraft descended to 2;300 at 65 kts at which time fuel selector was placed back to both and engine power restored.  ZZZ Approach was contacted and made aware of restored engine power.  Aircraft climbed to 4;500 enroute to ZZZ to check and monitor systems circling over ZZZ.  Once definitive evidence showed that engine failure was related to fuel tank selector in left position and that all other systems were functioning normally ZZZ Approach was contacted and aircraft resumed heading from ZZZ to ZZZ1 at 4;500 with no further system failures.




Synopsis: C182 pilot reported the engine failed soon after switching the fuel tank selector from 'both' to 'left' position due to uneven fuel burn.  The pilot immediately pitched the aircraft for best glide speed; followed procedures; and was able to regain engine power when the fuel tank selector was placed back to 'both' position.
Date: 201401
Local time of day: 1201-1800
Location: CZQX.ARTCC, NF
Weather elements / visibility: Turbulence
Aircraft: B767-300 and 300 ER
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Flight phase: Cruise
ATC / advisory: Center CZQX
Reporter organization: Air Carrier
Reporter function: Pilot Flying; First Officer; Relief Pilot
Reporter qualification: Flight Crew Air Transport Pilot (ATP)
Human factors: Communication Breakdown
Anomaly: Deviation - Altitude Excursion From Assigned Altitude; Deviation - Speed All Types; Inflight Event / Encounter Loss Of Aircraft Control; Inflight Event / Encounter Weather / Turbulence
Detector: Person Flight Attendant; Person Flight Crew; Person Passenger
When detected: In-flight
Result: Flight Crew FLC Overrode Automation; Flight Crew Regained Aircraft Control; General Maintenance Action
Contributing factors: Weather
Primary problem: Weather

Narrative: Aircraft at cruise level 350 over southern tip of Greenland. Encountered continuous moderate and occasional severe turbulence. Vertical speed changes of +/- 800 feet; airspeed loss and gain in excess of 30 knots with near over speed from an established cruise of .78 mach; bank deviations in excess of 20 degrees; rapid and erratic autothrottle movement which had to be manually controlled and dampened. Left yaw damper disengaged during event and was later successfully reset. No injuries reported. Flight attendants in rear of aircraft reported lying on the floor and holding on to the base of seats in the rear of the aircraft to keep from being tossed about even though they were given several minutes of warning ahead of time to take their seats with the expectation of possible moderate turbulence ahead as had been reported by an aircraft 20 miles ahead on the track. The event lasted about 20 minutes total. Three other aircraft on the same track at different altitudes reported severe turbulence encounters with one declaring a PAN PAN PAN emergency and ultimately leaving the route. The event was reported to Maintenance and the aircraft was to be removed from service for inspection. The Captain was in the crew rest facility at the time of the event. I; the Relief Pilot; was acting as pilot flying and the other First Officer was acting as pilot not flying.




Synopsis: A B-767ER flight suffered an extended encounter with moderate to severe turbulence over the North Atlantic.  Upon arrival the aircraft was removed from service for an inspection.
Date: 201905
Aircraft: Commercial Fixed Wing
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Other Preflight loading
Reporter organization: Air Carrier
Reporter function: Other / Unknown
Human factors: Communication Breakdown
Anomaly: Deviation / Discrepancy - Procedural Published Material / Policy; Deviation / Discrepancy - Procedural Hazardous Material Violation
Detector: Person Ground Personnel
When detected: Routine Inspection
Result: General Maintenance Action
Contributing factors: Human Factors; Procedure
Primary problem: Procedure

Narrative: The Cargo Planner called stating that two hazmat items were staged for flight.  Ramp loaded only one item due to the DG limit. Both items were held off by Trainer. I called Dispatch and advised we have hazmat onboard and I will send a revised pilot notification to crew.




Synopsis: Airline Ramp Loader reported correcting erroneous Hazmat documents and providing corrected Hazmat data to flight crew.
Date: 202112
Local time of day: 1201-1800
Location: ZZZ.Airport, US
Flight conditions: VMC
Light: Daylight
Aircraft: B787-900
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Takeoff / Launch; Taxi
Airspace: Class B ZZZ
ATC / advisory: Tower ZZZ
Aircraft component: Powerplant Fuel Valve
Component problem: Malfunctioning
Reporter organization: Air Carrier
Reporter function: First Officer; Pilot Not Flying
Reporter qualification: Flight Crew Instrument; Flight Crew Air Transport Pilot (ATP); Flight Crew Multiengine
Human factors: Troubleshooting
Second reporter function: Captain; Pilot Flying
Anomaly: Aircraft Equipment Problem Less Severe; Deviation / Discrepancy - Procedural Published Material / Policy; Ground Event / Encounter Fuel Issue
Detector: Person Flight Crew
When detected: Taxi
Result: Flight Crew Returned To Gate; General Maintenance Action
Contributing factors: Aircraft
Primary problem: Aircraft

Narrative: In position and hold with park brake set; master caution; followed by L ENG failure and L ENG fuel valve EICAS. Ran checklist and returned to gate.


Second narrative: While in position and hold; idle power. Left engine failed; we had a MEL XX-XX not sure MEL had any bearing on event.


Synopsis: Flight Crew reported while in position and holding; the Left Engine failed and they returned to the gate for maintenance.
Date: 201808
Location: ZZZ.Airport, US
Aircraft: Commercial Fixed Wing
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Other Load Planning
Reporter organization: Air Carrier
Reporter function: Other / Unknown
Human factors: Communication Breakdown
Anomaly: Deviation / Discrepancy - Procedural Published Material / Policy
Detector: Person Ground Personnel
When detected: Pre-flight
Result: General None Reported / Taken
Contributing factors: Company Policy; Procedure
Primary problem: Procedure

Narrative: ZZZ informed [Load Planner] that no DSTG [Departure Staging Guide] qualified employees working for morning departures. ZZZ expected [Load Planner] to close out these morning departures. As always; [Load Planner] assisted station with close-outs.ZZZ Supervisor contacted [Load Planner] again [a week later] for the same issue.




Synopsis: Load Planner reported inadequate qualified staffing available for morning departures.
Date: 202009
Local time of day: 0601-1200
Location: ZZZ.Airport, US
Flight conditions: VMC
Aircraft: Skyhawk 172/Cutlass 172
Operator: FBO
Operating under: Part 91
Mission: Training
Flight phase: Initial Climb
Airspace: Class D ZZZ
ATC / advisory: Tower ZZZ
Aircraft component: Engine
Component problem: Malfunctioning
Reporter organization: FBO
Reporter function: Pilot Flying; Instructor
Reporter qualification: Flight Crew Commercial; Flight Crew Flight Instructor; Flight Crew Instrument; Flight Crew Multiengine
Human factors: Troubleshooting
Anomaly: Aircraft Equipment Problem Critical
Detector: Person Flight Crew
When detected: In-flight
Result: Flight Crew Landed in Emergency Condition
Contributing factors: Aircraft
Primary problem: Aircraft

Narrative: After perform my run up; got clearance to take off. Checked heading indicator; RPM; engine pressure and temperature and rise of airspeed; Took off at Vr at about 500-600 feet AGL; Scanned my Fuel; Engine P and T; and RPM as usual.Perceived; RPM was fluctuating with partial power (2100-2200 RPM) with full throttle forward. Engine had an issue.Processed; I had enough altitude; to make 180 with partial power to west parallel runway with 9;000 ft. length+ fire engine available (best site for land). It would be best idea to try [to] land in there.Performed; [advised ATC and set] pitch and trim for Vglide. Upon approval of Tower; made easy bank back to RWY; once aligned to the RWY; dropped flap one at a time while maintaining airspeed; picked visual aiming point; slipped to lose altitude while maintaining airspeed flared; and landed safe.Communicated after taxiing out from runway to full stop with Ground. Shut off the engine as ordered following procedure; communicated to firefighters of what happened; determined aircraft can be taxied back to ramp safely; taxi back to ramp with caution; shut off engine again for inspection. No injuries to crew and passenger; no damages to aircraft/property. Safe on deck.




Synopsis: C172 pilot reported engine problems on climb and made a precautionary landing.
Date: 201202
Local time of day: 0601-1200
Location: ZZZ.Airport, US
Light: Daylight
Aircraft: MD-83
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Flight phase: Cruise
Airspace: Class A ZZZ
ATC / advisory: Center ZZZ
Aircraft component: INS / IRS / IRU
Component problem: Failed
Reporter organization: Air Carrier
Reporter function: Pilot Not Flying; First Officer
Anomaly: Aircraft Equipment Problem Critical
Detector: Person Flight Crew
When detected: In-flight
Result: General Declared Emergency; General Maintenance Action
Contributing factors: Aircraft
Primary problem: Aircraft

Narrative: During cruise we experienced a fault with the #2 IRU. Performed the procedures outlined in the QRH checklist and the problem was corrected. Approximately 15 minutes later; the copilots PFD and ND lost attitude; heading; map; etc information. The flight directors on both sides were lost and the autopilot also failed. The Captain's side Map display also failed. I checked the standby compass and confirmed the Captain's heading information appeared correct. He continued to hand fly using the VOR. We declared an emergency and relayed the status of our flight information display and navigation capability to ATC. We were given vectors and flew a visual approach to an otherwise uneventful landing.




Synopsis: MD83 First Officer experiences an IRU fault during cruise which is corrected using QRH procedures. Fifteen minutes later the IRU fails completely. An emergency is declared and the flight continues to destination uneventfully.
Date: 201904
Local time of day: 1801-2400
Location: SCT.TRACON, CA
Aircraft: Gulfstream V / G500 / G550
Flight plan: IFR
Flight phase: Descent
Airspace: Class E SCT
ATC / advisory: TRACON SCT
Reporter organization: Government
Reporter function: Approach
Reporter qualification: Air Traffic Control Fully Certified
Human factors: Communication Breakdown; Situational Awareness; Training / Qualification
Anomaly: ATC Issue All Types; Deviation - Altitude Excursion From Assigned Altitude; Deviation - Altitude Overshoot; Deviation / Discrepancy - Procedural Clearance; Inflight Event / Encounter CFTT / CFIT
Detector: Person Air Traffic Control
When detected: In-flight
Result: General None Reported / Taken
Contributing factors: Human Factors
Primary problem: Human Factors

Narrative: On initial contact we reduced Aircraft X's speed then descended them to 063. They read back 036 and we missed it as a training team. They checked on to Tustin descending to 036 and they missed it as well. The pilot descended into the MVA and we lost separation with the MVA. We need to pay attention to the pilot read back.




Synopsis: SCT TRACON Controller reported a read back error that resulted in an aircraft descending below the Minimum Vectoring Altitude.
Date: 201905
Location: ZZZ.Airport, US
Aircraft: B737 Undifferentiated or Other Model
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Taxi
Reporter organization: Air Carrier
Reporter function: Captain; Pilot Not Flying
Reporter qualification: Flight Crew Air Transport Pilot (ATP); Flight Crew Instrument; Flight Crew Multiengine
Human factors: Communication Breakdown
Anomaly: Deviation / Discrepancy - Procedural Hazardous Material Violation
Detector: Person Flight Crew
When detected: Taxi
Result: General Flight Cancelled / Delayed; General Maintenance Action; General Work Refused
Contributing factors: Human Factors; Procedure
Primary problem: Procedure

Narrative: After boarding and departing the gate on time; we taxied to the runway and never received our final weights.  When we queried Operations and Dispatch; we were told to return to the gate because 'Hazmat was improperly loaded'.  Once back at the gate; we were told that baggage needed to be loaded around the cargo in question.  When this was completed; we asked why we had not received a dangerous goods notification.  The Supervisor could not provide us an answer; so in the interest of not delaying further; we decided to have the cargo in question removed and depart without it.




Synopsis: B-737 Captain reported a communications breakdown with Dispatch and Ramp Supervisor regarding onboard Hazmat resulting in Hazmat cargo removal prior to departure.
Date: 201703
Local time of day: 0601-1200
Location: ZZZ.TRACON, US
Flight conditions: IMC
Weather elements / visibility: Icing; Rain
Light: Daylight
Aircraft: EMB ERJ 145 ER/LR
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Climb
Airspace: Class C ZZZ
ATC / advisory: TRACON ZZZ
Aircraft component: Aerofoil Ice System
Component problem: Failed
Reporter organization: Air Carrier
Reporter function: Captain; Pilot Not Flying
Reporter qualification: Flight Crew Air Transport Pilot (ATP)
Second reporter function: Pilot Flying; First Officer
Anomaly: Aircraft Equipment Problem Less Severe; Deviation / Discrepancy - Procedural Published Material / Policy; Inflight Event / Encounter Weather / Turbulence
Detector: Person Flight Crew
When detected: In-flight
Result: Flight Crew Returned To Departure Airport
Contributing factors: Aircraft; Weather
Primary problem: Aircraft

Narrative: On climb out around 7000 ft we had wing A/I (Anti-ice) fail then Ice cond A/I inop warning then we had BLEED 1 leak. We ran the QRH and returned to [the departure airport]. We [advised ATC]; we could not burn excess fuel in the weather and icing without our anti-icing protection so we ran the overweight landing checklist and landed about 1000 lbs overweight.  [This aircraft] had been written up numerous times for similar anti icing problems and bleed problems over the preceding days. It is clear that the source of the problem had not been fixed.


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


Synopsis: EMB-145 Crew reported anti-ice equipment failure on climb out in icing conditions and returned for overweight landing to departure airport.
Date: 202007
Location: ZZZ.TRACON, US
Flight conditions: VMC
Light: Dusk
Aircraft: Small Aircraft
Operator: Personal
Operating under: Part 91
Flight plan: None
Mission: Personal
Flight phase: Cruise
Airspace: TFR ZZZ
ATC / advisory: TRACON ZZZ
Aircraft component: Electronic Flt Bag (EFB)
Component problem: Malfunctioning
Reporter organization: Personal
Reporter function: Pilot Flying; Single Pilot
Reporter qualification: Flight Crew Commercial; Flight Crew Instrument; Flight Crew Multiengine
Human factors: Human-Machine Interface; Situational Awareness
Anomaly: Aircraft Equipment Problem Less Severe; Airspace Violation All Types
Detector: Person Air Traffic Control
When detected: In-flight
Contributing factors: Human Factors; Aircraft
Primary problem: Aircraft

Narrative: I packed my ForeFlight trip on my iPad and headed from ZZZ1 - ZZZ. I picked up flight following as I left ZZZ1 in order to climb through ZZZ2 airspace. I leveled off at 4;500 feet and stayed with ZZZ Approach for about 50 miles. I proceeded to cancel flight following and flew down the X River en route to ZZZ. ForeFlight did not notify me of the TFR. When I landed at ZZZ airport; the Airport Manager gave me a number to call for intruding on the TFR. I've flown this exact route dozens of times and filed flight plans or picked-up flight following every time a TFR was in effect. When I called the number given to me by the airport manager; I was told that I was the second person that night that said ForeFlight was not reporting/displaying TFRs. I'm concerned that there may be a bug in ForeFlight that is causing the software to fail to display TFRs. I will cross check with WingX Pro to ensure TFR status before flying this route again; and I'll maintain VFR flight filing to mitigate this risk in the future. I'm filing this report in case there's an issue with ForeFlight not connecting with the TFR database and properly displaying TFRs on the ForeFlight map.




Synopsis: GA pilot reported inadvertently entering a TFR when the TFR failed to display on his ForeFlight-equipped iPad.
Date: 201410
Flight conditions: VMC
Aircraft: A320
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Cruise
Reporter organization: Air Carrier
Reporter function: Dispatcher
Reporter qualification: Dispatch Dispatcher
Anomaly: Deviation / Discrepancy - Procedural Published Material / Policy; Deviation / Discrepancy - Procedural FAR
Detector: Person Dispatch
When detected: In-flight
Result: General None Reported / Taken
Contributing factors: Staffing
Primary problem: Staffing

Narrative: While working sector got a message to all dispatchers stating needed to move some Airbus flights to different desks due not having enough qualified A320 dispatchers.  Assumed meant maybe would get a few more releases to work up for later in shift. About :15 later an already enroute flight was added to DV for me to flight follow. No briefing was given on its status; just thrown onto my desk. Flight was in air 2 hours without a qualified A320 dispatcher exercising operational control. So to sum up---No operational control for 2 hours---no briefing to myself as assuming operational control of flight just tossed at me---and the biggest issue: Why is [company] not being more diligent about what dispatchers are able to assume what desks with what flights?




Synopsis: Air carrier Dispatcher reported operational control issues related to insufficient staffing.
Date: 201412
Local time of day: 0001-0600
Location: ABR.Airport, SD
Flight conditions: IMC
Weather elements / visibility: Fog; 1
Light: Night
Aircraft: Cessna Aircraft Undifferentiated or Other Model
Operating under: Part 91
Flight plan: IFR
Flight phase: Taxi
ATC / advisory: CTAF ABR
Reporter function: Pilot Flying; Single Pilot
Reporter qualification: Flight Crew Instrument; Flight Crew Multiengine; Flight Crew Air Transport Pilot (ATP)
Anomaly: Ground Excursion Taxiway
Detector: Person Flight Crew
When detected: Taxi
Contributing factors: Environment - Non Weather Related; Weather; Airport
Primary problem: Weather

Narrative: Between Taxiways B and F at the NW ramp area prior to each taxiway bordering the grass; does not have taxiway lighting (blue); unlike further to the north and south. The grass area was frozen with ice and unlit and unable to discern where the concrete ends and grass (iced over) begins.The aircraft was taxied away from the hangar area to avoid prop blast and after run-up while vacating the ramp toward the takeoff runway; moved forward off the concrete area and became stuck on the iced covered grass. Aircraft was shut down and removed by company personnel; without incident.Contributing Factors:This area is not lit either by ramp lighting or taxiway lighting and the grass area is not protected by markings discernible in the winter. There are no cones; or other protective devices between the entrances to taxiway B or F.The PIC was unfamiliar with that area of the airport only having completed 1 flight in a similar aircraft alone from this location previously.




Synopsis: A Cessna pilot taxiing for a night time takeoff at ABR; inadvertently exited the ramp hard surface between taxiways B and F; and became mired in the grass surface. The lack of area and/or edge taxiway lighting; as well as the grass obscured by ice; were cited as contributing factors.
Date: 201906
Aircraft: Any Unknown or Unlisted Aircraft Manufacturer
Operator: Air Carrier
Operating under: Part 121
Flight phase: Parked
Reporter organization: Air Carrier
Reporter function: Quality Assurance / Audit
Human factors: Situational Awareness; Communication Breakdown; Confusion; Training / Qualification
Anomaly: Deviation / Discrepancy - Procedural Published Material / Policy; Deviation / Discrepancy - Procedural Maintenance
Detector: Person Other Person
When detected: Other During Maintenance
Result: General None Reported / Taken
Contributing factors: Company Policy; Procedure; Human Factors; Equipment / Tooling
Primary problem: Human Factors

Narrative: Through several LOSA (Line Operations Safety Audit) observations; technicians are becoming complacent about fall prevention. In one example; technicians were performing an APU (Auxiliary Power Unit) change. The side rails to prevent a fall were removed from the cargo king being used. In another example; technicians were changing a door slide on an Airbus. A cargo king was used and positioned adjacent to the door requiring the slide change. The platform was raised to allow the technicians to perform the removal/installation. The platform entry safety chains were not put into place to prevent a fall. These occurrences occurred on midnight shifts were technicians could potentially be more susceptible to falling.




Synopsis: Aircraft Maintenance Technicians were observed working without proper safety precautions.