elihoole/asrs-aviation-reports huggingface dataset:
Date: 201509
Local time of day: 0601-1200
Location: LSZH.Airport, FO
Flight conditions: VMC
Aircraft: Large Transport; Low Wing; 2 Turbojet Eng
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Takeoff / Launch
ATC / advisory: Center LSAS
Reporter organization: Air Carrier
Reporter function: First Officer; Pilot Flying
Reporter qualification: Flight Crew Air Transport Pilot (ATP)
Human factors: Training / Qualification; Distraction; Confusion; Communication Breakdown; Situational Awareness
Second reporter function: Pilot Not Flying; First Officer
Anomaly: Deviation - Speed All Types; Deviation - Track / Heading All Types; Deviation / Discrepancy - Procedural Clearance; Deviation / Discrepancy - Procedural Published Material / Policy
Detector: Person Flight Crew
When detected: In-flight
Result: Flight Crew Returned To Clearance
Contributing factors: Human Factors
Primary problem: Human Factors

Narrative: I was the flying pilot. During the preflight set up; I positioned my V1 and Vr bugs at an incorrect setting that was at least 10 knots below where they should have been. Because of my unfamiliar and uncomfortable use of the preflight checklist I did not catch my error when the preflight checklist was read. We took off on Runway 16; the SID VEBIT_3S requires an aggressive tight turn to the left starting 'at 2000 feet but not before KLO 1.0 DME.' During the Takeoff roll I began to rotate at my incorrectly set Vr speed. The Captain put his hand on the yoke and said something like 'don't rotate yet'. I delayed the rotate until he said 'rotate'. My sight picture was strange and I was suffering from some poor situational awareness. This led to a slow reaction when we reached the SID turn point. I initiated the turn at about 2.0 DME and passing about 3000 feet MSL. As we had briefed I kept the speed at V2 +15 and used an aggressive AOB of 25deg - 30deg until we were heading toward BREGO. The rest of the flight was uneventful.


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


Synopsis: The First Officer set his airspeed bugs incorrectly; resulting in an early rotation which was corrected by the Captain. The resulting confusion and distraction led to a late turn on the departure.
Date: 201808
Local time of day: 1201-1800
Location: ZZZZ.Airport, FO
Flight conditions: VMC
Aircraft: B777-200
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Flight phase: Takeoff / Launch
Aircraft component: Hydraulic System Lines; Connectors; Fittings
Component problem: Malfunctioning
Reporter organization: Air Carrier
Reporter function: Pilot Flying; Captain
Reporter qualification: Flight Crew Multiengine; Flight Crew Instrument; Flight Crew Air Transport Pilot (ATP)
Second reporter function: First Officer; Pilot Not Flying
Anomaly: Aircraft Equipment Problem Less Severe
Detector: Person Flight Crew
When detected: In-flight
Result: Flight Crew Landed in Emergency Condition; Flight Crew Returned To Departure Airport
Contributing factors: Aircraft; Human Factors
Primary problem: Aircraft

Narrative: It was a normal takeoff. After the gear handle was selected to the up position; we heard an unusual noise; followed by an EICAS MSG 'HYD QTY LOW C.' After switching to departure control we got vectors. The aircraft PF (Pilot Flying) duties were transferred to the FO (First Officer). We started running the appropriate checklist. Eventually we got an additional EICAS MSG 'HYD PRESS SYS C.' That checklist was run; in addition to the non-routine Landing checklist and the Overweight Landing checklist. A call was made to the Flight Attendants to explain the situation; and a PA was made to the passengers to explain the situation. A message was sent to Dispatch via ACARS and a tug was requested. Coordination was accomplished with Approach and Tower. After accomplishing a landing assessment for our conditions knowing we had enough runway; even though we were overweight; we did not dump fuel. PF duties were transferred back to the Captain and a landing was made back at [departure airport]. After stopping on the runway; Tower requested we shut down all engines. The airport safety personnel accessed our plane. We were tugged to a hard stand.I understand there was a failure in one of the hydraulic lines.


Second narrative: Flight experienced center hydraulic failure upon gear retraction. After checklist procedures; the aircraft returned to land overweight. Improper crew coordination resulted in the lack of a logbook entry.


Synopsis: B777 flight crew reported returning to the departure airport after a HYD QTY LOW C EICAS message was received upon gear retraction.
Date: 201703
Local time of day: 1201-1800
Location: ZZZ.Airport, US
Flight conditions: VMC
Light: Daylight
Aircraft: Lancair Legacy
Operator: Personal
Operating under: Part 91
Flight plan: VFR
Mission: Personal
Flight phase: Landing
Airspace: Class D ZZZ
ATC / advisory: Tower ZZZ
Reporter organization: Personal
Reporter function: Pilot Flying; Single Pilot
Reporter qualification: Flight Crew Private; Flight Crew Instrument; Flight Crew Multiengine
Anomaly: Ground Event / Encounter Ground Strike - Aircraft
Detector: Person Flight Crew
When detected: In-flight
Result: Aircraft Aircraft Damaged; Flight Crew Became Reoriented
Contributing factors: Human Factors
Primary problem: Human Factors

Narrative: I took a VFR flight to ZZZ. After checking in with ZZZ tower I was instructed to enter left downwind for Runway XXR. I entered the pattern on a left downwind and lowered my landing gear abeam numbers as I usually do. Shortly after I was told by tower that I would be following a Cessna traffic two mile final. Anticipating a long downwind; I retracted my landing gear and requested tower to call my base. All was smooth and as expected from downwind to final when tower called out traffic that was landing at the same time on Runway XXL. I continued a vigorous visual lookout for traffic to short final. Over the threshold I did a visual check to confirm I had 3 greens. Not seeing green lights; I visually confirmed gear handle in up position and at the same time applied power. As the airplane slowed its descent and started to climb; I heard a loud sound outside of the aircraft. At this point I decided going around would not be a safe option. After the gears were fully lowered and locked; I confirmed ample runway available for a safe landing and performed a smooth; safe landing exiting the runway. After contacting ground controller; I then taxied to transient area via Alpha taxiway and shut down. When I inspected the aircraft after landing; I noticed that the propeller had been damaged.




Synopsis: Lancair Legacy pilot reported a propeller strike when he noticed he did not have three green lights on short final. He added power and lowered the gear for a safe landing.
Date: 201506
Location: ZZZ.Airport, US
Weather elements / visibility: Thunderstorm
Aircraft: Any Unknown or Unlisted Aircraft Manufacturer
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: Dispatcher
Anomaly: Deviation / Discrepancy - Procedural FAR; Deviation / Discrepancy - Procedural Published Material / Policy
Detector: Person Dispatch
When detected: In-flight
Result: General None Reported / Taken
Contributing factors: Equipment / Tooling
Primary problem: Equipment / Tooling

Narrative: Flight was holding due to severe thunderstorms.  The decision was made to divert to ZZZ1.  The first error occurred while trying to divert to ZZZ1.  I received [an aircraft performance error].  I was unable to divert the flight at all; requiring the Chief to be called over to resolve the issue.  The second error was far more substantial.  After we diverted to ZZZ1; weather began to build over the field and other aircraft began to go around.  The crew decided it was best to divert to ZZZ2.  I was unable to provide a new release or landing data due to numerous [software] errors. When I tried to divert from ZZZ1 to ZZZ2 [software] said [the diversion was already entered and it needed a non-stop entry].  After entering [non-stop]; I was still unable to divert the flight to ZZZ2.  Without performing the [data entry] properly; I was unable to release the flight to ZZZ2.  I was not able to provide the crew with an updated release; or landing data.  We were never able to get [software] to show the flight diverting to ZZZ2.  The aircraft landed in ZZZ2 without any updates; or release to ZZZ2.  It took numerous managers and the chief to get this issue sorted out and show the aircraft on the ground in ZZZ2.




Synopsis: An air carrier Dispatcher reported multiple problems with his software program that prevented him from properly handling a flight that encountered weather and diverted to another destination.
Date: 202003
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: Flight Attendant (On Duty)
Reporter qualification: Flight Attendant Current
Human factors: Confusion
Anomaly: Deviation / Discrepancy - Procedural Published Material / Policy
Detector: Person Flight Attendant
When detected: Aircraft In Service At Gate
Result: General None Reported / Taken
Contributing factors: Company Policy; Environment - Non Weather Related; Procedure
Primary problem: Procedure

Narrative: Aircraft X on 2 hour turn. Was told that during COVID-19 Pandemic all surfaces are to be wiped down by the cleaners. Surfaces include tray tables; countertops; and armrests among the items in question. Did not see cleaners wipe down any surfaces other than countertops. Was advised by Union Stewards to report any deviation from cleaning instructions briefed to technicians.




Synopsis: Flight Attendant reported witnessing the aircraft's cleaning crew did not follow Covid-19 procedures and only sanitized the galley counter tops.
Date: 202007
Local time of day: 1201-1800
Location: ZZZ.Airport, US
Flight conditions: VMC
Light: Daylight
Aircraft: B767 Undifferentiated or Other Model
Operator: Air Carrier
Operating under: Part 121
Mission: Passenger
Flight phase: Parked
Aircraft component: Nose Gear Wheel
Component problem: Improperly Operated
Reporter organization: Air Carrier
Reporter function: Technician
Reporter qualification: Maintenance Airframe; Maintenance Powerplant
Human factors: Confusion; Time Pressure
Anomaly: Aircraft Equipment Problem Critical; Deviation / Discrepancy - Procedural Maintenance; Deviation / Discrepancy - Procedural Published Material / Policy
Detector: Person Maintenance
When detected: Routine Inspection
Result: General Maintenance Action
Contributing factors: Incorrect / Not Installed / Unavailable Part; Human Factors; Aircraft; Procedure
Primary problem: Procedure

Narrative: On Aircraft X found left nose landing gear tire worn to limits; removed and replaced left nose gear tire I.A.W. (In Accordance With) B767 AMM 32-45-02 and serviced tire to 175 psi.During shop vist found nose landgear tire from Aircraft X to still had tang washer installed on tire and not to be installed on tire on aircraft.




Synopsis: Technician reported discovering the tang washer on the old nose tire and wheel assembly instead of reinstalled on the aircraft after a tire change.
Date: 201409
Local time of day: 1201-1800
Location: 0W3.Airport, MD
Flight conditions: VMC
Weather elements / visibility: 10
Light: Daylight
Aircraft: Small Aircraft; Low Wing; 1 Eng; Fixed Gear
Operator: Personal
Operating under: Part 91
Flight plan: None
Mission: Other Glider Towing
Flight phase: Landing
Airspace: Class G 0W3
Reporter organization: Personal
Reporter function: Pilot Flying; Single Pilot
Reporter qualification: Flight Crew Private
Human factors: Distraction; Situational Awareness; Time Pressure
Anomaly: Inflight Event / Encounter Bird / Animal
Detector: Person Flight Crew
When detected: In-flight
Result: Flight Crew Executed Go Around / Missed Approach; Flight Crew Took Evasive Action
Contributing factors: Airport; Environment - Non Weather Related; Procedure; Human Factors
Primary problem: Procedure

Narrative: At 0W3 with multiple skydive operation had skydivers turn over the active runway at 200-400 feet.  On two occasions I had to execute an aggressive go around. Discussed the matter with the skydive operation and the pattern continued except jumpers would land at the edge of the runway.




Synopsis: A pilot reported having to execute two aggressive go-arounds because of skydivers turning over the 0W3 runway at 200 - 400 FT.
Date: 201911
Local time of day: 0601-1200
Weather elements / visibility: Turbulence
Aircraft: B737 Undifferentiated or Other Model
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Landing
Airspace: Class A ZZZ
Aircraft component: Air Conditioning and Pressurization Pack
Component problem: Malfunctioning
Reporter organization: Air Carrier
Reporter function: Passenger
Human factors: Situational Awareness
Anomaly: Aircraft Equipment Problem Less Severe; Deviation / Discrepancy - Procedural Published Material / Policy; Flight Deck / Cabin / Aircraft Event Smoke / Fire / Fumes / Odor
Detector: Person Passenger
When detected: In-flight
Result: Air Traffic Control Provided Assistance; Flight Crew Diverted; Flight Crew Landed in Emergency Condition; Flight Crew Overcame Equipment Problem
Contributing factors: Aircraft
Primary problem: Aircraft

Narrative: Something was burning on our plane and we had to make an precautionary landing. We were given safety instructions; including the brace position; which we need to hold during landing. Before takeoff; we were told that there were computer and HVAC problems. There were clearly electrical wiring problems and I would like to know if there has been an investigation on this plane; and what is the outcome of the report.




Synopsis: Passenger on flight reported 'burning fumes' resulting in a diversion.
Date: 202009
Local time of day: 0001-0600
Location: FAI.TRACON, AK
Aircraft: UAV - Unpiloted Aerial Vehicle
Operator: Government
Operating under: Other 107
Flight plan: VFR
Flight phase: Final Approach
Second aircraft: Helicopter
Reporter organization: Government
Reporter function: Enroute
Reporter qualification: Air Traffic Control Fully Certified
Human factors: Communication Breakdown; Situational Awareness
Anomaly: ATC Issue All Types; Deviation / Discrepancy - Procedural Published Material / Policy
Detector: Person Air Traffic Control
When detected: In-flight
Result: Air Traffic Control Issued Advisory / Alert
Contributing factors: Human Factors
Primary problem: Human Factors

Narrative: Our LOA / COA with the UAS operators states they are required to establish 2 way communication and ATC approval prior to exiting R-XXXX. They are restricted to the recovery route called the Green Route; specifically designed to remain clear of 2 military airport finals in case of a lost link emergency scenario. Aircraft X exited R-XXXX on the green route; with Aircraft Y in trail; without establishing communications and approval with FAI approach. The controller attempted different frequencies; MAINS; STBYs; RTR's; and even guard calls with no success. Finally; the controller had to call FBK ATCT to request the call sign of the chase aircraft. The controller was successful in reaching the chase aircraft and had the chase aircraft relay to Aircraft X to contact approach. By the time communication was established; Aircraft X was 8.59 miles outside of R-XXXX; inbound to FBK on the green route. Follow the COA / LOA; or update it with more current operations since it is over 2 years old.




Synopsis: ATC reported a loss of communication with a UAV and its chase aircraft.
Date: 201207
Local time of day: 1201-1800
Location: ZZZ.ARTCC, US
Aircraft: A320
Operator: Air Carrier
Operating under: Part 121
Flight phase: Cruise
Airspace: Class A ZZZ
ATC / advisory: Center ZZZ
Reporter organization: Air Carrier
Reporter function: Dispatcher
Reporter qualification: Dispatch Dispatcher
Anomaly: Inflight Event / Encounter Fuel Issue
Detector: Person Flight Crew
When detected: In-flight
Result: Air Traffic Control Issued New Clearance; General Declared Emergency
Contributing factors: Airspace Structure; Procedure
Primary problem: Procedure

Narrative: VIP movement [resulted in] ATC hold; EFC 20 minutes; held 20 minutes; given another 20 minutes airborne hold; unable to hold; declared emergency fuel and landed [with] 4;500 LBS; reserve fuel 3;199 LBS.




Synopsis: Dispatcher reported an aircraft was holding because of VIP operations; but finally had to declare a fuel emergency when the delay dragged on.
Date: 201203
Local time of day: 0001-0600
Location: ZJX.ARTCC, FL
Flight conditions: IMC
Weather elements / visibility: Thunderstorm; Turbulence
Aircraft: Commercial Fixed Wing
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Climb
Airspace: Class E ZJX
ATC / advisory: Center ZJX
Reporter organization: Air Carrier
Reporter function: Pilot Not Flying
Human factors: Situational Awareness; Communication Breakdown; Time Pressure; Workload
Anomaly: Deviation - Track / Heading All Types; Deviation / Discrepancy - Procedural Clearance; Inflight Event / Encounter Weather / Turbulence
Detector: Person Flight Crew
When detected: In-flight
Result: Flight Crew Took Evasive Action; General Declared Emergency
Contributing factors: Airspace Structure; Weather; Environment - Non Weather Related; Procedure
Primary problem: Weather

Narrative: On initial climb out we were given a climb to 16;000 and a heading of 240; and handed off to JAX Center. We were unable to contact JAX Center due to frequency congestion and were forced to turn the aircraft to a heading of 180 to avoid level 5 convective activity at our 12 o'clock position. At that time we attempted to declare an emergency but were not sure if the Controller ever received it. At a later time the Controller handed us off and our flight resumed uneventfully.




Synopsis: An Air Carrier crew was unable to contact ATC during the climb and because of level 5 convective activity they declared an emergency in the blind; changed course to avoid the severe weather and ATC said nothing at the frequency change.
Date: 202002
Local time of day: 1201-1800
Location: ZZZ.Airport, US
Flight conditions: VMC
Weather elements / visibility: 10
Light: Daylight
Aircraft: Skyhawk 172/Cutlass 172
Operator: FBO
Operating under: Part 91
Flight plan: None
Mission: Training
Flight phase: Cruise
Second aircraft: Small Aircraft; High Wing; 1 Eng; Fixed Gear
Reporter organization: FBO
Reporter function: Single Pilot; Pilot Flying
Reporter qualification: Flight Crew Private; Flight Crew Instrument
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 practicing commercial maneuvers in the practice area during the initial climb of a lazy eight; I observed a tail wheel aircraft approximately 100 ft. vertically and 100 ft. horizontally from our aircraft. I immediately made an evasive climbing maneuver to avoid the aircraft. The aircraft was not observed on ADSB [and] did not make radio calls for the practice area.




Synopsis: C172 pilot reported an NMAC in the practice area.
Date: 202103
Local time of day: 1201-1800
Location: DAB.Tower, FL
Aircraft: Small Aircraft
Operator: Personal
Operating under: Part 91
Flight plan: IFR
Mission: Personal
Flight phase: Descent
Airspace: Class C DAB
ATC / advisory: TRACON DAB
Second aircraft: Any Unknown or Unlisted Aircraft Manufacturer
Reporter organization: Government
Reporter function: Approach; Instructor
Reporter qualification: Air Traffic Control Fully Certified
Human factors: Confusion; Distraction; Training / Qualification; Workload; Situational Awareness
Anomaly: ATC Issue All Types; Conflict Airborne Conflict; Deviation / Discrepancy - Procedural Published Material / Policy; Ground Event / Encounter Ground Equipment Issue; Inflight Event / Encounter CFTT / CFIT
Detector: Person Air Traffic Control
When detected: In-flight
Result: Air Traffic Control Issued New Clearance
Contributing factors: Airspace Structure; Human Factors; ATC Equipment / Nav Facility / Buildings; Manuals; Procedure
Primary problem: Procedure

Narrative: Aircraft X was descended to 3;000 feet by the trainee with control from the adjacent TRACON sector. We didn't talk to him soon enough to offer a 30 degree intercept for the RNAV Approach.  We vectored him back around after requesting control from the other TRACON again. We were discussing assigning 2;000 feet to Aircraft Y landing at a different airport. The trainee turned Aircraft X heading 340; which I questioned and suggested heading 270. When the trainee issued the amended heading; she also descended Aircraft X to 2;000 feet. I did not catch it as during the same time; the trainee had released Aircraft Y off one airport and Aircraft Z off another airport; who were in conflict; in addition to an air carrier departure requesting practice approaches. I took over the frequency; and noticed Aircraft X already at 2;000 feet but he was not quite established on the approach and therefore; assigned an altitude below the Minimum Vectoring Altitude. When doing something out of the ordinary  the controller trying to help could also put the aircraft on a better heading to intercept especially when we never approved the aircraft descending to 3;000 feet. Offer Aircraft X a different RNAV approach or offer to run the approach for the lows. The Low Altitude Alert never alarmed.




Synopsis: TRACON Controller conducting on the job training reported they did not hear the trainee descend an aircraft to an altitude below the Minimum Vectoring Altitude because they were distracted by the trainee releasing aircraft off airports that were on conflicting routes.
Date: 201504
Local time of day: 1801-2400
Location: LAX.Airport, CA
Flight conditions: VMC
Light: Night
Aircraft: B737-700
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Initial Climb; Takeoff / Launch
Airspace: Class B LAX
ATC / advisory: TRACON SCT
Reporter organization: Air Carrier
Reporter function: Pilot Flying; Captain
Reporter qualification: Flight Crew Air Transport Pilot (ATP)
Human factors: Situational Awareness
Second reporter function: Pilot Not Flying; First Officer
Anomaly: Deviation - Track / Heading All Types; Deviation / Discrepancy - Procedural Clearance; Deviation / Discrepancy - Procedural Published Material / Policy
Detector: Person Air Traffic Control
When detected: In-flight
Result: Air Traffic Control Issued New Clearance; Flight Crew Became Reoriented
Contributing factors: Human Factors; Procedure
Primary problem: Human Factors

Narrative: During the pre-departure briefing; while comparing our CDU route to the PDC; both pilots read the SID from the filed line; and missed the SID change to -VTU5- in the line directly above.  Upon check-in with SoCal on departure; we confirmed that we thought we were cleared for the CASTA 4 Departure; but after checking the PDC in-flight; we realized our error.SoCal re-cleared us via runway heading; expect radar vectors RZS..AVE..PXN.PXN3 Arrival.  Due to the later; evening departure traffic was light in that sector and there were no known conflicts.There is no reason to list the filed route in the PDC clearance.  Recommend listing only the actual cleared route in its entirety point-by-point.  Eliminating the unnecessary information would declutter the PDC and clarify exactly the route cleared by ATC.


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


Synopsis: A B737-700 flight crew reported they flew the wrong departure out of LAX when they failed to catch a routing change in the PDC.