elihoole/asrs-aviation-reports huggingface dataset:
Date: 201310
Local time of day: 1201-1800
Location: ZZZ.ARTCC, US
Flight conditions: VMC
Light: Daylight
Aircraft: IAI1125 (Astra)
Operator: Air Taxi
Operating under: Part 135
Flight plan: IFR
Mission: Passenger
Flight phase: Cruise
Airspace: Class A ZZZ
ATC / advisory: Center ZZZ
Aircraft component: Hydraulic Main System
Component problem: Malfunctioning
Reporter organization: Air Taxi
Reporter function: Captain; Check Pilot; Pilot Not 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: In-flight
Result: Air Traffic Control Issued New Clearance; Flight Crew Diverted; General Declared Emergency; General Maintenance Action
Contributing factors: Aircraft
Primary problem: Aircraft

Narrative: As flight neared destination; indications via the annunciator panel indicated a growing problem with the main hydraulic system including hydraulic levels (interment light display); illumination of left main 'Hyp Pump' light; intermittent activation of the auxiliary hydraulic pump to compensate for fluctuating main hydraulic pressure and intermittent illumination of right 'Hyd Pump' light. Aircraft QRH was consulted by Captain sitting in right seat as Pilot Not Flying and appropriate section referenced indicating only crew action necessary was to 'monitor' pressure. There was no requirement per the QRH for landing as soon as practical or possible; so flight continued toward the destination. At one point; perhaps 30-35 minutes out; the 'Hyd Level' light illuminated on the annunciator panel indicating to the crew a worsening problem with the main hydraulic system. Prior to this; the crew decided to divert to the nearby international airport since the runways were longer and more services were available rather than continue to the flight's destination. Once the 'Hyd Level' light illuminated and believing the aircraft was experiencing what would become a total loss of main hydraulic pressure/system and given this was a Part 135 passenger-carrying flight; the Captain; in consult with the First Officer; declared an emergency and so notified Center in order to receive priority handling. Center acknowledged and cleared the aircraft direct. The hydraulic system did not worsen from that point; there was no total loss of any aircraft hydraulic system; the aircraft's auxiliary hydraulic system performed as designed and intended and the landing; roll-out; braking and taxi-in were normal. There was no aircraft damage; crew or passenger injuries. Aircraft was followed by emergency vehicles to parking at the FBO and shut down. Passengers disembarked to their final destinations and the aircraft was turned over to Maintenance.




Synopsis: IAI1125 Captain experiences a main hydraulic system leak in cruise and elects to divert to an airport with longer runways. The main system continued to function normally throughout the approach and landing with a low quantity indication.
Date: 201210
Local time of day: 0001-0600
Location: ZZZ.Airport, US
Light: Night
Aircraft: B767-300 and 300 ER
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Final Approach
Airspace: Class B ZZZ
ATC / advisory: Tower ZZZ
Aircraft component: Landing Gear Indicating System
Component problem: Malfunctioning
Reporter organization: Air Carrier
Reporter function: Captain; Pilot Flying
Reporter qualification: Flight Crew Air Transport Pilot (ATP)
Human factors: Training / Qualification; Troubleshooting
Anomaly: Aircraft Equipment Problem Less Severe; Deviation / Discrepancy - Procedural Published Material / Policy
Detector: Person Flight Crew
When detected: In-flight
Result: Flight Crew Executed Go Around / Missed Approach; Flight Crew Landed in Emergency Condition; Flight Crew Overcame Equipment Problem; General Declared Emergency
Contributing factors: Aircraft
Primary problem: Aircraft

Narrative: Upon gear extension on approach after [overnight flight]; we had no right main gear indication from either bulb in the right main gear light. With [the] other 2 gear indicating down; set flaps to 25 to see if we would get a gear warning horn which we did not. However; I executed a precautionary go around. [I] notified ATC; the passengers; and flight attendants; declared an emergency. Requested ATC notify company and instructed the flight attendants to do their 30 second review and also briefed the passenger that as a precaution we will have them assume the brace position for landing. Accomplished this on a right hand closed pattern for Runway 9 with about a 10 mile final touch down was normal and uneventful and had Airfield Rescue and Fire Fighter team visually inspect gear after clearing runway and subsequently taxied to the gate. Initiated go around with 14;000 LBS of fuel and landed with 9;000 LBS. This flight plan was adequately planned for fuel but many flight plans I see from our company would have made this a fuel emergency too. This is exactly why I will add fuel if planned for arrival fuel of less than 12;000 on a B767 or 10;000 on a B757 regardless of the weather.




Synopsis: A B767-300 Right Landing Gear indicator did not illuminate with the gear down. Assuming a light malfunction; the Captain executed a go around; declared an emergency; set the flaps to 25; and with no warning sounds landed uneventfully.
Date: 201201
Local time of day: 0601-1200
Location: ZZZ.Airport, US
Flight conditions: IMC
Weather elements / visibility: Rain; 1
Light: Daylight
Aircraft: Golden Eagle 421
Operator: Personal
Operating under: Part 91
Flight plan: IFR
Mission: Personal
Flight phase: Initial Climb
Airspace: Class D ZZZ
ATC / advisory: Tower ZZZ
Aircraft component: Cargo Door
Component problem: Malfunctioning
Reporter organization: Personal
Reporter function: Single Pilot; Pilot Flying
Reporter qualification: Flight Crew Air Transport Pilot (ATP)
Human factors: Distraction; Situational Awareness; Other / Unknown
Anomaly: Aircraft Equipment Problem Less Severe; Ground Event / Encounter Ground Strike - Aircraft
Detector: Person Flight Crew
When detected: In-flight
Result: Aircraft Aircraft Damaged; Flight Crew Executed Go Around / Missed Approach; General Maintenance Action
Contributing factors: Aircraft; Human Factors
Primary problem: Aircraft

Narrative: IFR conditions on takeoff; 500 FT overcast; 1 mile visibility. After rotation and gear retraction the forward right cargo door popped open. The aircraft yawed right and began to slow. I elected to land straight ahead. I reduced power; lowered the nose selected gear down and flared. In the flare I heard two points of contact. Immediately pulled the nose up and applied power. I flew it around at low altitude to maintain VFR. I also left the gear in the down position. The landing was uneventful. After taxi in and shutdown I discovered that both props had the tips curled. There was evidence of light scrapping on both inboard gear doors. Thoughts: I prepare for normal abnormals by attending a recurrent simulator training specific to my airplane. On takeoff I am expecting an engine failure and have practice it many times. I would have continued with an engine failure; but elected to land with the cargo door! Prior to this event a friend told me a story about the same situation happening to him many years ago in a 421. Same door pops open on a clear day and he flew it around for landing. He claimed the aircraft was very difficult to control. I believe this story had an influence on my choice that day! The choice was take a potentially difficult to control airplane into the clouds or land straight ahead.




Synopsis: A C421 cargo door opened on takeoff so the pilot attempted a straight ahead landing. Upon hearing a scraping sound; the pilot went around. After landing found propeller and fuselage damage from runway contact.
Date: 201306
Local time of day: 1801-2400
Location: ATL.Airport, US
Flight conditions: VMC
Light: Night
Aircraft: Commercial Fixed Wing
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Cargo / Freight / Delivery
Flight phase: Taxi
ATC / advisory: Ground ATL
Reporter organization: Air Carrier
Reporter function: Captain; Pilot Flying
Reporter qualification: Flight Crew Air Transport Pilot (ATP)
Human factors: Confusion; Distraction; Situational Awareness
Anomaly: Conflict Ground Conflict; Critical; Deviation / Discrepancy - Procedural Published Material / Policy
Detector: Person Flight Crew
When detected: Taxi
Result: Flight Crew Requested ATC Assistance / Clarification; Flight Crew Took Evasive Action
Contributing factors: Human Factors
Primary problem: Human Factors

Narrative: Taxied from ATL Cargo ramp via taxiway A7 at the ATL airport. Held at point A7 and Taxiway A heading south. While waiting for taxi clearance from ATL Ground Control; there were three vehicles holding at traffic lane. One on the east of aircraft and two on west side of aircraft. Ground control cleared us to taxi to Runway 26L via taxiway A; to cross 26R then to 26L. I started to taxi while clearing to the left for a turn on Taxiway A. Cockpit jumpseater urgently and loudly said 'STOP.' Observed the second truck on the west side of the aircraft had driven around the first vehicle; entered Taxiway A then turned toward aircraft and went under our aircraft. At first; thought the vehicle would strike the nose gear but the vehicle appeared on the left side of aircraft. We immediately told Ground Control that a truck had blatantly moved and drove under our aircraft while we were taxiing. We watched the truck driver rapidly drive to facility to the far east of the cargo ramp. Driver exited the utility truck and entered a pickup truck and proceeded to drive on the perimeter road; east of the western runways. This was a reckless and blatant disregard for safety; airport rules; security and procedures. Atlanta airport police have been notified; airport safety director was notified; and ATL Ramp Manager were notified.




Synopsis: An aircraft on ATL Taxiway A7 stopped rapidly as a van drove under its nose. ATL Ground Control; Airport Police were notified.
Date: 202101
Local time of day: 1801-2400
Location: ATL.Airport, GA
Aircraft: Commercial Fixed Wing
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Final Approach
Airspace: Class B ATL
ATC / advisory: Tower ATL
Second aircraft: Any Unknown or Unlisted Aircraft Manufacturer
Reporter organization: Air Carrier
Reporter function: First Officer
Reporter qualification: Flight Crew Multiengine; Flight Crew Air Transport Pilot (ATP); Flight Crew Instrument
Human factors: Confusion; Situational Awareness
Anomaly: ATC Issue All Types; Conflict Airborne Conflict; Deviation - Speed All Types
Detector: Person Air Traffic Control
When detected: In-flight
Result: Air Traffic Control Issued New Clearance; Flight Crew Returned To Clearance
Contributing factors: Human Factors; Procedure; Environment - Non Weather Related
Primary problem: Human Factors

Narrative: On the CHPPR 1 RNAV arrival assigned 180 knots after NAVVY. Shortly thereafter was cleared for the approach ILS 9R. Captured glide slope and continued the approach at 180 knots. Told to contact Tower and we were cleared to land. At 1 mile prior to final approach fix began to configure; slow down to 160 knots; and then VREF (Approach speed). Fully configured and approach checklist complete; stable approach. I recall a Controller asking the traffic behind us to slow down. At 1;200 feet AGL Controller told us to cancel landing clearance; fly runway heading; and then 15 right turn shortly thereafter.Go-around procedure completed and we asked reason for go-around. Controller said we slowed down 6 miles prior to runway. Note: Final approach fix is 5 miles from the runway and we do not recall a 180 knot assigned speed to the final approach fix. We were vectored back to the ILS 9R and landed; all else normal.Tower to request go-around; task saturation.




Synopsis: Air carrier First Officer reported making a go-around per ATC's instructions due to spacing of aircraft on final into ATL.
Date: 201402
Local time of day: 0001-0600
Location: SLC.Airport, UT
Flight conditions: VMC
Light: Daylight
Aircraft: B737 Next Generation Undifferentiated
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Takeoff / Launch
ATC / advisory: Tower SLC
Second aircraft: Commercial Fixed Wing
Reporter organization: Air Carrier
Reporter function: Captain; Pilot Not Flying
Reporter qualification: Flight Crew Air Transport Pilot (ATP)
Human factors: Distraction; Situational Awareness
Anomaly: ATC Issue All Types; Conflict Ground Conflict; Less Severe; Deviation / Discrepancy - Procedural FAR; Deviation / Discrepancy - Procedural Published Material / Policy
Detector: Person Flight Crew
When detected: In-flight
Result: General None Reported / Taken
Contributing factors: Procedure
Primary problem: Procedure

Narrative: Cleared into position and wait [Runway] 16R and state whether aircraft ahead departing in sight. We replied the aircraft in sight. [We] cleared for takeoff as aircraft ahead lifting off. As soon as we were cleared for takeoff aircraft behind us instructed to line up and wait and call us in sight. We began our takeoff roll; approaching 70 KTS SLC Tower cleared the aircraft in position for takeoff. Our Vr speed was 150 KTS and we were nearly full. Had we aborted it may have resulted in a catastrophic accident had the aircraft behind us not stopped as we were both occupying the same runway for an extended period of time as we accelerated toward Vr.  ATC [was] rushing to depart aircraft. There were no aircraft landing on our runway; only departures. An unsafe practice by SLC Tower.




Synopsis: SLC Tower cleared a B737 for takeoff while the aircraft ahead was still on the runway. Then as the B737 accelerated beyond 70 KTS; the following aircraft was cleared for takeoff. An abort would have caused a serious problem.
Date: 201512
Local time of day: 1201-1800
Location: RSW.Airport, FL
Flight conditions: IMC
Aircraft: Medium Transport
Mission: Passenger
Flight phase: Climb
Airspace: Class C RSW
Aircraft component: FMS/FMC
Component problem: Malfunctioning
Reporter organization: Air Carrier
Reporter function: Captain; Pilot Flying
Reporter qualification: Flight Crew Air Transport Pilot (ATP)
Human factors: Situational Awareness
Anomaly: Deviation - Track / Heading All Types; Deviation / Discrepancy - Procedural Clearance
Detector: Person Flight Crew
When detected: In-flight
Result: Air Traffic Control Issued New Clearance; Flight Crew Became Reoriented
Contributing factors: Aircraft; Human Factors
Primary problem: Ambiguous

Narrative: Cleared by ATC from RSW via CSHEL5 ORL as filed. Briefed the departure at the gate before push back and verified the departure setup.Upon reaching runway 6; we completed the before takeoff checklist. Cleared for takeoff by tower - runway heading runway 6. Departing runway 6 from RSW; CSHEL fix is dropped from the legs page. Departure control cleared us direct CSHEL; however the fix dropped out of the legs page in the FMS. We advised ATC and they assigned a heading of 360deg to give us time to re-input the CSHEL fix. We confirmed the routing on the 20-3A RNAV SID and flew direct to CSHEL. Flight continued without incident.Future crews must be aware of this when departing runway 6 at RSW that CSHEL will drop out of the legs page. We flew this same departure yesterday departing runway 24 without incident. All of the fixes remain in when departing runway 24.




Synopsis: Captain reported that after departing Runway 6 in RSW the FMC dropped the CSHEL fix.
Date: 201208
Local time of day: 0601-1200
Location: ZZZ.Airport, US
Flight conditions: VMC
Aircraft: B757-200
Operator: Air Carrier
Operating under: Part 121
Mission: Passenger
Flight phase: Parked
Aircraft component: Exterior Pax/Crew Door
Component problem: Improperly Operated
Reporter organization: Air Carrier
Reporter function: Captain; Pilot Flying
Reporter qualification: Flight Crew Air Transport Pilot (ATP)
Human factors: Confusion
Second reporter function: Pilot Not Flying; First Officer
Anomaly: Deviation / Discrepancy - Procedural Published Material / Policy; Flight Deck / Cabin / Aircraft Event Other / Unknown
Detector: Person Flight Crew
When detected: Pre-flight
Result: General Maintenance Action; General Flight Cancelled / Delayed
Contributing factors: Aircraft; Human Factors
Primary problem: Ambiguous

Narrative: Ready for pushback; Flight Attendant from door 2L came to cockpit to indicate that door 2L was not arming properly; that the wedge was not coming out. [I] went to door 2L to investigate. Looking at door; moved lever to disarm and looked again. Opened door handle and it was apparent that door was not disarmed; door with assist opened partially. Slide was attached at bottom and partly out of pack. I tried to close door but slide then deployed. No one was hurt; no one else was involved in manipulating the door. Maintenance was called and it was determined that the slide would be replaced and flight to operate with a delay.


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


Synopsis: B757-200 Captain accidentally deployed the 2L slide while trouble shooting a problem with the door.
Date: 201311
Local time of day: 1201-1800
Location: ZZZ.ARTCC, US
Flight conditions: VMC
Weather elements / visibility: 10
Light: Daylight
Aircraft: Skyhawk 172/Cutlass 172
Operator: Personal
Operating under: Part 91
Flight plan: IFR
Mission: Personal
Flight phase: Cruise
Airspace: Class B ZZZ
ATC / advisory: Center ZZZ
Aircraft component: Engine
Component problem: Malfunctioning
Reporter organization: Personal
Reporter function: Pilot Flying; Single Pilot
Reporter qualification: Flight Crew Instrument; Flight Crew Private
Human factors: Human-Machine Interface; Situational Awareness
Anomaly: Aircraft Equipment Problem Critical; Inflight Event / Encounter Other / Unknown
Detector: Person Flight Crew
When detected: In-flight
Result: Air Traffic Control Provided Assistance; Flight Crew Landed in Emergency Condition; Flight Crew Requested ATC Assistance / Clarification; General Declared Emergency
Contributing factors: Aircraft
Primary problem: Aircraft

Narrative: While at cruise I heard a loud noise and then felt a massive shuddering of the aircraft. Both hands were used for control of the yoke. I declared an emergency with ATC; [and] then pulled the power back to idle. The oil access door came open and shortly afterwards the dip stick came flying out. ATC vectored us for a landing at an airport which was 3NM away from our present position. Upon reaching the airport environment; we flew a left hand circle around the approach end of runway while descending. Upon turning final; with landing assured; I pulled the mixture to full lean; and turned off the magnetos and fuel tanks. We landed on runway and rolled onto a taxiway. At that time we noticed that several inches of prop were missing from one end. There was no evidence of blood or feathers.




Synopsis: When; while at cruise; the unexplained loss of several inches of one prop blade resulted in uncontrollable vibration of the C172-R the pilot was vectored to a nearby airport where he landed safely. There was no visible evidence of a bird strike.
Date: 201910
Local time of day: 1801-2400
Location: ZZZ.ARTCC, US
Flight conditions: VMC
Light: Night
Aircraft: A319
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Descent
Airspace: Class A ZZZ
ATC / advisory: Center ZZZ
Aircraft component: Hydraulic System
Component problem: Malfunctioning
Reporter organization: Air Carrier
Reporter function: Pilot Flying
Reporter qualification: Flight Crew Air Transport Pilot (ATP); Flight Crew Instrument; Flight Crew Multiengine
Human factors: Situational Awareness
Anomaly: Aircraft Equipment Problem Critical; Flight Deck / Cabin / Aircraft Event Smoke / Fire / Fumes / Odor
Detector: Automation Aircraft Other Automation; Person Flight Crew
When detected: In-flight
Result: Flight Crew Landed in Emergency Condition
Contributing factors: Aircraft
Primary problem: Aircraft

Narrative: During cruise at FL320 ECAM showed HYD Y sys lo and quantity indicated zero. Accomplished ECAM actions IAW (In Accordance With) checklists and advised Dispatch and Maintenance Control. Elected to continue to ZZZ. During descent on autopilot; aircraft abruptly pitched down; autopilot disconnected; and ECAM momentarily showed HYD B + Y sys lo pr. [We] recovered [the] aircraft from pitch down and [requested priority handling with ATC]. The ECAM HYD B 'self healed' and disappeared from [the] ECAM display. We used the 7700 ACARS feature to notify Dispatch. Apparently; it did not work according to our Dispatcher. Accomplished non-routine landing considerations checklist; coordinating with cabin crew and ATC. Did not re-engage autopilot for the remainder of the flight and hand flew the approach. There is a discrepancy between ECAM and the manual on turning on Y sys engine pump during approach. We chose the ECAM guidance and turned on the pump after configuring. We expected only one reverse on rollout; but had indications of normal reverse on both engines. Taxied to gate with CFR (Crash Fire Rescue) following. Terminated [priority handling] with ground after shutdown. On post flight; FO (First Officer) found fluid covering the bottom of the airplane; in the left wheel well; and on the left main landing gear. During the van ride to our layover hotel; the FAs (Flight Attendant) told us a burning mechanical smell in mid cabin occurred soon after the pitch down.




Synopsis: A319 Pilot Flying reported loss of hydraulic fluid and subsequent pitching down of aircraft.