elihoole/asrs-aviation-reports huggingface dataset:
Date: 202112
Local time of day: 1201-1800
Location: ZZZ.Airport, US
Weather elements / visibility: 10
Light: Daylight
Aircraft: Skylane 182/RG Turbo Skylane/RG
Operator: Personal
Operating under: Part 91
Flight plan: None
Mission: Personal
Flight phase: Landing
Airspace: Class G ZZZ
ATC / advisory: UNICOM ZZZ
Second aircraft: Cirrus Vision SJ50
Reporter organization: Personal
Reporter function: Single Pilot; Pilot Flying
Reporter qualification: Flight Crew Instrument; Flight Crew Private
Human factors: Situational Awareness
Anomaly: Conflict Ground Conflict; Critical; Deviation / Discrepancy - Procedural Published Material / Policy
Detector: Person Flight Crew
When detected: In-flight
Result: Flight Crew Took Evasive Action; Flight Crew Executed Go Around / Missed Approach
Contributing factors: Airport; Human Factors
Primary problem: Human Factors

Narrative: Flying from ZZZ1 to ZZZ; I Called 3-mile final Runway XX with no one on the runway ahead of me; or in the pattern. Aircraft Y; was parked on Taxiway XX for departure on [Runway] XX. I Called 1-mile final. When I was about 100 feet AGL; Aircraft Y announced departing [Runway] XX as he pulled onto Runway XX. I asked if he saw me on short final. He replied; 'yeah I see ya'. He entered Runway XX slightly ahead and almost directly below me. I executed a go-around and safely landed. No one landed between my go-around and subsequent landing. Aircraft Y had plenty of time to take off ahead of me after I called 3-mile final or could have waited 30 seconds and taken off after I landed. It seemed he intentionally waited until the last minute; and almost caused a mid-air. I reported the incident to the airport managers office.




Synopsis: C182 pilot reported ground conflict with another aircraft that entered the runway while reporter was on final approach to land at a non-towered airport.
Date: 201307
Local time of day: 1201-1800
Location: ZZZ.Airport, US
Flight conditions: VMC
Weather elements / visibility: 10
Light: Daylight
Aircraft: Skylane 182/RG Turbo Skylane/RG
Operator: Personal
Operating under: Part 91
Flight plan: IFR
Mission: Personal
Flight phase: Climb
Airspace: Class D ZZZ
ATC / advisory: TRACON ZZZ; Tower ZZZ
Aircraft component: Electrical Wiring & Connectors
Component problem: Failed
Reporter organization: Personal
Reporter function: Pilot Flying; Single Pilot
Reporter qualification: Flight Crew Private
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 Landed in Emergency Condition; General Declared Emergency
Contributing factors: Aircraft
Primary problem: Aircraft

Narrative: Following departure; at about 3;000 FT; [I noticed] a burning smell followed by smoke coming out from under the circuit breakers. I notified Approach of the issue and requested permission to land immediately at the nearest airport. Approach approved request to land at an Air Force Base which was 3 miles to the north. I was asked to switch to Tower and they quickly cleared landing and would have emergency personnel assist. Emergency procedures implemented followed by a good landing and we stopped the plane at the first turn off. The plane was vacated and fire personnel inspected. A melted wire leading to the landing light had shorted and melted in two pieces. Due to the quick response; no damage was done to the aircraft other than smoke smell. Air Force incident paperwork was completed; mechanics consulted and determined that the aircraft was airworthy; followed by a departure about 1 hour later. The aircraft is now at a mechanic and avionic shop for repairs. The staff and support team at [the Air Force Base] were very understanding and courteous.




Synopsis: The pilot of a Cessna 182 observed smoke and a burning smell so he declared an emergency and landed at a nearby military base. A shorted wire was identified as the cause.
Date: 201903
Local time of day: 0601-1200
Location: LIT.Airport, AR
Light: Daylight
Aircraft: EMB ERJ 145 ER/LR
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Initial Climb
Airspace: Class C LIT
ATC / advisory: TRACON LIT
Aircraft component: Hydraulic System
Component problem: Malfunctioning
Reporter organization: Air Carrier
Reporter qualification: Flight Crew Air Transport Pilot (ATP); Flight Crew Instrument; Flight Crew Multiengine
Human factors: Human-Machine Interface; Situational Awareness
Anomaly: Aircraft Equipment Problem Critical; Deviation / Discrepancy - Procedural Published Material / Policy; Deviation / Discrepancy - Procedural Weight And Balance
Detector: Person Flight Crew
When detected: In-flight
Result: Air Traffic Control Issued New Clearance; Flight Crew Landed in Emergency Condition; Flight Crew Returned To Departure Airport
Contributing factors: Aircraft
Primary problem: Aircraft

Narrative: Upon further inspection; Maintenance determined that there was a severe leak in the system and after opening the engine 1 cowling; most all of the hydraulic fluid came rushing out on to the ground. After departing and getting approximately 500 feet off of the ground the flight crew was made aware of a Hydraulic System 1 issue. The EICAS (Engine Indication and Crew Alerting System) had the following messages displayed: Aileron System 1 inop; Rudder System 1 inop; E1 hydraulic pump fail; and Hydraulic 1 low quantity. Hydraulic 1 quantity read 0. After switching over to Departure; the flight crew mentioned the issue and requested to land. Departure put us on a downwind heading and leveled us at 4;000 feet. The flight crew needed to extend downwind and base legs in order to run all appropriate checklists and to brief the approach. When all of this was completed; the flight crew returned to the field and landed overweight with less than a 300 feet per minute descent before touchdown without any incidents.




Synopsis: EMB-145 flight crew reported loss of hydraulics system 1 after takeoff and returned back to departure airport.
Date: 201404
Local time of day: 1201-1800
Location: ZZZZ.Airport, FO
Aircraft: B747-400
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Flight phase: Cruise
ATC / advisory: Center ZZZZ
Reporter organization: Air Carrier
Reporter function: Pilot Not Flying; Relief Pilot; First Officer
Human factors: Other / Unknown
Anomaly: ATC Issue All Types
Detector: Person Dispatch
When detected: In-flight
Result: Flight Crew Became Reoriented
Contributing factors: Procedure; Human Factors
Primary problem: Ambiguous

Narrative: While en-route to ZZZZ we were contacted by Dispatch via ACARS and informed we needed to adjust our airspeed (slow down) because our destination airport was NOTAM'd closed. Captain said he remembered nothing about an airport closure in the NOTAMs and asked me to look through the flight envelope at the NOTAMs again. I looked through all the NOTAMs and at first did not locate anything that said 'Arpt closed' then upon a second look I found something that said 'AD Closed' I asked Captain if this could have meant 'Aerodrome' he agreed that I was probably right. We adjusted our airspeed and refused all direct routing that was offered by ATC. In the end; we arrived at ZZZZ after the airport opened. Non standard terminology...using the term 'AD' instead of 'Arpt' in the NOTAMs. As pilots we are familiar with the seldom used term 'aerodrome' but never have I seen it in the NOTAMs as 'AD' I have only seen the term 'Arpt' used..... adding this to recurrent and perhaps a training memo may be in order.




Synopsis: B747 First Officer reports receiving an ACARS message from Dispatch that the destination airport is closed by NOTAM and they will need to slow down to meet the opening time. The Captain does not recall such a NOTAM but a recheck finds a NOTAM indicating 'AD closed'.
Date: 201605
Local time of day: 1801-2400
Location: RIC.Airport, VA
Weather elements / visibility: 5
Light: Night
Aircraft: Small Transport
Operator: Corporate
Operating under: Part 91
Flight plan: IFR
Mission: Passenger
Flight phase: Takeoff / Launch
ATC / advisory: Tower RIC
Reporter organization: Corporate
Reporter function: Captain; Pilot Flying
Reporter qualification: Flight Crew Air Transport Pilot (ATP)
Human factors: Confusion; Situational Awareness
Anomaly: Deviation / Discrepancy - Procedural Clearance; Deviation / Discrepancy - Procedural FAR; Ground Incursion Taxiway
Detector: Person Air Traffic Control
When detected: In-flight
Result: Air Traffic Control Issued Advisory / Alert
Contributing factors: Airport; Human Factors
Primary problem: Ambiguous

Narrative: I was cleared for takeoff on Runway 20 at Richmond International. When I got to the runway there was a sign which did not appear to be a standard runway marking sign; more like a temporary one stuck into the dirt; with an arrow and RW20 pointing to the right. I was a little confused by the sign; but I lined up on the centerline lights and double checked my heading to ensure I was on Runway 20 and not Runway 16 which is very close in proximity. I began takeoff roll and noticed quickly something was not right. I completed takeoff and on climbout the tower said that I had departed from the taxiway. I think that the sign that was present was indicating that the taxiway was Runway 20; and was very misleading. Also; I don't understand why the Tower did not say something to prevent this situation; as I was lined up on the centerline lights with my landing lights on; as well as nav lights; for a brief period; while I was checking the runway heading. I am quite sure that the Tower person was not even looking at me the whole time this was going on; as they were extremely close to my position on the field.




Synopsis: Corporate aircraft Captain reported taking off on a taxiway at RIC; citing a confusing sign as a contributing factor.
Date: 201707
Local time of day: 0601-1200
Location: ZZZ.Airport, US
Flight conditions: VMC
Light: Daylight
Aircraft: HS 125 Series
Operator: Corporate
Operating under: Part 91
Flight plan: IFR
Mission: Passenger
Flight phase: Takeoff / Launch
ATC / advisory: CTAF ZZZ
Aircraft component: Wheels/Tires/Brakes
Component problem: Failed
Reporter organization: Corporate
Reporter function: Pilot Flying; Captain
Reporter qualification: Flight Crew Instrument; Flight Crew Multiengine; Flight Crew Flight Instructor; Flight Crew Commercial
Human factors: Situational Awareness
Anomaly: Aircraft Equipment Problem Critical; Ground Event / Encounter Loss Of Aircraft Control; Ground Excursion Runway
Detector: Person Flight Crew
When detected: In-flight
Result: Aircraft Aircraft Damaged; Flight Crew Rejected Takeoff; General Evacuated
Contributing factors: Aircraft
Primary problem: Aircraft

Narrative: The day started where the plane is based. We departed with two passengers and headed to ZZZ to pick up four more. We did a visual approach and landing with no abnormalities. I allowed the plane to roll out the full distance of the runway to use minimal braking. We taxied in and shut down both engines to load the passengers that were waiting. I performed a quick walk around before boarding the aircraft. Once on board I gave short safety briefing and restarted the engines. We taxied out for departure. From the marks left by the tires it seemed at some point one of the right mains started leaking air and started leaving marks on the pavement. Once we got a release from ATC for takeoff we proceeded onto the runway for departure. On the takeoff roll at just before 127 KTS the right mains blew causing a loss of directional control and the takeoff was aborted at that time. I regained direction control and proceeded to stop the aircraft. The 4 tires took out the brake hydraulic lines on the right side and was left with just the left side brakes. I was unable to bring the plane to a full stop at the end of the runway and continued into the grass for an estimated 500 ft. Once stopped we shut down the aircraft and proceeded to evacuate the plane. A couple of small grass fires were started from the hot brakes which we quickly extinguished with the use of an on board fire extinguisher. The proper authorities were informed of the incident. No one was hurt and seems to be minimal damage to the aircraft.




Synopsis: HS-125 Captain reported aborting the takeoff when the right main tires blew. The aircraft came to a stop in the grass at the end of the runway.
Date: 202107
Local time of day: 0601-1200
Location: 061.Airport, CA
Flight conditions: VMC
Light: Daylight
Aircraft: Small Aircraft
Operator: Personal
Operating under: Part 91
Flight plan: VFR
Mission: Personal
Flight phase: Takeoff / Launch
Airspace: Class E ZOA
ATC / advisory: CTAF O61
Second aircraft: Small Aircraft
Reporter organization: Personal
Reporter function: Single Pilot
Reporter qualification: Flight Crew Private
Human factors: Communication Breakdown; Confusion; Situational Awareness
Anomaly: Conflict Airborne Conflict; Deviation / Discrepancy - Procedural Published Material / Policy
Detector: Person Flight Crew
When detected: In-flight
Result: Flight Crew Took Evasive Action
Contributing factors: Human Factors; Procedure
Primary problem: Human Factors

Narrative: I was holding short of the runway and heard a radio call that a small aircraft was on a 2 mile final straight in. I thought I heard Runway 31; and I was holding short on 31 and had no visual sight of the small aircraft. I heard him call again a 1 mile final; and I still had no visual sight. I looked up and down the runway both ways made sure we were clear and felt I had plenty of time to takeoff before he came into land. As I took off on Runway 31 I saw him inbound on Runway 13. Immediately I turned right and got out of his way.Reflecting on it; I should not have taken the runway. Even though I could not see a plane in either direction; knowing there was a plane on final I should've held short and waited for him to land. I haven't had a chance to review the recording; if possible; so even though I heard Runway 31; and I knew that I had plenty of time to takeoff based on the visual site to final; it may have been confirmation bias. The pilot may have said 13; and I heard 31. Regardless; I will never again take the runway when someone is on final.




Synopsis: A pilot departing O61 non-towered airport reported they observed an arriving aircraft head on to them as they were taking off and had to turn to avoid them. The reporter thought they heard the aircraft report inbound to the opposite direction runway they departed from.
Date: 201507
Local time of day: 1201-1800
Location: ZZZ.Airport, US
Flight conditions: IMC
Weather elements / visibility: Haze / Smoke; 1
Light: Daylight
Aircraft: Skylane 182/RG Turbo Skylane/RG
Operator: Personal
Operating under: Part 91
Flight plan: IFR
Mission: Personal
Flight phase: Taxi
ATC / advisory: Tower ZZZ
Aircraft component: Electronic Flt Bag (EFB)
Component problem: Improperly Operated
Reporter organization: Personal
Reporter function: Pilot Flying
Reporter qualification: Flight Crew Instrument; Flight Crew Private
Human factors: Human-Machine Interface; Situational Awareness; Confusion
Anomaly: Deviation / Discrepancy - Procedural Clearance; Deviation / Discrepancy - Procedural Published Material / Policy; Ground Incursion Taxiway
Detector: Person Air Traffic Control; Person Flight Crew
When detected: Taxi
Result: Air Traffic Control Issued Advisory / Alert; Air Traffic Control Issued New Clearance; Flight Crew Became Reoriented; Flight Crew Returned To Clearance
Contributing factors: Human Factors; Procedure
Primary problem: Human Factors

Narrative: After receiving; copying; and identifying an unusual IFR clearance we asked tower permission to taxi. Our primary charts were a geo-referenced Foreflight taxi diagram. We were given taxi instructions that seemed easy enough - but the upside down orientation of the chart and [another aircraft] taxiing took us off heading in a wrong direction initially. Upon getting visibility of the taxiway marking B; we slowed down; realizing that we started in the wrong direction. A second later; we received word from the [tower] that we were heading into a non-movement area and to stop. We were then given instructions to proceed. There was not an immediate danger of a conflict; but by neglecting to study the runway diagrams and not flipping the Foreflight charts contributed to the conflict. In the future; will be more diligent about taxi instructions and making sure that charts are properly oriented.




Synopsis: Pilot with his EFB Foreflight in the geo-reference mode began taxiing the wrong direction because the Airport chart's orientation was upside down relative to his airport visual view.
Date: 202107
Local time of day: 0601-1200
Location: ZZZ.Airport, US
Flight conditions: VMC
Weather elements / visibility: 10
Light: Daylight
Aircraft: Skyhawk 172/Cutlass 172
Operator: FBO
Operating under: Part 91
Flight plan: None
Mission: Training
Flight phase: Landing
ATC / advisory: CTAF ZZZ
Reporter organization: Personal
Reporter function: Instructor
Reporter qualification: Flight Crew Commercial; Flight Crew Multiengine; Flight Crew Instrument; Flight Crew Flight Instructor
Human factors: Situational Awareness; Training / Qualification
Anomaly: Deviation / Discrepancy - Procedural Published Material / Policy; Ground Event / Encounter Loss Of Aircraft Control; Ground Excursion Runway
Detector: Person Observer
When detected: Other Take Off Roll
Result: Aircraft Aircraft Damaged; General Flight Cancelled / Delayed; General Maintenance Action
Contributing factors: Human Factors; Procedure
Primary problem: Human Factors

Narrative: Student Pilot was coming in to land on Runway XX.  Winds were variable at approximately 4 knots at the time; skies clear.  Instructor witnessed the landing from inside the line office.  It appeared to be stable and smooth.  Student intended to do a touch and go.  Student went off the runway into the grass on the left side of Runway XX.  Instructor drove the line truck to check on student who was in the grass with the engine idling.  Instructor told student via radio to shut down the engine and secure the aircraft.  Student was not injured and visual damage to the aircraft appeared to be impact to the left fairing.  Student told instructor that he had a good landing but when he applied power the plane veered to the left.  In a follow-up phone call to the student later in the day; student reported no injuries or pain.  This was the students second landing of the day.  He did one touch and go earlier in the day; and then departed to the practice area before returning.  Student has soloed twice before this.  Student has 2.8 solo hours.  Student has progressed in his training; shown interest in learning and completed the written exam.




Synopsis: Flight Instructor reported observing his student have a runway excursion during a touch and go; damaging the airplane and having to be told to shut down the engine.
Date: 201712
Local time of day: 1801-2400
Location: ZZZ.TRACON, US
Weather elements / visibility: 30
Light: Night
Aircraft: Beechjet 400
Operator: Corporate
Operating under: Part 91
Flight plan: IFR
Mission: Ferry / Re-Positioning
Flight phase: Climb
Aircraft component: Aircraft Heating System
Component problem: Improperly Operated
Reporter organization: Corporate
Reporter function: Pilot Flying; First Officer
Reporter qualification: Flight Crew Instrument; Flight Crew Flight Instructor; Flight Crew Commercial; Flight Crew Multiengine
Human factors: Situational Awareness
Anomaly: Aircraft Equipment Problem Critical; Deviation / Discrepancy - Procedural Published Material / Policy; Flight Deck / Cabin / Aircraft Event Smoke / Fire / Fumes / Odor
Detector: Person Flight Crew
When detected: In-flight
Result: Air Traffic Control Provided Assistance; Flight Crew Diverted
Contributing factors: Aircraft; Human Factors
Primary problem: Ambiguous

Narrative: After having Maintenance performed; departed on IFR flight plan. On climbout RH pitot heat fail annunciated. Climbing through 8000 ft Second in Command (SIC)/Pilot Flying (PF) noted hot; burning smell. After brief discussion crew noted smoke visible in beam of light from passenger reading lamp in cabin. Smoke was acrid in odor; whitish/light grey and similar in density to cigarette smoke in appearance; and caused no burning sensation or vision issues. Crew stopped climb at 14;000 ft. SIC/PF donned oxygen mask and Pilot in Command (PIC)/Pilot Not Flying (PNF) investigated cabin for approximately 45 seconds for source of smoke. PIC/PNF could not isolate source of smoke and returned to flight deck. Crew elected to return to [departure airport].PIC took over PF duties; [advised ATC]; and initiated descent to 9000 ft. SIC calculated landing performance and worked checklist. Descending through 12000 ft bleeds were selected OFF. Smoke seemed to dissipate as descent continued.ATC approach coordinated support to meet crew at ZZZ; and crew performed an uneventful visual approach.The following morning; cause of smoke was determined to be cabin temperature control set to Manual/full increase by maintenance crew. RH Pitot heat Circuit Breaker (CB) was found tripped and was reset. Maintenance check flight was uneventful and airplane was returned to service.




Synopsis: BE400 First Officer reported smoke in the cabin that resulted in a return to the departure airport.
Date: 201807
Aircraft: Large Transport; Low Wing; 2 Turbojet Eng
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Cruise
Airspace: Class B DEN
ATC / advisory: TRACON D01
Reporter organization: Air Carrier
Reporter function: Captain
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; Inflight Event / Encounter Weather / Turbulence
Detector: Person Flight Crew
When detected: In-flight
Result: General None Reported / Taken
Contributing factors: Company Policy; Human Factors
Primary problem: Company Policy

Narrative: Evidently; the ACARS code TG is no longer supported; despite its presence in the FOM QRH. We tried to use the TG code going into Denver on a day when wind shear or microbursts were possible; and got no response. We queried Dispatch; who relayed from the Chief Pilot that TG was not supported; and to try WSI [Pilotbrief].WSI does not show wind shear or microburst activity. The TG returned a real time bird's eye view of actual weather; gust front and microburst activity at the airport. It was vital to pilot awareness; and the information it relayed is not available in WSI. Furthermore; WSI relies on Wi-Fi; and on [this airplane]; the Wi-Fi is unreliable. Our Wi-Fi was in fact inoperative.I hope [our company] will reconsider the decision to remove a valuable tool for pilots' awareness of real-time weather events. This decision did nothing to enhance safety; and in fact degraded it.




Synopsis: Air carrier Captain reported their air carrier has apparently terminated a procedure that allowed flight crews to access real time weather information in favor of a Wi-Fi dependent system that doesn't work as well.