elihoole/asrs-aviation-reports huggingface dataset:
Date: 202104
Location: ZZZ.ARTCC, US
Flight conditions: VMC
Aircraft: Commercial Fixed Wing
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Cruise
Airspace: Class A ZZZ
ATC / advisory: Center ZZZ
Reporter organization: Air Carrier
Reporter function: Captain
Reporter qualification: Flight Crew Instrument; Flight Crew Air Transport Pilot (ATP); Flight Crew Multiengine
Human factors: Distraction; Situational Awareness
Anomaly: Deviation - Track / Heading All Types; Deviation / Discrepancy - Procedural Published Material / Policy; Deviation / Discrepancy - Procedural Clearance; Deviation / Discrepancy - Procedural FAR
Detector: Person Flight Crew
When detected: In-flight
Result: General None Reported / Taken
Contributing factors: Human Factors; Procedure; Environment - Non Weather Related
Primary problem: Environment - Non Weather Related

Narrative: Established on the F track and just prior to exiting radar service we instituted a 2 mile right offset as a SLOP.  This seemed routine to us until ATC asked if we were still on track to our next waypoint.  It then occurred to us that we should have not instituted SLOP until we were out of radar contact.  Both of us have flown very little this past year and although we are both veterans at flying [in State X]; the SOP here just did not properly come to mind.




Synopsis: Air carrier Captain reported a track heading deviation during cruise after instituting a 2 mile right offset as a SLOP while still under radar contact. Captain cited lack of flying as a contributing factor.
Date: 201810
Local time of day: 1201-1800
Location: DAB.TRACON, FL
Flight conditions: VMC
Weather elements / visibility: 10
Light: Daylight
Aircraft: Skyhawk 172/Cutlass 172
Operator: Personal
Operating under: Part 91
Flight plan: IFR
Mission: Personal
Flight phase: Cruise
Airspace: Class E DAB
ATC / advisory: TRACON DAB
Second aircraft: Skyhawk 172/Cutlass 172
Reporter organization: Personal
Reporter function: Pilot Flying; Single Pilot
Reporter qualification: Flight Crew Commercial; Flight Crew Instrument
Human factors: Situational Awareness; Communication Breakdown
Anomaly: Conflict NMAC
Detector: Person Flight Crew; Person Air Traffic Control
When detected: In-flight
Result: Air Traffic Control Issued Advisory / Alert; Flight Crew Took Evasive Action
Contributing factors: Human Factors
Primary problem: Human Factors

Narrative: While level at 4;000 feet on an Instrument Flight Rules flight plan the aircraft I was flying had a close call with a low wing single engine aircraft positioned 1-2 o'clock approaching head-on at same altitude. I; the pilot did not hear any radio calls by Approach Control regarding this traffic conflict well in advance until the other aircraft was approaching very close off the right side of the C172. The other aircraft made a sharp left climbing turn to avoid my aircraft while I dropped the nose to lose some altitude. It happened so quickly as I saw the traffic probably approximately 200-500 feet horizontal separation coming right at me as my aircraft flew past by him or her nearly missing my tail area by a vertical separation estimating approximately 50-100 feet or so; respectively. About 2-3 seconds prior I saw the other aircraft quickly approaching me; Approach was on the radio saying 'I was trying to give you traffic on somebody that just crossing on top of you; did you even see him?' At that point; I saw the aircraft REALLY close from my position and replied back to Approach I saw the traffic and that was a close one.' Approach Control frequency was congested and was blocked by multiple calls at times. Even though; I was flying a Cessna 172L Skyhawk with just basic flight instruments while IFR in VMC; I still need to have an effective visual scan in a highly concentrated airspace. Luckily a potential catastrophic event was avoided.




Synopsis: C172 pilot reported a near midair collision due to congested airspace and radios.
Date: 201412
Local time of day: 1801-2400
Location: I90.TRACON, TX
Flight conditions: VMC
Light: Dusk
Aircraft: EMB ERJ 145 ER/LR
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Flight phase: Descent
ATC / advisory: TRACON I90
Aircraft component: Autoflight System
Component problem: Malfunctioning
Reporter organization: Air Carrier
Reporter function: Pilot Not Flying; Captain
Human factors: Situational Awareness
Anomaly: Aircraft Equipment Problem Less Severe; Deviation - Track / Heading All Types; Deviation / Discrepancy - Procedural Clearance; Deviation / Discrepancy - Procedural Published Material / Policy
Detector: Person Flight Crew
When detected: In-flight
Result: Air Traffic Control Issued New Clearance
Contributing factors: Aircraft; Human Factors
Primary problem: Aircraft

Narrative: Flight filed the DRLLR3 arrival into IAH.  Upon [being] switched over to approach control with runway assigned and programmed in the FMS; aircraft continues to flying the arrival until DOMNO fix [when] ac took itself off LNAV mode and went into roll mode. Crew notify ATC of the situation; of which they are aware and had the crew fly a heading to re-intercept. ATC notified crew this is normal for [our] aircraft [type] or happens a lot for [company] aircraft.  This has happened a few times on this arrival with my crew coming into IAH.  There weren't any ghost fixes on the arrival once the runway was inputed into the FMS.  Crew review the arrival.




Synopsis: EMB-145 Captain reported that while flying the DRLLR3 RNAV to IAH his aircraft came out of LNAV and reverted to ROLL mode. Reporter commented this is not uncommon on this type aircraft.
Date: 201507
Local time of day: 1801-2400
Location: LAX.Airport, CA
Flight conditions: IMC
Light: Night
Aircraft: B737 Undifferentiated or Other Model
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Landing
ATC / advisory: Tower LAX
Reporter organization: Air Carrier
Reporter function: First Officer; Pilot Flying
Reporter qualification: Flight Crew Air Transport Pilot (ATP)
Human factors: Distraction
Anomaly: Inflight Event / Encounter Other / Unknown
Detector: Person Flight Crew
When detected: In-flight
Result: Flight Crew Returned To Clearance
Contributing factors: ATC Equipment / Nav Facility / Buildings; Equipment / Tooling; Human Factors; Weather
Primary problem: Equipment / Tooling

Narrative: During night flight and after break out at 200 feet and 1/2 mile or better; the new LED runway lights at 25L were so bright that the actual runway could not be seen normally. To clarify; the approach lights and runway outer marking lights may be bright; but the newer; high intensity runway centerline and landing threshold LED lights are far too bright for safe operation; and the high intensity; especially during hazy or foggy visibility conditions; makes it very difficult to actually see the runway itself.




Synopsis: Pilot reports of LED that are so bright that it was difficult to see the actual runway.
Date: 201910
Local time of day: 0601-1200
Location: ZZZZ.Airport, FO
Aircraft: A330
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Parked
Airspace: Class B LAX
Reporter organization: Air Carrier
Reporter function: Other / Unknown
Human factors: Situational Awareness
Anomaly: Deviation / Discrepancy - Procedural Published Material / Policy; Deviation / Discrepancy - Procedural Hazardous Material Violation
Detector: Person Ground Personnel; Person Other Person
When detected: Routine Inspection
Result: General Work Refused; General Maintenance Action
Contributing factors: Human Factors
Primary problem: Human Factors

Narrative: The electric skateboard (with Lithium[Ion] battery) was stopped/found in (security Xray); the board was offloaded from bag.




Synopsis: Airline Safety Officer reported skateboard with Lithium Ion battery loaded in checked baggage removed during security screening.
Date: 201503
Local time of day: 1801-2400
Location: ZZZ.Tower, US
Flight conditions: VMC
Weather elements / visibility: 10
Light: Night
Aircraft: Cessna Stationair/Turbo Stationair 6
Operator: Personal
Operating under: Part 91
Flight plan: None
Mission: Passenger
Flight phase: Initial Approach
Aircraft component: Reciprocating Engine Assembly
Component problem: Failed; Improperly Operated
Reporter organization: Personal
Reporter function: Captain; Pilot Flying
Reporter qualification: Flight Crew Commercial
Human factors: Human-Machine Interface; Situational Awareness
Anomaly: Aircraft Equipment Problem Critical; Inflight Event / Encounter Fuel Issue
Detector: Person Flight Crew
When detected: In-flight
Result: Flight Crew Diverted; Flight Crew Landed in Emergency Condition; General Maintenance Action
Contributing factors: Aircraft; Human Factors
Primary problem: Ambiguous

Narrative: The aircraft was topped off for a 3:45 flight. Fuel consumption was monitored and the engine leaned to between 14 and 15 GPH. Enroute and under an IFR flight plan with an instrument rated pilot; we diverted for fuel as a precaution. Conditions were VMC and we were cleared to land approximately five miles out. We cancelled IFR and I took command of the aircraft and the engine stopped producing power.  My copilot initiated E procedures and I trimmed for the best rate of glide and turned towards a lighted soccer field my left side. I advised ATC and immediately realized that I would not make the soccer field. The copilot saw a lighted two lane road off his side of the aircraft and took control of the aircraft. I completed the E checklist and put the flaps in when on final. The copilot landed without incident; damage to the aircraft; property on the ground or injury to the onboard passengers. The aircraft is in maintenance to have the fuel system calibrated.




Synopsis: C-206 Captain reports topping off his tanks for a 3 hour and 45 minute flight then running out of fuel 140 NM from destination. When a lighted soccer field became unreachable; the First Officer makes an off airport landing took place on a lighted two lane toad. No damage or injuries are reported.
Date: 202001
Local time of day: 0001-0600
Location: ZZZ.Airport, US
Flight conditions: VMC
Light: Night
Aircraft: A320
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Taxi
Reporter organization: Air Carrier
Reporter function: Pilot Flying; Captain
Reporter qualification: Flight Crew Air Transport Pilot (ATP); Flight Crew Instrument; Flight Crew Multiengine
Human factors: Communication Breakdown; Time Pressure
Anomaly: Deviation / Discrepancy - Procedural Published Material / Policy; Ground Event / Encounter Loss Of Aircraft Control
Detector: Person Flight Crew
When detected: Taxi
Result: Flight Crew Regained Aircraft Control; Flight Crew Took Evasive Action
Contributing factors: Aircraft; Procedure; Human Factors
Primary problem: Procedure

Narrative: I coordinated with the Ramp Agent for an early push off the gate; per his request; to ensure their understaffed ramp team could be ready for a subsequent arrival. During pushback; and after clearance to start engines by the Tug Operator; I advised the driver via interphone that we would be holding position on the ramp due to a controlled wheels up time. I queried to ensure there was room for the inbound aircraft to get to their gate. Shortly thereafter I felt the aircraft lurch and I instinctively applied brakes and queried the tug driver if they had a problem with the tug. The driver said no and that they were already disconnected from the aircraft. At no time after the 'Cleared to start engines' call did the push crew advise in accordance with SOP to 'Set brakes.'; nor give the standard tow bar phraseology 'Aircraft disconnected; by-pass pin removed.' After ensuring no one was in harm's way; no injury or damage occurred and clearing up the confusion with the tug driver regarding the lack of required phraseology; the 'Disconnect headset' command was given. As the tug driver backed away; one push crew member showed the tow bar disconnect pin and flag; and then the second team member gave the aircraft clear signal; but then turned and walked away towards their next arrival gate without waiting or noting the acknowledging light flash. The non-standard interphone and push procedures; possibly exacerbated by understaffing of this sub-contracted team; led to an inadvertent aircraft movement.




Synopsis: A320 Captain reported non standard procedures and communication caused the aircraft to roll away after towbar disconnect at push back completion.
Date: 201601
Local time of day: 0601-1200
Location: FTY.Airport, GA
Weather elements / visibility: Icing; 10
Light: Daylight
Aircraft: Robinson R22
Operator: Personal
Operating under: Part 91
Flight plan: None
Mission: Personal
Flight phase: Cruise
ATC / advisory: CTAF FTY
Second aircraft: Robinson R44
Reporter organization: Personal
Reporter function: Single Pilot
Reporter qualification: Flight Crew Private
Human factors: Situational Awareness
Anomaly: Conflict NMAC
Detector: Person Flight Crew
When detected: In-flight
Result: Flight Crew Took Evasive Action
Contributing factors: Human Factors
Primary problem: Human Factors

Narrative: While flying near Atlanta; another aircraft passed directly under only 200 (estimated) feet below with no radio contact. I was forced to increase altitude in order to increase aircraft separation distance.I had reported location and destination prior to this event.




Synopsis: R22 pilot reported an NMAC with another aircraft in the vicinity of Atlanta.
Date: 201507
Local time of day: 1201-1800
Location: ZZZ.Airport, US
Weather elements / visibility: Windshear; Rain
Light: Daylight
Aircraft: Beaver DHC-2
Operating under: Part 91
Flight plan: None
Mission: Passenger
Flight phase: Landing
Airspace: Class D ZZZ
ATC / advisory: Tower ZZZ
Reporter organization: Other FISHING LODGE
Reporter function: Single Pilot
Reporter qualification: Flight Crew Air Transport Pilot (ATP)
Human factors: Situational Awareness
Anomaly: Ground Event / Encounter Other / Unknown; Ground Excursion Runway; Inflight Event / Encounter Weather / Turbulence
Detector: Person Flight Crew
When detected: In-flight
Result: Aircraft Aircraft Damaged
Contributing factors: Weather; Human Factors; Airport
Primary problem: Weather

Narrative: I was returning guests/fishermen from a fishing location. The weather along the route was VFR with occasional rain (which reduced visibility to 3-4 miles). Approaching my destination I listened to the current ZZZ ATIS which was reporting wind from the north at 7 mph; few clouds at 3;500 feet; BKN at 5;500 feet and visibility greater than 10 miles with light rain. Considering the wind direction I decided to land to the north (on the river). During my approach I heard the controller reporting (to another landing traffic) of wind from the northwest. I saw the rain in the vicinity of my destination but didn't suspect it to be different from what I had encountered along my route of flight.Just before touching down I encountered what was probably a micro-burst with a wind shift and a torrential rain that hindered forward visibility through the windshield. I concentrated on my landing looking at the water through the side window and not being aware of the wind direction shift; to approximately 20 kts tailwind. Upon touching down and still 'on the step' I realized the situation and that I had no options left but to aim toward the furthest point of the river and shut off the engine. I hit the slope of the river bank with minimal force (though the ELT went off). There were no injuries and my 4 passengers immediately left the aircraft. There was no damage to the aircraft other than a small crack in the front of the right float.My main concern is that there is not much for me to learn from this event other than treating every landing as a new and unfamiliar location (and not relying solely on reports; including ATC).




Synopsis: A DHC2 floatplane pilot reports landing on a river and entering a microburst just before touch down. A tailwind results in a high touch down speed and insufficient time to stop before reaching the shore. Damage is minimal but contact with the shore activates the ELT.
Date: 202005
Light: Daylight
Aircraft: Commercial Fixed Wing
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Parked
Aircraft component: Portable Extinguisher
Component problem: Improperly Operated
Reporter organization: Air Carrier
Reporter function: Technician
Reporter qualification: Maintenance Powerplant; Maintenance Airframe
Human factors: Troubleshooting; Workload; Training / Qualification
Anomaly: Aircraft Equipment Problem Less Severe; Deviation / Discrepancy - Procedural FAR; Deviation / Discrepancy - Procedural Maintenance; Deviation / Discrepancy - Procedural Published Material / Policy
Detector: Person Maintenance
When detected: Other Storage
Result: General Maintenance Action
Contributing factors: Aircraft; Procedure; Manuals; Chart Or Publication
Primary problem: Chart Or Publication

Narrative: On or about [date]. I was working on Aircraft X returning to service from short term storage. I was made aware today that on work card XX-XX-XX step XX.a.Xa water fire bottles are not installed on company aircraft; for step Y; Halon extinguishers they were removed from aircraft and weighed per AMM XX-XX-XX for step Z the LAV bottles also were removed and weighed per AMM XX-XY-XX.




Synopsis: Technician reported errors and omissions in Work Cards relating to portable fire extinguishers on company aircraft being returned to service after storage.
Date: 201403
Local time of day: 1801-2400
Location: N90.TRACON, NY
Flight conditions: IMC
Weather elements / visibility: Snow; Rain; Icing; Fog; Thunderstorm; Windshear; Turbulence; 0
Aircraft: Gulfstream IV / G350 / G450
Operator: Corporate
Operating under: Part 91
Flight plan: IFR
Mission: Passenger
Flight phase: Descent
ATC / advisory: TRACON N90
Aircraft component: FMS/FMC
Component problem: Design
Reporter organization: Corporate
Reporter function: First Officer; Pilot Not Flying
Reporter qualification: Flight Crew Instrument; Flight Crew Air Transport Pilot (ATP); Flight Crew Multiengine
Human factors: Time Pressure
Second reporter function: Pilot Flying; Captain
Anomaly: ATC Issue All Types; Aircraft Equipment Problem Less Severe; Deviation - Track / Heading All Types; Deviation / Discrepancy - Procedural Published Material / Policy; Inflight Event / Encounter Weather / Turbulence
Detector: Person Air Traffic Control; Person Flight Crew
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: Human Factors; Procedure; Aircraft
Primary problem: Aircraft

Narrative: ATC instructed a descent to 6;000 FT by MUGZY Intersection; the weather was IMC zero visibility; ice; turbulence; etc. the aircraft was leveling at 6;000 FT when the Controller assigned holding at MUGZY. The aircraft was less than one minute from the holding fix and had a ground speed of 260 (220 Indicated). The crew loaded the hold and accepted the database recommendation which was right turns; however the hold is actually Left Turns. The crew ascertained the error. ATC requested a re entry which was accomplished without delay or issue. No separation of any type was lost. Contributing factors: The FMS Database is incorrect (subsequently the crew is advised that the approved software installed is not correct for many of these procedures this is / was unknown to the crew and is unacceptable). The Controller issued the hold without adequate time for the crew to load and verify the procedure. Although this event was not a safety issue it is certain that a chain of events occurred that could have a different outcome with minimal change to circumstance.


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


Synopsis: G-IV flight crew is issued a last minute hold at MUGSY; as depicted; on the LVZ4 arrival to TEB. The arrival chart shows left turns and the FMC shows a right turns which is accepted and executed. The FMC is not correct.
Date: 201812
Local time of day: 1801-2400
Location: ZZZ.ARTCC, US
Flight conditions: VMC
Aircraft: B777-200
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: Electrical Distribution
Reporter organization: Air Carrier
Reporter function: First Officer; Pilot Not Flying
Reporter qualification: Flight Crew Air Transport Pilot (ATP); Flight Crew Instrument; Flight Crew Multiengine
Anomaly: Aircraft Equipment Problem Critical; Deviation / Discrepancy - Procedural Maintenance
Detector: Automation Aircraft Other Automation; Person Flight Crew
When detected: In-flight
Result: Air Traffic Control Provided Assistance; Flight Crew Diverted; Flight Crew Landed As Precaution; Flight Crew Overcame Equipment Problem
Contributing factors: Aircraft
Primary problem: Aircraft

Narrative: We were operating flight from ZZZ to ZZZZ. The aircraft arrived from ZZZZ that day with numerous entries in the Aircraft Maintenance log book. ZZZ Maintenance worked to clear the issues (all electrical) including an engine run by the Captain and I while on the gate at ZZZ. We departed for ZZZZ within 10 min of our scheduled departure time. Approximately 2 hours into the flight we started observing several electrical issues including; flickering cabin lights; loss of all IFE's; failure to log onto CPDLC; failure of the SATCOM system; failure of all electrical door locking systems (cabin doors; boarding doors; galley; etc); and the electrical synoptic indicated the main left ac bus was without power. We were cruising at FL370. Smooth air and no mountain wave was reported. Our cruise airspeed was approximately 290K. Without notice; the airspeed jumped to 320 knots setting the overspeed warning clacker off and disconnecting the autopilot. We did not lose any altitude and the airspeed went back to our desired mach.  I'm not certain why this happened. The airplane had a lot of systems not functioning. I was buried in manuals and checklists at the time of the event. I have been in turbulence and mountain wave; experiencing plenty of airspeed fluctuations. This incident was very different and had no forewarning of the huge jump in airspeed. I think the Captain did a great job controlling the aircraft. We had compound events and cabin calls all happening at the same time. Perhaps calling the [Relief Pilot] up earlier from his crew break would have alleviated our workload. As the Pilot Monitoring; I could have done more monitoring. Like I stated above; I'm uncertain if this was a true overspeed or part of the electrical anomalies happening with this airplane. The aircraft is still unable to fly.




Synopsis: B777 First Officer reported critical electrical anomalies enroute resulting in unresolved multiple annunciations.
Date: 201508
Local time of day: 1201-1800
Location: ZZZ.Airport, US
Flight conditions: VMC
Light: Dusk
Aircraft: A319
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Initial Approach
Airspace: Class E ZZZ
ATC / advisory: TRACON ZZZ
Aircraft component: Trailing Edge Flap
Component problem: Malfunctioning
Reporter organization: Air Carrier
Reporter function: First Officer; Pilot Flying
Reporter qualification: Flight Crew Air Transport Pilot (ATP)
Anomaly: Aircraft Equipment Problem Less Severe
Detector: Person Flight Crew
When detected: In-flight
Result: Flight Crew Executed Go Around / Missed Approach; Flight Crew Overcame Equipment Problem; Flight Crew Landed in Emergency Condition
Contributing factors: Aircraft
Primary problem: Aircraft

Narrative: On approach I called for flaps 2 and the flaps jammed and were locked out at flaps 1 position. Discontinued the approach; climbed to 10;000 feet; held at the VOR and completed the QRH procedure; [advised ATC of the problem] and landed without incident.




Synopsis: A319 First Officer reported trailing edge flaps jammed and locked out at Flaps 1 position.