elihoole/asrs-aviation-reports huggingface dataset:
Date: 202007
Local time of day: 0001-0600
Location: DFW.Airport, TX
Aircraft: Commercial Fixed Wing
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Taxi
ATC / advisory: Tower DFW
Second aircraft: Commercial Fixed Wing
Reporter organization: Air Carrier
Reporter function: Captain; Pilot Flying
Reporter qualification: Flight Crew Air Transport Pilot (ATP)
Human factors: Other / Unknown; Troubleshooting
Anomaly: Conflict Ground Conflict; Less Severe; Deviation / Discrepancy - Procedural Clearance; Ground Incursion Taxiway
Detector: Person Flight Crew
When detected: Taxi
Result: General None Reported / Taken
Contributing factors: Airport; Chart Or Publication; Environment - Non Weather Related; Procedure
Primary problem: Ambiguous

Narrative: I'm writing this report because I observed a third occurrence of this happening yesterday while holding behind two aircraft on J; short of the turn for EG.  After getting their weather reroute; the first aircraft in line on J (an Aircraft Y) was told to make the turn to hold short at EG.  Aircraft Z was already holding short #1 on EG.  Aircraft Y taxied to right of; but not quite abeam thankfully of Aircraft Z and stopped when they saw how close they were.  Aircraft Y was stopped near that painted EG box I keep mentioning.  They then asked Tower if they could move over to EH which they could because no one was there.  Pilots are used to three hold points for 17R; but EF is temporarily closed for construction north of the pad.  When they see an aircraft already holding at the northern-most point and are told to hold short EG; they attempt to hold to the right of what they think is EF.  Also; there's a painted EG box about where in their minds will put them on EG between EF and EH.  That painted EG box is for telling aircraft on L that the turn onto EG is approaching.  I think a sequence sign-in message  would be most effective.  Having seen this now on three different flights; am I the only guy reporting this?  I'll bet DFW Tower can confirm this is occurring with some frequency.




Synopsis: Air carrier Captain reported witnessing re-occurring confusion from pilots at taxiways EH and EG in DFW airport.
Date: 202012
Local time of day: 0601-1200
Location: ZZZ.Airport, US
Aircraft: Light Transport; Low Wing; 2 Turboprop Eng
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Other destination unload
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 Hazardous Material Violation; Deviation / Discrepancy - Procedural Published Material / Policy
Detector: Person Flight Crew
When detected: Other post flight
Result: General Maintenance Action
Contributing factors: Human Factors
Primary problem: Human Factors

Narrative: Onboard the aircraft was a piece of Hazmat which I was unaware of.  The company manifest did not disclose it and I was not notified by any company personnel.  I am unsure of when the piece was loaded; if it was during the preload process or while I was present.  Upon finding the Hazmat during aircraft unloading; I reported it to Dispatch.




Synopsis: Captain reported the transport of undocumented Hazmat package.
Date: 201710
Local time of day: 1201-1800
Location: MEM.Airport, TN
Flight conditions: VMC
Aircraft: Widebody Transport
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Flight phase: Final Approach
Airspace: Class B MEM
ATC / advisory: Tower MEM
Second aircraft: Large Transport
Reporter organization: Government
Reporter function: Local
Reporter qualification: Air Traffic Control Fully Certified
Human factors: Situational Awareness; Time Pressure
Anomaly: ATC Issue All Types; Conflict Airborne Conflict; Deviation / Discrepancy - Procedural Clearance; Deviation / Discrepancy - Procedural Published Material / Policy; Ground Incursion Runway
Detector: Person Air Traffic Control
When detected: In-flight
Result: Air Traffic Control Separated Traffic; Air Traffic Control Issued New Clearance; Flight Crew Executed Go Around / Missed Approach
Contributing factors: Procedure; Airspace Structure; Human Factors
Primary problem: Procedure

Narrative: Aircraft Z was on a visual approach to Runway 27; Aircraft Y was ready to depart Runway 36L; Aircraft X was on a visual approach to Runway 36L. Aircraft Z was asked to keep his speed up as much as possible. Aircraft X was told to continue and reduce to final approach speed. Aircraft Y was instructed to line up and wait and told about the traffic and when he could expect to depart. Aircraft X was also informed when to expect landing clearance. Once Aircraft Z crossed the Runway 27 threshold and touched down Aircraft Y was cleared for takeoff. Aircraft Y was airborne about midfield when I observed Aircraft X initiate a go-around. Aircraft X immediately started a left hand turn; but never verbally communicated a pilot initiated go-around. I instructed Aircraft Y to fly runway heading and climb and maintain 5;000 feet so as not to conflict with Aircraft X in the left turn. I then instructed Aircraft X to turn left heading 270 and climb and maintain 3;000 feet.If I had not waited for Aircraft Z to touch down and used the Arrival Departure Window (ADW) procedure more effectively Aircraft Y would have been further down the runway thus possibly negating the need for Aircraft X to initiate a go-around. Also; I could have just waited to depart Aircraft Y.




Synopsis: MEM Tower Local Controller reported they had to issue last minute instructions to separate an arriving aircraft which initiated a go-around just as a departure was airborne.
Date: 201505
Local time of day: 1201-1800
Location: ZZZ.Airport, US
Flight conditions: VMC
Light: Daylight
Aircraft: Skyhawk 172/Cutlass 172
Operator: FBO
Operating under: Part 91
Mission: Training
Flight phase: Climb
Airspace: Class C ZZZ
ATC / advisory: TRACON ZZZ
Aircraft component: Reciprocating Engine Assembly
Component problem: Malfunctioning
Reporter organization: FBO
Reporter function: Instructor
Reporter qualification: Flight Crew Flight Instructor; Flight Crew Commercial
Anomaly: Aircraft Equipment Problem Less Severe
Detector: Person Flight Crew
When detected: In-flight
Result: Air Traffic Control Issued New Clearance; Aircraft Equipment Problem Dissipated; Flight Crew Landed As Precaution; Flight Crew Took Evasive Action; Flight Crew Returned To Departure Airport
Contributing factors: Aircraft
Primary problem: Aircraft

Narrative: During run-up procedures there was nothing that showed abnormal with the aircraft. Run-up mag check was within limitations and fuel tanks were sumped without any indications of water or contaminates in the fuel. Short field takeoff showed engine instruments in the green before release of the brakes. Climb out with full throttle on a 050 heading we were passed to approach at 1;500 feet and they cleared us for 2;500 feet. While continuing to climb at 1;800 feet; the engine had a large RPM drop and backfired. After 3-4 seconds the engine restored power. Returned to the field and landed without assistance.




Synopsis: C172 Instructor pilot experiences a backfire and a large RPM drop climbing through 1;800 feet. The reporter immediately turns back to the departure airport and lands uneventfully with the engine running.
Date: 201812
Local time of day: 0601-1200
Location: ZZZ.Airport, US
Flight conditions: VMC
Light: Daylight
Aircraft: A320
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Takeoff / Launch
Airspace: Class B ZZZ1
ATC / advisory: Tower ZZZ
Reporter organization: Air Carrier
Reporter function: Pilot Not Flying; Captain
Reporter qualification: Flight Crew Flight Engineer; Flight Crew Instrument; Flight Crew Air Transport Pilot (ATP); Flight Crew Multiengine
Human factors: Situational Awareness
Anomaly: Aircraft Equipment Problem Less Severe
Detector: Person Flight Crew
When detected: In-flight
Result: Flight Crew Diverted
Contributing factors: Aircraft
Primary problem: Aircraft

Narrative: On departure; gear failed to retract. Diverted to ZZZ1 for landing.




Synopsis: A320 Captain reported the landing gear failed to retract after takeoff that resulted in a diversion.
Date: 201602
Local time of day: 1201-1800
Location: DTO.Airport, TX
Flight conditions: VMC
Light: Daylight
Aircraft: PA-34-200 Seneca I
Operator: FBO
Operating under: Part 91
Flight plan: None
Mission: Training
Flight phase: Landing
Airspace: Class D DTO
ATC / advisory: Tower DTO
Reporter organization: FBO
Reporter function: Instructor
Reporter qualification: Flight Crew Flight Instructor; Flight Crew Commercial; Flight Crew Instrument; Flight Crew Multiengine
Human factors: Situational Awareness
Anomaly: Conflict NMAC
Detector: Person Flight Crew
When detected: In-flight
Result: Flight Crew Became Reoriented; Flight Crew Executed Go Around / Missed Approach; Flight Crew Took Evasive Action
Contributing factors: Human Factors
Primary problem: Human Factors

Narrative: We were in the left traffic pattern for runway 36 at DTO. This was a training flight in [a] Seneca and my student told tower that he had our traffic in sight; but was tracking the wrong plane. We were on left downwind turning base and came within 500 feet of another aircraft on a 2 mile final for runway 36. We turned out to the right and went around to avoid the other aircraft. Our plane was not equipped with TCAS or any traffic advisory system.




Synopsis: PA-34 Instructor Pilot reported an NMAC in the pattern at DTO.
Date: 201209
Local time of day: 0001-0600
Location: ZSE.ARTCC, WA
Aircraft: Skylane 182/RG Turbo Skylane/RG
Operator: Corporate
Operating under: Part 91
Flight plan: VFR
Flight phase: Climb
ATC / advisory: Center ZSE
Reporter organization: Government
Reporter function: Enroute
Reporter qualification: Air Traffic Control Fully Certified
Human factors: Human-Machine Interface
Anomaly: ATC Issue All Types
Detector: Person Air Traffic Control
When detected: In-flight
Result: General None Reported / Taken
Contributing factors: ATC Equipment / Nav Facility / Buildings
Primary problem: ATC Equipment / Nav Facility / Buildings

Narrative: A C182 called for flight following so I assigned a code. When the data block acquired onto the beacon code it began flashing conflict with what appeared to be the aircraft's previous 1200 code even though they had already switched to the newly assigned code. The altitudes were about 300 to 400 FT apart between the conflict code and the aircraft. I had keyed up to give a traffic alert but then the ghost target went away so I never gave it. This happens randomly and is very disconcerting for the pilots and controllers when you issue a traffic alert for an aircraft at the same location/merged and same altitude. It is impossible to tell the pilot an alternative course of action when the targets are merged! Which way do you tell him to go? This seems to happen about once out of every 15-20 call ups for VFR flight following. We need to find out why this happens and then prevent future occurrences.




Synopsis: ZSE Controller described an on going problem of an aircraft conflicting with itself and activating a 'Conflict Alert' when changed from a VFR code to an IFR code.
Date: 201409
Local time of day: 1201-1800
Location: NCT.TRACON, CA
Light: Daylight
Aircraft: Helicopter
Flight phase: Cruise
Airspace: Class D PAO
ATC / advisory: TRACON NCT
Reporter organization: Government
Reporter function: Approach
Reporter qualification: Air Traffic Control Fully Certified
Human factors: Communication Breakdown; Confusion; Workload
Anomaly: Airspace Violation 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 Provided Assistance
Contributing factors: Airspace Structure; Human Factors; Procedure
Primary problem: Procedure

Narrative: Aircraft X called for VFR flight following to SFO from south of Mt. Diablo. I issued a code and identified the aircraft. As the aircraft transitioned the OAK finals toward the bay; I pointed it out to the Woodside sector and initiated a hand off to SFO tower assuming that it would proceed down the bay and direct to SFO. As the aircraft passed the vicinity of SJC and PAO; it proceeded on a more southerly course and was leaving my airspace. I inquired if the pilot was still inbound to SFO. At this point OAK traffic was building and I determined that the Woodside sector could provide better services to the aircraft. I initiated a hand off to Woodside; which was accepted and issued the aircraft a frequency change. As the aircraft was proceeding south it flew into the PAO tower airspace with no request from the aircraft or coordination by me. Prior to my issuing the frequency change without my noticing; the aircraft proceeded to SFO without further incident.Getting the aircraft intended route of flight to SFO would have resolved all problems and allowed for the proper controllers to handle the flight.




Synopsis: NCT Controller reports of an aircraft under flight following and isn't sure of the routing the aircraft is flying. Aircraft enters PAO's Class Delta but isn't pointed out to the Tower.
Date: 201505
Aircraft: Any Unknown or Unlisted Aircraft Manufacturer
Operator: Air Carrier
Flight phase: Parked
Reporter organization: Air Carrier
Reporter function: Other / Unknown
Anomaly: Ground Event / Encounter Other / Unknown
Detector: Person Ground Personnel
When detected: Pre-flight
Result: General Maintenance Action
Contributing factors: Human Factors
Primary problem: Human Factors

Narrative: Employee was starting unhooking process of Air Conditioning (AC) air hose; as employee kneeled under fuselage the aircraft air pack units started operation and immediately sucked the employee's hat into the intake.  Tech Ops had to come out to open up the left air pack unit to get the hat out of the system; there were no injuries and no damage to the aircraft.




Synopsis: The reporter stated a ground employee's hat was sucked into a pack inlet during ground operations.
Date: 201603
Local time of day: 1801-2400
Location: IAH.Airport, TX
Flight conditions: VMC
Light: Night
Aircraft: A320
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Initial Approach
Airspace: Class E I90
ATC / advisory: TRACON I90
Aircraft component: FMS/FMC
Component problem: Malfunctioning
Reporter organization: Air Carrier
Reporter function: Captain; Pilot Not Flying
Reporter qualification: Flight Crew Air Transport Pilot (ATP)
Second reporter function: First Officer; Pilot Flying
Anomaly: Aircraft Equipment Problem Less Severe; Deviation - Altitude Crossing Restriction Not Met; Deviation - Altitude Excursion From Assigned Altitude; Deviation / Discrepancy - Procedural Published Material / Policy
Detector: Person Flight Crew
When detected: In-flight
Result: Flight Crew FLC Overrode Automation
Contributing factors: Aircraft
Primary problem: Aircraft

Narrative: Cleared to descend via the DRLLR landing 26R. 6000 set correctly in FCU window. DES mode used. Both pilots separately and completely checked each altitude restriction. Two separate times PF had to use full speed brakes for altitude corrections; and waypoints correctly showed orange indicating crossing problems. At our request ATC cleared us runway 27 by descending via the DRLLR4 runway 27 except maintain 6000; and after DOMNO fly heading 085. PF changed runway to 27. As the PM returned from a PA announcement; it was noted the PTROL intersection was crossed about 10;700 ft in the DES mode. The correct altitude is between 11000-13000 ft. The PF disengaged the A/P and leveled off. The occurrence happened in DES mode with no deviation from descent path and no orange waypoint.


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


Synopsis: A320 flight crew reported the FMS descended below one of the intersection fix altitudes while in descent mode on the DRLLR4 Arrival to IAH. Crew disengaged autopilot and returned to STAR clearance.
Date: 201209
Local time of day: 0601-1200
Location: EWR.Airport, NJ
Flight conditions: VMC
Light: Dawn
Aircraft: MD-11
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Cargo / Freight / Delivery
Flight phase: Takeoff / Launch
ATC / advisory: Tower EWR
Aircraft component: Turbine Engine Thrust Reverser
Component problem: Malfunctioning
Reporter organization: Air Carrier
Reporter function: Captain; Pilot Not Flying
Reporter qualification: Flight Crew Air Transport Pilot (ATP)
Anomaly: Aircraft Equipment Problem Critical
Detector: Person Flight Crew
When detected: In-flight
Result: Flight Crew Rejected Takeoff; General Maintenance Action
Contributing factors: Aircraft
Primary problem: Aircraft

Narrative: At 120 KTS on takeoff I received a level 2 thrust reverser failure warning. I did an immediate reject; we turned off about 6;000 FT down the runway. All required checklists were accomplished and we returned to the gate for required maintenance trouble-shooting; brake cooling; re- fueling; and new weight and balance; etc. I was the pilot monitoring on this event.




Synopsis: MD-11 Captain reported rejecting takeoff after receiving a thrust reverser failure warning. Flight returned to the gate.
Date: 201705
Aircraft: Commercial Fixed Wing
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Descent
Aircraft component: Galley Furnishing
Component problem: Malfunctioning
Reporter organization: Air Carrier
Reporter function: Flight Attendant (On Duty)
Anomaly: Aircraft Equipment Problem Less Severe; Flight Deck / Cabin / Aircraft Event Illness / Injury; Flight Deck / Cabin / Aircraft Event Smoke / Fire / Fumes / Odor
Detector: Person Flight Attendant
When detected: In-flight
Result: Flight Crew Took Evasive Action; General Maintenance Action
Contributing factors: Aircraft
Primary problem: Aircraft

Narrative: During initial [descent] I came from the back of the plane picking up trash. When I got to the front of the plane I told the galley FA that I smelled something burning. I opened the oven and saw flames in the back of the oven from the bottom to the top. I slammed the oven door shut and told her there was a fire in the oven and she immediately turned the breaker switch off and I grabbed the Halon fire extinguisher and handed it to her.I called the Captain and informed him of the situation while she put the fire out in the oven. It was put out in just a few seconds and when we landed he checked the oven out and he also wrote it up. No one was injured but when everyone was off the plane the agent said the passenger in [first class] was filing a complaint because he had a headache. No one else complained and we had no issues ourselves.




Synopsis: Flight Attendant reported a burning smell and a galley oven fire that was addressed with a fire extinguisher.
Date: 202011
Local time of day: 1201-1800
Location: ZZZ.Tower, US
Weather elements / visibility: 10
Light: Daylight
Aircraft: PA-28R Cherokee Arrow All Series
Operator: Personal
Operating under: Part 91
Flight plan: None
Mission: Training
Flight phase: Initial Climb
Aircraft component: Engine
Component problem: Malfunctioning
Reporter organization: Personal
Reporter function: Single Pilot; Pilot Flying
Reporter qualification: Flight Crew Student
Anomaly: Aircraft Equipment Problem Critical
Detector: Person Flight Crew
When detected: In-flight
Result: Air Traffic Control Provided Assistance; Flight Crew Returned To Departure Airport; Flight Crew Requested ATC Assistance / Clarification; General Maintenance Action; General Flight Cancelled / Delayed
Contributing factors: Aircraft
Primary problem: Aircraft

Narrative: Performed a touch and go during XC (Cross Country) flight. Upon rotation climbing out small vibration developed in yoke. At approximately 600 feet. MSL vibration began increasing slightly. Radio contact with request permission to do flyby to have them look at aircraft for landing gear possible issues. Was asked by ATC if I would like to return and land. I declined first request as I assessed the situation and began checking my instruments for indications of engine malfunction. Vibration began to increase rapidly and all systems were in the green. Power seem to be diminishing vibrations became excessive. I thought I saw light white smoke from right side of cowling and contacted ATC with information of my situation requesting landing clearance. Declining first runway; ATC cleared for alternative runway which I accepted and landed safely. Taxied to FBO and checked aircraft for fire potential. Performed file sump and oil level inspection to re verify conditions which appeared satisfactory. Oil lever had lowered from initial check list levels prior to departure. After 30 minutes I restarted the plane to check if icing has possibly been the issue. Having restarted the engine the violent vibration was even more pronounced and I shut down the engine. It has been verified by the mechanic a cylinder cracked and required replacement.




Synopsis: PA-28R Single pilot reported an uneventful air return due to engine malfunction.
Date: 202007
Local time of day: 1801-2400
Aircraft: No Aircraft
Flight plan: IFR
Reporter organization: Air Carrier
Reporter function: First Officer
Reporter qualification: Flight Crew Air Transport Pilot (ATP); Flight Crew Instrument; Flight Crew Multiengine
Human factors: Other / Unknown
Anomaly: Deviation / Discrepancy - Procedural Published Material / Policy
Detector: Person Flight Crew
Result: General None Reported / Taken
Contributing factors: Environment - Non Weather Related; Company Policy; Human Factors
Primary problem: Company Policy

Narrative: Again this morning; as has happened on many; many occasions the past few months; there were numerous crews in briefing rooms without masks...no food or drinks in sight.  The meaning of 'should' in the FOM indicates 'an action that is expected; a compelling reason must exist if the expectation cannot be met.'In accordance with State X Public Health Order; and current company documentation; employees must wear a face mask that covers the nose and mouth whenever training in a flight simulator training device with others; should wear a face mask while in hallways; briefing rooms and common areas.This is not just a chance 'error'.  I have repeatedly observed both instructors and evaluators not in compliance with the bulletin concerning mask wear.




Synopsis: Air carrier First Officer reported crews are not wearing COVID-19 mask in briefing rooms.
Date: 201904
Location: BOS.Airport, MA
Aircraft: A320
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Final Approach
Airspace: Class B BOS
ATC / advisory: Tower BOS
Second aircraft: UAV - Unpiloted Aerial Vehicle
Reporter organization: Air Carrier
Reporter function: Captain; Pilot Not Flying
Reporter qualification: Flight Crew Air Transport Pilot (ATP); Flight Crew Multiengine; Flight Crew Instrument
Human factors: Distraction; Situational Awareness
Anomaly: Conflict Airborne Conflict
Detector: Person Flight Crew
When detected: In-flight
Result: General None Reported / Taken
Contributing factors: Environment - Non Weather Related
Primary problem: Environment - Non Weather Related

Narrative: Drone 3;300 feet abeam Cohas ILS 33L BOS within a mile; ATC [was] notified.




Synopsis: A320 Captain reported UAV less than 1 mile abeam the ILS.