elihoole/asrs-aviation-reports huggingface dataset:
Date: 201812
Location: ZZZ.Airport, US
Flight conditions: VMC
Light: Daylight
Aircraft: PA-28 Cherokee/Archer/Dakota/Pillan/Warrior
Operator: FBO
Operating under: Part 91
Flight plan: None
Mission: Training
Flight phase: Landing
Airspace: Class E ZZZ
ATC / advisory: CTAF ZZZ
Second aircraft: Cessna Aircraft Undifferentiated or Other Model
Reporter organization: FBO
Reporter function: Pilot Flying
Reporter qualification: Flight Crew Commercial; Flight Crew Flight Instructor; Flight Crew Instrument; Flight Crew Multiengine
Human factors: Communication Breakdown
Anomaly: Conflict Ground Conflict; Critical; 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: Airspace Structure; Human Factors
Primary problem: Human Factors

Narrative: While performing flight training in the pattern at ZZZ; a runway incursion almost created an accident. While 3 aircraft are in the pattern all using Runway XX and all pilots communicating on the CTAF frequency; Aircraft Y entered active Runway XX during the touchdown phase of our landing. The aircraft was not talking on radios but looked like he was going to stop at the hold short line so we made the decision to continue. On round out just before touchdown aircraft entered runway and a go-around was executed. We missed aircraft by about 10 feet. That aircraft then continued to taxi to Runway XY and departed. I called him on the radios and the pilot responded 'Sorry didn't see you.' He also stated he was using his radios but no other aircraft nor the FBO could hear him.




Synopsis: PA-28 flight instructor reported a critical ground conflict when an aircraft taxied onto the runway; requiring evasive action.
Date: 202002
Local time of day: 1801-2400
Location: ZZZ.Airport, US
Aircraft: A321
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Takeoff / Launch
ATC / advisory: Tower ZZZ
Second aircraft: EMB ERJ 190/195 ER/LR
Reporter organization: Government
Reporter function: Coordinator; Local
Reporter qualification: Air Traffic Control Fully Certified
Second reporter function: Pilot Flying; Captain
Anomaly: ATC Issue All Types; Conflict Ground Conflict; Critical; Ground Incursion Runway
Detector: Person Flight Crew; Person Air Traffic Control
When detected: In-flight
Result: Air Traffic Control Issued Advisory / Alert; Flight Crew Rejected Takeoff; Flight Crew Took Evasive Action
Contributing factors: Human Factors
Primary problem: Human Factors

Narrative: I was working LCE (Local East); as a coordinator. I heard LCW (Local West) clear Aircraft X for takeoff. Right after that; I observed Aircraft Y starting to cross [the] runway. I pointed it out to LCW and told them to have Aircraft X abort their takeoff.


Second narrative: Taxied to XXR for departure due to weight. Cleared to line up and wait. After about 2 minutes in position cleared for takeoff. After setting takeoff power and cross checking instruments I noticed an aircraft taxiing southbound [toward the runway]. It didn't appear that the aircraft was going to hold short of our runway. Approaching 80 knots I decided to abort the takeoff. The First Officer also noticed the aircraft and brought this to my attention as we were aborting. About this time ATC told the other aircraft to stop. We managed to stop the aircraft before the taxiway. The other aircraft had passed the hold short bars and was on the runway. Cleared the runway and made a PA to the passengers. Called Dispatch with Maintenance on the line to make sure we didn't need to return to the gate since we were below 80 knots. After running the before takeoff checklist again we departed.


Synopsis: Tower Coordinator and an A321 flight crew reported a rejected takeoff due to a runway incursion.
Date: 201210
Flight conditions: VMC
Aircraft: Commercial Fixed Wing
Operator: Air Carrier
Operating under: Part 121
Mission: Passenger
Flight phase: Parked
Reporter organization: Air Carrier
Reporter function: First Officer; Pilot Flying
Anomaly: Aircraft Equipment Problem Critical; Deviation / Discrepancy - Procedural MEL / CDL; Deviation / Discrepancy - Procedural Published Material / Policy
Detector: Person Flight Crew
When detected: Pre-flight
Result: Flight Crew Overcame Equipment Problem; General Maintenance Action
Contributing factors: Human Factors
Primary problem: Human Factors

Narrative: Over night aircraft was written up as brake system 2 malfunction. Maintenance Release indicated Brake System 2 Circuit Breaker pulled and System 2 inoperative. System 1 good and crew to perform alternate brake check. After completing check; Captain noticed status page indicated System 1 inoperative. Upon further investigation noticed System 1 Brake Circuit Breaker pulled instead of 2. The Captain called Maintenance Controller and verified incorrect brake system inoperative. Crew pulled System 2 Brake Circuit Breaker and reset System 1 as per Maintenance Control instructions. Captain's attention to detail prevented us from departing with both brake systems inoperative.




Synopsis: It is unclear if there was a malfunction on Brake System 2 since there appears to have been no flight deck message. If the alternate brake test was successful; then in the worst case; the aircraft would have been released with only alternate brake systems available.
Date: 202002
Local time of day: 0601-1200
Location: PDK.Airport, GA
Flight conditions: VMC
Light: Daylight
Aircraft: UAV - Unpiloted Aerial Vehicle
Operator: Personal
Flight phase: Cruise
Airspace: Class D PDK
Reporter organization: Personal
Reporter function: Other / Unknown
Reporter qualification: Flight Crew Commercial; Flight Crew Instrument; Flight Crew Multiengine; Flight Crew Rotorcraft
Anomaly: Airspace Violation All Types; Conflict Airborne Conflict; Deviation / Discrepancy - Procedural FAR; Deviation / Discrepancy - Procedural Published Material / Policy
Detector: Person Other Person
Result: General None Reported / Taken
Contributing factors: Airspace Structure; Procedure
Primary problem: Ambiguous

Narrative: At the airport in Chamblee; GA; I observed then videoed a person flying a what appeared to be an older model white DJI Phantom drone above tree top level in a small open area 850ft from the 'Charley' helicopter pad (287 degrees magnetic from the pad) and about 500 ft from the approach path of Runway 16 at Peachtree Dekalb Airport PDK. The runway was active and in use by landing aircraft. A student pilot practicing in an R22 flew past the drone while landing on Runway 16 and apparently did not see it. I reported the drone activity to the Tower at PDK by telephone and they were unaware of the drone activity and could not see it from the Tower. The airport police were also notified when it was clear the person did not have permission to operate where he was flying. An R44 Helicopter was also flying over the area and didn't see the drone. This was also a training flight. I spoke to both pilots and neither saw the drone. The helicopter was also off the Charlie helicopter pad. The fact the drone could not be seen by the pilots in the air is what makes this activity so extremely dangerous this close to an airport.




Synopsis: Commercial drone operator reported observing a drone operating in the approach path of PDK airport and causing traffic conflict with aircraft. Tower was notified and made aware of the drone's location.
Date: 201909
Local time of day: 1201-1800
Location: ZZZ.Airport, US
Flight conditions: VMC
Weather elements / visibility: 10
Aircraft: Cessna 210 Centurion / Turbo Centurion 210C; 210D
Operator: Personal
Operating under: Part 91
Flight plan: None
Mission: Personal
Flight phase: Taxi
ATC / advisory: UNICOM ZZZ
Reporter organization: Personal
Reporter function: Pilot Flying; Single Pilot
Reporter qualification: Flight Crew Private
Human factors: Distraction; Situational Awareness
Anomaly: Deviation / Discrepancy - Procedural Published Material / Policy; Ground Event / Encounter Ground Strike - Aircraft; Ground Excursion Runway
Detector: Person Flight Crew
When detected: Taxi
Result: Aircraft Aircraft Damaged; General Flight Cancelled / Delayed
Contributing factors: Airport; Human Factors
Primary problem: Human Factors

Narrative: While taxiing to Runway XX at ZZZ; I crossed hold short line; announced departure on Unicom; [and] proceeded to make a left turn off taxi way [but] made turn too wide. Right main wheel came off black top. The runway black top is approximately 8 in. above surrounding ground. Surrounding ground is soft sand. Aircraft pulled to [the] right when main gear hit sand. Pulling nose gear off blacktop. Nose gear hit soft sand and sunk in. [Then the] prop struck ground. Aircraft came to rest with right wing touching ground. No other aircraft were involved. Probable speed was 1-2 mph. Turned off master and fuel selector. [Then] called Unicom to shut down runway [and] spoke with FAA on phone.




Synopsis: A Cessna 210 Pilot reported a runway excursion while turning into position for takeoff; resulting in the propeller and wingtip striking the ground.
Date: 201406
Location: ZZZ.ARTCC, US
Flight conditions: VMC
Aircraft: B757-300
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: Turbine Engine
Component problem: Malfunctioning
Reporter organization: Air Carrier
Reporter function: Captain
Reporter qualification: Flight Crew Air Transport Pilot (ATP)
Second reporter function: First Officer
Anomaly: Aircraft Equipment Problem Less Severe
Detector: Person Flight Crew
When detected: In-flight
Result: Flight Crew Diverted; General Declared Emergency
Contributing factors: Aircraft
Primary problem: Aircraft

Narrative: At cruise FL320 right engine had partial loss of power. Phone patched to Dispatch/Maintenance Control. Discussed with them the engine parameters. Maintenance/Dispatch told us to divert to a nearby airport. Airspeed and altitude were easily maintained with split throttles. Right engine thrust availability remained stable up to 1.6 EPR; so we declared an emergency and proceeded to our diversion airport. At power settings below 1.4 EPR the throttles were matched and the airplane flew normally. An overweight landing was made and entered into the logbook.


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


Synopsis: A B757 flight crew declared an emergency and diverted to a nearby airport when the right engine suffered a partial loss of power. An overweight landing was successfully accomplished.
Date: 202202
Local time of day: 0601-1200
Location: 6R3.Airport, TX
Weather elements / visibility: Rain; Fog; 3
Light: Daylight
Aircraft: Small Aircraft; Low Wing; 1 Eng; Retractable Gear
Operator: Personal
Operating under: Part 91
Flight plan: IFR
Mission: Personal
Flight phase: Final Approach
Airspace: Class E ZHU
ATC / advisory: CTAF 6R3
Reporter organization: Personal
Reporter function: Single Pilot; Pilot Flying
Reporter qualification: Flight Crew Instrument; Flight Crew Multiengine; Flight Crew Air Transport Pilot (ATP)
Human factors: Situational Awareness; Workload; Confusion; Distraction
Anomaly: ATC Issue All Types; Deviation / Discrepancy - Procedural FAR; Deviation / Discrepancy - Procedural Published Material / Policy; Ground Event / Encounter Ground Equipment Issue
Detector: Person Flight Crew
When detected: In-flight
Result: Flight Crew Overcame Equipment Problem
Contributing factors: Equipment / Tooling; Environment - Non Weather Related; Airport
Primary problem: Airport

Narrative: 6R3 airport runway lighting and PAPI have been out of service for '3 years' and is an ongoing issue. The RNAV/GPS Runway 16 and its circling component combined with all flight operations VFR and IFR should be reduced to VFR DAY ONLY due to the lighting deficiencies combined with the overgrown vegetation that block all runway/taxiway signage. In addition to the above the airport manager is promoting landing after dark by providing his pickup truck lighting at the approach end of Runway 16 for night time operations. I have personally witnessed this several times. The lack of NOTAMs referencing the RNAV approach RWY 16 has encouraged and continues airmen to attempt a landing from minimums on the LPV portion of the approach to an unlit runway or a runway illuminated with truck headlights. (this was updated on 02/24 FDC 2/27706)Houston TRACON recently vectored an emergency aircraft with engine problems to the airport at night due to the NOTAM incorrectly identified the Runway Edge Lighting Out of Service and should have read MIRL OTS. I urge the FAA to review all of the deficiencies associated with 6R3 and its associated approaches VFR and IFR as its a matter of time before someone is injured or killed as a result of the oversight.




Synopsis: A Pilot who routinely flies into Cleveland; Texas airport (6R3) reported the PAPI and runway lighting have been out of service for three years and the outages are not published in a NOTAM. The reporter stated the airport manager parks a pickup truck with the headlights on to facilitate nighttime operations.
Date: 201908
Local time of day: 1201-1800
Aircraft: Commercial Fixed Wing
Operator: Air Carrier
Operating under: Part 121
Mission: Passenger
Flight phase: Taxi
Reporter organization: Air Carrier
Reporter function: Other / Unknown
Human factors: Training / Qualification; Communication Breakdown; Situational Awareness
Anomaly: Conflict Ground Conflict; Critical; Deviation / Discrepancy - Procedural Published Material / Policy; Ground Event / Encounter Other / Unknown
Detector: Person Ground Personnel
When detected: Taxi
Result: Flight Crew Returned To Gate; General Flight Cancelled / Delayed; General Maintenance Action
Contributing factors: Procedure; Human Factors
Primary problem: Human Factors

Narrative: Aircraft X pushed back from Gate E8. As the aircraft was being pushed straight back [another company] tug with carts disobeyed the Wing Walker signal to stop for the aircraft being pushed and continued to drive behind the aircraft. Once the tug was directly behind the aircraft they finally stopped which prevented the aircraft from being pushed. The pushback Driver had to stop abruptly to prevent hitting the tug and carts. This caused the shear pin on the tow bar to break. Supervisor and Maintenance was called to the incident. Maintenance determined the aircraft was good to fly and the ramp crew changed out the tow bar and completed the push.




Synopsis: Ramp worker reported that during pushback; a baggage tug blocked the aircraft; causing the pushback driver to stop abruptly and break the tow bar shear pin.
Date: 202005
Local time of day: 1801-2400
Location: ZZZ.Airport, US
Flight conditions: VMC
Weather elements / visibility: 10
Light: Dusk
Aircraft: Bonanza 33
Operator: Personal
Operating under: Part 91
Flight plan: None
Mission: Personal
Flight phase: Landing
Airspace: Class E ZZZ
ATC / advisory: CTAF ZZZ
Second aircraft: PA-18/19 Super Cub
Reporter organization: Personal
Reporter function: Pilot Flying
Reporter qualification: Flight Crew Commercial; Flight Crew Flight Instructor; Flight Crew Multiengine; Flight Crew Instrument
Anomaly: Conflict Ground Conflict; Critical; Deviation / Discrepancy - Procedural FAR; Deviation / Discrepancy - Procedural Published Material / Policy; Ground Incursion Runway
Detector: Person Flight Crew
When detected: Other Landubg Rollout
Result: Flight Crew Took Evasive Action
Contributing factors: Human Factors
Primary problem: Human Factors

Narrative: A BE33 had just landed on Runway XX when a PA18 Super Cub rolled onto final. Myself; along with two other pilot-rated observers; watched the BE33 (we were friends with the pilots and passengers on that plane) make a 180 on the runway to taxi back to the only exit from the runway. It quickly became clear that the PA18 did not have room to land safely; however; instead of a normal go-around the pilot appeared to buzz the BE33 by approx. 20-40ft. Once passed the BE33; the PA18 made an aggressive 180 degree turn and proceeded to land on Runway XY while the BE33 was still occupying the runway and taxiing back to the only exit from the runway. The PA18 landed and taxied to a hangar while the BE33 eventually cleared the runway and parked on the ramp with the pilot noting the incident. The incident was a clear runway incursion and not safe at all. While we did not make an attempt to contact the pilot (we were preparing to leave the area and return to our home airport); we agreed it was an unsafe maneuver. The PA18 did not make any calls on CTAF at any time while both my plane and the BE33 made calls for each leg of the pattern.




Synopsis: Third party observer reported a BE-33 pilot experienced a Critical Ground Event during landing rollout with a 'NORDO' PA-18 landing with the BE-33 still on runway.
Date: 201901
Local time of day: 0601-1200
Location: ZZZ.Airport, US
Flight conditions: VMC
Aircraft: Regional Jet 900 (CRJ900)
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Taxi
ATC / advisory: Ground ZZZ
Second aircraft: Regional Jet 900 (CRJ900)
Reporter organization: Air Carrier
Reporter function: Captain; Pilot Flying
Reporter qualification: Flight Crew Multiengine; Flight Crew Instrument; Flight Crew Air Transport Pilot (ATP)
Second reporter function: First Officer; Pilot Not Flying
Anomaly: ATC Issue All Types; Conflict Ground Conflict; Less Severe; Deviation / Discrepancy - Procedural Clearance; Ground Incursion Runway
Detector: Person Flight Crew
When detected: Taxi
Result: Flight Crew Requested ATC Assistance / Clarification; Flight Crew Returned To Clearance
Contributing factors: Procedure; Human Factors
Primary problem: Procedure

Narrative: After landing on Runway XXR in ZZZ; we [exited] and were cleared to cross [another runway] and hold short of Runway XXL; behind a company aircraft. We were then both cleared to cross Runway XXL. The aircraft in front of us being cleared to cross and hold short of K. They stopped immediately after crossing the runway instead of holding short of K; leaving us no space to clear the hold short line. My First Officer contacted ground as quickly as possible to let them know of the issue. Then we both looked to the left and saw an aircraft taking off from Runway XXL while we were still on the runway.I do not think there was much more that me or my First Officer could have done in this case. We communicated to the best of our ability with ATC and the aircraft in front of us on frequency in order to move off of the runway and past the hold short line as quickly as possible. Luckily; we were on the far departure end of the runway and the runway incursion went without incident.


Second narrative: After landing Runway XXR; was given taxi with a clearance to hold short of Runway XXL. We were behind [Company traffic] and they were having language difficulties with tower. Eventually; both of us were cleared to cross Runway XXL. [Company traffic] was told to hold short of K but failed to pull far enough up to allow us to clear the runway. We were clear of runway but not clear of hold short line; I immediately notified ground we were not clear but ground had language issues with [Company traffic] to get the aircraft to move forward. I looked and saw that an aircraft was cleared for takeoff on Runway XXL and was airborne before we cleared the runway. I informed the captain and ground of the runway incursion. Have tower ensure to give clearances that allow both aircraft to clear runway when 2 or more aircraft are clear on the same taxiway. This is true for both inside runways at ZZZ.


Synopsis: CRJ-900 flight crew reported being unable to taxi clear off a runway due to preceding aircraft stopping; which resulted in runway incursion.
Date: 201908
Local time of day: 1201-1800
Location: ZZZ.Airport, US
Aircraft: Boeing Company Undifferentiated or Other Model
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Cargo / Freight / Delivery
Flight phase: Parked
Airspace: Class C RDU
Reporter organization: Air Carrier
Reporter function: First Officer; Pilot Not Flying
Reporter qualification: Flight Crew Multiengine; Flight Crew Instrument; Flight Crew Air Transport Pilot (ATP)
Human factors: Troubleshooting; Situational Awareness; Confusion
Anomaly: Deviation / Discrepancy - Procedural Other / Unknown
Detector: Person Flight Crew
When detected: Pre-flight
Result: General None Reported / Taken
Contributing factors: Airport; Chart Or Publication
Primary problem: Chart Or Publication

Narrative: ZZZ is undergoing a huge construction project on the south side of the airport.  It involves multiple taxiway closures. This has lead to very confusing taxiway closure and renaming NOTAMs at ZZZ are confusing which could lead to a potential safety issue.Looking at the diagram these two NOTAM overlap in most but not all areas.  If you misread them; it can become an issue for a crew in the middle of the night.  Even worse; three NOTAMs written several months apart all refer to taxiway T6.  So; which T6 is the first NOTAM talking about the old T6 in April or the new T6 in June?  Moreover; the JeppFD-Pro application has a AMM (Aircraft Maintenance Manual) diagram with SOME but not all construction highlighted.  But even that is incorrect. (There is no construction between B5 and B6 in real life; but it is highlighted on the AMM.) Without a date on the AMM it provides little utility to know if the highlights are good or bad.  Even the JeppFD-Pro page incorrectly marks the new taxiway names.Unclear NOTAMs and lack of up to date taxi diagram with highlighted to show current closures and taxiways names. The current Jepp page needs to be updated correctly and released.Publish a new construction diagram for ZZZ.  Release to aircrew. Examine NOTAMs for unnecessary and potentially misleading overlap.




Synopsis: First Officer reported NOTAMS at destination are ineffective in providing a useful taxi tool to navigate a huge airport construction area.
Date: 201411
Local time of day: 0601-1200
Location: DAL.Airport, TX
Flight conditions: VMC
Light: Daylight
Aircraft: Medium Large Transport; Low Wing; 2 Turbojet Eng
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Flight phase: Descent
Airspace: Class B DAL
ATC / advisory: Center ZFW
Reporter organization: Air Carrier
Reporter function: Captain
Reporter qualification: Flight Crew Air Transport Pilot (ATP)
Anomaly: Inflight Event / Encounter Weather / Turbulence
Detector: Person Flight Crew
When detected: In-flight
Result: General None Reported / Taken
Contributing factors: Weather; Aircraft; Procedure
Primary problem: Procedure

Narrative: No deviation occurred on this flight but the JFRYE STAR was found not flyable with a 70-knot tailwind.  During cruise the FMC generated two STEEP DESCENT messages; one for ZORDA and the second was for GUMMP. After crossing ZORDA; the aircraft went into VNAV SPD and was 400 feet on the path. The vertical path was recovered by using speedbrakes. Crossing GUMMP; the aircraft once again went into VNAV SPD and was 800 feet high on the vertical path. We had to change autopilot modes after GUUMP in an attempt to meet the altitude and speed restrictions at GREGS. Full speedbrake extension could not maintain a speed of 280 knots in the descent and re-establish the aircraft back on the vertical path to GREGS. Only using Vertical Speed; full speedbrake extension; and a speed of greater than 280 knots could we meet the altitude restriction at GREGS.  This STAR must be redesigned to meet aircraft capability with moderate to strong tailwind components.




Synopsis: Captain reported the aircraft was unable to fly the JFRYE STAR in VNAV to DAL with a 70 knot tailwind.