elihoole/asrs-aviation-reports huggingface dataset:
Date: 202009
Local time of day: 1201-1800
Location: MIA.Airport, FL
Flight conditions: VMC
Aircraft: Commercial Fixed Wing
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Taxi
ATC / advisory: Tower MIA
Reporter organization: Air Carrier
Reporter function: First Officer; Pilot Flying
Reporter qualification: Flight Crew Air Transport Pilot (ATP); Flight Crew Instrument; Flight Crew Multiengine
Human factors: Confusion; Situational Awareness
Anomaly: Deviation / Discrepancy - Procedural Clearance; Ground Incursion Runway
Detector: Person Flight Crew
When detected: Taxi
Result: Flight Crew Became Reoriented
Contributing factors: Airport; Human Factors
Primary problem: Airport

Narrative: Taxiing to [Runway] 8R in Miami. Runway 12 closed. No aircraft in front of us and no aircraft on final. The triangular shape hold bars are confusing and difficult to see. We stopped in the middle of the triangle before proceeding with our takeoff clearance.




Synopsis: Air carrier First Officer reported a runway incursion at MIA occurred in part because the Runway 8R hold bars are confusing and hard to see.
Date: 202103
Local time of day: 1801-2400
Location: ZZZ.Airport, US
Flight conditions: VMC
Weather elements / visibility: 10
Light: Night
Aircraft: Skyhawk 172/Cutlass 172
Operator: Personal
Operating under: Part 91
Flight plan: VFR
Mission: Personal
Flight phase: Landing
Airspace: Class D ZZZ
ATC / advisory: Tower ZZZ
Second aircraft: Any Unknown or Unlisted Aircraft Manufacturer
Reporter organization: Personal
Reporter function: Single Pilot
Reporter qualification: Flight Crew Private
Human factors: Situational Awareness; Training / Qualification; Communication Breakdown
Anomaly: Conflict Ground Conflict; Critical; Deviation / Discrepancy - Procedural Clearance; Deviation / Discrepancy - Procedural Published Material / Policy; Ground Incursion Runway
Detector: Person Flight Crew; Person Air Traffic Control
When detected: Taxi
Result: Air Traffic Control Issued Advisory / Alert; Flight Crew Took Evasive Action
Contributing factors: Aircraft; Human Factors; Procedure; Airport
Primary problem: Procedure

Narrative: Night landing on Runway XX bounced and as recovering from second bounce received call from TWR (Tower) to exit left onto Taxiway XX. Stopped plane on RWY (Runway) and called TWR for directions to [Taxiway] XX. Told to proceed down RWY. Next call from TWR was to exit left on [Taxiways] XY2; XY and hold short [Taxiway] XX. Turned off at [Taxiway] XY2 and started down [Taxiway] XY looking for sign for [Taxiway] XX. Saw sign for [Taxiways] XX/XY. Before coming to complete stop; noticed plane approaching from left on Taxiway XX. Accelerated to get out of way and inadvertently crossed Runway XX. Too late saw runway hold lines. TWR called and requested telephone call for possible runway incursion.Factors:1. kept speed up because other planes in pattern; resulting in bounce.2. landing longer than planned.3. received taxi instruction from TWR while in active landing phase.3. loss of situational awareness of position on runway; called TWR for direction.4. should have asked for more specific information from TWR.5. Should have reviewed airport diagram in more detail for names and positions of taxiwaysin cause of landing long.6. In hindsight; should have stopped as soon as turned from [Taxiway] XY2 to XY and asked TWRfor further instructions when didn't see edge of Taxiway XX.Corrective Actions:1. Review Airport diagram2. Review Airport signage from Wings/FAA programs3. Fly with instructor and work on taxiing.




Synopsis: Pilot reported confusion over airport layout and entered an active runway with landing traffic; causing critical ground conflict.
Date: 201209
Local time of day: 1801-2400
Location: ZZZ.Airport, US
Aircraft: B777 Undifferentiated or Other Model
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Flight phase: Descent
Airspace: Class B ZZZ
ATC / advisory: TRACON ZZZ
Second aircraft: Small Aircraft
Reporter organization: Government
Reporter function: Departure; Approach
Reporter qualification: Air Traffic Control Fully Certified
Human factors: Situational Awareness; Other / Unknown
Anomaly: ATC Issue All Types; Conflict NMAC
Detector: Person Air Traffic Control
When detected: In-flight
Result: General None Reported / Taken
Contributing factors: Human Factors; Procedure; Airspace Structure
Primary problem: Human Factors

Narrative: The North Final Controller and I were working the finals. It was a slow period of traffic volume. The supervisor at the time was having a conversation with both of us while we were on position. The North Final's Conflict Alert (CA) started to go off which caught our attention. His aircraft responded to an RA; but didn't see the other aircraft who was VFR not talking to any Controller. It was a Class B violator at 9;500 FT MSL. Once I heard the CA go off on his aircraft; I told my aircraft who was staggered behind and to the left on the South Final to expedite his decent thinking he could get below the target. He then replied he was responding to an RA. He did see the aircraft. He then filed a near mid air when he landed. The East Feeder sector also never saw the target. The [previous] Controller was controlling both the north and south final aircraft. I would recommend a better alert/awareness during periods of slow traffic. Meaning both management and the controllers involved; which I believe were all three controllers and the supervisor. The Feeder Controller missed the Class B violator; the North Final Controller; me; and the supervisor who was standing around us




Synopsis: TRACON Controller described a TCAS RA event when IFR traffic inbound to the airport responded to unknown VFR traffic identified as a Class B violator.
Date: 202106
Local time of day: 0601-1200
Location: ZZZ.Airport, US
Flight conditions: VMC
Weather elements / visibility: 10
Light: Daylight
Aircraft: Skyhawk 172/Cutlass 172
Operator: Corporate
Operating under: Part 91
Flight plan: None
Mission: Training
Flight phase: Takeoff / Launch
Airspace: Class D ZZZ
ATC / advisory: Tower ZZZ
Aircraft component: Rudder Trim System
Component problem: Improperly Operated; Malfunctioning
Reporter organization: Corporate
Reporter function: Pilot Flying; Instructor
Reporter qualification: Flight Crew Commercial; Flight Crew Flight Instructor; Flight Crew Instrument; Flight Crew Multiengine
Human factors: Communication Breakdown
Anomaly: Aircraft Equipment Problem Critical; Deviation / Discrepancy - Procedural Published Material / Policy; Ground Event / Encounter Loss Of Aircraft Control
When detected: In-flight
Result: Aircraft Aircraft Damaged; Flight Crew Returned To Gate; Flight Crew Regained Aircraft Control; Flight Crew Rejected Takeoff; General Flight Cancelled / Delayed; General Maintenance Action
Contributing factors: Aircraft; Company Policy; Human Factors; Procedure
Primary problem: Aircraft

Narrative: During take off; the decision was made by the PIC(self) to abort owing to a bang and the aircraft pulling left requiring extreme right rudder use.  It was later determined by the PIC this was due to the spring loaded rudder trim jumping to the left from the right. It had previously been advised by the other flight instructors at the school to leave the rudder trim in the right side position during all phases of flight; owing to a extreme left turning tendency. However; by doing this it put undue stress on the rudder trim spring and when left rudder was used during take off the spring gave way and released the trim fully left. At the time this cause was not known to the PIC; hence the decision to abort the flight. Later it was advised that this should be in neutral; as per the POH; however incorrect local guidelines had been advised.  PIC will revert to the POH for all future use in Aircraft X.




Synopsis: Pilot reported a Rejected Take Off after hearing a loud bang.
Date: 202108
Local time of day: 1201-1800
Location: ZZZ.Airport, US
Flight conditions: VMC
Weather elements / visibility: 10
Light: Daylight
Aircraft: PA-28 Cherokee/Archer/Dakota/Pillan/Warrior
Operator: Personal
Operating under: Part 91
Flight plan: None
Mission: Training
Flight phase: Taxi
ATC / advisory: Ground ZZZ
Second aircraft: Skyhawk 172/Cutlass 172
Reporter organization: Personal
Reporter function: Instructor; Pilot Not Flying
Reporter qualification: Flight Crew Commercial; Flight Crew Multiengine; Flight Crew Instrument; Flight Crew Flight Instructor
Human factors: Communication Breakdown; Human-Machine Interface; Situational Awareness
Anomaly: Conflict Ground Conflict; Critical; Deviation / Discrepancy - Procedural Clearance; Deviation / Discrepancy - Procedural Published Material / Policy; Ground Incursion Taxiway
Detector: Person Flight Crew
When detected: Taxi
Result: Flight Crew Took Evasive Action
Contributing factors: Human Factors; Procedure
Primary problem: Human Factors

Narrative: I was training a primary student.  We received clearance from the ground controller to taxi to the runway and contact tower.  As we taxied onto the taxiway; Aircraft Y with an elderly gentleman operating single-pilot at the controls was parked facing the taxiway at a perpendicular angle in the run-up area.As we neared this airplane while taxiing down the taxiway toward [Runway] XXR abeam intersection 1; he started moving forward while looking to the left.  We got within 20-feet of each other and he never noticed because he failed to clear to his right prior to taxiing onto the taxiway.  This other pilot failed to request a taxi on ground from the run-up area as is our local procedure.We slammed on our brakes; coming to an abrupt stop and avoided the collision.




Synopsis: Instructor Pilot reported braking hard to avoid a collision with another aircraft during taxi.
Date: 201207
Local time of day: 1201-1800
Location: LGA.Airport, NY
Aircraft: EMB ERJ 170/175 ER/LR
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Flight phase: Parked
Reporter organization: Air Carrier
Reporter function: Pilot Flying; Captain
Reporter qualification: Flight Crew Air Transport Pilot (ATP)
Human factors: Situational Awareness; Communication Breakdown
Anomaly: Aircraft Equipment Problem Critical; Deviation / Discrepancy - Procedural FAR; Deviation / Discrepancy - Procedural MEL / CDL; Deviation / Discrepancy - Procedural Maintenance; Deviation / Discrepancy - Procedural Published Material / Policy
Detector: Person Other Person
When detected: Other After the fact
Result: General None Reported / Taken
Contributing factors: Aircraft; Chart Or Publication; Human Factors
Primary problem: Human Factors

Narrative: I was recently informed that several months ago I flew an aircraft that had an MEL item requirement that was not properly completed by Maintenance. Since there is a note in a portion of the MEL Remarks/Exceptions section that says an EICAS message of E1(2) [Engine one or two] REV INHIBIT will be displayed continuously. I did not notice that this message was not displayed; and that meant the TR was not properly inhibited.There are notes in both the Remarks/Exceptions column of the MEL as well as in the Flight Crew Operation Procedures. Usually the Remarks/Exceptions column is used in the application of the MEL as I understand it. Putting the note in the Flight Crew Operating Procedures column of the MEL would allow us to more easily serve as a backup for maintenance properly complying with this MEL. Other MELs have notes about EICAS messages being displayed; and the lack of consistency could cause confusion.




Synopsis: An ERJ Captain was advised he had failed to comply with the requirements of an MEL item on an aircraft he had flown several months prior to his notification.
Date: 201807
Local time of day: 1201-1800
Location: BOI.Airport, ID
Aircraft: Super King Air 200
Operating under: Part 91
Flight plan: IFR
Flight phase: Initial Climb
Airspace: Class C BOI
ATC / advisory: Tower BOI
Reporter organization: Government
Reporter function: Supervisor / CIC; Local
Reporter qualification: Air Traffic Control Fully Certified
Human factors: Time Pressure; Situational Awareness
Anomaly: ATC Issue All Types; Deviation / Discrepancy - Procedural Published Material / Policy; Deviation / Discrepancy - Procedural Clearance; Inflight Event / Encounter CFTT / CFIT
Detector: Person Air Traffic Control; Person Flight Crew
When detected: In-flight
Result: Air Traffic Control Issued New Clearance; Flight Crew Requested ATC Assistance / Clarification
Contributing factors: Human Factors; Procedure
Primary problem: Human Factors

Narrative: Aircraft X was ready Runway 28L and I had a regional jet ready to depart the parallel and I looked at Aircraft's strip noticing he was going ZZZ. That is north and cleared him for takeoff and told him to proceed on course. I waited until Aircraft X was about departure end and cleared the regional jet for takeoff and told him the upwind traffic will be in a right hand turn. Aircraft X started his turn and I thought nothing of it and shipped him to Departure then shipped the regional jet to Departure. Then the Radar Controller made us aware that he had taken corrective action because Aircraft X was not VFR as I had mistakenly thought.  He was IFR and was not turned within the DVA (Diverse Vector Area). This may have caused a loss of separation with the MVA (Minimum Vectoring Altitude). The only reason I bring up the regional jet is because getting Aircraft X going and out of the way contributed to me making a quick judgment to turn Aircraft X on course. Aircraft X ended up telling Radar that he had the terrain and wanted a VFR climb.I will be more diligent in the future to notice the full strip indicating IFR and not be trapped by the single fix flight plan as being VFR. The vast majority of IFR flight plans at BOI get a PDR (Preferred Departure Routing) so the strips have a look to them and it can trick you if you aren't careful when you get one that is ZZZ [destination] for a route on the strip. The half strip for VFR aircraft is relatively new in our order and maybe I just haven't adjusted yet.  I don't recommend any change it was my mistake and I won't make it again.




Synopsis: BOI Tower Controller reported issuing an IFR BE20 a turn; not in compliance with Minimum Vectoring Altitude procedures.
Date: 201603
Local time of day: 1201-1800
Location: ZZZ.Airport, US
Flight conditions: VMC
Weather elements / visibility: 10
Light: Daylight
Aircraft: Amateur/Home Built/Experimental
Operator: Personal
Operating under: Part 91
Flight plan: None
Mission: Personal
Flight phase: Initial Approach
Airspace: Class E ZZZ
ATC / advisory: CTAF ZZZ
Second aircraft: Any Unknown or Unlisted Aircraft Manufacturer
Reporter organization: Personal
Reporter function: Single Pilot
Reporter qualification: Flight Crew Instrument; Flight Crew Private
Human factors: Communication Breakdown; Situational Awareness
Anomaly: Conflict NMAC; Deviation / Discrepancy - Procedural Published Material / Policy
Detector: Person Flight Crew
When detected: In-flight
Result: Flight Crew Took Evasive Action
Contributing factors: Human Factors
Primary problem: Human Factors

Narrative: While approaching [the airport] I monitored the frequency from 30 miles out. There were multiple [flight school] aircraft training in the pattern doing closed circuit work. It was clear that the students were not fully familiar with the English language; however; the instructors were not on the radios except to occasionally speak with each other. Given the difficulty the student pilots had with the language; it was very difficult for me to get situational awareness as to how many planes were in the pattern. I called my intentions to join the right pattern for runway 28; which was currently in use; at 15 NM; 10 NM; and 5 NM out. I then called a 45-to-right-downwind; listening for and looking for traffic. When I turned downwind a [flight school] aircraft was approximately 150 feet off my right wingtip and at the same 1000 foot altitude. I called an immediate left 360-degree turn; performed the turn; and re-entered the pattern. Upon re-entering I saw a plane on final and another turning base. I asked if the plane I had had the near miss with had seen me. An English-speaking instructor came on the frequency and stated he had seen me and heard me call my positions and intentions. Neither he nor his student were transmitting position reports on that circuit of the pattern. I landed behind that plane; which did a touch-and-go and departed the pattern.




Synopsis: The pilot of a small experimental aircraft reported a near midair collision at a non-towered airport.
Date: 201909
Local time of day: 1201-1800
Location: LAS.Airport, NV
Flight conditions: VMC
Aircraft: B737 Next Generation Undifferentiated
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Descent
Airspace: Class B LAS
ATC / advisory: TRACON L30
Second aircraft: Widebody Transport
Reporter organization: Air Carrier
Reporter function: Captain; Pilot Not Flying
Reporter qualification: Flight Crew Instrument; Flight Crew Multiengine; Flight Crew Air Transport Pilot (ATP)
Anomaly: Inflight Event / Encounter Loss Of Aircraft Control; Inflight Event / Encounter Wake Vortex Encounter
Detector: Person Flight Crew
When detected: In-flight
Result: Flight Crew Regained Aircraft Control; Flight Crew Requested ATC Assistance / Clarification; General Physical Injury / Incapacitation
Contributing factors: Environment - Non Weather Related; Procedure
Primary problem: Ambiguous

Narrative: We were on descent [on an] RNAV arrival into LAS. ATC was attempting to create separation [with] a heavy aircraft we were following. The autopilot was engaged and [we] encountered a rapid roll to the left which created an upset that required full aileron flight control deflection to stabilize the aircraft in level flight. After the aircraft was stabilized I was in contact with the flight attendants and was informed by the purser that one crew member was down in the aft galley. I landed without further event in LAS. Paramedics met the flight and evaluated the cabin crew. There were no passenger injuries [since] they were all in their seats with the seat belt sign on. The flight attendants were up in the cabin performing their final cabin checks. The event took place at 14;000 feet. Both LAX Center and Vegas Approach Control were trying to create separation for [us] right after departure from LAX. When I informed Vegas Approach that we had an upset he asked if [it] was wake turbulence from the heavy we were following.




Synopsis: B737NG Captain reported an injury to a Flight Attendant resulting from an upset in a wake turbulence encounter on arrival into LAS.
Date: 201910
Local time of day: 1201-1800
Location: ZZZ.Airport, US
Aircraft: A320
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 Multiengine; Flight Crew Air Transport Pilot (ATP); Flight Crew Instrument
Human factors: Communication Breakdown
Anomaly: Aircraft Equipment Problem Less Severe; Deviation / Discrepancy - Procedural Published Material / Policy; Ground Event / Encounter Other / Unknown
Detector: Person Flight Crew
When detected: Aircraft In Service At Gate
Result: General None Reported / Taken
Contributing factors: Equipment / Tooling; Human Factors
Primary problem: Human Factors

Narrative: Aircraft X had an APU on MEL. We arrived and were met by the ramp crew and jetway driver as normal. Shut down #2 engine and kept #1 running for electric until jetway power plugged in. Cargo doors and boarding door were opened and passengers began to deplane.Several minutes later I received a signal from a ramp person asking about external power availability and gave them the thumbs down that it was not available on the overhead. I waited for several more minutes and then called Operations to advise of the situation. I was informed that the city had been advised of the jetway power issue; and I asked about an external power cart. I was told this was in the works as well.About 5 min later when the aircraft was almost completely deplaned; I noticed the refueling message on ECAM. I advised Operations that a fuel truck had hooked up to the aircraft with the #1 engine still running. I immediately proceeded to shut down the engine and depower the aircraft. The next flight crew was in the boarding area and they were advised of the situation.




Synopsis: A320 Captain reported that ground personnel began refueling the aircraft while the #1 engine was still running.
Date: 201206
Local time of day: 0601-1200
Location: ZZZ.ARTCC, US
Flight conditions: VMC
Light: Daylight
Aircraft: Challenger 300
Operator: Corporate
Operating under: Part 91
Flight plan: IFR
Mission: Passenger
Flight phase: Cruise
Airspace: Class A ZZZ
ATC / advisory: Center ZZZ
Aircraft component: Pressurization System
Component problem: Failed
Reporter organization: Personal
Reporter function: Captain
Reporter qualification: Flight Crew Air Transport Pilot (ATP)
Anomaly: Aircraft Equipment Problem Critical
Detector: Person Flight Crew
When detected: In-flight
Result: Air Traffic Control Issued New Clearance; Flight Crew Diverted; Flight Crew Took Evasive Action; Flight Crew Landed As Precaution; General Declared Emergency
Contributing factors: Aircraft
Primary problem: Aircraft

Narrative: While enroute a depressurization was experienced at FL410; approximately 60 miles west of ZZZ. An emergency descent was conducted to 13;000 FT. ATC was notified and 7700 was squawked. The aircraft diverted to ZZZ without further incident.




Synopsis: CL300 Captain reports a loss of cabin pressurization at FL410 and the resulting emergency descent and diversion to a suitable airport.