elihoole/asrs-aviation-reports huggingface dataset:
Date: 201507
Local time of day: 1201-1800
Location: IYK.Airport, CA
Flight conditions: VMC
Weather elements / visibility: clear; 10
Light: Dusk
Aircraft: Skyhawk 172/Cutlass 172
Operator: Personal
Operating under: Part 91
Flight plan: VFR
Mission: Training
Flight phase: Takeoff / Launch
ATC / advisory: CTAF IYK
Second aircraft: Small Transport; Low Wing; 2 Turbojet Eng
Reporter organization: Personal
Reporter function: Instructor; Pilot Not Flying
Reporter qualification: Flight Crew Flight Instructor; Flight Crew Instrument; Flight Crew Multiengine; Flight Crew Air Transport Pilot (ATP)
Human factors: Communication Breakdown
Anomaly: Conflict NMAC; Deviation / Discrepancy - Procedural Published Material / Policy; Ground Incursion Runway
Detector: Person Flight Crew
When detected: In-flight
Result: Flight Crew Took Evasive Action
Contributing factors: Airport; Environment - Non Weather Related; Human Factors
Primary problem: Human Factors

Narrative: Cessna 172 made CTAF 122.8 VHF radio call to enter Runway 33 for takeoff. Cessna 172 paused on runway as student prepared to add takeoff power. A helicopter operating on the east ramp made a direct west takeoff call. Cessna 172 immediately queried helicopter who then answered that he would hold position for Cessna. Cessna 172 added power for takeoff roll; at approximately 1;000-1;250 feet on takeoff roll instructor glanced down for instrument check and verify maximum power was set and flying speed attained. Student pilot began to rotate with instructor in backup position. Instructor noticed jet aircraft rapidly approaching in the opposite direction (Runway 15) on its takeoff roll at just past rotation in a moderate Angle of Attack (AOA) takeoff. Cessna 172 instructor immediately pushed nose over for evasive action and added slight left Angle of Bank (AOB) for lateral clearance. Estimated about 50 feet vertical as aircraft passed above and just right of the Cessna. Cessna 172 called on CTAF 122.8 to aircraft to identify with negative response. Cessna 172 queried helicopter if the jet was working with his photo group and for call sign but was not successful in communicating with departing jet. Communications were never established with the jet on Inyokern CTAF or on Joshua Approach. The jet was not on proper CTAF frequency; or was on frequency and did not make any radio calls. Runway end is not clearly visible during dusk conditions from the approach end.




Synopsis: C172 instructor pilot departing Runway 33 at IYK reports a NMAC with a departing jet on Runway 33. Evasive action is taken by the C172 instructor; at low altitude near midfield. CTAF procedures were in use and the reporter had communicated with a helicopter planning a departure but the jet pilot was apparently never on the CTAF.
Date: 201306
Aircraft: No Aircraft
Reporter organization: Air Carrier
Reporter function: Dispatcher
Reporter qualification: Dispatch Dispatcher
Human factors: Communication Breakdown; Distraction; Workload
Anomaly: No Specific Anomaly Occurred All Types
Detector: Person Dispatch
Result: General Maintenance Action
Contributing factors: Equipment / Tooling
Primary problem: Equipment / Tooling

Narrative: The computer system experienced a total failure. I was unable to flight follow or have any awareness of the flights assigned to me. The computer screens locked up so I was unable to gain access to the program created for this sort of incident. I was able to contact 2 of my airborne flights through the ATC Center they were in to advise them of our no-comm situation and to monitor [the communications network]. The backup laptops brought in failed to function at all. There was a hastened approach taken to work way ahead just in case the computers crashed again. Coincidentally; an on-duty Dispatcher was able to use his phone as a hotspot and sign in on his personal laptop during this incident. Although the system got back to functioning I thought there was a hastened approach taken to work ahead just in case the computers crashed again. This one hour plus incident was pretty exhausting for all of us and to rush into working ahead without a chance to take a break once things were restored should have been avoided I think.




Synopsis: Air Carrier Dispatcher describes a one plus hour computer outage and the difficulties encountered trying to work without it.
Date: 202012
Location: ZZZ.ARTCC, US
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; Pilot Flying
Reporter qualification: Flight Crew Air Transport Pilot (ATP); Flight Crew Instrument; Flight Crew Multiengine
Human factors: Communication Breakdown
Anomaly: Deviation / Discrepancy - Procedural Published Material / Policy; Flight Deck / Cabin / Aircraft Event Passenger Misconduct
Detector: Person Flight Attendant
When detected: In-flight
Result: General None Reported / Taken
Contributing factors: Company Policy; Human Factors; Environment - Non Weather Related
Primary problem: Environment - Non Weather Related

Narrative: About 2 hours into the flight; I received a call from A Flight Attendant that a passenger was told on 5 occasions to properly wear face mask and would not comply.  The situation never escalated to heated verbal exchanges or threats.  I informed the flight attendant to pass on to the passenger that the Captain will have law enforcement meet the aircraft upon gate arrival if he does not comply with policy on wearing of a face mask.  The passenger complied for the duration of the flight which had approximately 1 hour remaining.  I called ahead to have a Customer Service Agent meet the aircraft at gate arrival and talk with the passenger; which was done.Some passengers believe that certain policies regarding flying do not pertain to them.Keep backing up the flight crew when passenger disregard airline and FAA policy when on board an aircraft.




Synopsis: Air carrier Captain reported a passenger was not compliant with face mask policy.
Date: 202006
Local time of day: 0601-1200
Location: ZZZ.Airport, US
Light: Daylight
Aircraft: B737-700
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Parked
Reporter organization: Air Carrier
Reporter function: Pilot Not Flying; Captain
Reporter qualification: Flight Crew Air Transport Pilot (ATP)
Human factors: Communication Breakdown
Second reporter function: Pilot Flying; Captain
Anomaly: Aircraft Equipment Problem Less Severe; Deviation / Discrepancy - Procedural Published Material / Policy; Deviation / Discrepancy - Procedural Weight And Balance; Inflight Event / Encounter Fuel Issue
Detector: Person Flight Crew
When detected: Pre-flight
Contributing factors: Human Factors; Procedure
Primary problem: Human Factors

Narrative: The #2 thrust reverser was deferred under MEL (Minimum Equipment List) 78-1-01; which does not allow tanker fuel. Tanker fuel was added and planned by Dispatch and was not identified by Captain. Weather was good at departure and destination. We had a light load and performance was not an issue. Read the MEL in detail. Better communication about tankering fuel with an MEL from Dispatch.


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


Synopsis: Flight Crew operated 737-700 aircraft in violation of Minimum Equipment List restrictions.
Date: 201912
Local time of day: 0601-1200
Location: ZZZ.Airport, US
Flight conditions: VMC
Light: Dawn
Aircraft: Eurocopter AS 350/355/EC130 - Astar/Twinstar/Ecureuil
Operator: Air Taxi
Operating under: Part 135
Mission: Passenger
Flight phase: Parked
Airspace: Class B ZZZ
ATC / advisory: Ramp ZZZ
Aircraft component: Lifevest/Jacket
Component problem: Improperly Operated
Reporter organization: Air Taxi
Reporter function: Captain; Pilot Flying
Reporter qualification: Flight Crew Commercial; Flight Crew Instrument; Flight Crew Private
Human factors: Time Pressure; Communication Breakdown; Distraction
Anomaly: Deviation / Discrepancy - Procedural Published Material / Policy
Detector: Person Flight Crew
When detected: Routine Inspection
Result: General None Reported / Taken
Contributing factors: Human Factors
Primary problem: Human Factors

Narrative: I was scheduled for a flight to ZZZ1 from ZZZ. I did a routine pre-flight and ordered fuel. When I completed my inspections a fuel truck had still not arrived but I had relayed my fuel request through comm center so I went inside assuming I would be fueled. I gathered my passengers and briefed them for the flight; but when I turned on the master battery I found that I had not received fuel. The passengers and I returned inside the terminal while we waited for fuel. Upon returning to the aircraft once fueled I was trying to hurry to get out without further delay. I had already briefed the passengers so I seated them and helped them secure their safety belts. I closed the doors did a walk around and checked the fuel cap then continued on with my normal flight duties and took the passengers to ZZZ1. Upon exiting the aircraft I realized that the passengers were not wearing their PFD's. This was remedied before the return flight. Not confirming my fuel before a flight and assuming that it would be correct was the first error that I made. Following procedure would have alleviated this mistake. When your normal flow or checklist is interrupted I know that I should be especially careful to assure items are not skipped; but I did not do this on this event. Lastly when switching between flights that do not require a PFD and ones that do I should incorporate this into a personal checklist.




Synopsis: ECC-130 Captain reported becoming distracted during the preflight on the outbound flight and forgetting to check that passengers were wearing their Personal Flotation Device; PFD.
Date: 201702
Local time of day: 1801-2400
Location: SFO.Airport, CA
Aircraft: B737 Undifferentiated or Other Model
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Final Approach
Airspace: Class B SFO
ATC / advisory: TRACON NCT
Second aircraft: Light Transport; Low Wing; 2 Turbojet Eng
Reporter organization: Air Carrier
Reporter function: First Officer
Reporter qualification: Flight Crew Air Transport Pilot (ATP)
Human factors: Situational Awareness; Distraction; Workload
Anomaly: Conflict Airborne Conflict; Deviation - Altitude Excursion From Assigned Altitude; Deviation - Track / Heading All Types; Deviation / Discrepancy - Procedural Clearance
Detector: Automation Aircraft RA; Person Flight Crew
When detected: In-flight
Result: Air Traffic Control Issued New Clearance; Flight Crew Became Reoriented; Flight Crew Took Evasive Action
Contributing factors: Human Factors; Procedure
Primary problem: Human Factors

Narrative: On descent on the Bridge Visual approach to 28R at 4;500 feet and descending a business jet doing a visual approach to 28L overshot the center line of 28L and crossed underneath us at 500 once on the overshoot and once again while they corrected back to centerline of 28L. We complied with our RA and notified ATC about RA. About the same time Approach told us to level off to avoid a collision. We were always on our approach with no deviations. We had the airplane in site the whole time until he was underneath us and I commented how I didn't think he was going to make his turn and was going to overshoot. The Captain made an uneventful superb landing 28R.




Synopsis: A B737 First Officer reported that while flying the SFO 28R Bridge Visual; a business jet overshot Runway 28L centerline then flew 500 feet beneath them. The crew took evasive action to the TCAS RA then returned to profile for an uneventful approach.
Date: 202201
Local time of day: 0601-1200
Location: CVG.Airport, KY
Light: Daylight
Aircraft: B737 Next Generation Undifferentiated
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Climb
Airspace: Class B CVG
ATC / advisory: TRACON CVG
Second aircraft: Large Transport; Low Wing; 2 Turbojet Eng
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: Situational Awareness; Communication Breakdown
Anomaly: Deviation - Track / Heading All Types; Deviation / Discrepancy - Procedural Clearance; Inflight Event / Encounter Wake Vortex Encounter
Result: Air Traffic Control Issued New Clearance; Flight Crew Returned To Clearance
Contributing factors: Procedure; Environment - Non Weather Related; Human Factors
Primary problem: Human Factors

Narrative: During departure; we experienced some minor wake turbulence from a departing heavy aircraft.  While hand flying; I deviated 10 degrees right while navigating to the BONLE fix; but I didn't notify ATC as we were VFR.  When we asked for right turn direct to the next fix; we were queried if we were proceeding direct to BONLE fix.  We replied 'yes; but request direct JBNCH'.  The Controller; clearly confused of our current heading just gave us his own heading; and then cleared us to JBNCH less than a minute later.  No other conflict or deviation occurred.




Synopsis: B737NG Captain reported a track deviation occurred departing CVG when he turned off course to avoid wake turbulence.
Date: 201606
Local time of day: 1201-1800
Location: ZZZ.ARTCC, US
Flight conditions: IMC
Weather elements / visibility: Turbulence; Windshear; 0
Light: Daylight
Aircraft: M-20 J (201) / Allegro
Operator: Personal
Operating under: Part 91
Flight plan: IFR
Mission: Personal
Flight phase: Climb
Airspace: Class E ZZZ
ATC / advisory: Center ZZZ
Reporter organization: Personal
Reporter function: Single Pilot
Reporter qualification: Flight Crew Private; Flight Crew Instrument
Human factors: Distraction; Situational Awareness
Anomaly: Inflight Event / Encounter Weather / Turbulence; Inflight Event / Encounter Loss Of Aircraft Control
Detector: Person Flight Crew
When detected: In-flight
Result: Air Traffic Control Issued New Clearance; Flight Crew Regained Aircraft Control
Contributing factors: Weather
Primary problem: Weather

Narrative: I was flying in IMC conditions and encountered turbulence at 7;000 feet. I was cleared to 9;000 feet to avoid turbulence. I was climbing through 8;500 feet when I encountered severe turbulence. I lost control of the aircraft and descended to 5;600 before regaining control of the aircraft.




Synopsis: The pilot of a M20J reported a loss of control due to severe turbulence that resulted in a descent prior to regaining control.
Date: 201304
Local time of day: 1801-2400
Location: BWI.Airport, MD
Aircraft: B757-200
Operator: Air Carrier
Operating under: Part 121
Flight plan: VFR
Flight phase: Initial Climb
Airspace: Class B BWI
ATC / advisory: Tower BWI
Second aircraft: B737 Undifferentiated or Other Model
Reporter organization: Government
Reporter function: Approach; Departure
Reporter qualification: Air Traffic Control Fully Certified
Human factors: Situational Awareness
Anomaly: ATC Issue All Types; Deviation - Track / Heading All Types
Detector: Person Air Traffic Control
Result: General None Reported / Taken
Contributing factors: Human Factors; Procedure
Primary problem: Human Factors

Narrative: I was working on Local 1 position. I launched three departures; 3 miles apart without issuing any right turns. I then was told by the TRACON to stop all my departures because they were all runway heading; I responded that I one rolling so the TRACON told me to give him a left turn out to 330 degrees; which I did. I realized I had made a mistake; by not issuing the first aircraft a right turn out; which was a deviation; but if I had then turned the second and third aircraft it would have been a separation error. I just feel at that time my mind was somewhere else thinking about this furlough. The whole day had me upset because of the sequestration and furloughs; and this was the result!




Synopsis: Tower Controller described a failure to comply with local procedures with respect to departure headings listing preoccupation with 'furlough' concerns as a casual factor.
Date: 202111
Local time of day: 0001-0600
Location: ZZZ.Airport, US
Aircraft: Embraer Jet Undifferentiated or Other Model
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Initial Approach
Airspace: Class C ZZZ
ATC / advisory: Tower ZZZ
Reporter organization: Air Carrier
Reporter function: Pilot Not Flying
Reporter qualification: Flight Crew Instrument; Flight Crew Multiengine; Flight Crew Air Transport Pilot (ATP)
Anomaly: Deviation - Altitude Excursion From Assigned Altitude; Deviation / Discrepancy - Procedural Clearance; Deviation / Discrepancy - Procedural Published Material / Policy; Inflight Event / Encounter CFTT / CFIT; Inflight Event / Encounter Unstabilized Approach
Detector: Automation Aircraft Terrain Warning; Person Flight Crew
When detected: In-flight
Result: Flight Crew Overcame Equipment Problem; Flight Crew Took Evasive Action
Contributing factors: Human Factors
Primary problem: Human Factors

Narrative: On DATE I was pilot monitoring on Aircraft X ZZZ1-ZZZ. Upon arrival into ZZZ; we were being vectored for the right downwind for Runway XX. It was clear skies and good visibility. Shortly after passing the airport off our right; Tower asked us if we had the runway in sight and we did. We were then cleared for the visual XX. On our base turn we received a terrain alert. The FO (First Officer) disconnected the autopilot and started the climb. Not a second later the warning went away. We were still in a good position to land so we continued and landed normally.




Synopsis: Air carrier flight crew reported a CFIT event during a visual approach. Pilot initialed a climb which silenced terrain alert immediately.
Date: 202011
Local time of day: 1201-1800
Location: ZZZ.Tower, US
Aircraft: PA-28 Cherokee/Archer/Dakota/Pillan/Warrior
Operator: Personal
Operating under: Part 91
Flight plan: VFR
Flight phase: Climb
Airspace: Class D ZZZ
ATC / advisory: Tower ZZZ
Second aircraft: PA-28 Cherokee/Archer/Dakota/Pillan/Warrior
Reporter organization: Government
Reporter function: Local
Reporter qualification: Air Traffic Control Fully Certified
Human factors: Communication Breakdown; Confusion; Distraction; Situational Awareness
Anomaly: ATC Issue All Types; Conflict NMAC
Detector: Person Flight Crew
When detected: In-flight
Result: Air Traffic Control Issued Advisory / Alert; Flight Crew Took Evasive Action
Contributing factors: Human Factors; Aircraft
Primary problem: Aircraft

Narrative: I was on Local 2. The Local 1 controller coordinated a northbound [departure]. I approved the coordination outside of Aircraft Y which was just off the departure end climbing. Aircraft Y was in left closed traffic. Aircraft X turned immediately causing Aircraft Y to dive 100 ft. to miss Aircraft X.I quickly gave traffic and instructions to avoid the collision. Aircraft Y informed that there was only 50 ft. separation. I noticed Aircraft X turning and informed the Local 1 controller. He did nothing to control his aircraft or mediate the incident.This is not the first or 50th or last time this controller has not or will not control the aircraft on his frequency. He continously put aircraft in dangerous situations. He is lazy and subpar.




Synopsis: Tower Controller reported another tower controller wasn't doing their job correctly which led to a NMAC.
Date: 201708
Local time of day: 0601-1200
Location: LGA.Airport, NY
Light: Daylight
Aircraft: Regional Jet 900 (CRJ900)
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Final Approach
Airspace: Class B NYC
ATC / advisory: Tower LGA
Second aircraft: UAV - Unpiloted Aerial Vehicle
Reporter organization: Air Carrier
Reporter function: Captain; Pilot Flying
Reporter qualification: Flight Crew Air Transport Pilot (ATP)
Human factors: Situational Awareness
Anomaly: Conflict NMAC
Detector: Person Flight Crew
When detected: In-flight
Result: Flight Crew Requested ATC Assistance / Clarification
Contributing factors: Human Factors
Primary problem: Human Factors

Narrative: On short final; ILS Runway 4; I saw what appeared to be a big black object fly past the aircraft. Upon asking the first officer what he saw; he described in great detail in what was an unmanned drone at about 500 ft AGL. As soon as we touched down; we informed ATC of the aircraft and incident.




Synopsis: CRJ-900 Captain reported a NMAC with a UAV on short final to LGA Runway 4.
Date: 201908
Local time of day: 0601-1200
Location: ZZZ.Airport, US
Aircraft: Embraer Jet Undifferentiated or Other Model
Operator: Air Carrier
Operating under: Part 121
Flight phase: Parked
Reporter function: Dispatcher
Reporter qualification: Dispatch Dispatcher
Human factors: Communication Breakdown; Situational Awareness
Anomaly: Deviation / Discrepancy - Procedural FAR; Deviation / Discrepancy - Procedural Published Material / Policy
Detector: Person Dispatch
When detected: Aircraft In Service At Gate
Result: General None Reported / Taken
Contributing factors: Company Policy; Human Factors; Procedure
Primary problem: Company Policy

Narrative: Station posted a delay to this flight of 26 minutes in violation of the FARs and their manuals.




Synopsis: Dispatcher reported that station personnel posted a flight delay without notifying Dispatch.
Date: 201210
Local time of day: 1801-2400
Location: PHX.Airport, AZ
Aircraft: MD-83
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Flight phase: Descent
Airspace: Class E PHX
ATC / advisory: TRACON P50
Aircraft component: FMS/FMC
Component problem: Design
Reporter organization: Air Carrier
Reporter function: Pilot Not Flying; First Officer
Reporter qualification: Flight Crew Air Transport Pilot (ATP)
Human factors: Confusion; Communication Breakdown; Situational Awareness
Second reporter function: Captain; Pilot Flying
Anomaly: Aircraft Equipment Problem Critical; Deviation - Altitude Crossing Restriction Not Met; Deviation - Speed All Types; Deviation / Discrepancy - Procedural Published Material / Policy; Deviation / Discrepancy - Procedural Clearance
Detector: Person Flight Crew
When detected: In-flight
Result: Flight Crew Became Reoriented; Flight Crew FLC Overrode Automation; Flight Crew Returned To Clearance
Contributing factors: Aircraft; Human Factors; Procedure
Primary problem: Human Factors

Narrative: On STAR to PHX cleared to descend via the EGUL RNAV STAR; landing Runway 26. The Captain was flying pilot and selected VNAV on the FMS aircraft. VNAV made all crossings prior to VNMOM then suddenly could not keep up with the steep descent needed from HOMRR to VNMOM. We both noticed this and the Captain took corrective action but at VNMOM we were still 10 KTS fast and 2;500 high. Upon noticing that correction was needed the Captain got out of VNAV and made all the other restrictions in VS mode. No indication of any conflict with other aircraft.It is IMPORTANT TO GAUGE descent rates between points on arrival; we had four miles to lose 5;000 FT if we crossed HOMRR at 16;000 (chart says HOMRR 16;000 or below).


Second narrative: No substantive additional information was included in the secondary narrative.


Synopsis: An MD-83 fLight crew failed to comply with the crossing restriction at VNNOM when flying the EGUL RNAV STAR to PHX.