elihoole/asrs-aviation-reports huggingface dataset:
Date: 201503
Local time of day: 0001-0600
Location: ZZZ.ARTCC, US
Light: Night
Aircraft: B767 Undifferentiated or Other Model
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Cruise
Airspace: Class A ZZZ
ATC / advisory: FSS ZZZ
Aircraft component: Cockpit Window
Component problem: Failed
Reporter organization: Air Carrier
Reporter function: Captain; Pilot Not Flying; Check Pilot
Reporter qualification: Flight Crew Air Transport Pilot (ATP); Flight Crew Multiengine; Flight Crew Instrument; Flight Crew Flight Instructor; Flight Crew Flight Engineer
Human factors: Communication Breakdown; Training / Qualification
Anomaly: Aircraft Equipment Problem Less Severe; Deviation / Discrepancy - Procedural Published Material / Policy; Flight Deck / Cabin / Aircraft Event Other / Unknown
Detector: Person Flight Attendant; Person Flight Crew
When detected: Aircraft In Service At Gate; In-flight
Result: Aircraft Aircraft Damaged; Flight Crew Overcame Equipment Problem
Contributing factors: Aircraft; Human Factors
Primary problem: Aircraft

Narrative: During cruise Captain's forward windshield cracked. Complied with all checklists and the QRH. Phone patch to company discussing options we determined that we could continue to our destination. Advised flight attendants; but did not need to advise passengers. We continued to our destination. Upon arrival; Lead A Flight Attendant deployed emergency slide due to not following procedures. No further events.




Synopsis: A B767 Captain reported a cracked cockpit windshield; but was able to continue. Separate to this event; a flight attendant deployed an emergency slide.
Date: 201809
Local time of day: 1201-1800
Location: ZZZ.Airport, US
Light: Daylight
Aircraft: Cessna 402/402C/B379 Businessliner/Utiliner
Flight plan: IFR
Mission: Passenger
Flight phase: Climb
Airspace: Class D ZZZ
ATC / advisory: Tower ZZZ
Aircraft component: Powerplant Lubrication System
Component problem: Malfunctioning
Reporter function: Pilot Not Flying
Reporter qualification: Flight Crew Air Transport Pilot (ATP); Flight Crew Instrument; Flight Crew Multiengine
Human factors: Situational Awareness; Time Pressure
Anomaly: Aircraft Equipment Problem Critical
Detector: Person Flight Crew
When detected: In-flight
Result: Flight Crew Landed As Precaution; Flight Crew Returned To Departure Airport
Contributing factors: Aircraft
Primary problem: Aircraft

Narrative: As we were climbing out; we noticed the right engine oil pressure steadily decreasing; we cancelled the IFR with ATC; advised the passengers of what was happening and our intentions; came back and landed at [the departure airport]; wrote in the can and called [Maintenance].




Synopsis: A Cessna 402 pilot reported an oil system pressure anomaly during climb out; which resulted in an air return to the departure airport.
Date: 201812
Local time of day: 1801-2400
Location: GJT.Airport, CO
Aircraft: Citation V/Ultra/Encore (C560)
Flight plan: IFR
Flight phase: Final Approach
Airspace: Class E D01
ATC / advisory: TRACON D01
Reporter organization: Government
Reporter function: Approach
Reporter qualification: Air Traffic Control Fully Certified
Human factors: Situational Awareness
Anomaly: Aircraft Equipment Problem Less Severe; Deviation - Track / Heading All Types; Inflight Event / Encounter CFTT / CFIT
Detector: Person Air Traffic Control
When detected: In-flight
Result: Air Traffic Control Issued Advisory / Alert; Air Traffic Control Issued New Clearance
Contributing factors: Aircraft; Human Factors
Primary problem: Ambiguous

Narrative: Aircraft X came into GJT from the east; I asked him what approach he wanted to RY 29 and he requested the RNAV with direct HANSU. I explained to him that to turn him southwest bound to get him lower and then to expect direct HANSU from south of the fix. When he got lower; I gave him a 330 heading when able direct HANSU. Then I went back and cleared him for the approach. I immediately noticed he was going past HANSU and into an area of higher terrain. I gave him the low altitude alert and asked him if he could visually see the ground. He replied that he could and that he was correcting. He said he had a problem with the 'box' and asked to be vectored for the same approach; but with vectors to intercept the final. He landed without incident.




Synopsis: Denver TRACON Controller reported an aircraft did not turn as cleared and entered an area of higher terrain.
Date: 201308
Local time of day: 0001-0600
Location: ZZZ.Airport, US
Aircraft: A320
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Flight phase: Climb
Airspace: Class C ZZZ
ATC / advisory: TRACON ZZZ
Second aircraft: Gulfstream V / G500 / G550
Reporter organization: Government
Reporter function: Approach; Departure
Reporter qualification: Air Traffic Control Fully Certified
Human factors: Situational Awareness
Anomaly: ATC Issue All Types; Deviation / Discrepancy - Procedural Published Material / Policy
Detector: Person Air Traffic Control
Result: Air Traffic Control Issued New Clearance
Contributing factors: Human Factors
Primary problem: Human Factors

Narrative: An A320 departed on SID X. A GLF5 departed on the SID Y and was instructed to maintain visual separation with the A320 departing before him. The GLF5 failed to maintain visual separation with the departing aircraft because the GLF5 had a greater climb rate than the A320. The GLF5 was leaving 041 as he reported he lost sight of the departing traffic which was at 035. I called traffic and the GLF5 still did not have the A320 in sight. The next transmission was a vector for separation. When the GLF5 reported he lost sight of departing traffic; I should have vectored for separation first and then call traffic. Unfortunately I called traffic first; then vectored for separation.




Synopsis: TRACON Controller experienced a loss of separation when attempting to establish visual separation between two successive departures; the second aircraft climbed faster than the first.
Date: 201601
Local time of day: 0601-1200
Location: ZZZ.Airport, US
Flight conditions: VMC
Weather elements / visibility: 10
Light: Daylight
Aircraft: Amateur/Home Built/Experimental
Operator: Personal
Operating under: Part 91
Flight plan: None
Mission: Training
Flight phase: Taxi
Second aircraft: Commercial Fixed Wing
Reporter organization: Personal
Reporter function: Instructor; Pilot Not Flying
Reporter qualification: Flight Crew Flight Instructor; Flight Crew Commercial
Human factors: Distraction; Communication Breakdown; Situational Awareness
Anomaly: Conflict Ground Conflict; Less Severe; Deviation / Discrepancy - Procedural Clearance; Ground Incursion Runway
Detector: Person Flight Crew
When detected: Taxi
Result: Flight Crew Exited Penetrated Airspace
Contributing factors: Human Factors
Primary problem: Human Factors

Narrative: On the landing rollout; ATC (tower) gave me a clearance to Exit at a specific intersection; hold short of the parallel runway; and stay on that frequency. My student was asking a question during the busy radio exchanges. I acknowledged the instruction but thought I had heard the instruction to taxi across the parallel runway. So I went ahead and taxied across. However the tower had cleared an aircraft (a commercial airliner) to takeoff on that runway (on another frequency- that airport uses different frequencies for different runways). I saw the airplane holding and taxied across. However; he had been cleared and was beginning his takeoff roll. I was across the runway before the aircraft taking off reached my position but it was too close. The lesson here is not to let a student distract you with a question during high work-load phases of a training flight. He was a new student and did not know to not ask questions then.




Synopsis: A flight instructor reported that he became distracted by his student's question during taxi and crossed onto an active runway as an air carrier began a takeoff roll.
Date: 201507
Local time of day: 0601-1200
Location: RFD.Airport, IL
Flight conditions: VMC
Weather elements / visibility: 10
Light: Daylight
Aircraft: PA-34-200 Seneca I
Operator: Personal
Operating under: Part 91
Flight plan: VFR
Mission: Personal
Flight phase: Cruise
Airspace: Class D RFD
ATC / advisory: Center ZAU
Aircraft component: GPS & Other Satellite Navigation
Component problem: Malfunctioning
Reporter organization: Personal
Reporter function: Pilot Flying; Single Pilot
Reporter qualification: Flight Crew Air Transport Pilot (ATP); Flight Crew Instrument; Flight Crew Multiengine
Human factors: Confusion; Situational Awareness
Anomaly: Aircraft Equipment Problem Less Severe; Airspace Violation All Types; Deviation - Track / Heading All Types; Deviation / Discrepancy - Procedural FAR
Detector: Person Flight Crew
When detected: In-flight
Result: Flight Crew Overcame Equipment Problem; Flight Crew Exited Penetrated Airspace
Contributing factors: ATC Equipment / Nav Facility / Buildings; Aircraft
Primary problem: ATC Equipment / Nav Facility / Buildings

Narrative: While enroute to OSH; were using VFR flight following until past Chicago Center where this was terminated; encountered limited GPS signal; and changed to VOR guidance for enroute navigation. While approaching RFD VOR from the south nearing Class C airspace at 5500 feet; DME came active indicating 15 miles south of the VOR and immediately turned west to leave airspace in the event this was entered. Continued west then north to make sure clear and continued to OSH.  Better preflight planning for back up VOR guidance in the event of loss of GPS signal would have helped route planning to correct situation and prevent future occurrence.




Synopsis: Piper 34 pilot reported loss of GPS signal when approaching RFD led to a Class C airspace penetration.
Date: 201203
Local time of day: 1201-1800
Location: ZZZ.ARTCC, US
Flight conditions: VMC
Light: Daylight
Aircraft: MD-82
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Climb
Airspace: Class A ZZZ
ATC / advisory: Center ZZZ
Aircraft component: ACARS
Component problem: Malfunctioning
Reporter organization: Air Carrier
Reporter function: Pilot Flying; First Officer
Reporter qualification: Flight Crew Air Transport Pilot (ATP)
Human factors: Distraction; Physiological - Other; Training / Qualification
Second reporter function: Pilot Not Flying; Captain
Anomaly: Aircraft Equipment Problem Critical; Flight Deck / Cabin / Aircraft Event Smoke / Fire / Fumes / Odor
Detector: Person Flight Crew
When detected: In-flight
Result: Flight Crew Returned To Departure Airport; Flight Crew Landed in Emergency Condition; Flight Crew FLC complied w / Automation / Advisory; General Declared Emergency
Contributing factors: Aircraft
Primary problem: Aircraft

Narrative: On climb out I (First Officer) happened to notice a wisp of smoke coming from under the ACARS area of the instrument panel. After a short time we began to smell a slight burning odor. We decided to return to the departure airport. The smoke and odor stopped. We continued to return; ran the QRH checklist and declared an emergency. We did an uneventful overweight landing. We entered both the overweight landing and smoke in the logbook.


Second narrative: [Narative #2 had no additional information.]


Synopsis: A MD82 crew returned to the departure airport after a wisp of smoke and an electrical odor appeared to come from the ACARS unit.
Date: 202006
Local time of day: 1201-1800
Location: ZZZ.Tower, US
Weather elements / visibility: Icing; .1
Light: Daylight
Aircraft: PA-28R Cherokee Arrow All Series
Operator: Personal
Operating under: Part 91
Flight plan: IFR
Mission: Personal
Flight phase: Descent
Airspace: Class C ZZZ
ATC / advisory: Tower ZZZ
Reporter organization: Personal
Reporter function: Single Pilot
Reporter qualification: Flight Crew Instrument
Human factors: Communication Breakdown; Distraction; Situational Awareness; Training / Qualification; Troubleshooting; Workload
Anomaly: ATC Issue All Types; Deviation - Altitude Excursion From Assigned Altitude; Deviation / Discrepancy - Procedural Clearance; Deviation / Discrepancy - Procedural Published Material / Policy; Inflight Event / Encounter Loss Of Aircraft Control; Inflight Event / Encounter Weather / Turbulence
Contributing factors: Human Factors; Procedure; Weather
Primary problem: Weather

Narrative: ATC requested that I descend from 8;000 ft. I entered the clouds and picked up ice very quickly. Pitot iced over and lost altitude & VSI (Vertical Speed Indicator) gauges. I began trouble-shooting; immediately turned on pitot heat. Immediately turned on defroster for windscreen de-icing (very busy in a bumpy situation) and most important to keep cool and wings level. Lost altitude and was reminded by ATC (Air Traffic Control) not to deviate from assigned altitude. I informed ATC that I was rapidly picking up ice and was busy resolving. I was aviating and navigating; but possibly not communicating as clearly I could have. I was busy being safe... Losing my altimeter was not helpful at that time. ATC requested that I call them after landing at ZZZ airport. Proceeded to perform the RNAV 1 (Area Navigation) and called ATC on the ground. It was summer and I was not expecting ice to build up so fast.




Synopsis: PA28 pilot reported an icing encounter that necessitated a deviation from an assigned altitude.
Date: 201905
Local time of day: 1201-1800
Location: EWR.Airport, NJ
Flight conditions: VMC
Aircraft: B737 Undifferentiated or Other Model
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Taxi
Airspace: Class B EWR
ATC / advisory: Ramp EWR
Reporter organization: Air Carrier
Reporter function: Captain; Pilot Flying
Reporter qualification: Flight Crew Multiengine; Flight Crew Air Transport Pilot (ATP); Flight Crew Instrument
Human factors: Situational Awareness
Anomaly: Ground Event / Encounter Other / Unknown
Detector: Person Flight Crew
When detected: Taxi
Result: General None Reported / Taken
Contributing factors: Human Factors
Primary problem: Human Factors

Narrative: While sitting on taxiway A short of RK the First Officer and I observed a roughly 12' drone overfly the ramp. The drone approached from the ball park and flew between Gate 1 and Gate 2. It was at roughly 30 feet. We advised Ramp of the drone and another aircraft on frequency confirmed that they also had a visual on the drone. Upon contact with Ground Control we also advised them of the drone sighting.




Synopsis: B737 Captain reported sighting a small UAV flying at approximately 30 feet over adjacent taxiways at EWR.
Date: 201308
Local time of day: 1801-2400
Location: ZZZ.ARTCC, US
Light: Night
Aircraft: MD-82
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Climb
Airspace: Class A ZZZ
ATC / advisory: Center ZZZ
Aircraft component: Engine Air Pneumatic Ducting
Component problem: Design; Malfunctioning
Reporter organization: Air Carrier
Reporter function: Captain; Pilot Not Flying
Reporter qualification: Flight Crew Air Transport Pilot (ATP)
Human factors: Time Pressure; Workload
Second reporter function: Pilot Flying; First Officer
Anomaly: Aircraft Equipment Problem Critical
Detector: Automation Aircraft Other Automation; Person Flight Crew
When detected: In-flight
Result: Flight Crew FLC complied w / Automation / Advisory; Flight Crew Landed in Emergency Condition; Flight Crew Returned To Departure Airport; General Declared Emergency; General Maintenance Action
Contributing factors: Aircraft
Primary problem: Aircraft

Narrative: First Officer is Pilot Flying; I am Pilot Monitoring. As the aircraft is climbing through FL250; about 65 NM after takeoff; the Master Warning flickered twice and then came on steady. We both consulted the overhead panel and observed the TAIL COMP TEMP HIGH light illuminated in red. I extinguished the Master Warning light and the First Officer called for the QRH and performed the Memory Items; calling out each step as he accomplished them. I then started the clock and read aloud the procedure from the Bulletin. The light extinguished in less than 2 minutes and I called the checklist complete at the LAND ...NEAREST SUITABLE AIRPORT step. I told the First Officer to fly and talk; declare an emergency and advise ATC of our intention to return to the departure airport and land. I asked ATC to notify the Company and roll the ARFF. We received vectors to XXL and landed normally. I taxied off the runway and was met by the Command (ARFF); who examined the aft tail area with infrared. They said it was cool and followed us to the gate. Maintenance and ARFF inspected the aircraft and it was taken out of service. We completed the flight with a new aircraft.


Second narrative: [No additional information contained in Narrative #2.]


Synopsis: During climb after takeoff; a MD-83 Master Warning and TAIL COMP TEMP HIGH lights illuminated so an emergency was declared; the QRH completed and the flight returned to the departure airport.
Date: 202007
Local time of day: 0601-1200
Location: ZZZ.TRACON, US
Flight conditions: VMC
Weather elements / visibility: Haze / Smoke; 6
Light: Daylight
Aircraft: Small Aircraft; Low Wing; 1 Eng; Fixed Gear
Operator: FBO
Operating under: Part 91
Flight plan: IFR
Mission: Personal
Flight phase: Cruise
Airspace: Class E ZZZ
ATC / advisory: TRACON ZZZ
Aircraft component: Cylinder
Component problem: Malfunctioning
Reporter organization: FBO
Reporter function: Pilot Flying; Single Pilot
Reporter qualification: Flight Crew Commercial; Flight Crew Instrument; Flight Crew Multiengine
Human factors: Workload
Anomaly: Aircraft Equipment Problem Critical
Detector: Person Flight Crew
When detected: In-flight
Result: Air Traffic Control Provided Assistance; Flight Crew Landed in Emergency Condition
Contributing factors: Aircraft
Primary problem: Aircraft

Narrative: This is a correction. Departed from ZZZ on the departure and was vectored for altitude climb for VXX [airway]. The departure was normal and the aircraft was stable in the climb. While passing 7;000ft MSL I notice a rise in the CHT in cylinder 1;4;& 6. Temperatures where stable prior of takeoff and in the beginning climb at 356F. At 7;000 ft. MSL temperature jumped to 386F than 2mins later to 400F with several quick spikes in the EGT sensors for cylinder 6 and followed later by 1 & 4. Prior to reaching 11;000 ft. MSL the temps with the CHT began to climb faster to 420F. Reaching 11;000 ft. MSL I began to; trying to make small adjustments to throttle and mixture to cool the 3 cylinders down. The adjustments were not making a difference and the engine began to sputter and quit. I panic for a millisecond realizing the problem was worsening and noted the mountains; west of the ZZZ1; I was about to travel over. With a quick decision I informed Approach as I felt still in control of aircraft and still had somewhat of power available. I began a quick left turn to an airport on my left about; maybe; 30 miles and tried a steep descent to see if I could cool the engine down and get power back. ZZZ2 was chosen with the help of Approach and prior to the threshold of the runway power came back and engine was cooled down to 345F. Quickly did a landing checklist and through flaps in and landed safely on a 13;000 ft. runway. Was met with ARFF and Military Police. Informed the operator/owner of the problem and concluded that the magnetos R side went bad possibly in the climb after taking a video after the landing to show him what I was seeing. Mechanics came out on date to find more problems on the engine that may of been a caused to the performance decrease with the help of the R side magnetos. Aircraft is currently grounded and is in the process of being repaired.




Synopsis: Pilot reported problems with the engine overheating and having to make an expedited landing.
Date: 202012
Local time of day: 1201-1800
Location: ZZZ.Airport, US
Flight conditions: VMC
Light: Daylight
Aircraft: B757-200
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Cargo / Freight / Delivery
Flight phase: Taxi; Parked
Aircraft component: Hydraulic Lines; Connectors; Fittings
Component problem: Failed
Reporter organization: Air Carrier
Reporter function: First Officer
Reporter qualification: Flight Crew Air Transport Pilot (ATP); Flight Crew Instrument; Flight Crew Multiengine
Second reporter function: Captain
Anomaly: Aircraft Equipment Problem Less Severe; Flight Deck / Cabin / Aircraft Event Smoke / Fire / Fumes / Odor; Ground Event / Encounter Other / Unknown
Detector: Person Ground Personnel; Person Maintenance
When detected: Aircraft In Service At Gate
Result: General Evacuated
Contributing factors: Aircraft
Primary problem: Aircraft

Narrative: After an auto brakes 3 landing; we taxied to the gate. Upon arrival to the gate; we accepted ground power and shut down the number one engine. I went to the back to crack the door. Returning to the flight deck; the external power was flickering and kicking on and off. The Captain started the APU as we noticed a smell. Thinking it was associated with the electrical fluctuations we looked around the flight deck for evidence of a tripped circuit breaker. After a few moments; a mechanic came up to the aircraft to inform us the aircraft is on fire. We expeditiously exited the aircraft. Maintenance explained it was a main landing gear fire due to a hydraulic leak.Hydraulic leak in the left main landing gear well and associated fire. 'Fire' was left out of the maintenance write-up. The fire department was called and responded. The mechanic that came on board to inform us after the fire had been fought described the aircraft as 'on fire;' but 'fire' was not communicated in the write-up.


Second narrative: During shutdown after block in; I noticed an acrid smell in the cockpit. My First Officer (FO) smelled the same thing; we had no cockpit indications that indicated any problems. I asked the FO to leave the jet via the stairs as I shut the aircraft down. Shortly after maintenance came into the cockpit and told me to evacuate the jet because there was a fire. Maintenance notified the ARFF (Aircraft Rescue and Fire Fighting) service and they were on the scene as I got to the foot of the steps.Per maintenance; a hydraulic leak associated with malfunctioning electrical hydraulic pump.


Synopsis: Flight crew reported that after parking the aircraft the main landing gear caught fire; which maintenance attributed to a malfunctioning hydraulic pump.