elihoole/asrs-aviation-reports huggingface dataset:
Date: 202008
Local time of day: 0601-1200
Location: X26.Airport, FL
Flight conditions: VMC
Light: Daylight
Aircraft: Small Aircraft; Low Wing; 1 Eng; Fixed Gear
Operator: Personal
Operating under: Part 91
Flight plan: None
Mission: Training
Flight phase: Final Approach
Airspace: Class G ZMA
ATC / advisory: CTAF X26
Reporter organization: Personal
Reporter function: Pilot Flying; Single Pilot
Reporter qualification: Flight Crew Air Transport Pilot (ATP); Flight Crew Flight Engineer; Flight Crew Flight Instructor; Flight Crew Instrument
Anomaly: Inflight Event / Encounter Other / Unknown
Detector: Person Flight Crew
When detected: In-flight
Result: General None Reported / Taken
Contributing factors: Environment - Non Weather Related
Primary problem: Environment - Non Weather Related

Narrative: On short final to runway 10 at Sebastian; FL (X26); there is a treetop that is very close to the VASI glideslope. This tree should be trimmed or a displaced threshold painted on runway 10. There are many student operations at X26 and this represents a great hazard to them.




Synopsis: Light aircraft pilot reported a tree poses a possible hazard on approach to X26 Runway 10.
Date: 201204
Local time of day: 0601-1200
Location: SEA.Airport, WA
Light: Daylight
Aircraft: B737-700
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Taxi
ATC / advisory: Ramp SEA
Aircraft component: Parking Brake
Component problem: Improperly Operated
Reporter organization: Air Carrier
Reporter function: First Officer; Pilot Flying
Human factors: Communication Breakdown; Training / Qualification
Second reporter function: Captain; Pilot Flying
Anomaly: Conflict Ground Conflict; Less Severe; Deviation / Discrepancy - Procedural Published Material / Policy
Detector: Person Flight Crew
When detected: Taxi
Result: Flight Crew Took Evasive Action
Contributing factors: Company Policy; Procedure; Human Factors
Primary problem: Company Policy

Narrative: On push back; while starting the #1 engine; the Ground Controller disconnected the tug and his headset prior to getting clearance from the Captain. This resulted in the brakes not being set and hence a movement of the airplane forward before we realized the situation and applied the brakes.


Second narrative: We were getting ready for pushback; the Ground Crew said that the walk around was complete and the bypass pin was in and that I was cleared to release brakes. After getting a cleared to push clearance from Ramp Control I told Ground Crew that his transmission was weak; but that the brakes were released and cleared for push. During the push the Ground Crew said something that I couldn't understand so I asked him to repeat which he did and although it was weak and had a lot of static noise I was able to make out that we were cleared to start engines. I started #2 engine and then he said something that was totally unreadable due to the static and noise and the First Officer and I asked each other if either of us understood what he had said which we did not. At that point I was starting the #1 engine and monitoring the start when I glanced up momentarily and felt as though we were moving forward and I made a comment questioning why they would be towing us forward; since I could see the tug going backward; it was at that point when the First Officer told me that we were not connected and that we were rolling forward and to set brakes. I set the brakes and the First Officer said he got a wave off from the ground crew with the bypass pin. The Marshaler on the left then gave me a cleared to go hand signal and wave off as they cleared and went back to the gate. I never received a 'set brakes' command nor did I give a' brakes are set cleared to disconnect go to hand signals'. Ground Crew disconnecting without verbal clearance to due so; compounded by poor ground crew communications.


Synopsis: A B737-700 crew reported that the ground crew disconnected the tow bar after pushback without any communications; which caused the aircraft to roll backward because the brakes were not set.
Date: 201906
Local time of day: 0001-0600
Location: ZZZ.Airport, US
Aircraft: B767-300 and 300 ER
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Parked
Reporter organization: Air Carrier
Reporter function: First Officer; Pilot Not Flying
Reporter qualification: Flight Crew Air Transport Pilot (ATP); Flight Crew Multiengine; Flight Crew Instrument
Human factors: Situational Awareness
Anomaly: Deviation / Discrepancy - Procedural Published Material / Policy; Deviation / Discrepancy - Procedural Hazardous Material Violation
Detector: Person Flight Crew
When detected: Pre-flight
Result: General Flight Cancelled / Delayed; General Maintenance Action
Contributing factors: Procedure; Human Factors
Primary problem: Procedure

Narrative: I was the FO [First Officer] on Aircraft X; on my exterior preflight inspection; the Crew Chief was loading cargo; [and] I asked the Crew Chief if we had any Dangerous Goods (DG) on board? He stated that we have dry ice in the bulk cargo and lithium batteries in the forward cargo. When we received the load closeout; the DG was only noted in the forward cargo bin. After talking with ZZZ OPS frequency and the Dispatched on the phone; I also called ZZZ OPS on the phone; all while with the parking brake set and in a safe manner. It took about 1 hr for us to recede a proper load closeout. If I did not talk to the Crew Chief and inquire about DG and him telling me the location of the DG we would have departed as the load closeout had DG; but it was not in the correct location.




Synopsis: B767 First Officer reported Dangerous Goods cargo (Dry Ice & Lithium Batteries) incorrectly loaded in cargo pits.  DG cargo load corrected prior to departure.
Date: 201410
Local time of day: 0601-1200
Location: ISM.Airport, FL
Flight conditions: VMC
Light: Daylight
Aircraft: Model 269A/300/Osage
Operator: FBO
Operating under: Part 91
Flight plan: None
Mission: Training
Flight phase: Final Approach
Airspace: Class D ISM
ATC / advisory: Tower ISM
Second aircraft: Cessna Aircraft Undifferentiated or Other Model
Reporter organization: FBO
Reporter function: Single Pilot; Pilot Flying
Reporter qualification: Flight Crew Student
Human factors: Situational Awareness; Training / Qualification; Communication Breakdown
Second reporter function: Instructor
Anomaly: Conflict NMAC; Deviation - Track / Heading All Types; Deviation / Discrepancy - Procedural Clearance
Detector: Automation Air Traffic Control; Person Air Traffic Control
When detected: In-flight
Result: Air Traffic Control Separated Traffic; Flight Crew Took Evasive Action
Contributing factors: Human Factors
Primary problem: Human Factors

Narrative: I was cleared to land runway 15 and told I was number two. I saw a cessna on the runway and misjudged it as the number one aircraft. Tower asked if I had the aircraft at sight and at that point I thought it was the aircraft on the runway he was referring to so I confirmed I had aircraft at sight. He came in again and asked if I had aircraft short final at sight and I reported I was still looking out for traffic. He told the aircraft to terminate the approach and told me to turn left immediately which I did. He told me to inform my instructor to contact the tower upon landing.


Second narrative: My student was on a solo cross country flight. I reviewed his flight plan and all of his weather. All of the conditions were great for flying. I gave him a single Q and P endorsement stating I found him ready for the flight to ISM then on to MLB and return. He was instructed by tower to join right downwind for runway 15. Student did this fine. Tower then told him he was number 2 following a Cessna on final. The student mistook an airplane on the runway as this aircraft and reported it in sight and stated number 2 cleared to land. The student then turned base and was making his final leg when tower asked if he had the Cessna traffic on short final over the approach lights in sight. Student then stated he was looking for traffic. At this point the Cessna was too close for comfort and tower told him to go-around. He then told my student to turn left immediately and head eastbound. He then gave student instructions to call tower when he lands. Student could not understand what he was saying and tower finally told him to have me the instructor call when he landed. I believe that the students situational awareness was the key factor to this occurrence. It is hard to think for a student on a solo flight and make decisions for them.


Synopsis: A student pilot had difficulty understanding ATC instructions and mis-identified the aircraft he was to follow. His early turn led to a traffic conflict that was separated by ATC. The current and former flight instructors provided similar accounts and suggestions.
Date: 201910
Light: Daylight
Aircraft: B737-700
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Cruise
Reporter organization: Air Carrier
Reporter function: Flight Attendant (On Duty)
Reporter qualification: Flight Attendant Current
Human factors: Confusion; Fatigue; Situational Awareness
Anomaly: Flight Deck / Cabin / Aircraft Event Other / Unknown
Detector: Person Passenger
When detected: In-flight
Result: General None Reported / Taken
Contributing factors: Human Factors
Primary problem: Human Factors

Narrative: Woke at 2AM to begin my day. All went relatively smoothly. While I was setting up galley in the rear; the 'C' Flight Attendant came to the rear and asked me to move on a couple rows on taking drink orders. So instead of beginning on row 17; I began orders on row 15. My first tray consisted of 7 waters; 2 cokes; a rum & coke and 2 coffees. I inadvertently poured the rum into a cup of water and not the Coke. Then I accidentally served that to a child roughly the age of 14. I also served his father a water. They were sitting next to him. Immediately after serving their row; I was still in the aisle serving. They informed me of the mistake and handed it back to me. I apologized. I went to the rear and brought them a closed can of water and a cup. I asked if he felt alright; if they needed snacks or paramedics to meet us to evaluate his son. He replied 'Oh no no; we are fine; I understand but everything is fine.' We continued the flight.




Synopsis: Flight attendant reported mistakenly serving a 14 year old child an alcoholic drink instead of what was ordered.
Date: 201909
Local time of day: 0601-1200
Location: ZZZ.Airport, US
Flight conditions: VMC
Weather elements / visibility: 10
Light: Daylight
Aircraft: Cessna 195
Operator: Personal
Operating under: Part 91
Flight plan: None
Mission: Personal
Flight phase: Landing
Aircraft component: Landing Gear
Component problem: Failed
Reporter organization: Personal
Reporter function: Pilot Flying; Single Pilot
Reporter qualification: Flight Crew Air Transport Pilot (ATP); Flight Crew Flight Engineer
Human factors: Situational Awareness
Anomaly: Aircraft Equipment Problem Critical; Ground Event / Encounter Ground Strike - Aircraft; Ground Excursion Runway
Detector: Person Flight Crew
When detected: Taxi
Result: General Maintenance Action
Contributing factors: Aircraft
Primary problem: Aircraft

Narrative: Shortly after normal landing I felt a shift to the left. Then left main landing gear collapsed sending the aircraft off the runway. No injuries to pilot or passenger.




Synopsis: NTSB Accident Number:CEN19LA322
Date: 201306
Location: ZZZ.Airport, US
Aircraft: B737-300
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Initial Approach
Airspace: Class B ZZZ
ATC / advisory: Tower ZZZ
Aircraft component: Landing Gear Indicating System
Component problem: Design; Improperly Operated
Reporter organization: Air Carrier
Reporter function: Captain; Pilot Not Flying
Human factors: Situational Awareness; Training / Qualification; Troubleshooting
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 Maintenance Action
Contributing factors: Aircraft; Company Policy; Manuals; Procedure
Primary problem: Ambiguous

Narrative: While dealing with a right main gear indication problem; I attempted to visually confirm the condition of the right main gear through the cabin floor view port. I was unable due to the installation of a thick; fiberglass view port cover. After landing; Maintenance needed to use a metal tool to pry the cover off. It was attached with a tremendous amount of Velcro.Crew needs to be informed of this cover and installation method needs to allow for ease of removal; not requiring tools.




Synopsis: A B737 right main gear viewing port was unusable because a thick Velcro cover could not be removed to permit gear down-lock verification.
Date: 202107
Local time of day: 1201-1800
Location: ZZZ.Airport, US
Flight conditions: VMC
Light: Daylight
Aircraft: B787 Dreamliner Undifferentiated or Other Model
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Takeoff / Launch
Airspace: Class B ZZZ
ATC / advisory: Tower ZZZ
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: Situational Awareness; Training / Qualification; Confusion; Communication Breakdown
Anomaly: Deviation / Discrepancy - Procedural Published Material / Policy; Deviation / Discrepancy - Procedural Clearance; Ground Event / Encounter Person / Animal / Bird
Detector: Person Air Traffic Control
When detected: Other Take Off Roll
Result: Air Traffic Control Separated Traffic; Flight Crew Took Evasive Action
Contributing factors: Human Factors; Procedure
Primary problem: Human Factors

Narrative: First; the biggest threat to the flight was that I hadn't flown in a little over a year; zero hours. This was due to COVID related reduction in flying at my airline. This flight was my first flight on Operator Experience (OE).We were cleared to line up and wait on Runway XXY at ZZZ. A regional jet was also cleared to line up and wait on Runway XXZ. The tower frequency was busy due to landing traffic on the crossing runway and communication between tower and a previously departed aircraft reporting bird activity. I haven't flown at ZZZ for a long time and had forgotten that they normally clear the smaller aircraft to takeoff before the heavy due to wake turbulence. Tower cleared the regional jet for takeoff and in the busyness my brain processed the clearance as ours. The last factor for me was we were right in the middle of transferring the aircraft from the captain to me and so the radio call; acknowledging the takeoff clearance I thought I heard; got dropped. I don't recollect making it. In addition; I failed to verbalize; verify and monitor the clearance with the captain.When tower saw us begin our takeoff roll prematurely; they cancelled our takeoff clearance and we rejected the takeoff at very low speed...I estimate 50 knots. We acknowledged; cleared the runway and taxied back to XXY. The following takeoff was uneventful.Lastly; we noticed on our second takeoff that red lights on the runway were illuminated in front of us prior to getting takeoff clearance. They extinguished when we received takeoff clearance. The lights were not used for our first takeoff.




Synopsis: First Officer reported a rejected take off after mishearing a take off clearance as theirs; that was meant for another aircraft.
Date: 202106
Local time of day: 0001-0600
Location: ZZZ.ARTCC, US
Aircraft: B737 Undifferentiated or Other Model
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Cruise
Airspace: Class A ZZZ
ATC / advisory: Center ZZZ
Reporter organization: Air Carrier
Reporter function: Flight Attendant (On Duty); Flight Attendant In Charge
Reporter qualification: Flight Attendant Current
Human factors: Confusion
Anomaly: Deviation / Discrepancy - Procedural FAR; Deviation / Discrepancy - Procedural Published Material / Policy; Flight Deck / Cabin / Aircraft Event Other / Unknown
Detector: Person Flight Attendant
When detected: In-flight
Result: General None Reported / Taken
Contributing factors: Human Factors
Primary problem: Human Factors

Narrative: [Passenger] has a large blow up pillow in exit row.Passenger in [exit row] has a air/blow up pillow that she put her arms in holes through the bottom; placed on her lap; and head through a hole in the top.  Was not connected to the plane but larger than a regular air pillow.  C and D flight attendants didn't know if this was allowed and asked me to let them know what I find out.   Larger than a normal air pillow but was not connected to any part of the plane.  Is this an obstruction of the exit or could it be popped or thrown forward was advised. Is this air pillow allowed in the exit or is it an obstruction of exit?




Synopsis: Flight Attendant reported an passenger seated in an exit row had a large inflatable pillow.  Flight attendant did not know if this pillow is allowed or should not be allowed in the exit row.
Date: 201508
Local time of day: 0601-1200
Location: ZZZ.Airport, US
Flight conditions: VMC
Weather elements / visibility: 10000
Light: Daylight
Aircraft: Small Aircraft
Operator: Personal
Operating under: Part 91
Flight plan: None
Mission: Personal
Flight phase: Landing
ATC / advisory: CTAF ZZZ
Reporter organization: Personal
Reporter function: Single Pilot; Pilot Flying
Reporter qualification: Flight Crew Private
Human factors: Situational Awareness; Distraction
Anomaly: Deviation / Discrepancy - Procedural Published Material / Policy; Ground Event / Encounter Object; Inflight Event / Encounter Loss Of Aircraft Control; Inflight Event / Encounter Object
Detector: Person Flight Crew
When detected: In-flight
Result: Aircraft Aircraft Damaged; Flight Crew Took Evasive Action
Contributing factors: Human Factors; Weather
Primary problem: Weather

Narrative: Crosswind lifted left wingtip on landing. Plane ground looped and right wing impacted a fence. Slight damage and no injury




Synopsis: A Hatz CB-1 pilot ground looped his aircraft in a crosswind causing slight damage when the right wing impacted a fence.
Date: 201907
Local time of day: 0601-1200
Location: PCT.TRACON, VA
Flight conditions: VMC
Weather elements / visibility: Thunderstorm
Aircraft: Light Transport; Low Wing; 2 Turbojet Eng
Operator: Air Taxi
Operating under: Part 135
Flight plan: IFR
Mission: Passenger
Flight phase: Climb
Airspace: Class E PCT
ATC / advisory: Center PCT
Reporter organization: Air Taxi
Reporter function: Pilot Flying; Captain
Reporter qualification: Flight Crew Air Transport Pilot (ATP); Flight Crew Instrument
Human factors: Confusion; Human-Machine Interface
Anomaly: ATC Issue All Types; Deviation - Track / Heading All Types; Deviation / Discrepancy - Procedural Clearance; Inflight Event / Encounter Weather / Turbulence
Detector: Person Air Traffic Control
When detected: In-flight
Result: Air Traffic Control Issued Advisory / Alert; Air Traffic Control Issued New Clearance; Flight Crew Became Reoriented
Contributing factors: Procedure; Chart Or Publication
Primary problem: Procedure

Narrative: We were circumnavigating a large area of thunderstorms after departure. Our cleared route was V213 which had the fixes CONLE and COLIN on it about 18 miles apart. We were abeam fix CONLE deviating when ATC cleared us to what sounded like COLIN. The PNF went direct to COLIN in the FMS and we verified it and executed. Not long after ATC queried and said CONLE was the intended clearance and re-cleared us. He didn't indicate that it was a problem and we re-entered the new fix and continued on uneventfully. My concern is having two very similar sounding fixes so close to each other on the same airway. It appears ripe for confusion or a misunderstanding; especially when deviating off airway for weather avoidances. Perhaps these fixes can be looked at and possibly renamed. Both ATC and pilots should listen very closely when on this airway to avoid this mix up in the future.




Synopsis: Light Transport aircraft Captain reported a track/heading deviation due to similar sounding fixes CONLE and COLIN located on the same airway.
Date: 201910
Local time of day: 1801-2400
Location: ZME.ARTCC, TN
Flight conditions: VMC
Light: Dusk
Aircraft: Gulfstream III (G1159A)
Operator: Government
Operating under: Part 91
Flight plan: IFR
Mission: Utility / Infrastructure
Flight phase: Cruise
Airspace: Class A ZME
ATC / advisory: Center ZME
Reporter organization: Government
Reporter function: Instructor; Pilot Flying; First Officer; Check Pilot
Reporter qualification: Flight Crew Air Transport Pilot (ATP); Flight Crew Flight Engineer; Flight Crew Flight Instructor; Flight Crew Instrument; Flight Crew Multiengine
Human factors: Communication Breakdown
Anomaly: Deviation - Track / Heading All Types; Deviation / Discrepancy - Procedural Clearance; Deviation / Discrepancy - Procedural Published Material / Policy
Detector: Automation Air Traffic Control
When detected: In-flight
Result: General None Reported / Taken
Contributing factors: Human Factors
Primary problem: Human Factors

Narrative: While maneuvering the aircraft to line up our run-in line that was on a 190 heading; we made a check turn to the north. The Controller asked us our intentions and we politely informed him of our desires. He stated that we needed to notify him of any maneuvers like that in the future. We have since passed this information on to the rest of our pilot cadre.




Synopsis: Gulfstream III First Officer reported accidental deviation from a clearance that resulted in an ATC alert.
Date: 201910
Aircraft: Commercial Fixed Wing
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Aircraft component: Communication Systems
Component problem: Malfunctioning
Reporter organization: Air Carrier
Reporter function: Dispatcher
Human factors: Communication Breakdown
Anomaly: Aircraft Equipment Problem Less Severe; Flight Deck / Cabin / Aircraft Event Illness / Injury
Detector: Person Dispatch
When detected: In-flight
Result: General None Reported / Taken
Contributing factors: ATC Equipment / Nav Facility / Buildings; Human Factors; Aircraft
Primary problem: Ambiguous

Narrative: Aircraft coasted off the gulf coast west of LEV when CALL ME ACARS came over Dispatch ACARS crew to try frequency. When calling on that frequency another flight was involved on a medical call as well. Asked flight to try another Frequency; could not be raised on new frequency so NY ARINC asked for SELCAL to start another patch. While on that SFO ARINC called aircraft on the line. Tried to bring MEDLINK on. Another call and ARINC back on with Aircraft; no medlink. Aircraft could not hear me; so tried to relay through ARINC but I was a whisper to them as well. They called me again on another line. Neighbor picked up that one and by this point Medical assistance on board requested landing ASAP. Aircraft headed towards PNS. Relayed via ACARS and ARINC to copy PNS Divert. Hung up all lines and sent landing data and medical info to them via ACARS. This was a baby that was choking and turning blue. In the patch prior to trying to get medlink on; I was trying to just get them to turn around and go to MSY. MOB would have been closer as well. In retrospect; the hospital in PNS was the closest of all 3 but they also could have been on the ground faster. If a patch could have been established the MEDLINK Dr. could have helped the ER nurse assisting the Flight Attendant's. This was a very frustrating experience where I just felt helpless in my job that I could not communicate with my crew and get them all the info they needed.




Synopsis: Dispatcher reported communication problems during an airborne medical divert.