elihoole/asrs-aviation-reports huggingface dataset:
Date: 201911
Local time of day: 1201-1800
Location: ZZZ.Airport, US
Flight conditions: VMC
Light: Daylight
Aircraft: B767 Undifferentiated or Other Model
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Takeoff / Launch
ATC / advisory: Tower ZZZ
Aircraft component: Fan Reverser
Component problem: Malfunctioning
Reporter organization: Air Carrier
Reporter function: Captain; Pilot Flying
Reporter qualification: Flight Crew Air Transport Pilot (ATP); Flight Crew Instrument; Flight Crew Multiengine
Anomaly: Aircraft Equipment Problem Less Severe
Detector: Person Flight Crew
When detected: In-flight
Result: Flight Crew Rejected Takeoff; Flight Crew Returned To Gate; General Flight Cancelled / Delayed; General Maintenance Action
Contributing factors: Aircraft
Primary problem: Aircraft

Narrative: At 120 kts FO (First Officer) said 'Left Reverser.' I did not feel any yaw and looked at engines. FO said 'Left Reverser' again. I announced 'Rejecting' and began procedure. Vr was 151 kts. Reject initiated at 130 kts. I felt it was safer to reject at that point even though there was no yaw then rotate with the possibility of the reverser opening as I lifted the nose. RTO (Rejected Takeoff) engaged. I took over manually and exited at high speed and brought the plane to a stop. We asked for emergency equipment as our brake temperatures were rising. We ran the rejected takeoff checklist. We were towed to a gate after the brakes had cooled enough to be approached. No injuries reported among crew or passengers.




Synopsis: B767 Captain reported a rejected takeoff after a reverser light illuminated on takeoff roll.
Date: 201505
Local time of day: 1201-1800
Location: DCA.Airport, VA
Flight conditions: VMC
Light: Daylight
Aircraft: Regional Jet 200 ER/LR (CRJ200)
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Takeoff / Launch
ATC / advisory: Tower DCA
Reporter organization: Air Carrier
Reporter function: Pilot Flying; Captain
Reporter qualification: Flight Crew Air Transport Pilot (ATP)
Anomaly: ATC Issue All Types; Conflict Ground Conflict; Less Severe; Ground Incursion Runway
Detector: Person Flight Crew
When detected: In-flight
Result: Air Traffic Control Issued New Clearance; Flight Crew Rejected Takeoff
Contributing factors: Human Factors
Primary problem: Human Factors

Narrative: We were cleared for takeoff from Runway 1. There was an aircraft holding short of Runway 1 downfield at Taxiway F. That aircraft had been stationary and holding short as we were taking the runway. After applying takeoff thrust and beginning our takeoff roll the other aircraft starting moving towards the runway. It appeared to me that they were attempted to cross Runway 1 and I initiated an abort and a split second later the Tower also told us to abort the takeoff. The abort occurred at less than 80 kts. As we were decelerating the other aircraft on Taxiway F appeared to stop and never entered the runway area. We cleared Runway 1 on to Runway 4/22 and taxied back to the hold block. I contacted Dispatch to inform them of the abort and revalidate the release. During that time the Tower asked us to call them at our convenience. I spoke with the Tower Manager on duty and she informed me that the aircraft that attempted to cross the runway mistakenly read back a clearance for a different flight to cross Runway 4. She informed us that we did nothing wrong and that they would be performing an investigation on their side. After revalidating we departed and the flight continued without incident. This was simply a read back error for another crew that could have resulted in a runway incursion. The only suggestion I would bring is to be certain the flight is operating under sterile cockpit procedures on the ground and if in doubt of a clearance to clarify before taking action on it. I'd also like to give accolades to both the Tower and Ground controllers for catching the other crew's error quickly and correcting the situation in such a timely fashion.




Synopsis: After commencing takeoff roll; CRJ-200 crew noticed an aircraft about to enter the runway and rejected the takeoff.
Date: 201308
Location: ZZZ.Airport, US
Aircraft: Commercial Fixed Wing
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Parked
Aircraft component: Hydraulic System Lines; Connectors; Fittings
Component problem: Failed
Reporter organization: Air Carrier
Reporter function: Ramp
Human factors: Training / Qualification; Situational Awareness
Anomaly: Aircraft Equipment Problem Less Severe; Deviation / Discrepancy - Procedural Other / Unknown; Flight Deck / Cabin / Aircraft Event Smoke / Fire / Fumes / Odor
Detector: Person Ground Personnel
When detected: Aircraft In Service At Gate
Result: General Maintenance Action
Contributing factors: Human Factors; Aircraft; Company Policy
Primary problem: Aircraft

Narrative: While parking aircraft a major hydraulic leak came pouring out of wing and ran down to aircraft brakes. I chocked and went to get fire bottle. Since [the company] did not hire me to fight fire and with the severe potential of an explosion we needed to contact not only [operations] but the fire department. The Supervisor felt it not necessary to provide a lead so I had no way of contacting anyone. I did not feel it safe to not man the fire bottle. With not only an aircraft full of passengers but employees at the same risk of serious injury some thing had to be done. Finally I went inside and called the Local Controller. The smoke coming from the main gear was terrible and we did not have the resources to protect our passengers properly. The Supervisor should have staffed the proper people so the threat would have been minimal.




Synopsis: Ramp person reports a large hydraulic leak as he marshals the aircraft into parking. The fluid runs down the landing gear strut and onto the hot brakes causing a great deal of smoke. The fire bottle is manned but no flames erupt.
Date: 202104
Local time of day: 1801-2400
Location: ZZZ.Airport, US
Aircraft: A321
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 Air Transport Pilot (ATP); Flight Crew Multiengine; Flight Crew Instrument
Human factors: Human-Machine Interface; Other / Unknown; Time Pressure
Anomaly: Deviation / Discrepancy - Procedural Published Material / Policy; Deviation / Discrepancy - Procedural Hazardous Material Violation
Detector: Person Flight Attendant; Person Flight Crew
When detected: Pre-flight; Routine Inspection; Aircraft In Service At Gate
Result: Aircraft Equipment Problem Dissipated; Flight Crew Overcame Equipment Problem; General Maintenance Action; General Flight Cancelled / Delayed
Contributing factors: Company Policy; Chart Or Publication; Human Factors; Manuals
Primary problem: Chart Or Publication

Narrative: During passenger boarding there was confusion regarding the carriage of batteries in overhead compartment in passenger cabin. Initially batteries were thought not to be allowed. CSM (Customer Service Manager) was very concerned that the passenger required them for a mobility device. He stated that we carry them all the time in cabin and he was certain that they are permitted. After discussing situation with gate agent; supervisor; Dispatch; and CSM a reference was found in manual leading me to believe that batteries were allowed in cabin. Flight eventually departed late and was otherwise uneventful. Having time the following morning I looked deeper into FOM. The table in FOM which led me to agree with all involved that batteries were permissible has a hyperlink. The link leads to more information stating that the batteries were not allowed. Both gate agent supervisor and CSM stated that [Company] allows these batteries in the passenger cabin and that we carry them all the time. The passenger carried these on a prior flight the same day from ZZZ1.  [Captain suggests] FOM could be written more clearly without having to jump around reference to reference to obtain the proper information. Agents should be made aware these items are not allowed to be carried in passenger cabin.




Synopsis: A-321 Captain reported a need for clear definitive Hazmat policy to avoid ambiguities which exist among FOM; company publications and SOP regarding carriage of batteries in the passenger cabin.
Date: 201209
Local time of day: 0001-0600
Location: SMO.Airport, CA
Flight conditions: VMC
Light: Night
Aircraft: Helicopter
Flight plan: None
Mission: Passenger
Flight phase: Landing
Airspace: Class D SMO
Aircraft component: GPS & Other Satellite Navigation
Component problem: Malfunctioning
Reporter organization: Air Taxi
Reporter function: Pilot Flying; Single Pilot
Reporter qualification: Flight Crew Air Transport Pilot (ATP)
Anomaly: Aircraft Equipment Problem Less Severe
Detector: Person Flight Crew
When detected: In-flight
Result: General None Reported / Taken
Contributing factors: Aircraft; Environment - Non Weather Related
Primary problem: Ambiguous

Narrative: Loss of GPS reception to a dual set of GARMIN 430/530 receivers while landing at the [building's] helicopter pad. When on the pad; the reception page of the GPS units was referenced and zero satellites were acquired and the strength of reception indicators were zero. [I have] been having this problem sporadically in recent months after three years of never having this problem at this location.




Synopsis: Helicopter pilot reports a loss of GPS signal during landing at a building's helicopter pad. The loss of signal has been occurring sporadically over the last three months with no previous problems detected.
Date: 201909
Local time of day: 1801-2400
Location: ZZZZ.Airport, FO
Light: Daylight
Aircraft: Commercial Fixed Wing
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Flight phase: Parked
Aircraft component: Autoflight Yaw Damper
Component problem: Malfunctioning
Reporter organization: Air Carrier
Reporter function: Technician
Reporter qualification: Maintenance Airframe; Maintenance Powerplant
Human factors: Communication Breakdown
Anomaly: Aircraft Equipment Problem Less Severe; Deviation / Discrepancy - Procedural Maintenance; Deviation / Discrepancy - Procedural Published Material / Policy
Detector: Person Flight Crew
When detected: In-flight
Result: General Flight Cancelled / Delayed; General Maintenance Action
Contributing factors: Procedure; Manuals; Logbook Entry; Aircraft; MEL
Primary problem: Procedure

Narrative: Aircraft [Logbook Deferral Sheet] ITE 72XXXXX. Aircraft arrived with the following entry ( yaw damper 1 fault ) accomplished troubleshooting using post flight report; which showed a class 2 fault for the yaw damper sys. No ECAM status MSG displayed. accomplished EFCS 1 and 2 sys test both passed with no display faults. Contacted [Maintenance Control]; the advised that they would raised a [Repetitive Check Deferral] for a class 2 fault; under the guidance of the [Maintenance Control] the following entry was made in the log book. (TSM INTRO CLASS 2 MAINTENANCE MSG REF 8.A.5D FINAL RECTIFICATION NO LONGER THAN 800 FLIGHT HOURS)




Synopsis: Technician reported while following guidance in applying an MEL for a yaw damper fault; errors were made in the maintenance log.
Date: 201910
Location: ZZZ.Airport, US
Weather elements / visibility: VFR; 6
Aircraft: Citationjet (C525/C526) - CJ I / II / III / IV
Operator: Corporate
Operating under: Part 91
Flight plan: IFR
Mission: Passenger
Flight phase: Takeoff / Launch
ATC / advisory: CTAF ZZZ
Second aircraft: Any Unknown or Unlisted Aircraft Manufacturer
Reporter organization: Corporate
Reporter function: Captain; Pilot Flying; Single Pilot
Reporter qualification: Flight Crew Instrument; Flight Crew Multiengine; Flight Crew Air Transport Pilot (ATP); Flight Crew Flight Instructor
Human factors: Communication Breakdown; Time Pressure; Situational Awareness
Anomaly: Conflict Ground Conflict; Critical
Detector: Person Flight Crew
When detected: In-flight
Result: Flight Crew Took Evasive Action
Contributing factors: Human Factors
Primary problem: Human Factors

Narrative: Takeoff morning flight. VFR day winds light closest Runway 6 visibility fair. Taxi to Runway 6 called approach to get a squawk code. Then switch to announced to depart Runway 6. Both aircraft announced at same time blocking initial communications did not hear other aircraft until announcing takeoff roll. At that time I have taxi into position to depart. The other aircraft continued departing opposite runway; at that time I heard the takeoff announcing. I aborted the takeoff immediately got off the runway first taxiway and clear off the runway; the other aircraft continue the takeoff.Lesson uncontrolled field bright sun limited visibility to see the other end of the runway. Probably best way to avoid is to do multiple announcements and monitor closely UNICOM before getting clearance and depart to avoid any traffic conflicts. Only maneuver was immediate aborting the initial takeoff roll and clear the runway for the other aircraft. Being vigilant at all phases of flight the best policy.




Synopsis: Corporate jet Captain reported rejecting takeoff and exiting runway to avoid opposite direction traffic.
Date: 202007
Local time of day: 1801-2400
Location: ZZZ.Airport, US
Flight conditions: Mixed
Weather elements / visibility: 10
Light: Dusk
Aircraft: B737-700
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Takeoff / Launch
Airspace: Class B ZZZ
ATC / advisory: TRACON ZZZ
Aircraft component: Horizontal Stabilizer Trim
Component problem: Failed
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: Aircraft Equipment Problem Less Severe; Deviation / Discrepancy - Procedural Published Material / Policy
Detector: Person Flight Crew
When detected: In-flight
Result: Air Traffic Control Provided Assistance; Air Traffic Control Issued New Clearance; Flight Crew Returned To Departure Airport; Flight Crew Requested ATC Assistance / Clarification; Flight Crew Landed As Precaution; General Flight Cancelled / Delayed; General Maintenance Action
Contributing factors: Aircraft
Primary problem: Aircraft

Narrative: Departing Runway XXR during initial climb I realized the Electric Stabilizer trim was inoperative. I was the PF (Pilot Flying) and advised the Captain who was the PM (Pilot Monitoring). We continued the climb at a reduced speed 210 knots and leveled at 10;000 ft. to run the QRH Stabilizer Trim Inoperative Checklist. We advised the Departure Controller and requested vectors to return to ZZZ. Completed the QRH; computed the performance non-normal and brake energy information. The Controller [gave up priority handling] and the fire trucks were standing by during landing. We conducted an uneventful flaps 15 landing to XXR and cleared the runway and taxied to the gate. Maintenance met the aircraft and a discrepancy was entered into the logbook by the Captain.




Synopsis: B737 First Officer reported Electric Stabilizer Trim inoperative.
Date: 202201
Local time of day: 0601-1200
Location: ZZZZ.ARTCC, FO
Flight conditions: VMC
Weather elements / visibility: Wind
Light: Daylight
Aircraft: MD-11
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Climb
ATC / advisory: Center ZZZZ
Aircraft component: Reverser Translating Sleeve
Component problem: Malfunctioning
Reporter organization: Air Carrier
Reporter function: First Officer; Pilot Flying
Reporter qualification: Flight Crew Multiengine; Flight Crew Instrument; Flight Crew Air Transport Pilot (ATP)
Human factors: Troubleshooting
Second reporter function: Pilot Flying; Captain
Anomaly: Aircraft Equipment Problem Critical; Deviation / Discrepancy - Procedural Clearance; Deviation / Discrepancy - Procedural Published Material / Policy
Detector: Person Flight Crew
When detected: In-flight
Result: Air Traffic Control Provided Assistance; Flight Crew Returned To Departure Airport; Flight Crew Requested ATC Assistance / Clarification; Flight Crew Overcame Equipment Problem; Flight Crew Inflight Shutdown; Flight Crew Took Evasive Action; General Maintenance Action; General Flight Cancelled / Delayed
Contributing factors: Aircraft
Primary problem: Aircraft

Narrative: Passing 10;000 feet we received a red U/L (Un Locked) reverser light; accompanied with a significant vibration on the number one engine. We shut down the engine in accordance with the QRH. We requested priority handling with ZZZ Center and notified Dispatcher of our intentions to return to ZZZZ. After completing all checklists and briefings we completed an uneventful auto land to [Runway] XXR. Maintenance inspection showed the reverser was partially cracked open (deployed). After landing the red U/L light turned yellow; and stayed on through shutdown. No fuel dump required.


Second narrative: Passing 10;000 feet we received a red U/L reverser light; accompanied with significant vibration on the number one engine. We shut the engine down in accordance with the QRH. We requested priority handling with ZZZ Center. We notified company operations of our intentions to return to ZZZ.  After completing all checklists and briefings we completed an uneventful auto land to runway XXR. Maintenance inspection showed the reverser was partially cracked open (deployed). After landing the red U/L light turned yellow; and stayed on through shutdown. No fuel dump required.


Synopsis: MD-11 flight crew reported an engine reverser unlocked light on climbout. The flight crew performed an in flight shut down and air turn back. They requested priority handling and made a precautionary landing at departure airport.
Date: 201711
Local time of day: 0601-1200
Location: SFO.Airport, CA
Aircraft: Widebody Transport
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Taxi; Parked
Reporter organization: Air Carrier
Reporter function: Pilot Flying; Captain
Reporter qualification: Flight Crew Air Transport Pilot (ATP)
Anomaly: 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: After establishing communications with the cockpit; the ground crew stated 'Ready for push and 'they' would like brake release.' I advised the push crew that it was not procedure to release brakes without push clearance; and to standby.I don't know who 'THEY' are but we all understand that it is against SOP to release brakes without pushback clearance. This is occurring on more of my flights and in San Francisco in particular (about 50% of the time in SFO). There is a noticeable trend here in my experience and it is happening in many stations.




Synopsis: Air carrier Captain reported pushback brake release procedure SOP deviations are becoming more common.
Date: 201910
Local time of day: 1201-1800
Location: ZZZ.Airport, US
Flight conditions: VMC
Weather elements / visibility: 10
Aircraft: Baron 58/58TC
Operator: Personal
Operating under: Part 91
Flight plan: VFR
Mission: Training
Flight phase: Landing
Airspace: Class D ZZZ
ATC / advisory: Tower ZZZ
Second aircraft: Any Unknown or Unlisted Aircraft Manufacturer
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
Human factors: Communication Breakdown; Workload
Anomaly: ATC Issue All Types; Conflict Ground Conflict; Less Severe; Deviation / Discrepancy - Procedural Clearance
Detector: Person Air Traffic Control; Person Flight Crew
When detected: In-flight
Result: Air Traffic Control Issued Advisory / Alert; Flight Crew Landed As Precaution
Contributing factors: Airport; Procedure
Primary problem: Procedure

Narrative: Training a [passenger] how to land the Baron in case of the pilot having a medical emergency. Flying the LPV GPS approach to Runway XXR with the [passenger] flying the aircraft from 200 ft. to the touchdown. A slower and smaller airplane was 2 miles ahead when we received clearance to land; that aircraft did not clear the runway expeditiously and was just clearing as we crossed the end of the runway. At the very last moment; when the [passenger] was flaring the aircraft at about 25 ft. or lower; the Tower said 'Go around'. I said unable and let the [passenger] finish training and we landed. I could see the other aircraft had cleared the runway; but maybe was not across the hold short line.




Synopsis: BE58 Flight Instructor reported runway incursion and ATC late go around instruction while in landing flare.
Date: 202110
Local time of day: 1801-2400
Location: ZLC.ARTCC, UT
Aircraft: Small Aircraft; Low Wing; 1 Eng; Fixed Gear
Operator: Personal
Operating under: Part 91
Flight plan: IFR
Mission: Personal
Flight phase: Descent
Airspace: Class E ZLC
ATC / advisory: Center ZLC
Reporter organization: Government
Reporter function: Enroute
Reporter qualification: Air Traffic Control Fully Certified
Human factors: Communication Breakdown
Anomaly: ATC Issue All Types; Deviation - Altitude Overshoot; Deviation / Discrepancy - Procedural Clearance; Deviation / Discrepancy - Procedural Published Material / Policy; Inflight Event / Encounter CFTT / CFIT
Detector: Person Air Traffic Control
When detected: In-flight
Result: Air Traffic Control Issued New Clearance; Air Traffic Control Issued Advisory / Alert; Air Traffic Control Provided Assistance
Contributing factors: Human Factors
Primary problem: Human Factors

Narrative: Aircraft X asked for an RNAV approach; I cleared him over the initial fix. The aircraft deviated right of course and began descending below the MIA as well as the altitudes published on the approach. I made several attempts to contact the aircraft; including a low altitude alert. I then asked Aircraft Y to switch to a UNICOM to see if Aircraft X was over there. He was; and he came back to me and informed me that he had intended on cancelling IFR and was proceeding visually to the field. I told him he needs to tell me what he's doing prior to doing it; and to not switch frequencies without ATC approval.




Synopsis: ZLC Center Controller reported that an aircraft changed radio frequency as well as deviated from the approach course and approach altitude before being given ATC approval.
Date: 201210
Local time of day: 1201-1800
Location: LAS.Airport, NV
Flight conditions: VMC
Weather elements / visibility: 10
Light: Daylight
Aircraft: Citation V/Ultra/Encore (C560)
Operator: Personal
Operating under: Part 91
Flight plan: IFR
Mission: Passenger
Flight phase: Descent
Airspace: Class E L30
ATC / advisory: TRACON L30
Second aircraft: Widebody Transport
Reporter organization: Personal
Reporter function: Single Pilot; Pilot Flying
Reporter qualification: Flight Crew Air Transport Pilot (ATP)
Anomaly: Inflight Event / Encounter Wake Vortex Encounter; Inflight Event / Encounter Loss Of Aircraft Control
Detector: Person Flight Crew
When detected: In-flight
Result: Flight Crew Regained Aircraft Control
Contributing factors: Procedure; Environment - Non Weather Related
Primary problem: Ambiguous

Narrative: Our flight was on a vector heading to 320 degrees assigned; descending from 12;000 to 8;000 MSL on the TYSSN 3 to LAS. A [widebody transport] was ahead and lower; approximately 8 miles ahead. While descending; encountered wake turbulence in still air. Aircraft rolled approximately 50 degrees bank with autopilot engaged. Aircraft was in a right turn to begin with and descending to an assigned altitude; 8;000 MSL. TRACON then advised of wake turbulence. I responded that we encountered wake turbulence upset. TRACON leveled our flight at 9;000 MSL. We proceed to a visual approach to Runway 19R without further incident.




Synopsis: A CE-560 pilot reported a wake vortex encounter inbound to LAS 8 miles in trail of a widebody aircraft that resulted in a 50 degree roll.