elihoole/asrs-aviation-reports huggingface dataset:
Date: 201812
Local time of day: 1201-1800
Location: ZZZ.Airport, US
Flight conditions: VMC
Weather elements / visibility: clear; 10
Light: Daylight
Aircraft: Cessna 162 Skycatcher
Operator: Personal
Operating under: Part 91
Flight plan: VFR
Mission: Training
Flight phase: Taxi
Second aircraft: Commercial Fixed Wing
Reporter organization: FBO
Reporter function: Pilot Flying; Single Pilot
Reporter qualification: Flight Crew Instrument; Flight Crew Private
Human factors: Communication Breakdown; Situational Awareness
Anomaly: Ground Event / Encounter Aircraft
Detector: Person Flight Crew
When detected: Taxi
Result: General None Reported / Taken
Contributing factors: Environment - Non Weather Related; Human Factors
Primary problem: Human Factors

Narrative: When I just landed at ZZZ; Ground gave me instruction to taxi via Bravo-Echo (for refueling). So after that I went to the parking spot and parked my plane; and one gentleman from [the FBO] came and told me to move my plane all the way to the end to park my plane because the current place is for helipad (in my defense they didn't put any sign for the helipad; etc.); so I agreed to taxi the plane to the very end of their parking spot.When I am taxiing until the end; my parking spot was on the right side; the ground crew from [the FBO] gave me a turn sign (turn lights sign); instead of turn off the plane; so we can tow the plane and park (give an X sign).Before I can proceed my turn; I was pointed to the jet airplane that parked on my left side and the ground crew keep giving a sign for me to turn (because the ground crew parked his golf cart on the right side of my wings). With caution I proceeded to turn and I collide with the very tip part of the jet airplane wing. Before the accident happened there wasn't any cones around the jet plane.As the pilot-in-command I failed to secure the safety of my aircraft; and will evaluate this as part of learning process for me to be a safe and professional pilot.




Synopsis: C162 pilot reported contacting the wingtip of a parked aircraft during taxi to parking spot.
Date: 201904
Location: ZDV.ARTCC, CO
Light: Daylight
Aircraft: B737-700
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Climb
Airspace: Class A ZDV
ATC / advisory: Center ZDV
Reporter organization: Air Carrier
Reporter function: Captain; Pilot Flying
Reporter qualification: Flight Crew Air Transport Pilot (ATP); Flight Crew Multiengine; Flight Crew Instrument
Human factors: Time Pressure
Anomaly: Deviation - Track / Heading All Types; 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 Returned To Clearance
Contributing factors: Environment - Non Weather Related; Human Factors
Primary problem: Environment - Non Weather Related

Narrative: Climbing through FL380; we observed significant wing tip vortices and wake turbulence approaching our flight path. Anticipating possible aircraft upset I quickly turned off course to avoid; but did not have time to notify ATC until after initiating the turn. ATC called us to inquire about the turn as we were about to notify them. We turned back on course after avoiding the wake turbulence.Initially we believed we were going to avoid the wake turbulence; but it quickly moved towards our flight path. I should have been more conservative and requested a turn from ATC earlier to avoid even the possibility of encountering the wake turbulence.




Synopsis: B737-700 Captain reported a track deviation occurred when he turned to avoid visible indications of wake turbulence; which did not allow enough time to coordinate with ATC.
Date: 201912
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: Taxi
Airspace: Class B ZZZ
ATC / advisory: Tower ZZZ
Second aircraft: Widebody; Low Wing; 2 Turbojet Eng
Reporter organization: Government
Reporter function: Instructor; Local
Reporter qualification: Air Traffic Control Fully Certified
Human factors: Communication Breakdown; Training / Qualification
Anomaly: ATC Issue All Types; Conflict Ground Conflict; Critical; Flight Deck / Cabin / Aircraft Event Illness / Injury
Detector: Person Flight Crew
When detected: Taxi
Result: Flight Crew Took Evasive Action
Contributing factors: Human Factors; Aircraft
Primary problem: Human Factors

Narrative: While providing training on outbound ground; the following event happened:Aircraft X was given taxi instructions to Runway 28R/N5 intersection departure. The session was extremely heavy/mostly difficult for the CPCIT Career Professional Controller In Training. After giving taxi instructions; the CPCIT moved on to other tasks that needed to be handled. After the session; the FLM told both the CPCIT and me that Aircraft X had to 'slam on the brakes' to avoid hitting another taxiing aircraft on an adjacent taxiway. When that happened; a flight attendant was injured; forcing the aircraft to return to the gate.After watching and listening to the replay; it is obvious that both the CPCIT and I missed a traffic call that should have been made to avoid the situation.While I cannot speak for the CPCIT; CPCIT may have thought that the aircraft established on the A taxiway would be blocked by that heavy jet; allowing the time needed to taxi Aircraft X off gate XWE. However; after viewing the replay; I do not believe this is the case. My focus was on things elsewhere on the airport when this aircraft was taxied; and I missed the instruction and traffic call.The only thing I can recommend that would have prevented this from happening is to ensure that my scan; as well as the CPCIT's scan is complete and through; and that any coordination between outbound ground and inbound ground is accomplished.I will continue to work on my abilities as a veteran Controller to maintain my scan; and pass those traits on to those who I train.




Synopsis: Tower Controller reported aircraft under their control had to slam on the brakes to avoid contact with another taxing aircraft; resulting in a Flight Attendant injury.
Date: 201309
Local time of day: 1201-1800
Location: TPA.TRACON, FL
Flight conditions: VMC
Weather elements / visibility: 10
Light: Daylight
Aircraft: British Aerospace Undifferentiated or Other Model
Operator: Personal
Operating under: Part 91
Flight plan: IFR
Mission: Passenger
Flight phase: Initial Approach
Airspace: Class B TPA
ATC / advisory: TRACON TPA
Reporter organization: Personal
Reporter function: Captain
Reporter qualification: Flight Crew Air Transport Pilot (ATP); Flight Crew Flight Instructor; Flight Crew Instrument; Flight Crew Multiengine
Human factors: Communication Breakdown; Distraction; Workload; Confusion
Anomaly: ATC Issue All Types; 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 New Clearance; Air Traffic Control Issued Advisory / Alert; Flight Crew Became Reoriented
Contributing factors: Airspace Structure; Procedure
Primary problem: Procedure

Narrative: As we were being vectored for an ILS; TRACON gave us successive headings that turned us toward localizer interception. Then we heard and acknowledged a heading change to 170 degrees; almost 180 degrees from the inbound course. We were still several miles away from the localizer course. I commented that was odd; the PM said they must have had a conflict and wanted us behind another aircraft. A few moments later; TRACON commented that there were two aircraft with similar sounding callsigns; and called Aircraft X (us) to return to 330 degrees heading; our last previous intercept course; and for Aircraft Y to fly heading 170. No mention was made of any conflict. All subsequent radio calls were made with our complete call sign; and active crew concurrence of each transmission. We noted that the other aircraft required repeated contact attempts for Controller instructions. I should have pressed for verifying the instructions when we received the heading that put us on radar downwind after being on a 45 deg heading to intercept final. Had we been aware there was a similar callsign situation; we would have been more wary.




Synopsis: Two aircraft were on TPA TRACON frequency with similar sound call signs; one aircraft took the other aircraft vector which put it nearly 180 out of the intended track. ATC realized the error and became more accurate.
Date: 201910
Local time of day: 1801-2400
Location: ZZZ.Airport, US
Flight conditions: VMC
Aircraft: B737 Undifferentiated or Other Model
Operator: Air Carrier
Flight plan: IFR
Flight phase: Cruise
Airspace: Class C ZZZ
Aircraft component: FMS/FMC
Component problem: Failed
Reporter organization: Air Carrier
Reporter function: Captain; Pilot Not Flying
Human factors: Situational Awareness
Anomaly: Aircraft Equipment Problem Less Severe
Detector: Person Flight Crew
When detected: In-flight
Result: Flight Crew Overcame Equipment Problem
Contributing factors: Aircraft
Primary problem: Aircraft

Narrative: Approaching ZZZ we had a Dual FMC failure for about 32 minutes. We completed QRH for dual FMC failure. Advised ATC and [Maintenance Control]. Finished flight with conventional navigation. VOR to VOR and vectors for an ILS in ZZZ1.




Synopsis: B737 Captain reported Dual Flight Management Computer failure in flight.
Date: 201304
Local time of day: 0601-1200
Location: PRC.Airport, AZ
Flight conditions: VMC
Weather elements / visibility: Turbulence
Light: Daylight
Aircraft: Skyhawk 172/Cutlass 172
Operator: FBO
Operating under: Part 91
Flight plan: None
Mission: Training
Flight phase: Descent
Airspace: Class D PRC
ATC / advisory: Tower PRC
Second aircraft: Skyhawk 172/Cutlass 172
Reporter organization: FBO
Reporter function: Instructor; Pilot Not Flying
Reporter qualification: Flight Crew Multiengine; Flight Crew Instrument; Flight Crew Flight Instructor; Flight Crew Commercial
Human factors: Training / Qualification; Other / Unknown
Anomaly: Conflict NMAC
Detector: Automation Aircraft TA; Person Flight Crew
When detected: In-flight
Result: Flight Crew Took Evasive Action
Contributing factors: Procedure; Human Factors
Primary problem: Procedure

Narrative: We were extended for almost 5 miles upwind before being cleared to turn our crosswind. While still far out on the downwind; Tower cleared another aircraft not even in the pattern yet to land and follow another aircraft on final. The aircraft replied they were still looking for traffic. I kept monitoring my student's downwind. About midfield downwind while watching my student's airspeed and altitude; a target popped up on our ADS-B MFD display just in time for me to look up and see this aircraft diving down from above and behind us on the left into the downwind right in front of us. I immediately took the controls from my student and initiated a 360 turn in the downwind and informed Tower what we were doing. Tower replied and apologized and soon after I noticed another Controller took over. I believe the incident occurred because the previous Controller was not monitoring traffic flow and sequencing correctly and the fact that this other aircraft had an inoperative transponder as do several other aircraft from this FBO. Being a highly congested airspace; having a transponder would have allowed us to see the aircraft earlier and possibly slow down or maneuver appropriately for spacing. Tower needs to address issues with sequencing and flow as there has been an increase in these problems recently.




Synopsis: C172 instructor pilot on downwind at PRC reports a NMAC with another C172 entering the pattern under Tower control. Reporter informs the Tower and initiates a right 360 to reenter the downwind.
Date: 201810
Local time of day: 0601-1200
Location: ZZZ.Airport, US
Flight conditions: VMC
Aircraft: DA42 Twin Star
Operator: FBO
Operating under: Part 91
Flight plan: None
Mission: Training
Flight phase: Taxi
Reporter organization: FBO
Reporter function: Pilot Not Flying
Reporter qualification: Flight Crew Instrument; Flight Crew Private
Human factors: Training / Qualification
Second reporter function: Instructor; Pilot Flying
Anomaly: Ground Event / Encounter Aircraft
Detector: Person Flight Crew
When detected: Taxi
Result: Aircraft Aircraft Damaged
Contributing factors: Procedure; Human Factors
Primary problem: Human Factors

Narrative: We finished flight and taxied back to ramp. When we were close to the entrance of the ramp; my instructor took the flight controls and I just focused on the front side and left side. My instructor thought we can taxi clear of the King Air beside us; but we made a mistake and our aircraft's right wingtip scratched the nose of the King Air; which caused the strobe lights of our aircraft broken and a hole in the nose of King Air.


Second narrative: I went on a flight with my student to complete an incomplete lesson. As soon as we got back he was supposed to go to his commercial multi [checkride]. We went out and flew and came back and landed with no incident. As we taxied in I noticed that there was a pull through spot for the aircraft available. While turning into the ramp I took controls from my student. There were a line of two King Airs and a Twinstar to my right. While I was taxiing in I looked to the right and cleared the first aircraft. I then looked back to the right to see if I would clear the second aircraft and it looked like I would. I looked forward to ensure I didn't hit anything else. While I looked forward I struck the King Air. I then parked the aircraft and advised my supervisor.


Synopsis: DA-42 flight instructor and student reported contacting a parked King Air during taxi.
Date: 201902
Local time of day: 0601-1200
Location: IAH.Airport, TX
Flight conditions: IMC
Weather elements / visibility: Rain
Aircraft: B757 Undifferentiated or Other Model
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Initial Approach
Airspace: Class B IAH
ATC / advisory: TRACON I90
Reporter organization: Air Carrier
Reporter function: Captain; Pilot Not Flying
Reporter qualification: Flight Crew Multiengine; Flight Crew Instrument; Flight Crew Commercial; Flight Crew Air Transport Pilot (ATP)
Human factors: Situational Awareness; Time Pressure
Anomaly: Deviation - Track / Heading All Types; Deviation / Discrepancy - Procedural Clearance
Detector: Person Air Traffic Control; Person Flight Crew
When detected: In-flight
Result: Air Traffic Control Issued Advisory / Alert; Air Traffic Control Issued New Clearance; Flight Crew Became Reoriented; Flight Crew Returned To Clearance
Contributing factors: Human Factors; Procedure
Primary problem: Human Factors

Narrative: We were on the DRLLR 5 RNAV. The First Officer had already briefed the assigned runway which was the ILS 26R. I believe just prior to the DOMNO fix Approach asked us if we would be interested in the RNAV Y Runway 26R. Approach stated it would be much quicker getting us in. We both agreed and accepted the new assigned approach. I selected the approach in the FMC with the transition and we both verified the box. We felt a little bit rushed since it was a last minute reassignment; but it was totally self-induced.We were cleared to 5;000 feet and cleared for the RNAV Y Runway 26R just prior to SKLER intersection. To be honest; I don't remember if I actually saw the DRKAR fix in the box or not. Shortly after crossing SKLER fix I heard the First Officer state the aircraft is not turning. I directed my attention to the FMC to see what had gone wrong. Apparently; the First Officer had already selected heading to try to stay on the lateral portion of the approach; but over compensated in the turn.When I looked up and was about to say you need to come left; ATC was already giving us instructions to break away from the approach; and gave us vectors followed by a climb to 7;000 feet. ATC also advised us of a course deviation. Shortly after; ATC vectored us for the ILS 26R. The [remainder] of approach and landing was uneventful.




Synopsis: B757 Captain reported a track deviation occurred on the DRLLR RNAV STAR into IAH; following a late change in the arrival.
Date: 201701
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: Landing
ATC / advisory: CTAF ZZZ
Aircraft component: Main Gear
Component problem: Failed
Reporter organization: Personal
Reporter function: Pilot Flying; Single Pilot
Reporter qualification: Flight Crew Sea; Flight Crew Rotorcraft; Flight Crew Private; Flight Crew Instrument; Flight Crew Multiengine
Human factors: Situational Awareness
Anomaly: Aircraft Equipment Problem Critical; Ground Event / Encounter Loss Of Aircraft Control; Ground Event / Encounter Ground Strike - Aircraft; Ground Excursion Runway
Detector: Person Flight Crew
When detected: In-flight
Result: Aircraft Aircraft Damaged; Flight Crew Took Evasive Action
Contributing factors: Aircraft; Human Factors
Primary problem: Human Factors

Narrative: Upon touching down; the aircraft immediately made an uncommanded right turn. I immediately applied left rudder and brake. This halted the rotation; but my plane was headed for a parked jet on the ramp. I made the decision to apply hard right brake to keep from hitting the parked jet; knowing that it would most likely result in a ground loop. The left landing gear was sheared off; the prop hit with engine running; and the left wing hit the ground.I believe that I probably had some right brake applied when the wheels touched down; which initiated the initial right turn. Upon reflection; I feel that when the foot is on the rudder pedal; maintaining clearance between the toe brakes and rudder is a difficult position for the foot. I plan to mention this to the kit manufacturer. A little more angle would provide a safety factor. Secondly; the long landing gear strut has a weak point at the threads of the long shock; which makes a strong side loads problematic. A reinforcement collar at that location would help in this area. I plan to also mention this to the kit manufacturer. In any case; since this is an experimental classed aircraft; I will make these modifications to my aircraft.




Synopsis: JA30 experimental aircraft pilot reported an immediate uncommanded right turn on touchdown. Left rudder and brake were applied to stop the rotation; but the aircraft was headed for a parked aircraft; so right rudder and brake were applied to avoid them. The left gear was sheared off and the wing hits the ground.
Date: 201508
Local time of day: 1201-1800
Location: BKL.Airport, OH
Flight conditions: VMC
Light: Daylight
Aircraft: Skyhawk 172/Cutlass 172
Operator: Personal
Operating under: Part 91
Flight plan: VFR
Mission: Training
Flight phase: Landing
Airspace: Class D BKL
ATC / advisory: Tower BKL
Reporter organization: Personal
Reporter function: Pilot Flying; Instructor
Reporter qualification: Flight Crew Flight Instructor; Flight Crew Instrument; Flight Crew Multiengine; Flight Crew Commercial
Human factors: Situational Awareness
Anomaly: Conflict Ground Conflict; Critical; Inflight Event / Encounter Other / Unknown
Detector: Person Flight Crew
When detected: In-flight
Result: Flight Crew Took Evasive Action
Contributing factors: Human Factors; Procedure; Airport
Primary problem: Ambiguous

Narrative: I was with a student doing work in the pattern practicing takeoffs and landing. While set up on final a ship turned right into our flight path within a few hundred feet of 24L. I asked the Tower if they knew about the [ship] and the immediate response was; the Tower does not control the waterways and it was all reported in the AFD and NOTAMs. We took evasive action and landed safely. My concern was although no hazard or potential hazard existed; a student pilot; or another pilot with limited hours or experience would end up in a LOC situation with an obstacle so close to the approach end of Runway 24L. Once discussed with the Tower; the same response was; they have no control over the waterways. There was no concern about safety; there was no concern about communications with a potential incursion from a ship. There was only concern; that this issue was not the responsibility of the Tower.




Synopsis: C172 pilot reported he took evasive action on final at BKL to avoid a conflict with a ship near the end of 24L.
Date: 202101
Location: ZZZZ.Airport, FO
Aircraft: Commercial Fixed Wing
Operator: Air Carrier
Operating under: Part 121
Mission: Other unknown
Flight phase: Other N/A
Reporter organization: Air Carrier
Reporter function: Captain
Reporter qualification: Flight Crew Multiengine; Flight Crew Instrument; Flight Crew Air Transport Pilot (ATP)
Human factors: Situational Awareness; Confusion; Other / Unknown; Physiological - Other; Communication Breakdown
Anomaly: Deviation / Discrepancy - Procedural Published Material / Policy; Ground Event / Encounter Other / Unknown
Detector: Person Flight Crew
When detected: Other crew van transportation
Result: General None Reported / Taken
Contributing factors: Company Policy; Human Factors; Environment - Non Weather Related
Primary problem: Human Factors

Narrative: We were met at the hotel by the van to be transported to ZZZZ [airport]. The driver wasn't wearing a mask when he loaded the bags. He finished loading and sat down in his seat without a mask. I said something to the effect of; 'You aren't wearing a mask?' He didn't really say anything. After a few seconds; I said; 'Since you aren't wearing a mask; we will need fresh air.' I assumed that after seeing the 4 pilots with masks on and me saying something; he would put his mask on. He never did.Instead; he started fumbling with the AC controls. I told him that without a mask; we would need the front windows opened in order to ensure ventilation in the van. He eventually complied. We then drove 30 minutes to ZZZZ with the windows open with the OAT ~ 34 degrees. We were freezing cold.We were all upset; cold; and potentially distracted for our flight. This is a safety of flight issue. We used our CRM skills to identify this threat and deal with it. But; the bottom line is that we shouldn't have had to deal with this easily avoidable threat in the first place.




Synopsis: Air Carrier Captain reported the van driver from the hotel to the airport would not wear a face mask.