elihoole/asrs-aviation-reports huggingface dataset:
Date: 201405
Local time of day: 1201-1800
Location: HPN.Airport, NY
Flight conditions: VMC
Weather elements / visibility: 10
Light: Daylight
Aircraft: Challenger 605
Operator: Corporate
Operating under: Part 91
Flight plan: IFR
Mission: Passenger
Flight phase: Final Approach
Airspace: Class D HPN
ATC / advisory: Tower HPN
Second aircraft: Bonanza 36
Reporter organization: Corporate
Reporter function: Pilot Flying; Captain
Reporter qualification: Flight Crew Air Transport Pilot (ATP)
Second reporter function: Single Pilot; Pilot Flying
Anomaly: Conflict Airborne Conflict
Detector: Automation Aircraft RA; Person Flight Crew
When detected: In-flight
Result: Air Traffic Control Issued New Clearance; Flight Crew Took Evasive Action
Contributing factors: Human Factors; Procedure
Primary problem: Procedure

Narrative: On 3 NM final for Runway 34 at HPN; TCAS RA and visual evasive maneuver to avoid aircraft being initially vectored for Runway 29. Aircraft passed within 150 FT (estimated).


Second narrative: I was on final for Runway 29 ATC changed my runway and stated I was number 2 for Runway 34. I acknowledged the change and stated that I was entering the base for 34. There was another aircraft inbound for 29. While on base I was trying to query if the jet rolling on 34 was my traffic. Then noticed another aircraft on final at my 9 [o'clock]. As I started a climb to avoid Tower instructed me to fly through the final and make a right turn to rejoin 34. I followed those instructions after visually confirming the other aircraft was safely below and ahead of me. While turning final the other aircraft inbound for 29 was instructed to go around for the landing traffic on 34.The problem could have been avoided if the other inbound traffic for 29 switched runways and I continued on final (better spacing) or if I was instructed specifically to join a downwind for 34.


Synopsis: A CL605 Captain and a BE36 pilot approaching HPN; describe an airborne conflict that develops while both aircraft are being controlled by ATC. The CL605 Captain takes evasive action for a TCAS RA with the BE36 and the BE36 pilot is issued a 360 by ATC to rejoin final for Runway 34. A third aircraft on approach to Runway 29 is issued a go-around.
Date: 201708
Local time of day: 0601-1200
Location: ZZZ.Airport, US
Flight conditions: VMC
Light: Daylight
Aircraft: Dash 8-300
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Taxi
Aircraft component: DC Generator
Component problem: Failed
Reporter organization: Air Carrier
Reporter function: First Officer; Pilot Flying
Reporter qualification: Flight Crew Air Transport Pilot (ATP)
Anomaly: Aircraft Equipment Problem Less Severe
Detector: Automation Aircraft Other Automation; Person Flight Crew
When detected: Taxi
Result: Aircraft Aircraft Damaged; General Maintenance Action; General Flight Cancelled / Delayed
Contributing factors: Aircraft
Primary problem: Aircraft

Narrative: After number 2 engine start; crew noticed number 2 DC generator failed to come online; seconds later number 2 DC generator hot caution illuminated. We then were notified by ground personnel that smoke was coming from the number 2 nacelle. We immediately shut down the number 2 engine and First Officer then proceed to verified smoke was still coming out of the number 2 engine nacelle; we then immediately evacuated the passenger and fired both fire bottles and called fire and rescue services.




Synopsis: De Havilland DHC-8 First Officer reported that a DC generator failed after engine start causing smoke to come out of the nacelle.
Date: 201505
Local time of day: 0601-1200
Location: JAX.Airport, FL
Flight conditions: VMC
Light: Dawn
Aircraft: B737-700
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Cruise
Airspace: Class A ZMA
ATC / advisory: Center ZMA
Reporter organization: Air Carrier
Reporter function: Captain
Reporter qualification: Flight Crew Air Transport Pilot (ATP)
Anomaly: Flight Deck / Cabin / Aircraft Event Illness / Injury; Inflight Event / Encounter Other / Unknown
Detector: Person Flight Crew
When detected: In-flight
Result: General None Reported / Taken
Contributing factors: Airspace Structure; Aircraft
Primary problem: Ambiguous

Narrative: During cruise flight at FL390 and approximately 160 NM southeast of JAX; we needed to contact [Medical Services].  The 'Enroute Radio Frequencies' section of our Dispatch Release indicated Frequency 130.70 departing FLL; and 131.17 at LENDS intersection.  We had not yet reached LENDS intersection.  Trying frequency 130.70 had no response; even with the squelch off.  On 131.17 we could hear radio but the voice quality was weak with static.  [Medical Services] on 131.17 was un-useable.  There was a severe echo and distortion of their transmissions.  However; Company Dispatch and [Medical Services] said they could hear us loud and clear.  We finally reached [Medical Services] via JAX Operations on 131.70.  This process took about 12 minutes to establish useable communications.Communications capability needs to be improved using existing technology.  This type of delay could require Pilots to make divert decisions without the benefit of [Medical Services] advice if the medical emergency was time critical.




Synopsis: A B737 Captain experiences difficulties contacting Medical Services on the listed Commercial Radio frequencies over the Atlantic Ocean east of MLB. Eventually a usable frequency is found to discuss the condition of an ill passenger.
Date: 202101
Local time of day: 0601-1200
Location: ZZZ.Airport, US
Aircraft: Commercial Fixed Wing
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Other All Phases
Reporter organization: Air Carrier
Reporter function: Flight Attendant (On Duty)
Reporter qualification: Flight Attendant Current
Human factors: Other / Unknown; Situational Awareness; Physiological - Other; Confusion
Anomaly: Deviation / Discrepancy - Procedural Published Material / Policy
Detector: Person Flight Attendant
When detected: In-flight; Taxi
Result: General None Reported / Taken
Contributing factors: Environment - Non Weather Related
Primary problem: Environment - Non Weather Related

Narrative: This report is due to the COVID-19. I'm an X Flight Attendant. My jumpseat now is X4 due to the COVID-19. These are more than XX empty seats from the main cabin but our system allows customer upgrade themselves to X6; which is next to me without 6 feet between us. On the current flight; with turbulence; I have been seating next to a customer for more than 1 hour and 45 minutes. I think this unsafe for me to be there. I can feel the breathing from the customer as he is right next to me. Please fix the system until we all have vaccine.




Synopsis: Flight Attendant reported concerns regarding the assigned jump-seat and its location near passenger seats.
Date: 201202
Local time of day: 0601-1200
Location: ZZZ.Airport, US
Flight conditions: VMC
Light: Daylight
Aircraft: Beechjet 400
Operator: Fractional
Operating under: Part 91
Flight plan: IFR
Mission: Passenger
Flight phase: Climb
Airspace: Class E ZZZ
ATC / advisory: TRACON ZZZ
Aircraft component: Flight Dynamics Navigation and Safety
Component problem: Failed
Reporter organization: Fractional
Reporter function: Pilot Flying; Captain
Reporter qualification: Flight Crew Air Transport Pilot (ATP)
Human factors: Confusion; Distraction; Human-Machine Interface
Second reporter function: Pilot Flying; First Officer
Anomaly: Aircraft Equipment Problem Critical
Detector: Person Flight Crew
When detected: In-flight
Result: Flight Crew Returned To Departure Airport
Contributing factors: Aircraft; Human Factors
Primary problem: Aircraft

Narrative: Approximately 15 into the flight the First Officer's flight display went black followed shortly by the Captain's PFD and MFD display and ultimately by the FMS displays and annuncuatior panel. The First Officer informed ATC that the flight was in a descending turn and returning to the airport with flight display information inoperative. An Emergency was not declared by the crew. The crew investigated and evaluated the aircraft condition(s) enroute back to the airport and was unable to conclusively identify the anomaly. The crew then directed full attention to completing the flight and landing the aircraft.The aircraft displayed acceptable controllability in roll and yaw; with pronounced down force in pitch. It was determined that acceptable pitch control could be achieved by the crew to control the aircraft. The crew worked through the Check List for the emergency landing gear extension procedure and extended the landing gear. The flight descended to pattern altitude and flew a low approach down the runway in order for the Tower to view the landing gear. The Tower reported that the gear appeared normal. A left hand pattern was flown and a no-flap landing was performed per the Check List to the runway. Hydraulic braking was available and effective. Emergency braking was not used. The aircraft turned off the runway approximately 5;000 FT from touchdown. The First Officer performed a cabin evacuation and the Captain secured the flight deck. Post flight inspection revealed no sign of damage to the aircraft.


Second narrative: [No substantive additional information was included in the secondary narrative.]


Synopsis: A BE-400XP flight crew returned to their departure airport when they experienced multiple nav system and pitch control anomalies.
Date: 202112
Local time of day: 1201-1800
Flight conditions: IMC
Aircraft: EMB ERJ 145 ER/LR
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Descent
ATC / advisory: Tower ZZZ
Reporter organization: Air Carrier
Reporter function: Pilot Flying; First Officer
Reporter qualification: Flight Crew Instrument; Flight Crew Air Transport Pilot (ATP); Flight Crew Multiengine
Anomaly: Inflight Event / Encounter CFTT / CFIT
Detector: Automation Aircraft Terrain Warning; Person Flight Crew
When detected: In-flight
Result: General None Reported / Taken
Contributing factors: Environment - Non Weather Related; Airspace Structure
Primary problem: Environment - Non Weather Related

Narrative: ATC made us hold at 3;000 ft.; once ATC cleared us for the approach; I did start descent to 2;100 to catch the glide slope; and as soon we did start [the] descent we got the GPWS.




Synopsis: EMB-145 First Officer reported receiving a GPWS during approach descent.
Date: 202008
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: Captain
Reporter qualification: Flight Crew Instrument; Flight Crew Air Transport Pilot (ATP); Flight Crew Multiengine
Human factors: Situational Awareness; Communication Breakdown
Anomaly: Deviation / Discrepancy - Procedural Hazardous Material Violation; Deviation / Discrepancy - Procedural Published Material / Policy
Detector: Person Flight Crew
When detected: Pre-flight
Result: General None Reported / Taken
Contributing factors: Environment - Non Weather Related; Human Factors; Company Policy
Primary problem: Company Policy

Narrative: The disinfectant cabin wipes provided for crews are being used with no knowledge by flight attendants of the hazard they pose.  I have mentioned this to flight ops management and some onboard inflight supervisors who all expressed surprise and a willingness to get the word out.  Apparently that effort is short of the target if they've tried.  Virtually 90% of the flight attendants I brief when I see this product on board are completely surprised of the apparent hazard of the product.  Many use it like a Clorox wipe often without gloves.  The bottle warns against contact with the skin and says to contact a poison control center after rinsing for 20 minutes.  Would you either get the word out to crews about how to use this or remove it from the plane?




Synopsis: Air carrier Captain reported concerns regarding the products used to disinfect the cabin.
Date: 201907
Local time of day: 0601-1200
Location: ZZZ.Airport, US
Flight conditions: VMC
Aircraft: B737 Undifferentiated or Other Model
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Parked
Aircraft component: Hydraulic Fluid
Reporter organization: Air Carrier
Reporter function: Pilot Not Flying; Captain
Reporter qualification: Flight Crew Instrument; Flight Crew Air Transport Pilot (ATP); Flight Crew Multiengine
Second reporter function: First Officer
Anomaly: Aircraft Equipment Problem Less Severe; Deviation / Discrepancy - Procedural Published Material / Policy
Detector: Person Flight Crew
When detected: Pre-flight
Result: Aircraft Equipment Problem Dissipated; General Physical Injury / Incapacitation
Contributing factors: Procedure; Aircraft
Primary problem: Aircraft

Narrative: During preflight action external inspection; First Officer was exposed to hydraulic fluid which was leaking in wheel well area. Fluid leak became mist when the air from packs came in contact with the leak. Prior to leaving the flight deck; the hydraulic systems were pressurized due to control movement from outside sources. After exposure to First Officer's eyes; [Chief Pilot] was contacted which lead to medical attention per [Chief Pilot] checklist procedures.


Second narrative: During the preflight exterior inspection; I was sprayed in the eyes with a mist of hydraulic fluid.  Prior to exterior inspection; hydraulic system was pressurized to stop control column movements. APU was running and providing conditioned air. As I approached the wheel well area; I thought I noticed an unusual smell. When I stood up into wheel well; I was sprayed in the face with a fine mist. My eyes began to burn. I warned one of the nearby crew chiefs to stay clear of the wheel well. He directed me to the nearest eye wash station. On the way to the eye wash; I went to cockpit; notified Captain we had a leak. Depressurized the two electric hydraulic pumps. Told him I was going to the eye wash. Maintenance's subsequent inspection found a loose hydraulic fitting near where the conditioned air is exhausted. The exhausted air was turning the leaking hydraulic fluid into a fine spray.


Synopsis: B737 flight crew reported that during preflight inspection; leaking hydraulic fluid came in contact with Air Conditioning Pack exhaust air; becoming mist which contaminated the eyes of the First Officer; requiring medical attention.
Date: 202108
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: Flight Attendant (On Duty)
Reporter qualification: Flight Attendant Current
Anomaly: Deviation / Discrepancy - Procedural Security; Deviation / Discrepancy - Procedural Published Material / Policy; Deviation / Discrepancy - Procedural Hazardous Material Violation; Flight Deck / Cabin / Aircraft Event Passenger Electronic Device
Detector: Person Flight Attendant
When detected: Routine Inspection; Aircraft In Service At Gate; Pre-flight
Result: Aircraft Equipment Problem Dissipated; Flight Crew Overcame Equipment Problem
Contributing factors: Human Factors
Primary problem: Human Factors

Narrative: There was an unclaimed vape in the aft galley on the counter that we believed may have belonged to either one of the cleaners; one of the caterers; or one of the people who did the security checks on the plane. Originally; [other flight attendant] thought it was mine and I thought it was his but when we found out it was neither one of ours; we disposed of it in the trash bin.  After realizing very soon (within a few minutes after putting in in the trash bin) that it was a bad idea to put it in there; we took it out.  We noticed that the light on the vape was flashing so we tried looking through the Operations Manual to figure out what we should do with the device.  After not finding any information on it; we contacted the purser who contacted the Captain who then advised us to put the device into the thermal containment bag. I was concerned with the vape flashing because I have seen it before where it would flash and start producing smoke. We were not comfortable with leaving it out and exposed.




Synopsis: Air carrier Flight Attendant reported an unclaimed vape device was left in the aft galley. After consulting with the Captain the device was placed in a Thermal Containment bag.
Date: 202112
Local time of day: 0001-0600
Location: ZZZ.Airport, US
Flight conditions: VMC
Light: Night
Aircraft: B737 Next Generation Undifferentiated
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Taxi
ATC / advisory: Ground ZZZ
Aircraft component: Wheels/Tires/Brakes
Component problem: Malfunctioning
Reporter organization: Air Carrier
Reporter function: Pilot Flying; Captain
Reporter qualification: Flight Crew Instrument; Flight Crew Air Transport Pilot (ATP); Flight Crew Multiengine
Human factors: Troubleshooting; Confusion
Anomaly: Aircraft Equipment Problem Critical; Deviation / Discrepancy - Procedural FAR; Deviation / Discrepancy - Procedural Published Material / Policy; Inflight Event / Encounter Loss Of Aircraft Control
Detector: Person Flight Crew
When detected: Taxi
Result: Air Traffic Control Provided Assistance; Flight Crew Requested ATC Assistance / Clarification; General Maintenance Action
Contributing factors: Aircraft
Primary problem: Aircraft

Narrative: We pushed back normally from the gate. A single engine taxi was attempted and the aircraft would not move. The other engine was started and an abnormally high power setting was necessary to taxi. Initially we considered the high density altitude of ZZZ requiring more thrust; but the aircraft also slowed to a stop very quickly when power was reduced. A gate return was performed; and a quick inspection was done by Maintenance; who found nothing visually abnormal. The passengers were deplaned. Maintenance then jacked up the main landing gear and found an internal wheel bearing on the outboard landing gear that had frozen to the axle; causing the drag on the outboard tire. It was the first flight of the day for this aircraft.




Synopsis: B737 Captain reported a gate return after finding it took abnormally high thrust to move the airplane. Maintenance replaced a main tire and wheel assembly due to a frozen wheel bearing.
Date: 201502
Weather elements / visibility: Rain
Aircraft: Commercial Fixed Wing
Operator: Air Carrier
Mission: Passenger
Flight phase: Taxi
Reporter organization: Air Carrier
Reporter function: Ramp
Human factors: Distraction; Training / Qualification; Communication Breakdown
Anomaly: ATC Issue All Types; Conflict Ground Conflict; Less Severe; Deviation / Discrepancy - Procedural Clearance; Deviation / Discrepancy - Procedural Published Material / Policy
Detector: Person Flight Crew
When detected: Taxi
Result: General Flight Cancelled / Delayed
Contributing factors: Procedure; Human Factors; Airport
Primary problem: Human Factors

Narrative: During Pushback a van cut off the pushback procedure causing operator to slam on the brakes. When he slammed on the brakes the tow bar broke. This was a near miss event.




Synopsis: A pushback driver was forced to slam on the brakes to avoid a van which was cutting off the pushback procedure. The tow bar broke.
Date: 202109
Local time of day: 0601-1200
Location: ZZZ.Airport, US
Aircraft: PA-34-200 Seneca I
Operator: FBO
Operating under: Part 91
Flight plan: VFR
Mission: Training
Flight phase: Takeoff / Launch
Airspace: Class D ZZZ
ATC / advisory: Tower ZZZ
Aircraft component: Landing Gear
Component problem: Improperly Operated
Reporter organization: FBO
Reporter function: Instructor; Pilot Flying
Reporter qualification: Flight Crew Instrument; Flight Crew Multiengine; Flight Crew Flight Instructor; Flight Crew Commercial
Human factors: Situational Awareness
Anomaly: Aircraft Equipment Problem Critical; Deviation / Discrepancy - Procedural Published Material / Policy; Ground Event / Encounter Other / Unknown
Result: Aircraft Aircraft Damaged
Contributing factors: Human Factors; Aircraft
Primary problem: Human Factors

Narrative: Coming in to land on Runway XX at ZZZ and landed hard and nose gear collapsed on runway. No injuries. Softer landing next time and take more precautions.




Synopsis: PA-34 Flight Instructor reported the nose gear collapsed during a hard landing.
Date: 201301
Local time of day: 1201-1800
Location: ZPH.Airport, FL
Flight conditions: VMC
Weather elements / visibility: 10
Light: Daylight
Aircraft: PA-25 Pawnee
Operator: Personal
Operating under: Part 91
Mission: Personal
Flight phase: Initial Approach
Airspace: Class E ZPH
ATC / advisory: CTAF ZPH
Second aircraft: Cheetah; Tiger; Traveler AA5 Series
Reporter organization: Personal
Reporter function: Pilot Flying; Single Pilot
Reporter qualification: Flight Crew Air Transport Pilot (ATP); Flight Crew Flight Instructor; Flight Crew Multiengine; Flight Crew Instrument
Human factors: Communication Breakdown
Anomaly: Conflict NMAC
Detector: Person Flight Crew
When detected: In-flight
Result: Flight Crew Took Evasive Action
Contributing factors: Airport; Human Factors
Primary problem: Human Factors

Narrative: After releasing a glider at 3;000 AGL and descending to traffic pattern altitude (1;000 AGL) rolled out to enter a right base leg for Runway 18 at ZPH. A Grumman AA5 was coming at me slightly to the left of my nose in level flight at about 1;000 FT AGL. I pulled up and missed the aircraft by an estimated 50-100 FT. The AA5 took no evasive action and did not respond to a radio call. The AA5 continued on a long; wide downwind for left traffic on Runway 22. The AA5 finally made a radio call turning base. No response about the near miss.ZPH is a very busy airport; with sky diving and glider operations on weekends. Per agreement with the airport; skydiving and glider operations are conducted on Runway 18/36; with normal operations on Runway 4/22; wind permitting. All traffic is to the west of the airport; right hand pattern for 18 and 22; left hand pattern for 36 and 04.The glider and skydiving operations report downwind and/or base prior to entry and base to final. These operations have worked will for many years; when everybody monitors the CTAF frequency. It appears that the AA5 did not make a pattern entry call or was on the wrong frequency. The AA5 is a regular user of ZPH and may be based there.




Synopsis: PA25 pilot experiences a NMAC in the traffic pattern for Runway 18 at ZPH with an AA5 entering for left traffic for Runway 22. The AA5 pilot is not on the CTAF and takes no evasive action.