elihoole/asrs-aviation-reports huggingface dataset:
Date: 201304
Local time of day: 1201-1800
Location: ZZZ.Airport, US
Flight conditions: VMC
Weather elements / visibility: Gusty; 10
Light: Daylight
Aircraft: Skyhawk 172/Cutlass 172
Operator: Personal
Operating under: Part 91
Flight plan: VFR
Mission: Training
Flight phase: Landing
ATC / advisory: CTAF ZZZ
Reporter organization: Personal
Reporter function: Single Pilot
Reporter qualification: Flight Crew Student
Human factors: Human-Machine Interface; Training / Qualification
Anomaly: Deviation / Discrepancy - Procedural Published Material / Policy; Ground Event / Encounter Object; Ground Excursion Runway; 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 Regained Aircraft Control
Contributing factors: Human Factors; Weather
Primary problem: Ambiguous

Narrative: I made my first solo cross-country flight and I arrived in the vicinity of the airport and listened to the ASOS which reported sky conditions as clear and wind at 210 at 10 knots.  No gusts indicated.  The airport has two runways and I chose XX instead of XY; making the angle of the wind 50 off instead of 30 off.  Continuing to fly in the left pattern for Runway XX; I turned final.  The wind had turned gusty.  My airspeed indicator was varying five to ten knots on final; so I added a little power to stabilize.  I touched down on the right side of the center line and in trying to counter the effect of the gust factor; I forgot that a little power was still on.  Finally I was pretty straight on the runway and thinking I'm in control I put the throttle to idle trying to lose airspeed and stop; when a gust pushed me off the left side of the runway where I hit a runway light with my left main gear; and continued more to the left.  I added some power as a reflex to try to control my direction and applied right rudder in an attempt to get back to the runway; but instead continued straight until I came to a low hill on the side of Runway XX that I hit laterally making my airplane bank severely to the right.  The added power kept the plane from turning over and it came back down the hill toward the runway.  Finally; I got back on the runway and cut the power to idle.  I taxied to the FBO; stopped the engine and called my home base.In retrospect my first mistake was to choose the wrong runway; even though 10 knots of cross wind is not really much.  After I stopped the airplane at the FBO; I listened to the ASOS for the wind and it was 200; 14 knots gusting to 23 knots.  I believe the quick change of the wind made my landing a lot more difficult.  My second mistake was to not go-around and instead trying land.  After a one-hour flight without any problem; I guess I wanted my first cross-country solo flight to be good.  Finally; I think a possible lack of crosswind evaluation and more intense training and experience in a crosswind landing was a problem.




Synopsis: C172 student pilot on his first solo cross country experiences a runway excursion during landing in a gusty crosswind.
Date: 201409
Local time of day: 0001-0600
Location: SLC.Airport, UT
Aircraft: Any Unknown or Unlisted Aircraft Manufacturer
Flight plan: VFR
Mission: Skydiving
Flight phase: Other Holding Pattern
Airspace: Class B SLC
ATC / advisory: Tower SLC
Reporter organization: Government
Reporter function: Other / Unknown
Reporter qualification: Air Traffic Control Fully Certified
Human factors: Distraction; Confusion; Communication Breakdown; Situational Awareness; Troubleshooting; Workload
Anomaly: Conflict Airborne Conflict; Deviation / Discrepancy - Procedural Clearance; Deviation / Discrepancy - Procedural Published Material / Policy
Detector: Person Air Traffic Control
When detected: In-flight
Result: Air Traffic Control Separated Traffic
Contributing factors: Procedure; Aircraft; Human Factors
Primary problem: Procedure

Narrative: The tower supervisor coordinated with S56 a specific plan to handle a parachute operation that was in progress east of SLC.  The Tracon was supposed to let us know when the Jumpers were 2 to 3 minutes from jumping.  At that point the Tracon was going to hold all VFR aircraft out that would cause a problem for the jumpers until we called them and reported that the jumpers were on the ground. The first time the jump aircraft called jumpers away the Tracon had already gave us a VFR aircraft after the fact; but we were able to call off the jump until that VFR aircraft landed.  The next time the Jump aircraft reported jumpers away the jumpers did jump this time.  The jump aircraft exited the Bravo airspace and told the Tracon controller that the jumpers were down and clear; but we were informed that the pilot was not in communication with the jumpers so there was know way for him to know they were all on the ground.  We had already coordinated that we would tell the Tracon when they could start sending VFR back into the airspace; but that didn't happen.  The Tracon just took the jump report from the pilot and resumed normal ops. The Tracon controller started to let the VFR aircraft(s) back into Bravo again; thinking the jumpers were down; but the tower could still see one parachute still in the air.  We tried to get the Tracon to hold the VFR aircraft(s) out; but we ended up having to move the VFR's out of the way on our own until we observed all the jumpers were down.  The jump pilot obviously assumed the jumpers were down; but that wasn't the case.We have these parachute jumps every year and they never go as planned. They are always planned at very busy times and very close to the airport.  I don't think it is a safe operation and I think it should not be allowed to do any more.




Synopsis: SLC Controller reports of miscommunication between TRACON and Tower reference jumpers being on the ground and allowing aircraft in close proximity.
Date: 201712
Local time of day: 0601-1200
Location: ZZZ.Airport, US
Weather elements / visibility: 10
Light: Daylight
Aircraft: Cheetah; Tiger; Traveler AA5 Series
Operator: Personal
Flight plan: None
Mission: Personal
Flight phase: Landing
Reporter organization: Personal
Reporter function: Single Pilot
Reporter qualification: Flight Crew Student
Human factors: Training / Qualification
Anomaly: Ground Event / Encounter Object; Ground Event / Encounter Loss Of Aircraft Control; Ground Excursion Runway
Detector: Person Flight Crew
When detected: In-flight
Result: Aircraft Aircraft Damaged
Contributing factors: Weather; Human Factors
Primary problem: Human Factors

Narrative: I was going to start that day practicing with some Touch and Go's then maneuvers. On my first attempt to land I was coming in for [landing] there was a light crosswind as provided by the AWOS. When flaring I slightly ballooned the plane and decided to do a Go around. On second attempt wind was at 6kts from 230. When on final for second attempt I lined up on centerline and proceeded toward my aiming point on the runway. I flared the plane and at the same time it started to drift to the right side of the runway. I then attempted to correct the drift but touched down at an angle and the plane headed to left edge of the runway. At this time I made the decision to attempt to get the plane between the runway lights as I did not feel that I could get it to stay on the runway safely. As I rolled through the space between the lights my left flap struck one of the light causing damage to the flap and some of the internal components. No damage to light.




Synopsis: Student pilot reported the loss of directional control on landing resulting in runway excursion and striking runway edge light.
Date: 201808
Local time of day: 0001-0600
Flight conditions: VMC
Light: Dawn
Aircraft: Regional Jet 200 ER/LR (CRJ200)
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Descent
Aircraft component: Electronic Flt Bag (EFB)
Component problem: Malfunctioning
Reporter organization: Air Carrier
Reporter function: Captain; Pilot Flying
Reporter qualification: Flight Crew Multiengine; Flight Crew Air Transport Pilot (ATP)
Anomaly: Aircraft Equipment Problem Less Severe; Deviation - Track / Heading All Types; Deviation / Discrepancy - Procedural Clearance
Detector: Person Flight Crew
When detected: In-flight
Result: Air Traffic Control Issued New Clearance; Flight Crew Requested ATC Assistance / Clarification; Flight Crew Returned To Clearance; Flight Crew Overcame Equipment Problem
Contributing factors: Aircraft; Human Factors
Primary problem: Aircraft

Narrative: On our morning flight we were only able to navigate by VOR. We were given a new clearance to fly direct to a specific VOR. While the FO was getting the clearance I tried to use my EFB to locate the VOR frequency. The FO was still getting the clearance and my Jeppesen App froze and then shut off. We were still navigating via the original clearance. The FO had trouble finding the VOR frequency so we asked ATC for vectors because my Jepp App was still loading after about a minute. We got a heading from ATC and flew the heading because my EFB failed and the FO had difficulty finding the frequency. We were in the approach area and I knew there was significantly more traffic around so we were trying to be as quick as possible. We didn't cause any traffic deviations. The cause of the event is that my EFB froze and the Jepp app shut down for no reason whatsoever. Also the FO was task saturated by talking to ATC and verifying the clearance and then having to find a VOR frequency quickly. The way to fix this problem is to get an EFB that won't have these problems.




Synopsis: CRJ-200 Captain reported an EFB malfunction while requsting essential navigation information.
Date: 201510
Local time of day: 1201-1800
Location: ZZZ.Airport, US
Flight conditions: VMC
Weather elements / visibility: 10
Light: Daylight
Aircraft: Cessna Stationair/Turbo Stationair 6
Operator: Personal
Operating under: Part 91
Flight plan: None
Mission: Personal
Flight phase: Takeoff / Launch
Airspace: Class G ZZZ
ATC / advisory: CTAF ZZZ; UNICOM ZZZ
Aircraft component: Nose Gear
Component problem: Improperly Operated
Reporter organization: Personal
Reporter function: Captain; Pilot Flying; Single Pilot
Reporter qualification: Flight Crew Instrument; Flight Crew Private
Human factors: Time Pressure; Situational Awareness; Distraction
Anomaly: Aircraft Equipment Problem Less Severe; Deviation / Discrepancy - Procedural Published Material / Policy
Detector: Person Observer
When detected: In-flight
Result: Flight Crew Returned To Departure Airport
Contributing factors: Human Factors; Environment - Non Weather Related; Procedure
Primary problem: Human Factors

Narrative: I had just completed an annual inspection of my aircraft and was preparing for a post annual test flight. I completed a preflight inspection in my hangar; installed a towbar; and located the aircraft on the taxiway. After the aircraft was positioned I removed the bar and returned it to my hangar and returned to the aircraft to complete the preflight. Upon return; I noticed a small patch of sand directly below the prop. Not wanting to sand blast my prop; I retrieved the towbar from the hangar; and attempted to move the aircraft. I was not able to relocate the aircraft using the bar and resorted to a push on the left strut which is adjacent to the pilot's door. Without thinking; I got in the plane; buckled the seat belt; started the engine; proceeded to the runway; completed an engine run up and launched with the bar in place. During climb; I received a radio call from unicom alerting me to the situation. I then remained in the pattern and returned to runway 15 where I was able to make a slow; nose high landing. I was extremely lucky and fortunate to survive the incident with NO DAMAGE to anything except my pride. I blame this event on rushing and a change in my normal routine of preflight; i.e. position the plane and stow the bar. In this event; one additional walk around would have prevented the issue. I plan to never let this happen again!




Synopsis: The pilot of a C206 re-engaged the tow bar after preflight inspection had been completed in order to reposition the aircraft. The pilot neglected to remove the tow bar and took off. A ground observer notified the pilot of the condition. The pilot was able to successfully land with no damage to the aircraft.
Date: 201411
Local time of day: 1201-1800
Location: ZZZ.TRACON, US
Flight conditions: VMC
Light: Daylight
Aircraft: B737-700
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Descent
Airspace: Class B ZZZ
ATC / advisory: TRACON ZZZ
Reporter organization: Air Carrier
Reporter function: Captain; Pilot Not Flying
Reporter qualification: Flight Crew Air Transport Pilot (ATP)
Human factors: Communication Breakdown
Second reporter function: Pilot Flying; First Officer
Anomaly: ATC Issue All Types; Deviation - Speed All Types; Ground Incursion Taxiway
Detector: Person Air Traffic Control
When detected: In-flight
Result: Air Traffic Control Issued New Clearance; Air Traffic Control Separated Traffic
Contributing factors: Human Factors; Procedure
Primary problem: Procedure

Narrative: On downwind for Runway XXL; Approach instructed us to slow from assigned 310 knots to 250 knots and descend from 14;000 feet to 7;000 feet and advised 'expect a short approach'.  The PF slowed to 250-240 knots and asked for flaps 5 to expedite the descent.  Shortly thereafter; we were given further descent to 3;000 feet and once again advised 'expect a short approach'.   Since we were still high; PF slowed to 200-210 knots and asked for flaps 10 to help get down quicker; thinking he was going to turn us on a base soon.  A couple of minutes later; ATC asked our speed and I told him 200 knots.  Another carrier's flight was closing from behind; and although minimum separation was never compromised; ATC gave us a 20 degree vector to the right to increase spacing.  The other carrier was re-assigned to Runway XY and we continued receiving vectors to XXL where we landed uneventfully; but just as we were exiting the runway the Tower gave us 'possible Pilot deviation notice from Approach Control; let me know when you're ready to copy a phone number'.   The Controller's comments about making a short approach several times led us to believe he wanted us to descend and slow for the approach rather than fly fast away from the airport.There is no specific speed assignment on this arrival; and nothing on the 10-7 page under 'Arrival' that mandates maintaining a certain speed.


Second narrative: The Controller's comments about making a short approach several times led us to believe he wanted us to descend and slow for the approach.


Synopsis: After being issued a speed restriction by ATC along with the advice; 'Expect short approach;' B737-700 flight crew slowed below assigned speed due to their high; in close position. ATC advised of a possible violation.
Date: 201705
Location: HNL.Airport, HI
Flight conditions: VMC
Light: Daylight
Aircraft: Widebody; Low Wing; 2 Turbojet Eng
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Descent
Airspace: Class B HNL
ATC / advisory: TRACON HCF
Reporter organization: Air Carrier
Reporter function: Captain; Pilot Flying
Reporter qualification: Flight Crew Air Transport Pilot (ATP)
Anomaly: Deviation / Discrepancy - Procedural Published Material / Policy
Detector: Person Flight Crew
When detected: In-flight
Result: General None Reported / Taken
Contributing factors: Chart Or Publication
Primary problem: Chart Or Publication

Narrative: While prepping for arrival and approach to Honolulu via the KAENA TWO RNAV and the ILS 8L; I noted the FMC showed crossing MAKOA 3700B 3400A. This agreed with the arrival chart but the ILS 8L chart shows MAKOA 3300.




Synopsis: Air carrier Captain reported the KAENA2 RNAV Arrival to ILS Runway 8L at HNL shows MAKOA to be crossed between 3;400 and 3;700 feet while the ILS 8L shows above 3;300 feet at MAKOA.
Date: 201909
Location: ZZZ.Tower, US
Light: Daylight
Aircraft: B737-800
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Climb; Cruise; Descent; Parked
Reporter organization: Air Carrier
Reporter function: Flight Attendant (On Duty)
Reporter qualification: Flight Attendant Current
Human factors: Physiological - Other
Anomaly: Aircraft Equipment Problem Less Severe; Deviation / Discrepancy - Procedural Published Material / Policy; Flight Deck / Cabin / Aircraft Event Illness / Injury; Flight Deck / Cabin / Aircraft Event Smoke / Fire / Fumes / Odor
Detector: Person Passenger; Person Flight Crew; Person Flight Attendant
When detected: In-flight
Result: Aircraft Equipment Problem Dissipated; Flight Crew Overcame Equipment Problem
Contributing factors: Aircraft
Primary problem: Aircraft

Narrative: This was a fume event. Immediately after takeoff there was a smell of rancid/dirty socks through the cabin; galley and the cockpit smelled it too. Odor stayed well past 10;000 feet and for an additional 15-20 minutes thereafter. The cabin crew experienced the same fumes all through the final phase of flight until we parked at the gate and opened up the doors. Some passengers asked for aspirin for headaches mid-flight and many were coughing throughout the flight. The flight attendants experienced burning throat and eyes; and scratchy eye symptoms. All 4 flight attendants had a funny feeling of floating/equilibrium issues exiting the aircraft in ZZZ1 while we walked through the airport terminal.




Synopsis: B737-800 Flight Attendant reported 'rancid/dirty socks' odor immediately after takeoff until parked at destination with periods of time when fumes dissipated but resumed later. Both flight attendants and passengers experienced health issues.
Date: 201706
Aircraft: Commercial Fixed Wing
Operator: Air Carrier
Reporter organization: Air Carrier
Reporter function: Flight Attendant (On Duty)
Reporter qualification: Flight Attendant Current
Human factors: Situational Awareness; Distraction; Communication Breakdown; Workload
Anomaly: Deviation / Discrepancy - Procedural FAR; Deviation / Discrepancy - Procedural Security; Flight Deck / Cabin / Aircraft Event Passenger Misconduct; Ground Event / Encounter Other / Unknown
Detector: Person Flight Attendant
When detected: In-flight
Result: Flight Crew Took Evasive Action; General Police / Security Involved
Contributing factors: Human Factors
Primary problem: Human Factors

Narrative: During initial beverage after takeoff; misconduct Passenger using excessive offensive vulgar language; showing extremely offensive; aggressive; belligerent; unstable and abnormal behavior towards multiple working crew members. Passenger using excessive vulgar language while I served him multiple beverages. After double check with him if there is anything I can get for him; I politely move on to next customers. He suddenly [started] getting extremely angry; unstable and aggressive. He was yelling in multiple vulgar language about the coffee doesn't have the 'thing'. I explain to him that I can't understand; He start severe yelling loudly and aggressively with unstable emotion; offensive and belligerent using vulgar language. He lost control. My flying partner and myself advise him to calm down but he continue the abnormal aggressive behavior. We report to Aft-purser and she told us [the] passenger have been very aggressive and verbal abusive using vulgar language towards her and other working flight attendants. That was even before we first meet him; and he was extremely unstable and showing abnormal behavior. The other Flight Attendant had already reported to the cockpit captain in regards and we were told to monitor his condition but not to response to his verbally abusive vulgar language and unstable abnormal behavior.




Synopsis: A Flight Attendant reported a verbally abusive and apparently emotional unstable passenger became belligerent and aggressive.
Date: 202112
Local time of day: 1201-1800
Location: SFO.Tower, CA
Flight conditions: VMC
Weather elements / visibility: 10
Aircraft: Commercial Fixed Wing
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Final Approach
Airspace: Class B SFO
ATC / advisory: Tower SFO
Second aircraft: UAV: Unpiloted Aerial Vehicle
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: Distraction
Second reporter function: Pilot Not Flying; First Officer
Anomaly: Airspace Violation All Types; Conflict Airborne Conflict; Deviation / Discrepancy - Procedural Unauthorized Flight Operations (UAS); Deviation / Discrepancy - Procedural Published Material / Policy; Deviation / Discrepancy - Procedural FAR; Inflight Event / Encounter Object
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: At the FAF on Runway 28R in SFO; the pilots noticed a small drone at our 2 o' clock position for about 1 or 2 seconds. The drone appeared black in color and had no lights. It was dark out and at first the pilots thought it was a bird but then determined it was man made. The aircraft lighting made us able to spot the drone on approach. Could not determine direction; speed or if hovering.


Second narrative: SFO 28L approach; just prior to sundown and descending through approx 1400 ft. AGL a black drone with no lights passed just outside the right wing. This was not a small toy UAV. We reported the sighting to Tower and landed.


Synopsis: B737 Flight Crew reported a UAS passed near the aircraft while on final approach into SFO.