elihoole/asrs-aviation-reports huggingface dataset:
Date: 202006
Local time of day: 0601-1200
Location: AVQ.Airport, AZ
Flight conditions: VMC
Weather elements / visibility: 10
Light: Daylight
Aircraft: Small Aircraft; Low Wing; 1 Eng; Fixed Gear
Operator: Personal
Operating under: Part 91
Flight plan: None
Mission: Personal
Flight phase: Initial Approach
Second aircraft: Skyhawk 172/Cutlass 172
Reporter organization: Personal
Reporter function: Pilot Flying; Single Pilot
Anomaly: Conflict NMAC
Detector: Automation Aircraft TA; Person Flight Crew
When detected: In-flight
Result: Flight Crew Took Evasive Action
Contributing factors: Human Factors
Primary problem: Human Factors

Narrative: I was conducting touch-and-go's with a flight instructor friend. Both I and Aircraft Y were making radio calls. There were two other aircraft in the pattern as well as skydivers landing at the airport. During my second touch-and-go; Aircraft Y entered the pattern directly below me from a 45-degree entry to the left downwind for Runway 21. My friend noticed traffic advisory alerts on an iPad running Foreflight that alerted us to the proximity. I maneuvered out of the pattern away from the runway to create space. Aircraft Y appeared to have no notice of my presence above him/her. Aircraft Y appeared on my right side (outside the pattern); disappeared under my [airplane]; and reappeared on my left (inside the pattern from me).




Synopsis: Pilot reported an NMAC event during landing practice with a nonreporting aircraft entered the landing pattern.
Date: 202106
Local time of day: 1801-2400
Location: ZZZ.Airport, US
Flight conditions: VMC
Weather elements / visibility: 10
Light: Night
Aircraft: Bonanza 35
Operator: Personal
Operating under: Part 91
Flight plan: VFR
Mission: Personal
Flight phase: Initial Approach
Airspace: Class D ZZZ
ATC / advisory: Tower ZZZ
Aircraft component: Electrical Power
Component problem: Failed
Reporter organization: Personal
Reporter function: Single Pilot; Pilot Flying
Reporter qualification: Flight Crew Private
Human factors: Time Pressure; Workload; Troubleshooting
Anomaly: Aircraft Equipment Problem Critical; Flight Deck / Cabin / Aircraft Event Other / Unknown; Ground Event / Encounter Gear Up Landing
Detector: Person Flight Crew
When detected: In-flight
Result: Flight Crew Landed As Precaution
Contributing factors: Aircraft
Primary problem: Aircraft

Narrative: Lost electrics in aircraft and cockpit went dark. Issue began with pulsating sounds in headset. Changed Comms 2 to 1 to see if [it was] a comm issue and [it] was not. Tried to call ZZZ Approach and had no PTT (Push-to-Talk) functions. At that time; I noticed the cockpit dimming fast. I changed comms and channels and made calls to ZZZ; Guard on [frequency]; and ZZZ1 Tower if anyone could hear me. Tried to operate runway lights but had no PTT functions.[I put the] gear down and the cockpit blacked out; airplane did not react as it usually does with full gear extension. Tried to input flaps but had no reaction. Opened emergency gear handle and tried to crank with a lot of thoughts running through my head. At this point; I was in complete darkness and in a left downwind for XXL. [I] had thoughts about a Tower fly-by or diversion to another airport via ForeFlight on iPhone; but without comms inside the SFRA and in a high stress situation; I committed to landing the airplane on XXL and went with it.




Synopsis: BE-35 pilot reported a loss of electric power inflight along with an overall loss of other aircraft functions; including proper landing gear retraction.
Date: 201407
Local time of day: 0601-1200
Location: HTO.Airport, NY
Flight conditions: VMC
Light: Dawn
Aircraft: Light Transport
Flight plan: IFR
Mission: Passenger
Flight phase: Taxi
ATC / advisory: Ground HTO
Reporter function: First Officer; Pilot Not Flying
Reporter qualification: Flight Crew Air Transport Pilot (ATP)
Human factors: Confusion; Situational Awareness
Anomaly: No Specific Anomaly Occurred All Types
Detector: Person Flight Crew; Person Air Traffic Control
When detected: Taxi
Result: Air Traffic Control Issued New Clearance; Flight Crew Became Reoriented
Contributing factors: Chart Or Publication; Human Factors; Procedure
Primary problem: Human Factors

Narrative: Ground issued a taxi clearance to taxi to Runway 10; via Runway 16 and Alpha.  We were parked at the main terminal ramp.  Trying to figure out where to exit the ramp; we stopped at the hold short line; of what turned out to be Runway 16/34.  Runway 4/22 is depicted on the airport Diagram as a closed runway; and does not have the runway numbers depicted.  We realized this; and before we could ask to use 16/34 to taxi to (closed) Runway 4; ATC told us to utilize Runway 16 to Runway 4 to Alpha to hold short Runway 10.  Based upon various parking conditions and congestion; it would be very easy to depart the ramp area; and mistake Runway 16/34 as a parallel taxiway due to its close relative position to the ramp area; and narrow width.  The lack of a Runway 4/22 on the Airport Diagram; congested; small ramp; added to the confusion and increase workload.  Additionally; this airport does not utilize the enhanced runway hold short markings; and the hold short markings at Taxiway A and Runway 10 are a bit faded.    Additionally; Ground Control mentioned to us that the AWOS frequency needs to be activated; and sometimes works by keying the microphone 3 times.  This isn't listed as a NOTAM; or on the Jeppesen chart. Please update Company Ops Notes to include these items.  Please recommend that ATC be cognizant of these issues when issuing taxi clearance to our aircraft; and provide an initial progressive taxi; whether requested or not; to ensure that the aircraft make the proper exit at the North end of the terminal ramp to avoid a potential for runway incursion by entering Runway 16/34 unintentionally.  Issues with the AWOS should be resolved as an issuance of a NOTAM; especially considering that HTO is a part-time Tower; without Radar surveillance.




Synopsis: First Officer reports confusion after being cleared by HTO Ground to taxi via Runway 16 and Taxiway A to Runway 10. The crew winds up holding short of Runway 16/34 at Taxiway F.
Date: 201903
Local time of day: 1801-2400
Location: ROA.Airport, VA
Flight conditions: VMC
Weather elements / visibility: 10
Light: Dusk
Aircraft: Small Aircraft
Operator: Personal
Operating under: Part 91
Flight plan: VFR
Mission: Personal
Flight phase: Final Approach
Airspace: Class C ROA
ATC / advisory: Tower ROA
Second aircraft: UAV - Unpiloted Aerial Vehicle
Reporter organization: Personal
Reporter function: Pilot Flying
Reporter qualification: Flight Crew Commercial; Flight Crew Flight Instructor; Flight Crew Instrument
Human factors: Distraction; Situational Awareness; Workload
Anomaly: Conflict Airborne Conflict; Deviation / Discrepancy - Procedural FAR; Deviation / Discrepancy - Procedural Published Material / Policy
Detector: Person Flight Crew
When detected: In-flight
Result: Flight Crew Took Evasive Action
Contributing factors: Human Factors
Primary problem: Human Factors

Narrative: On final approach segment of LDA Z Approach to Runway 6 at ROA; a drone was spotted by safety pilot. The drone was at 2 o'clock position and same altitude which was 200 feet AGL. The drone appeared to be flying in same direction or toward aircraft. Evasive turn away from drone was initiated but only a minor change in course was possible in the brief time available. The drone came within 1;500 feet of aircraft. Landing was completed and Roanoke Tower was advised of near miss.




Synopsis: Small aircraft pilot reported an airborne conflict with a UAV on final approach to ROA.
Date: 201510
Local time of day: 1801-2400
Location: ZZZ.ARTCC, US
Flight conditions: VMC
Light: Daylight
Aircraft: Texan T6/Harvard (Antique)
Operator: Personal
Operating under: Part 91
Flight plan: VFR
Mission: Personal
Flight phase: Cruise
Airspace: Class D ZZZ
ATC / advisory: Center ZZZ
Aircraft component: Engine
Component problem: Malfunctioning
Reporter organization: Personal
Reporter function: Pilot Flying; Single Pilot
Reporter qualification: Flight Crew Air Transport Pilot (ATP); Flight Crew Flight Instructor; Flight Crew Instrument; Flight Crew Multiengine
Anomaly: ATC Issue All Types; Aircraft Equipment Problem Critical; Ground Incursion Runway
Detector: Person Flight Crew
When detected: In-flight
Result: Flight Crew Landed in Emergency Condition; Flight Crew Landed As Precaution; Flight Crew Diverted
Contributing factors: Aircraft
Primary problem: Aircraft

Narrative: While flying at 1;500 ft MSL I experienced an engine malfunction where the engine rapidly began running rough and there was a significant loss of power.  It appeared that one of the 9 cylinders had malfunctioned.  I began a climb and pointed at the closest runway and [contacted] Center.  While in the climb to approximately 2;500 ft it appeared that both runways were closed however XYR had men and equipment on it.  I questioned Center as to what runway was open and they advised me to squawk a code and I advised I was unable to squawk at that time and that it was an emergency situation and I was landing.  I then landed the aircraft uneventfully with the engine still running.




Synopsis: North American T6 pilot reported diverting to a nearby airport when his engine began running rough.
Date: 201206
Local time of day: 1801-2400
Location: ZZZ.Airport, US
Flight conditions: VMC
Aircraft: A319
Operator: Air Carrier
Operating under: Part 121
Flight phase: Parked
Reporter organization: Air Carrier
Reporter function: Pilot Flying; Captain
Reporter qualification: Flight Crew Air Transport Pilot (ATP)
Human factors: Human-Machine Interface; Communication Breakdown
Anomaly: Deviation / Discrepancy - Procedural MEL / CDL; Deviation / Discrepancy - Procedural Published Material / Policy; Deviation / Discrepancy - Procedural Maintenance
Detector: Person Flight Crew
When detected: Aircraft In Service At Gate
Contributing factors: Aircraft; Company Policy; Human Factors; Procedure
Primary problem: Company Policy

Narrative: [The condition of the aircraft I received for a short turn around sequence is a good example of the low maintenance standards acceptable to our airline.] The aircraft had 12 MEL's including no auto throttle and no flight director. You [the reader] should all read the MEL's; our release; the routing and then just sit there and role play the scene [that would predictably follow]. I didn't bother calling my Flight Managers as I have tried that before and found [name] to be an out of touch 'pilot pusher' who will attempt to question your skills as opposed to addressing your legitimate concerns and [second name] who blasted a pilot for having gone to the FAA when he was concerned about the current state of operations. Instead of me describing the flight; I really think that role playing the event will be more enlightening. It would be great if you would just show up at the jet and--right then--get the release; the weather; the clearance; an MEL and pretend like it is you guys on the Flight Deck with the same situation. Brief everything like you are doing the flight.My intention is not to do harm to our airline by bringing our low standards to light. In fact; just the opposite our airline is like a practicing alcoholic in complete denial. When you read [Manager's name] letter about [our situation; he basically says] 'we just have some issues with our seats;' you realize that they are not grasping what is really going on here. Going to the FAA and providing this information in safety reports is actually helping the 'alcoholic' ([our airline]) to admit; get help; and get better even though in their current mental state they completely miss this point.Here are some suggestions. Please fix the auto throttle on this jet as it has been a chronic problem for about one year. I don't think that was the intention of the MEL. Flight Management's phone conversations with pilots should be tape recorded. Fix our airplanes in a timely manner. Back the pilots to help raise the bar not berate them (ala [previously mentioned managers]) so as to lower the bar. I would be OK with going before [our safety evaluation committee] if you feel that this would help fix the problem.




Synopsis: An A-319 Captain expressed his concern regarding his airline's failure to adequately address long term maintenance issues; pilot pushing and pilot intimidation.
Date: 202001
Local time of day: 1201-1800
Location: MDW.Airport, IL
Light: Daylight
Aircraft: Large Transport; Low Wing; 2 Turbojet Eng
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Taxi
ATC / advisory: Tower MDW
Reporter organization: Air Carrier
Reporter function: First Officer; Pilot Flying
Reporter qualification: Flight Crew Air Transport Pilot (ATP); Flight Crew Instrument; Flight Crew Multiengine
Human factors: Communication Breakdown; Situational Awareness; Confusion
Anomaly: ATC Issue All Types; Deviation / Discrepancy - Procedural Published Material / Policy; Ground Incursion Taxiway
Detector: Person Air Traffic Control
When detected: Taxi
Result: Air Traffic Control Issued Advisory / Alert; Flight Crew Requested ATC Assistance / Clarification
Contributing factors: Human Factors; Airport; Procedure
Primary problem: Procedure

Narrative: We were given the taxi instructions taxi to Runway 31C via [Taxiways] Y; P; G; cross [Runway] 31R. When we arrived at [Runway] 31C there was an aircraft holding short of [Runway] 31C on [Taxiway] E1 and one on E3. The Captain went around the aircraft on E1 and pulled into E2 holding short of [Runway] 31C. ATC then gave us a phone number to call.




Synopsis: An Air Carrier First Officer reported incomplete taxi instructions which caused a taxiway incursion.
Date: 201904
Local time of day: 0601-1200
Location: ZZZZ.Airport, FO
Flight conditions: VMC
Aircraft: B777 Undifferentiated or Other Model
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Final Approach
ATC / advisory: Center ZZZZ
Reporter organization: Air Carrier
Reporter function: Pilot Not Flying; Captain
Reporter qualification: Flight Crew Multiengine; Flight Crew Instrument; Flight Crew Air Transport Pilot (ATP)
Anomaly: Aircraft Equipment Problem Less Severe; Flight Deck / Cabin / Aircraft Event Smoke / Fire / Fumes / Odor
Detector: Person Flight Attendant
When detected: In-flight
Result: General None Reported / Taken
Contributing factors: Aircraft
Primary problem: Aircraft

Narrative: On approach to ZZZZ Runway 11 descending through 8;800; the flight attendants reported the odor of chemical smoke (fumes) in the cabin by door 2L. They did not report seeing any smoke. We asked them to look in the lavatory and at the fluorescent lights. They reported that they were unable to identify the source of the odor. We advised them to monitor the area as we were minutes from touchdown. Upon clearing the runway; our relief pilot immediately entered the cabin to determine the source of the odor. He reported that any odor had disappeared and that the flight attendants agreed with his conclusions. We taxied to the gate without incident.




Synopsis: B777 Captain reported being informed by flight attendants of chemical smoke fumes in the cabin during approach.
Date: 201308
Local time of day: 1801-2400
Location: ZZZ.TRACON, US
Flight conditions: VMC
Light: Night
Aircraft: Regional Jet 200 ER/LR (CRJ200)
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Descent
Airspace: Class E ZZZ
ATC / advisory: TRACON ZZZ
Aircraft component: Air Conditioning and Pressurization Pack
Component problem: Failed
Reporter organization: Air Carrier
Reporter function: Captain; Pilot Flying
Human factors: Situational Awareness
Anomaly: Aircraft Equipment Problem Less Severe
Detector: Automation Aircraft Other Automation; Person Flight Crew
When detected: In-flight
Result: Flight Crew FLC complied w / Automation / Advisory; General Maintenance Action
Contributing factors: Aircraft
Primary problem: Aircraft

Narrative: While descending to 11;000 FT our left pack automatically switched off and all airflow stopped. The right pack was deferred. The cabin started to climb at approximately 700 FPM. The Captain was the pilot flying. The pilot flying stated he had the controls and the radios and the First Officer ran the unpressurised flight checklist. The pilot flying asked ATC for an immediate descent to 3;000 FT. ATC replied the lowest they could give us was 3;500 FT. We accepted that clearance and immediately made a descent to 3;000 FT. During the descent the First Officer finished the QRH Checklist. The Captain then instructed him to tell the Flight Attendant of the situation as our ears were definitely popping with the quick decrease in cabin pressure. The cabin met us at approximately 5;000 FT (Cabin and Aircraft were at 0.0 Delta P). We advised her we were at a safe cabin altitude and no action would need to be taken. We would be landing in less than 5 minutes. We were operating with a single PACK as the right pack was deferred. This was a previous write up on the plane; twice prior to this event within the week. The Captain had actually briefed the Flight Attendant and First Officer to the previous write-ups and stated that we needed to look out for this. When we initially took the plane 3 flights prior. We were mentally prepared for this issue as it was a previous write-earlier. Pressurization issues are serious. If this had happened at FL250 (Max altitude for a single PACK) we would have had only a few minutes of useful consciousness to react. This was the third write-up in a short period of time on the same issue. These maintenance issues should be corrected better and not so easily signed off as fixed.




Synopsis: CRJ200 Captain reports being dispatched with a pack inoperative then losing the second pack during descent at 11;000 FT. Flight continues to destination with the cabin unpressurized below 5;000 FT.
Date: 202001
Local time of day: 1201-1800
Location: ZZZ.Airport, US
Light: Daylight
Aircraft: Commercial Fixed Wing
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Parked
Reporter organization: Air Carrier
Reporter function: Pilot Flying; Captain
Reporter qualification: Flight Crew Instrument; Flight Crew Multiengine; Flight Crew Air Transport Pilot (ATP)
Anomaly: Deviation / Discrepancy - Procedural Hazardous Material Violation; Deviation / Discrepancy - Procedural Published Material / Policy
Detector: Person Flight Crew
When detected: Aircraft In Service At Gate
Result: General None Reported / Taken
Contributing factors: Human Factors
Primary problem: Human Factors

Narrative: Upon arriving at the gate in ZZZ; we (Cockpit Crew) were given a Hazmat cargo report with the normal paper work Operations Agents give the cockpit upon arrival. I initially thought we (Crew) were going to be taking Hazmat on our next flight; but after looking at the 'origin/destination' section of the report; I realized it was for the flight that was just completed. I went up the jetway and inquired about the Hazmat report we (Cockpit Crew) were given and informed the Operations Agent that we (Cockpit Crew) were unaware of any Hazmat onboard. The Operations Agent called a Supervisor who came to the gate and I informed them (Supervisor and Operations Agent) that we (Cockpit Crew) were unaware of any Hazmat onboard; and were not given any verbal notification or a NOTAC to sign before we departed from ZZZ1. I contacted the Chief Pilot on Call to apprise them of the situation and to see if there were any hoops we (Cockpit Crew) had to jump through or boxes that need to be checked before we (Crew) continued on our next flight.




Synopsis: Air carrier Captain reported receiving required Hazmat documents for flight at destination instead of prior to departure.
Date: 202112
Local time of day: 1201-1800
Location: ZZZ.Airport, US
Aircraft: EMB ERJ 145 ER/LR
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Initial Climb
Airspace: Class B ZZZ
ATC / advisory: TRACON ZZZ
Aircraft component: Cockpit Window
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
Human factors: Time Pressure; Troubleshooting
Second reporter function: Captain; Pilot Flying
Anomaly: Aircraft Equipment Problem Critical
Detector: Person Flight Crew
When detected: In-flight
Result: Air Traffic Control Provided Assistance; Flight Crew Returned To Departure Airport; Flight Crew Overcame Equipment Problem; Flight Crew Landed As Precaution
Contributing factors: Aircraft; Weather
Primary problem: Aircraft

Narrative: Climbing through 16;000 ft after departing from ZZZ I noticed what appeared to be a 6 inch crack in the captain's windscreen. Neither the Captain nor myself had seen it before that moment. We stopped our climb at 17;000 and told ATC. We decided to return to ZZZ and [requested priority]. The Captain had me run the QRH for cracked windscreen. He informed the flight attendant; dispatch; and the passengers. After some delay vectors to burn fuel to get under max landing weight we landed back at ZZZ.


Second narrative: During climb out; First Officer pointed out what appeared to be a crack in the Captain's windshield. We decided to return to ZZZ. After burning fuel down to acceptable landing weight; we had a normal landing and taxi to gate. On the ground; Maintenance determined it was a scratch and within limits. The scratch was almost impossible to see while the windshield was wet in the rain; [and] we didn't see it until we were in the air above the clouds.If we had a note or list of damage on the aircraft that is already noted and acceptable; it would help crews avoid maintenance diversions.


Synopsis: EMB145 flight crew reported what they thought was a cracked window.  They returned to the departure airport and had aircraft checked by maintenance to reveal it was a scratch within tolerance.