elihoole/asrs-aviation-reports huggingface dataset:
Date: 201811
Local time of day: 0601-1200
Location: 1TE4.Airport, TX
Aircraft: No Aircraft
Reporter function: Pilot Not Flying
Reporter qualification: Flight Crew Air Transport Pilot (ATP); Flight Crew Instrument; Flight Crew Multiengine
Anomaly: Deviation / Discrepancy - Procedural Published Material / Policy
Detector: Person Flight Crew
Result: General None Reported / Taken
Contributing factors: Chart Or Publication
Primary problem: Chart Or Publication

Narrative: Zuehl Airport (1TE4) is no longer on the San Antonio Sectional Chart. For more than a year Zuehl has been charted as 'OBJECTIONABLE' with no elevation or runway data depicted. I found that to be hazardous; but wait; it is now even more hazardous! An airport that absolutely does not exist is now depicted about .9 mile Northeast of where Zuehl does exist. Charted as Nighthawks Nest (TT45) featuring a 7634' x 150' asphalt runway and a 4387' x40' turf runway. Might be planned; but it ain't there. That is hazardous in my book. Zuehl belongs on the chart; it is definitely there and many people and airplanes live there. Additionally it is a viable emergency landing field and should be accessible via a typical 'nearest' button on a GPS. For the same reason TT45 should NOT be charted.




Synopsis: GA pilot reported that airport 1TE4 (Zuehl) is no longer on the San Antonio Sectional chart and near its place is TT45; a private airport.
Date: 201211
Local time of day: 1201-1800
Location: EWR.Airport, NJ
Flight conditions: VMC
Aircraft: Commercial Fixed Wing
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Taxi
ATC / advisory: Ground EWR
Reporter organization: Air Carrier
Reporter function: Captain; Pilot Flying
Reporter qualification: Flight Crew Air Transport Pilot (ATP)
Human factors: Confusion
Anomaly: Deviation / Discrepancy - Procedural Clearance; Ground Incursion Taxiway
Detector: Person Air Traffic Control; Person Flight Crew
When detected: Taxi
Result: Air Traffic Control Issued New Clearance; Flight Crew Became Reoriented
Contributing factors: Human Factors; Chart Or Publication; Airport
Primary problem: Airport

Narrative: We were cleared to taxi to Runway 4L via [RG;] B and D. Looking out across RG the signage is confusing and it doesn't look like it does on the airport page. It appears to be straight across to B but I think it was actually more of a left jog and then a hard right. I took a right on A thinking it was the quickest way to B but it doesn't work that way. Ground told us to continue down A and then take N to D. Once there; however; the signage where A intersects with N is also confusing as you approach it.




Synopsis: The Captain of an unidentified aircraft type cleared to Runway 4L was confused by the complexity of the taxiway layout and signage at EWR and inadvertently turned from RG to A vice B as cleared. Ground Control supplied a revised clearance.
Date: 201706
Local time of day: 1801-2400
Location: 5BL.Airport, AK
Flight conditions: VMC
Weather elements / visibility: 50
Light: Daylight
Aircraft: Seaplane or Amphibian
Operator: Personal
Operating under: Part 91
Flight plan: VFR
Mission: Personal
Flight phase: Initial Climb
ATC / advisory: CTAF 5BL
Reporter organization: Personal
Reporter function: Pilot Flying; Single Pilot
Reporter qualification: Flight Crew Commercial; Flight Crew Sea; Flight Crew Rotorcraft; Flight Crew Instrument
Human factors: Situational Awareness
Anomaly: Deviation / Discrepancy - Procedural Published Material / Policy; Deviation / Discrepancy - Procedural FAR; Inflight Event / Encounter Weather / Turbulence
Detector: Person Flight Crew
When detected: In-flight
Result: Flight Crew Became Reoriented; Flight Crew Took Evasive Action
Contributing factors: Aircraft; Human Factors; Weather
Primary problem: Ambiguous

Narrative: After landing in salt water I landed at Beluga Lake to rinse the salt off before proceeding north; I'm on amphibs. The afternoon southwest daybeeze was blowing so I took off southwest on the lake climbing to the recommended 1;000 feet before initiating a slow turn to the right toward rising terrain judging that with the slow turn and lift from the rising terrain and onshore wind; and a high performance aircraft; that I could easily reach the 2;000 feet desirable to avoid noise and flying too low over houses. As the turn progressed I encountered sinking air which reduced my climb rate; but I thought it only temporary. By the time I came to the realization the sinking air was not going away; hot day may have also been a factor; I was too close to the ground 500 or so; to go to full power (I was at 25 squared); as to the noise issue. I still had room to turn back and glide to safety; and was going to easily clear the rising terrain; but was at least 500 feet lower than I wanted to be; at a high power setting over homes in a noise sensitive are. I was very uncomfortable with the situation I put myself into.What I should have done was climb to at least 1;800 or more before initiating to turn. I also think that a recommended altitude in the Alaska Supplement for 5BL that aircraft taking off westerly should climb to some altitude; 1;500-2;000; before initiating a turn north. I am an experienced local and still found myself in this situation where anticipated aircraft performance and too early of a turn initiation put me in a too low situation.




Synopsis: General aviation pilot reported encountering sinking air after departing 5BL west bound and turning right at 1;000 feet. This resulted in being at 500 feet AGL over a noise sensitive area at high power.
Date: 201203
Local time of day: 1201-1800
Location: ZZZ.ARTCC, US
Aircraft: LA-4 A/B Buccaneer
Operating under: Part 91
Flight plan: VFR
Mission: Training
Flight phase: Cruise
Airspace: Class G ZZZ
Aircraft component: Engine
Component problem: Malfunctioning
Reporter qualification: Flight Crew Student
Anomaly: Aircraft Equipment Problem Critical
Detector: Person Flight Crew
When detected: In-flight
Result: Flight Crew Diverted; Flight Crew Landed in Emergency Condition
Contributing factors: Aircraft
Primary problem: Aircraft

Narrative: Made an emergency landing on highway.




Synopsis: Lakes amphibian student pilot reports an emergency landing on a highway.
Date: 201605
Local time of day: 0001-0600
Location: ZZZ.ARTCC, US
Flight conditions: VMC
Aircraft: A320
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Flight phase: Cruise
Airspace: Class A ZZZ
ATC / advisory: Center ZZZ
Aircraft component: Cargo Compartment Fire/Overheat Warning
Component problem: Malfunctioning
Reporter organization: Air Carrier
Reporter function: Captain; Pilot Not Flying
Reporter qualification: Flight Crew Air Transport Pilot (ATP)
Human factors: Confusion; Situational Awareness
Anomaly: Aircraft Equipment Problem Less Severe; Deviation / Discrepancy - Procedural FAR; Deviation / Discrepancy - Procedural Published Material / Policy; Flight Deck / Cabin / Aircraft Event Smoke / Fire / Fumes / Odor
Detector: Person Flight Crew
When detected: In-flight
Result: Flight Crew Overcame Equipment Problem
Contributing factors: Aircraft; Human Factors
Primary problem: Aircraft

Narrative: During cruise; a momentary 'Smoke Fwd (aft) Cargo Smoke' ECAM warning appeared. The ECAM lasted approximately 2-4 seconds then disappeared. The ECAM could not be recalled using the 'Recall' key on the switching panel. However; the ECAM status display showed the Deferred Items as depicted in the Flight Manual and the overhead Cargo Fire Warning panel showed a 'Disch1' light; as if the initial ECAM warning was still displayed.After consultation with Dispatch and maintenance; verifying with the cabin crew that there were no indications in the rear of the airplane indicating a problem; and the fact that the Cargo Smoke system tested correctly prior to flight; it was agreed that this was some type of momentary system fault and NOT a threat to the aircraft's safety. No emergency [situation reported to ATC] and we proceeded towards our destination.Although the ECAM had cleared itself immediately with no action taken by the pilots; we continued to consult the QRH where applicable and coordinated to have all passengers disembarked prior to the cargo doors being opened on the ground. Additionally; Dispatch coordinated to have Fire Fighting personnel available to use infrared scanning to ensure there wasn't any unusual heat signature in the hold. The potential issue requiring this filing centers around whether it was necessary to land the plane as soon as possible as the Flight Manual calls for if the ECAM warning had persisted. As the ECAM warning had disappeared almost instantly and couldn't be recalled; and I had conferred with dispatch and maintenance; I didn't deem that landing as soon as possible in an overweight airplane at the closest suitable field to be appropriate.




Synopsis: A320 Captain reported continuing to destination after receiving a momentary ECAM for cargo smoke.
Date: 201401
Local time of day: 0601-1200
Location: ZZZ.Airport, US
Flight conditions: VMC
Light: Dawn
Aircraft: BAe 125 Series 800
Operating under: Part 91
Flight phase: Takeoff / Launch
Airspace: Class D ZZZ
ATC / advisory: Tower ZZZ
Aircraft component: Aeroplane Flight Control
Component problem: Malfunctioning
Reporter function: First Officer; Pilot Flying
Reporter qualification: Flight Crew Air Transport Pilot (ATP)
Human factors: Human-Machine Interface
Anomaly: Aircraft Equipment Problem Critical; Deviation - Track / Heading All Types
Detector: Person Flight Crew
When detected: In-flight
Result: Flight Crew Returned To Departure Airport
Contributing factors: Aircraft
Primary problem: Aircraft

Narrative: We were assigned a short repositioning flight. We ran all the checks for Taxi and T/O and everything checked ok. We were cleared for takeoff and when; at 80 knots; the Captain transferred the controls to me the aircraft pulled to the right a bit; which some of them do occasionally on control transfer; so I put more left rudder in and straightened the aircraft out. The aircraft was now back on centerline and felt normal again. On rotation the aircraft yawed to the right; as if weather vaning into the wind but there was no cross wind; so it took more left rudder to keep it going straight. I noticed it and so did the Captain so he took control to see if he could fix it. We climbed on course for a couple of minutes to try to fix it or see if it would correct itself and it did not. We then advised ATC that we needed to return to the airport and received vectors back for an overweight but uneventful landing on 02.




Synopsis: A BAE125-850XP flight crew experienced unexplained right yaw on takeoff and returned to their departure airport.
Date: 201911
Local time of day: 1201-1800
Location: PIT.Airport, PA
Flight conditions: VMC
Aircraft: Large Transport
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Taxi
Reporter organization: Air Carrier
Reporter function: Captain; Pilot Not Flying
Reporter qualification: Flight Crew Air Transport Pilot (ATP); Flight Crew Instrument; Flight Crew Multiengine
Human factors: Other / Unknown; Workload
Anomaly: 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
Primary problem: Chart Or Publication

Narrative: Since I have not flown into PIT very much; I was unfamiliar with the taxiway issue. It would be nice if they fix the airport diagram in the charts and add a taxiway sign or paint the names on the ground. I will spread the word.




Synopsis: Air carrier Captain reported lack of taxiway signage and an outdated airport diagram resulted in confusion during taxi at PIT airport.
Date: 201810
Local time of day: 1801-2400
Location: EWR.Airport, NJ
Flight conditions: IMC
Weather elements / visibility: Rain
Aircraft: B767 Undifferentiated or Other Model
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Final Approach
Airspace: Class B EWR
ATC / advisory: Tower EWR
Aircraft component: Autoflight System
Component problem: Malfunctioning
Reporter organization: Air Carrier
Reporter function: First Officer; Pilot Not Flying
Reporter qualification: Flight Crew Multiengine; Flight Crew Air Transport Pilot (ATP); Flight Crew Instrument
Second reporter function: Relief Pilot; First Officer; Pilot Not Flying
Anomaly: Aircraft Equipment Problem Less Severe; Inflight Event / Encounter Unstabilized Approach; Inflight Event / Encounter Weather / Turbulence
Detector: Person Flight Crew
When detected: In-flight
Result: Flight Crew Executed Go Around / Missed Approach
Contributing factors: Aircraft
Primary problem: Aircraft

Narrative: EWR had low ceilings and shifting winds. The 4R was out of service; and RNAV approaches were advertised on the ATIS. We prepared and briefed the RNAV (RNP) Z 4R; as the minima were lowest; to better ensure seeing the runway at or before minimums. The autoflight and VNAV functions worked normally until passing the FAF. Upon passing the FAF; and as the winds aloft were shifting towards a headwind; VNAV PTH remained displayed; however the aircraft did not descend; despite touchdown zone altitude being set in the altitude window; per procedure. Indeed; all 3 of us noted that the Captain PFD showed us as being below the vertical path; whereas mine showed being above. The vertical path deviation indicators rapidly diverged and the aircraft remained at 1700 FT as we progressed toward the runway. This was obviously unacceptable; exceeding tolerances; and as such we elected to conduct a missed approach and informed ATC. We subsequently briefed and flew the ILS 4R GS out of service; using LOC and VNAV. This approach was uneventful.


Second narrative: I was in the jumpseat for the RNAV RNP Z 4R. Per the QRH briefing; we briefed if aircraft deviates outside of limits on the vertical path of +75 FT on prog page 2; it is an automatic disqualification for the approach criteria and necessitates a go-around. On the approach; the autopilot deviated from the vertical path by +75 FT and caused us to go-around per the briefing in the QRH.


Synopsis: B767 First Officer and Relief Pilot reported executing a go-around at EWR when the autopilot failed to track the vertical path accurately.
Date: 202009
Aircraft: Commercial Fixed Wing
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Cruise
Airspace: Class A ZZZ
Reporter organization: Air Carrier
Reporter function: Flight Attendant (On Duty)
Reporter qualification: Flight Attendant Current
Human factors: Situational Awareness; Confusion; Troubleshooting
Anomaly: Aircraft Equipment Problem Less Severe; Deviation / Discrepancy - Procedural Published Material / Policy
Detector: Person Flight Attendant
When detected: In-flight
Result: General None Reported / Taken
Contributing factors: Company Policy; Human Factors
Primary problem: Company Policy

Narrative: FA D on this aircraft is assigned a jumpseat that is located in the aisle at/adjacent to the AFT RH LAV door (legs and feet cross pass LAV door). With COVID precautions to lower the spread of this disease; the X row of this aircraft is normally blocked for FA use only. At boarding time; someone released the X row and filled with paying passenger; even though this flight went out with 8-10 non-revs and had an additional 7 open seats (scattered about the main cabin). At cruise level of flight; FA D used a galley box to sit on in the AFT Galley to enable passenger's access to the AFT LAV without tripping over feet and/or possible exchange of disease between passengers and FA. FA was in assigned jumpseat for taxi; takeoff; and landing.Equip this aircraft with a jumpseat at the AFT RH door so that FA D is out of path to LAV and is closest to the AFT RH door for evacuation needs.




Synopsis: Flight Attendant reported a row that is typically blocked for Flight Attendant use was released for passenger seating.
Date: 202107
Local time of day: 1201-1800
Location: FCM.Airport, MN
Flight conditions: VMC
Weather elements / visibility: 10
Light: Daylight
Aircraft: Small Aircraft; Low Wing; 1 Eng; Retractable Gear
Operator: Personal
Operating under: Part 91
Flight plan: IFR
Mission: Personal
Flight phase: Initial Approach
Airspace: Class D FCM
ATC / advisory: Tower FCM
Aircraft component: GPS & Other Satellite Navigation
Component problem: Malfunctioning
Reporter organization: Personal
Reporter function: Single Pilot
Reporter qualification: Flight Crew Private; Flight Crew Instrument
Human factors: Workload; Troubleshooting; Human-Machine Interface; Confusion; Distraction
Anomaly: Aircraft Equipment Problem Less Severe
When detected: In-flight
Result: Flight Crew Requested ATC Assistance / Clarification; Flight Crew Became Reoriented
Contributing factors: Software and Automation; Aircraft; ATC Equipment / Nav Facility / Buildings
Primary problem: ATC Equipment / Nav Facility / Buildings

Narrative: Complete GPS Signal loss for 2 minutes without NOTAM or other notification. I have 5 devices with built-in GPS devices connected to 3 GPS antennas.  Additionally; I had a portable GPS; with its own GPS antenna and power supply.  All GPS devices reported a complete lost of signal.  I covered about 3.5 miles while on the visual approach.  Signal was restored; but the virtual glideslopes from the GPS's were not available. I reported the event to the tower. Since I was in visual condition; I was able to maintain control of the aircraft and was hand flying for the landing.  Since I had been navigating with GPSS and the autopilot; this could have created a surprise in the loss of GPSS steering.  Additionally; had this been in IMC; I would have lost the glideslope and needed to make changes.  I do not know how the coupled autopilot would have responded. I do not know where else to report this sudden loss of GPS signal.




Synopsis: A General aviation pilot reported loss of GPS signal. The reporter had five GPS receivers in the aircraft.
Date: 202111
Local time of day: 0601-1200
Location: ZZZ.TRACON, US
Flight conditions: VMC
Aircraft: EMB ERJ 145 ER/LR
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Cruise
Airspace: Class A ZZZ
ATC / advisory: TRACON ZZZ
Aircraft component: Cargo Compartment Fire/Overheat Warning
Component problem: Malfunctioning
Reporter organization: Air Carrier
Reporter function: Pilot Flying; Captain
Reporter qualification: Flight Crew Multiengine; Flight Crew Instrument; Flight Crew Air Transport Pilot (ATP)
Human factors: Workload; Time Pressure
Anomaly: Aircraft Equipment Problem Less Severe; Deviation / Discrepancy - Procedural Clearance; Deviation / Discrepancy - Procedural Weight And Balance; Deviation / Discrepancy - Procedural Published Material / Policy; Flight Deck / Cabin / Aircraft Event Smoke / Fire / Fumes / Odor
Detector: Automation Aircraft Other Automation; Person Flight Crew
When detected: In-flight
Result: Air Traffic Control Provided Assistance; Flight Crew Diverted; Flight Crew Landed As Precaution; Flight Crew Requested ATC Assistance / Clarification
Contributing factors: Aircraft
Primary problem: Aircraft

Narrative: BAGG SMOKE posted while in cruise flight at FL340. [Requested priority handling] and applied QRH and diverted to nearest suitable (ZZZ) [airport] and performed emergency/overweight landing (with clearance from ATC and Dispatch also applied QRH related to overweight landing (in-flight) and emergency evacuation (after landing in ZZZ). Was unable to determine in-flight if the BAGG SMOKE was a 'legitimate' fire; or merely a faulty system indication; so assumed the worst in the interest of safety. ZZZ Approach was particularly unhelpful in this situation. They did not volunteer information (such as that XXL LOC/GS was out-of-service) that could have been helpful in the crew picking a suitable landing runway (the crew had not reviewed NOTAMs for ZZZ as it was neither our destination; nor filed alternate). Also; on final-approach; they simply stated 'Contact Tower' (without providing the frequency) thus forcing the crew to look it up on EFB and thus go 'heads-down' during a critical emergency landing; etc. A supplemental system to monitor the temperature of the Cargo Compartment (in addition to the presence of smoke) would assist the crew in determining the legitimacy of BAGG SMOKE warnings...and the subsequent need (or lack thereof) for post-landing emergency evacuation on the runway.




Synopsis: ERJ-145 Captain reported Baggage Smoke EICAS warning during cruise. Flight crew executed a diversion to nearest suitable airport and completed a safe overweight landing.
Date: 202101
Local time of day: 1201-1800
Location: ZZZ.Airport, US
Weather elements / visibility: 10
Aircraft: Amateur/Home Built/Experimental
Operator: Personal
Operating under: Part 91
Flight plan: None
Mission: Personal
Flight phase: Takeoff / Launch
Reporter organization: Personal
Reporter function: Pilot Flying; Single Pilot
Reporter qualification: Flight Crew Commercial; Flight Crew Instrument
Human factors: Situational Awareness
Anomaly: Deviation / Discrepancy - Procedural Clearance; Deviation / Discrepancy - Procedural Published Material / Policy; Ground Excursion Runway; Ground Incursion Runway; Inflight Event / Encounter Loss Of Aircraft Control
Detector: Person Flight Crew
When detected: In-flight
Result: General Flight Cancelled / Delayed
Contributing factors: Aircraft; Human Factors
Primary problem: Ambiguous

Narrative: Cleared for takeoff; power was applied; and aircraft veered left and departed the pavement coming to rest in the grass next to the parallel turf runway. Main runway was temporarily closed; and alternate intersecting runway put into use. Once responding airport vehicles released the aircraft to taxi back to parking; aircraft taxied on closed turf runway prior to stopping at main (closed) concrete runway and calling Ground for taxi instructions. It would probably have been preferable for aircraft to call for taxi instructions prior to any movement. Signage could possibly be added as reminder that turf operations should have taxi instructions as well.




Synopsis: Single pilot reported that during takeoff roll the aircraft veered left and departed the runway. During taxi back to parking; pilot did not call ground control for taxi clearance.