elihoole/asrs-aviation-reports huggingface dataset:
Date: 201902
Local time of day: 0601-1200
Location: ZZZ.Airport, US
Light: Daylight
Aircraft: Gulfstream G200 (IAI 1126 Galaxy)
Operator: Corporate
Operating under: Part 135
Flight plan: IFR
Mission: Passenger
Flight phase: Cruise
Aircraft component: Service/Access Door
Component problem: Failed
Reporter organization: Corporate
Reporter function: Pilot Flying; Captain
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: Aircraft In Service At Gate
Result: General None Reported / Taken
Contributing factors: Aircraft
Primary problem: Aircraft

Narrative: The aircraft came out of maintenance. After the aircraft was staged; the pilot in command performed a thorough preflight inspection and no issues were observed with the aircraft. The 4 hour flight was uneventful with no warnings showing on the EICAS display or anywhere in the cockpit. No loud noises; no vibration or any anomalies were observed.Upon landing; while performing a post-flight inspection; the pilot in command observed the left battery door missing. It separated during flight. Pilot in command inspected the compartment as well as the entire area aft of the battery compartment including the fuselage; the left engine pylon; the elevator and the directional fins and no damage was observed. The door opened up and separated in flight with no indication to the crew or any of the systems.




Synopsis: G200 Captain reported noticing in the post flight inspection that the left battery door had departed the aircraft in flight.
Date: 201212
Local time of day: 1201-1800
Location: SNA.Airport, CA
Flight conditions: VMC
Weather elements / visibility: 10
Light: Daylight
Aircraft: Medium Transport; Low Wing; 2 Turbojet Eng
Operator: Corporate
Operating under: Part 91
Flight plan: IFR
Mission: Passenger
Flight phase: Cruise
Airspace: Class A ZLA
ATC / advisory: Center ZLA
Aircraft component: FMS/FMC
Component problem: Improperly Operated
Reporter organization: Corporate
Reporter function: First Officer; Pilot Flying
Reporter qualification: Flight Crew Air Transport Pilot (ATP); Flight Crew Multiengine; Flight Crew Flight Instructor; Flight Crew Instrument
Human factors: Situational Awareness; Confusion
Second reporter function: Pilot Flying; Captain
Anomaly: Deviation - Track / Heading All Types; Deviation / Discrepancy - Procedural Clearance; Deviation / Discrepancy - Procedural Published Material / Policy
Detector: Person Air Traffic Control
When detected: In-flight
Result: Air Traffic Control Issued Advisory / Alert; Flight Crew Returned To Clearance
Contributing factors: Chart Or Publication; Human Factors; Procedure
Primary problem: Ambiguous

Narrative: Clearance was PONDD Intersection; TAFTO Intersection; FLM VOR then the TANDY 3 arrival. PONDD Intersection was inserted manually into the FMS as PONND which resulted in a 10 mile error when LA Center noticed the deviation. LA Center issued a heading to fly with no traffic incursion. The error was a result of the close proximity of both intersections with similar spellings. No traffic issues resulted from the error.


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


Synopsis: A flight crew reported a track deviation in ZLA airspace after entering PONND Intersection in the FMS when the clearance was to a nearby PONDD Intersection.
Date: 201502
Local time of day: 0001-0600
Location: ASG.Airport, AR
Flight conditions: VMC
Aircraft: Skyhawk 172/Cutlass 172
Flight plan: VFR
Flight phase: Taxi
ATC / advisory: Tower AGC
Second aircraft: Skyhawk 172/Cutlass 172
Reporter organization: Government
Reporter function: Local
Reporter qualification: Air Traffic Control Fully Certified
Human factors: Confusion
Anomaly: Ground Event / Encounter Other / Unknown; Ground Incursion Runway
Detector: Person Air Traffic Control
When detected: Taxi
Result: Air Traffic Control Issued Advisory / Alert; Air Traffic Control Issued New Clearance; Air Traffic Control Separated Traffic
Contributing factors: Airport; Human Factors
Primary problem: Ambiguous

Narrative: The C172 pilot called local control ready for takeoff.  I told the pilot to hold short of Runway 28 because of traffic turning final.  The pilot read back the hold short instructions.  I noticed that it appeared the C-172 had crossed the hold short lines on taxiway Alpha (east end) and I told the inbound aircraft; on [short] final to go around; the aircraft on Alpha had crossed the hold short lines.  The pilot went around.  I then advised the C-172 pilot that he had crossed the hold short lines; and he apologized. I then cleared the C-172 for takeoff.  I then gave the C-172 pilot the Brasher Warning and asked him to call the tower when he landed at his destination.  He copied the tower phone number and said he would call.  I had no further contact with the pilot.I did not file this pilot deviation until local management advised that it could be considered a safety issue because of poor hold short markings.The airport authority should add additionally signage/markings/lights to the hold lines at each end of taxiway Alpha.  The hold lines at each end of taxiway Alpha are further back than the hold lines on all the other intersections for Runway 10/28; thus causing confusion for pilots.  Adding flashing lights to the current signs may be a possible solution.




Synopsis: A C-172 failed to stop prior to crossing the hold short line abnormally distant from Runway 28 on the parallel south taxiway. The reporter/Local Controller directed an aircraft on final to go-around and; after clearing the C-172 for takeoff advised its pilot of the Tower's phone number and requested a call upon landing. The Controller was never contacted.
Date: 202106
Local time of day: 1801-2400
Location: ZNY.ARTCC, NY
Flight conditions: VMC
Aircraft: Large Transport; Low Wing; 2 Turbojet Eng
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Climb
Second aircraft: UAV: Unpiloted Aerial Vehicle
Reporter organization: Air Carrier
Reporter function: Captain; Pilot Not Flying
Reporter qualification: Flight Crew Multiengine; Flight Crew Commercial; Flight Crew Instrument; Flight Crew Air Transport Pilot (ATP)
Human factors: Distraction
Anomaly: Airspace Violation All Types; Conflict NMAC; Deviation / Discrepancy - Procedural FAR; Deviation / Discrepancy - Procedural Published Material / Policy; Deviation / Discrepancy - Procedural Unauthorized Flight Operations (UAS)
Detector: Person Flight Crew
When detected: In-flight
Result: Air Traffic Control Provided Assistance; Flight Crew Requested ATC Assistance / Clarification
Contributing factors: Human Factors; Environment - Non Weather Related
Primary problem: Human Factors

Narrative: While climbing northeast bound toward GREKI and passing through approx 13;000 feet the FO (First Officer; Pilot Flying) looked out his side window and said we had just passed over a drone by approximately 200 feet. We reported this to ATC who queried us on its color (green); size (approx 3FT by 3FT); altitude (approx 12;800 feet); and direction of flight (apparently south).




Synopsis: Air carrier flight crew climbing through 13;000 feet reported a near miss with a UAS approximately 200 feet below the aircraft. ATC was notified.
Date: 201402
Local time of day: 1201-1800
Location: ZZZ.Airport, US
Aircraft: Regional Jet 200 ER/LR (CRJ200)
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Taxi
ATC / advisory: Tower ZZZ
Reporter organization: Air Carrier
Reporter function: First Officer; Pilot Not Flying
Reporter qualification: Flight Crew Commercial
Anomaly: Ground Event / Encounter Loss Of Aircraft Control
Detector: Person Flight Crew
When detected: Taxi
Result: Flight Crew Regained Aircraft Control
Contributing factors: Airport; Procedure; Weather
Primary problem: Ambiguous

Narrative: We obtained the arrival weather which designated Runway 20 for landing and advised us that Braking Action was medium to poor on the runway; and poor on all taxiways and ramps. We landed on Runway 20 without any complications and were instructed to exit a G Taxiway and cross [the intersecting] runway to the ramp. Braking action was noticeably worse once we turned on to G; so we continued at a slow pace of 5-10 MPH. While taxiing down G near G2 Intersection; the Captain mentioned that he was beginning to lose traction and he began applying the brakes but to no avail and the aircraft began drifting to the left. With the intent of regaining control of the aircraft the Captain deployed the thrust reversers and continued braking but nothing worked; the airplane slid about 90 degrees to the left. The Captain stowed the reversers and kept applying the brakes and we came to a stop on the taxiway; the parking brake was set and we advised the Tower of our situation. Airport and ground operations employees came out to our location and took some pictures before towing the aircraft to the gate.




Synopsis: CRJ-200 flight crew experiences NIL braking action during taxi in after landing resulting in the aircraft coming to a stop perpendicular to but on the taxiway. A tow to the gate is requested.
Date: 202004
Local time of day: 1201-1800
Location: ZZZ.Airport, US
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 Published Material / Policy; Flight Deck / Cabin / Aircraft Event Passenger Misconduct
Detector: Person Flight Attendant
When detected: Pre-flight
Result: General None Reported / Taken
Contributing factors: Human Factors; Company Policy; Environment - Non Weather Related
Primary problem: Company Policy

Narrative: Before boarding; the Y Flight Attendant noticed a cigarette butt found in Row XX. She picked it up and showed it to me. It looked like 3/4 of a smoked cigarette.Also on this aircraft; there was no alcohol-based hand sanitizer present for the flight attendants. The only sanitizer that was stocked on the aircraft were the usual foam sanitizers.If there was someone actually smoking on the previous flight at their seat; that's a huge safety hazard. I also don't know how the cleaners (if there were any) missed this; as it was clearly visible if a flight attendant spotted it. Also; it's my understanding that each flight is supposed to have alcohol-based sanitizers. Please make sure that they are available to flight attendants on every flight.




Synopsis: Flight Attendant reported they found a 3/4 used cigarette on the aircraft while doing initial inspections and wondered how the cleaning crew missed it.  Also; there were no alcohol based cleaning/sanitation supplies on the aircraft.
Date: 202001
Local time of day: 0001-0600
Location: FLL.Airport, FL
Flight conditions: VMC
Aircraft: A320
Operator: Air Carrier
Flight plan: IFR
Flight phase: Takeoff / Launch
Airspace: Class C FLL
ATC / advisory: Tower FLL
Aircraft component: Flap Control (Trailing & Leading Edge)
Component problem: Improperly Operated
Reporter organization: Air Carrier
Reporter function: First Officer; Pilot Flying
Reporter qualification: Flight Crew Air Transport Pilot (ATP)
Human factors: Time Pressure; Workload; Situational Awareness; Distraction; Communication Breakdown
Anomaly: ATC Issue All Types; Deviation / Discrepancy - Procedural Published Material / Policy
Detector: Person Flight Crew
When detected: In-flight
Result: Aircraft Equipment Problem Dissipated; Flight Crew Became Reoriented; Flight Crew Overcame Equipment Problem; Flight Crew Took Evasive Action
Contributing factors: Airport; Environment - Non Weather Related; Human Factors
Primary problem: Human Factors

Narrative: We failed to correctly set flaps for takeoff after a runway changeI was First Officer and Pilot Flying. We were delayed for over an hour for an EDICT time. When we finally left our pushback clearance was changed twice then we were given taxi instructions to 10L. We started taxiing with a hold short clearance and completed the before takeoff checklist to the line but were then given a runway change to 10R along with new taxi instructions and a second hold short clearance. I updated the FMS and I allowed myself to be distracted and forgot to inform the Captain that the new runway required us to change our flap setting. We were told to expect a XA08L departure but immediately after starting the second engine we were given an early position and hold clearance with traffic on final. We completed the before takeoff checklist without repeating the items above the line. We completed a normal takeoff and climb and I only noticed my error when we retracted the flaps. Vls came up faster than normal so I lowered the pitch to ensure we would continue to accelerate. The rest of the climb was uneventful.My biggest error was not asking for more time when I felt rushed to be ready for a position and hold. Other errors were not resetting flap in accordance with the takeoff date for our new runway and not repeating the entire before takeoff checklist.




Synopsis: A320 First Officer reported pre-departure high workload coupled with a runway change that resulted in taking off with an improper flap setting. Once flaps were retracted; the flight proceeded uneventfully.
Date: 201906
Local time of day: 1201-1800
Location: MOD.Airport, CA
Flight conditions: VMC
Weather elements / visibility: 10
Light: Daylight
Aircraft: Helicopter
Operator: Air Taxi
Operating under: Part 135
Flight plan: IFR
Mission: Passenger
Flight phase: Descent
Airspace: Class D MOD
ATC / advisory: Tower MOD
Second aircraft: Any Unknown or Unlisted Aircraft Manufacturer
Reporter organization: Air Taxi
Reporter function: Pilot Flying; Single Pilot; Captain
Reporter qualification: Flight Crew Commercial; Flight Crew Flight Instructor; Flight Crew Instrument
Anomaly: ATC Issue All Types; Conflict NMAC
Detector: Automation Aircraft RA; Automation Aircraft TA
When detected: In-flight
Result: Flight Crew FLC complied w / Automation / Advisory; Flight Crew Took Evasive Action
Contributing factors: Procedure
Primary problem: Procedure

Narrative: I received a clearance to transition to a hospital in Modesto's Class D airspace at 1;500 feet MSL. Upon crossing the airport and getting close to my destination I requested to descend. I received approval to descend at pilot's discretion and report landing at the hospital. After initiating my descent the TCAS (Traffic Collision Alerting System) alerted me of traffic and I had eyes out when I saw a single engine fixed wing aircraft cross in front of me and below me from left to right. It came into view after passing my instrument panel which had blocked my view from being able to see it. I estimated the aircraft to be in a right crosswind turning to a downwind for the airport. I had not received any traffic advisories. I also do not recall hearing any advisories given to any other aircraft at that time as well. I stopped my descent briefly before continuing to land at the hospital where I shut down and contacted Modesto Tower directly via phone to notify them of the occurrence.




Synopsis: Helicopter Captain reported an NMAC during descent to destination. Received TA followed by RA.
Date: 202112
Local time of day: 1801-2400
Location: ZZZ.Airport, US
Aircraft: Small Transport; Low Wing; 2 Turbojet Eng
Flight plan: IFR
Flight phase: Cruise
Airspace: Class E ZZZ
ATC / advisory: TRACON ZZZ
Reporter organization: Government
Reporter function: Approach
Reporter qualification: Air Traffic Control Fully Certified
Human factors: Communication Breakdown
Anomaly: ATC Issue All Types; Airspace Violation All Types; Deviation - Track / Heading All Types; Deviation / Discrepancy - Procedural Clearance; Inflight Event / Encounter CFTT / CFIT
Detector: Person Air Traffic Control
When detected: In-flight
Result: Air Traffic Control Issued Advisory / Alert; Flight Crew Returned To Clearance
Contributing factors: Human Factors
Primary problem: Human Factors

Narrative: Aircraft X was level at [FL]040 direct ZZZZZ; as coordinated by Center. I gave the pilot a 350 heading to fly for a left downwind Runway XX. The pilot read back the correct heading and then turned to a 035 heading. I immediately noticed the pilot turning to an incorrect heading and corrected his heading to turn further west as to avoid the 050 MVA to his east. The pilot did not respond to the first or second time that I tried to correct his heading. On the third attempt to correct his heading; the pilot admitted that he was on a 035 heading and I continued to turn him further west to avoid the 050 MVA. He started his turn right after he had entered the 050 MVA and exited shortly after. The pilot was deviated after he landed. I recommend pilots fly the heading that they read back.




Synopsis: Approach Controller reported aircraft read back clearance correctly; yet turned to wrong heading resulting in entering a higher MVA.
Date: 201903
Local time of day: 1201-1800
Location: CLT.Airport, NC
Flight conditions: VMC
Aircraft: B737-800
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Descent
Airspace: Class B CLT
ATC / advisory: TRACON CLT
Reporter organization: Air Carrier
Reporter function: Captain; Pilot Flying
Reporter qualification: Flight Crew Multiengine; Flight Crew Instrument; Flight Crew Air Transport Pilot (ATP)
Human factors: Situational Awareness; Human-Machine Interface
Second reporter function: First Officer; Pilot Not Flying
Anomaly: Deviation - Altitude Undershoot; Deviation / Discrepancy - Procedural Clearance; Deviation / Discrepancy - Procedural Published Material / Policy
Detector: Person Flight Crew
When detected: In-flight
Result: Air Traffic Control Issued New Clearance; Flight Crew Requested ATC Assistance / Clarification
Contributing factors: Airspace Structure; Chart Or Publication; Procedure; Weather
Primary problem: Airspace Structure

Narrative: On BANKR 2; in VNAV path; autopilot on; on path; on speed approaching DEBBT. The aircraft suddenly became high on the RNAV descent profile and entered a steep descent to try and catch the path. The aircraft accelerated from 270 kts to 300 kts. I exited VNAV and went to vertical speed mode to slow the rate of descent. We immediately advised approach that we were high and fast and unable to comply with the remainder of the profile. We were told to descend to 7;000 feet and given a phone number to call after landing. The remainder of the arrival; approach and landing was uneventful.Appears to have been a problem with either the VNAV system on the aircraft; the BANKR 2 profile; or both. Not sure how we could avoid this in the future. The aircraft was tracking the profile perfectly up until DEBBT intersection. We had entered tail winds in the box before the arrival since we anticipated a tail wind.


Second narrative: [Report narrative contains no additional information.]


Synopsis: B737-800 flight crew reported the aircraft was not able to meet the required restrictions on an BANKR2 RNAV Arrival.
Date: 201211
Local time of day: 0601-1200
Location: HOU.Airport, TX
Flight conditions: VMC
Light: Daylight
Aircraft: B737-700
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Taxi
Reporter organization: Air Carrier
Reporter function: Pilot Flying; Captain
Reporter qualification: Flight Crew Air Transport Pilot (ATP)
Human factors: Situational Awareness; Communication Breakdown
Second reporter function: Pilot Not Flying; First Officer
Anomaly: ATC Issue All Types; Conflict Ground Conflict; Critical; Ground Incursion Runway
Detector: Person Flight Crew
When detected: Taxi
Result: Air Traffic Control Issued New Clearance; Flight Crew Took Evasive Action; Flight Crew Executed Go Around / Missed Approach
Contributing factors: Airport; Human Factors; Procedure
Primary problem: Procedure

Narrative: Our taxi clearance was; 'Taxi to Runway 30L; via Y; C; M; and hold short of 4 on C.' While on Y; Ground Control told us to 'keep your speed up to cross Runway 4 on Charlie. Company [aircraft] on a four-mile final.'  I could not maintain or increase my speed because I still had two turns to make in order to cross Runway 4 (from Y onto C and a slight jog crossing 4). The company on final looked close. I asked the First Officer to confirm with Ground Control that we were definitely cleared to cross but he received no response. I was already slowing and; when no response was received; I opted to stop but could not do so in time and went past the hold short line 10 or 15 feet. We then saw a small prop on takeoff roll. The First Officer told Ground we were past the hold short line but; again; got no response from Ground. I got on the radio and forcefully reiterated that we were past the hold short line. (Company was now on short final.) Ground said; 'Just hold where you are.'  The other carrier continued its takeoff roll past us and the company was now on the go [around]. Ground then cleared us to cross Runway 4 and taxi C; M; to Runway 30L. Nothing else was said to us and our takeoff was uneventful. If you have what you believe to be a clearance; but it doesn't look right; stop; preferably; in time not to cross the hold short line. ATC needs a better choice of words. 'Keep your speed up to cross' is not a 'cleared to cross' but certainly can be construed as such given the circumstances.


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


Synopsis: An attempt by Ground Control to expedite operations resulted in the reporter's aircraft crossing the hold short line and stopping while another continued its takeoff despite the encroachment and a third on short final executed a go-around.
Date: 201503
Local time of day: 0001-0600
Location: ZZZ.Airport, US
Light: Daylight
Aircraft: B737 Undifferentiated or Other Model
Operator: Air Carrier
Operating under: Part 121
Mission: Passenger
Flight phase: Taxi
ATC / advisory: Tower ZZZ
Reporter organization: Air Carrier
Reporter function: Captain; Pilot Not Flying
Reporter qualification: Flight Crew Air Transport Pilot (ATP)
Human factors: Communication Breakdown
Anomaly: Conflict Ground Conflict; Critical; Deviation / Discrepancy - Procedural Clearance
Detector: Person Flight Crew
When detected: Taxi
Result: General None Reported / Taken
Contributing factors: Human Factors
Primary problem: Human Factors

Narrative: While holding short of Runway on taxiway 'C' a light civil aircraft passed our aircraft on the right side after being told by ground to go around our aircraft on the left side.  We were holding on taxiway 'C' offset to the right of the centerline in case an aircraft had to clear the Runway at 'C' due to numerous taxiway closures.  The aircraft had to pass under part of our right wing and being equipped with the split winglets there was a real danger of the aircraft contacting our right winglet.




Synopsis: B737 Captain reports a light civil aircraft passing his aircraft on the right with wing overlap (underlap) due to taxiway confines. Being equipped with the split winglets (scimitar); there was a real danger of the aircraft contacting the right lower winglet.