elihoole/asrs-aviation-reports huggingface dataset:
Date: 201409
Local time of day: 1201-1800
Location: CN13.Airport, CA
Flight conditions: VMC
Light: Daylight
Aircraft: Amateur/Home Built/Experimental
Operator: Personal
Flight plan: None
Mission: Personal
Flight phase: Landing
Reporter organization: Personal
Reporter function: Pilot Flying; Single Pilot
Reporter qualification: Flight Crew Instrument
Anomaly: Deviation - Speed All Types; Inflight Event / Encounter Loss Of Aircraft Control; Inflight Event / Encounter Object
Detector: Person Flight Crew
When detected: In-flight
Result: Aircraft Aircraft Damaged; General Evacuated
Contributing factors: Airport; Human Factors
Primary problem: Airport

Narrative: I landed into the wind with too much speed on a grass runway and attempted a go-around.  On climb-out; at about 6 feet AGL; the plane collided with an unseen; free standing; three inch diameter; 6'6'  high; steel; vertical pipe at the end of the runway. The S7S lost directional control and made contact with a tree.  The aircraft landed upright and was heavily damaged.  There were no injuries to my passenger or me.




Synopsis: The pilot of a homebuilt S7S aborted his landing on a grass runway due to excessive speed.  During the subsequent attempt to go around the aircraft struck a steel pipe and a tree.  Although there were no injuries to himself or his passenger the aircraft was badly damaged.
Date: 202104
Local time of day: 0601-1200
Location: JYO.Airport, VA
Flight conditions: VMC
Light: Daylight
Aircraft: Small Aircraft
Operator: FBO
Operating under: Part 91
Mission: Training
Flight phase: Initial Approach
Airspace: Class D JYO
ATC / advisory: Tower JYO
Second aircraft: Small Aircraft
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: Communication Breakdown
Anomaly: Conflict NMAC
Detector: Automation Aircraft Other Automation; Person Flight Crew
When detected: In-flight
Result: General None Reported / Taken
Contributing factors: Human Factors
Primary problem: Human Factors

Narrative: We were doing pattern operations at Leesburg with a student. We were on the left downwind for Runway 17 at Leesburg. It was busy with at least one other in the pattern and several aircraft waiting for takeoff and I believe two aircraft approaching for landing. About midfield I noticed on my portable ADS-B indicating an aircraft adjacent to us. Looking to the left there was an aircraft passing on our left just below and to our left. We were completely surprised by this. As far as I could tell the aircraft was doing a left downwind departure to the north which was unusual at Leesburg. I do not know if the aircraft had visual contact with us. Doubtful as we were in his blindspot. Most departures from 17 do a right hand departure to exit the pattern expeditiously. I heard nothing from the Tower that approved this and there was no warning from the Tower of the oncoming traffic. I confirmed with a fellow CFI in the pattern that I hadn't missed a call. The other CFI was about a half mile on downwind and witnessed the near collision. I called the Tower about the traffic and was just told he was departing to the North.




Synopsis: GA pilot reported an NMAC during initial approach to JYO airport.
Date: 201904
Local time of day: 0001-0600
Location: ZZZ.Airport, US
Flight conditions: VMC
Light: Daylight
Aircraft: Regional Jet 200 ER/LR (CRJ200)
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Climb; Initial Climb
Airspace: Class B ZZZ
ATC / advisory: TRACON ZZZ
Aircraft component: Oil Pressure Indication
Component problem: Malfunctioning
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: Time Pressure; Workload
Anomaly: Aircraft Equipment Problem Critical; Deviation / Discrepancy - Procedural Weight And Balance
Detector: Automation Aircraft Other Automation; Person Flight Crew
When detected: In-flight
Result: Air Traffic Control Provided Assistance; Flight Crew FLC complied w / Automation / Advisory; Flight Crew Landed As Precaution; Flight Crew Returned To Departure Airport; Flight Crew Requested ATC Assistance / Clarification
Contributing factors: Aircraft
Primary problem: Aircraft

Narrative: At approximately 500 feet AGL after departure; we received an 'R ENG Oil Press' Master Warning message just as we were being handed off to departure. The CA (Captain) immediately jumped into the QRC while I checked in with Departure requesting delaying vectors while we worked through the checklist. Once the checklist was accomplished (which directed us to keep the Right throttle at idle) the CA requested a return to ZZZ. No Emergency; as we still had the throttle available to us if needed and were already receiving the level of support needed by ATC. We exchanged controls just as we were intercepting the course to ILS final to Runway 34R. Touchdown was firm at approximately 300 FPM at approximately 51;000 pounds (4;000 pounds above max landing weight). We returned to gate uneventfully and the passengers were re-booked on another flight.Cause of the event was a 'R ENG Oil Press' Master Warning with oil pressure approximately 38 psi and a need to land before something worse happened to the engine.We did what we felt was the only safe option: get it down safely before something worse happened. Delaying our arrival to burn down fuel and decrease our landing weight would have exposed us to unnecessary risk; as this would have taken approximately one hour to accomplish. I believe this was the right course of action given the proximity of a long runway; the indications we were receiving and the weather in the area.




Synopsis: CRJ-200 pilot reported returning to departure airport after a 'R ENG Oil' pressure warning indication.
Date: 201705
Local time of day: 1201-1800
Location: OAK.Airport, CA
Flight conditions: VMC
Weather elements / visibility: 10
Light: Daylight
Aircraft: Bombardier Learjet Undifferentiated or Other Model
Operator: Personal
Operating under: Part 91
Flight plan: IFR
Mission: Personal
Flight phase: Initial Climb
Airspace: Class B SFO
ATC / advisory: TRACON NCT
Reporter organization: Personal
Reporter function: Captain; Pilot Flying
Reporter qualification: Flight Crew Air Transport Pilot (ATP); Flight Crew Multiengine; Flight Crew Flight Engineer; Flight Crew Flight Instructor; Flight Crew Instrument
Second reporter function: Pilot Not Flying; First Officer
Anomaly: Deviation - Altitude Overshoot; Deviation - Track / Heading All Types; Deviation / Discrepancy - Procedural Clearance
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: Departed OAK on an IFR flight plan which included the Skyline Six departure procedure. My First Officer was a low time pilot with 500 hrs total time and 125 hrs in the Learjet. He read the departure procedure to me which was fly heading 278 to 3;000 then left heading 200 to intercept the 135 radial from PYE. He failed to read the departure route description which was to climb on heading 278 vectors to PYE 135; cross 4 DME northwest of OAK at or below 2;000 and above 1;400. I did not verify the routing on my iPad and assumed what he told me was correct. After turning to 200 at 3;000 feet; ATC shortly thereafter vectored me back to heading 270. We were then vectored and assigned higher altitudes. We were assigned FL190 and then ATC said we needed to copy a phone number for NORCAL. In the process of copying the phone number we flew through FL190 by about 1;500 feet.Several factors contributed to these deviations:1. It was a long day and by the time we departed OAK we had been up for 12 hours. I discovered that my First Officer did not get any sleep the night before.2. My First Officer is very inexperienced and has not had much instrument procedure time other than what he received to get his ratings.3. Captain failed to verify departure procedure with FO.4. Captain tried to multi-task by flying the airplane and copying a phone number from ATC.5. Captain failed to use appropriate automation to lighten the work load i.e. Altitude Capture feature of the autopilot.I feel fatigue; an inexperienced FO; not verifying departure procedure with FO; and not using auto flight features of the Learjet all contributed to these deviations. To correct some situations; I feel it is necessary to fly a high performance aircraft with a more experienced crew member. Use Crew Resource Management techniques to verify that both crew members are in agreement with procedures and to use aircraft automation to lighten the work load in high workload environments.


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


Synopsis: Learjet flight crew reported a heading deviation on the SKYLINE 6 Departure from OAK.
Date: 201901
Local time of day: 1201-1800
Location: SEA.Airport, WA
Flight conditions: VMC
Light: Daylight
Aircraft: B737-800
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Descent
Airspace: Class B SEA
ATC / advisory: TRACON S46
Second aircraft: Medium Large Transport
Reporter organization: Government
Reporter function: Approach
Reporter qualification: Air Traffic Control Fully Certified
Human factors: Situational Awareness; Distraction
Anomaly: Conflict Airborne Conflict; Deviation / Discrepancy - Procedural Published Material / Policy
Detector: Person Air Traffic Control
When detected: In-flight
Result: Air Traffic Control Separated Traffic; Air Traffic Control Issued New Clearance
Contributing factors: Human Factors
Primary problem: Human Factors

Narrative: On final with strong northwest winds. Vectored Aircraft X from NW descended to 4000. I was vectoring Aircraft Y from east side to go behind to set up a stagger. When Aircraft X was at 5300 feet and Aircraft Y was at 064 feet. I gave Aircraft X 4000 again; then descended Aircraft Y to 5000. I thought I would have 1000 feet easily with the way aircraft were descending that day. Unfortunately; I had to give Aircraft X a speed reduction which I assume is why he leveled at 5000 and descended very slowly; while Aircraft Y descended quickly. I lost my 3 miles/1000feet. Then Aircraft X did not join the localizer as instructed. Aircraft X read the instruction to join back. I then broke out Aircraft Y and called traffic. I would also like to mention that I got about 5 hours of sleep that night and the night before. The questionnaire asks how many hours I try to get; which is 8. But how much I actually get is usually between 5 and 6.Also; before I took position; the supervisor handed me a paper with a name and number; my bank called about my mortgage. I was trying to figure out how to delay a payment because we had been furloughed and unpaid for 34 days or so; so I was distracted by that a little; because I was worried about what I was going to do since I was unpaid.I misapplied the altitude leaving rule. I didn't visually observe Aircraft X leaving 5000 before I gave Aircraft Y lower. I pressured myself into descending Aircraft Y so he wouldn't be high on the approach; since it was IFR. I should have based Aircraft Y a little later; and held altitude longer to guarantee I could use altitude leaving.




Synopsis: Seattle TRACON Controller reported a loss of separation due to a rule being misapplied as well as possible fatigue and distraction by the government furlough.
Date: 202106
Local time of day: 0601-1200
Location: ZZZ.Airport, US
Flight conditions: VMC
Aircraft: B777 Undifferentiated or Other Model
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Climb
Airspace: Class B ZZZ
ATC / advisory: TRACON ZZZ
Aircraft component: Toilet Furnishing
Component problem: Malfunctioning
Reporter organization: Air Carrier
Reporter function: Pilot Not Flying; Captain
Reporter qualification: Flight Crew Multiengine; Flight Crew Air Transport Pilot (ATP); Flight Crew Instrument
Human factors: Troubleshooting
Anomaly: Aircraft Equipment Problem Less Severe; Deviation / Discrepancy - Procedural Published Material / Policy; Flight Deck / Cabin / Aircraft Event Smoke / Fire / Fumes / Odor
Detector: Person Flight Attendant; Person Flight Crew
When detected: In-flight
Result: Aircraft Equipment Problem Dissipated; Flight Crew Overcame Equipment Problem; General Maintenance Action
Contributing factors: Aircraft
Primary problem: Aircraft

Narrative: During our flight from ZZZ to ZZZ1; Aircraft X; a flight attendant seated near the 4L lavatory reported that about 3 minutes after take off he began to notice a urine smell coming from the 4L lav.  The smell began to dissipate about 15 minutes later.  We suspected a contributing factor could be the high deck angle associated with the take off.  This has been a continuing write up for a few weeks.  Unfortunately maintenance personnel have been unable to identify and fix the exact cause.  Hopefully this report will help bring together the appropriate resources to fix this problem.  Our passengers and flight attendants will appreciate it.




Synopsis: B777 Captain reported urine odor emanating from the aft lavatory during initial climb which lasted for approximately 15 minutes.
Date: 201601
Local time of day: 1801-2400
Location: ZZZZ.ARTCC, FO
Light: Night
Aircraft: B777 Undifferentiated or Other Model
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Cruise
ATC / advisory: Center ZZZZ
Reporter organization: Air Carrier
Reporter function: Flight Attendant (On Duty)
Reporter qualification: Flight Attendant Current
Human factors: Other / Unknown
Anomaly: Flight Deck / Cabin / Aircraft Event Illness / Injury; Inflight Event / Encounter Weather / Turbulence
Detector: Person Flight Attendant
When detected: In-flight
Result: General Physical Injury / Incapacitation
Contributing factors: Aircraft; Weather
Primary problem: Weather

Narrative: We experience severe turbulence unexpected in flight and cabin crews in main cabin were thrown around and 2 or 3 were actually hurt during the incident. Captain called back to advised to put carts away; but at that point it was too late for everyone. I was able to bring my cart back to the galley; but not everyone was able. Other crew members [saw a] cart on the floor flipped and crew members on the floor trying to hold on to anything they could since the flight was full and we did not have enough jumpseats in the back for every flight attendant to take one.




Synopsis: B777 Flight Attendant reported the flight encountered unreported severe turbulence and several flight attendants were hurt. Flight Attendant noted there were not enough jumpseats in the back for all flight attendants.
Date: 201905
Local time of day: 1201-1800
Location: ROA.Airport, VA
Flight conditions: VMC
Light: Daylight
Aircraft: EMB ERJ 145 ER/LR
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Initial Approach
ATC / advisory: Tower ROA
Reporter organization: Air Carrier
Reporter function: First Officer; Pilot Not Flying
Reporter qualification: Flight Crew Instrument; Flight Crew Air Transport Pilot (ATP); Flight Crew Multiengine
Human factors: Training / Qualification
Anomaly: Deviation / Discrepancy - Procedural Published Material / Policy; Inflight Event / Encounter CFTT / CFIT; Inflight Event / Encounter Unstabilized Approach
Detector: Automation Aircraft Terrain Warning; Person Flight Crew
When detected: In-flight
Result: Flight Crew Executed Go Around / Missed Approach; Flight Crew Took Evasive Action
Contributing factors: Human Factors
Primary problem: Human Factors

Narrative: Encountered GPWS (Ground Proximity Warning System) warning while on approach into ROA which resulted in go around. GPWS warning and voice saying too low terrain. Possible close proximity to terrain. Added power and leveled pitch which resulted in getting above the approach path in VMC conditions and resulted in go around. On the visual approach into ROA using 24 ask if winds allow use Runway 34 or the terrain mapping feature up.




Synopsis: EMB-145 flight crew encountered terrain warning on final approach to ROA.
Date: 201908
Local time of day: 1201-1800
Location: ZZZ.Airport, US
Flight conditions: VMC
Light: Daylight
Aircraft: PA-28 Cherokee/Archer/Dakota/Pillan/Warrior
Operator: Personal
Operating under: Part 91
Flight plan: IFR
Mission: Training
Flight phase: Initial Climb
Airspace: Class D ZZZ
ATC / advisory: Tower ZZZ
Aircraft component: Reciprocating Engine Assembly
Component problem: Failed
Reporter organization: Personal
Reporter function: Instructor; Pilot Not Flying
Reporter qualification: Flight Crew Private; Flight Crew Flight Instructor
Human factors: Troubleshooting; Workload
Anomaly: Aircraft Equipment Problem Critical
Detector: Person Flight Crew
When detected: In-flight
Result: Air Traffic Control Provided Assistance; Flight Crew Returned To Departure Airport; Flight Crew Requested ATC Assistance / Clarification; Flight Crew Landed in Emergency Condition
Contributing factors: Aircraft
Primary problem: Aircraft

Narrative: I was performing a training flight under an IFR flight plan with my student.We were taking off Runway XXR at ZZZ all engine instruments were in the green; after 100 ft. we start to feel roughness. I took the controls from the student and initiated a right turn to make it to Runway XY. During the turn I was able to climb and maintain close to 200 ft. I then decided to land on any suitable runway at that time. We eventually landed on the midsection of Runway XXR; close to the XX taxiway. After landing and exiting the runway to Taxiway XX; I tried to start the engine to taxi back to the ramp; but wasn't able to so I contacted Ground Control and Maintenance towed the aircraft to the ramp.During the entire event and us being at a very low altitude; we did not monitor the engine parameters as we were focused on landing the aircraft safely.




Synopsis: PA-28 Instructor reported engine failure on departure during a training flight.
Date: 201307
Local time of day: 0601-1200
Location: ATL.Airport, GA
Light: Daylight
Aircraft: Regional Jet 700 ER/LR (CRJ700)
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Ferry / Re-Positioning
Flight phase: Initial Approach
Airspace: Class B ATL
ATC / advisory: Tower ATL
Reporter organization: Air Carrier
Reporter function: Captain; Pilot Flying
Reporter qualification: Flight Crew Air Transport Pilot (ATP)
Human factors: Other / Unknown
Anomaly: ATC Issue All Types
Detector: Automation Air Traffic Control; Person Air Traffic Control
Result: Air Traffic Control Issued New Clearance
Contributing factors: ATC Equipment / Nav Facility / Buildings
Primary problem: ATC Equipment / Nav Facility / Buildings

Narrative: On the ILS PRM 9R; approximately at BURNY; Final Monitor called stating something to the effect of '[Air Carrier X]; I show you right of course; return to the LOC immediately.'  We were coupled to the AP. I looked up and confirmed on both left and right LOC that we were dead center on the LOC. Also; we had the runway in sight at this point and visually; we were right on centerline with 9R. The First Officer replied stating that we indicated we were on the LOC center. The Monitor then replied something to the effect of 'I had a RADAR error; my apologies; continue.' We then continued without issue.  Cause; this is something that I haven't seen or heard of before. Fortunately; we were VMC to where we could confirm our location. Because we could see both the runway and traffic to our left and right on parallel approaches; we did not make a left turn. I'm not sure what caused this brief confusion; but I thought it would be worth noting in a report.




Synopsis: Air Carrier on ILS PRM 9R to ATL was questioned by ATC as to LOC tracking; the flight crew confirmed both via instruments and visually 'on course'; Controller acknowledged ATC equipment faults.
Date: 201910
Local time of day: 1201-1800
Location: FTW.Tower, TX
Flight conditions: VMC
Weather elements / visibility: 10
Light: Daylight
Aircraft: Small Aircraft; Low Wing; 1 Eng; Fixed Gear
Operator: Personal
Operating under: Part 91
Flight plan: VFR
Mission: Training
Flight phase: Landing
Airspace: Class D FTW
ATC / advisory: Tower FTW
Second aircraft: UAV - Unpiloted Aerial Vehicle
Reporter organization: Personal
Reporter function: Pilot Flying
Reporter qualification: Flight Crew Instrument; Flight Crew Flight Instructor
Anomaly: Conflict NMAC; Inflight Event / Encounter Object
Detector: Person Flight Crew
When detected: In-flight
Result: Flight Crew Requested ATC Assistance / Clarification
Contributing factors: Aircraft; Human Factors
Primary problem: Human Factors

Narrative: My student and I were practicing landings. While in the downwind of the traffic pattern for Runway 17 at FTW we flew past a drone. We did not have to take evasive action. The drone was approximately 100 ft. away from our wing. The drone appeared to be orange-red in color and was about the size of a forearm. We made the report to tower shortly after seeing the drone. During our next lap in the traffic pattern we looked for the drone again; but we were unable to find it.




Synopsis: Flight Instructor reported a near mid-air collision in the traffic pattern with a drone.