elihoole/asrs-aviation-reports huggingface dataset:
Date: 202105
Local time of day: 1201-1800
Location: ZLA.ARTCC, CA
Aircraft: Commercial Fixed Wing
Operator: Air Taxi
Operating under: Part 121
Flight plan: IFR
Flight phase: Cruise
Reporter function: Enroute; Captain; Pilot Not Flying
Reporter qualification: Flight Crew Instrument; Flight Crew Air Transport Pilot (ATP); Flight Crew Multiengine
Anomaly: Deviation / Discrepancy - Procedural Published Material / Policy; Inflight Event / Encounter Other / Unknown
Detector: Person Flight Crew
When detected: In-flight
Result: Flight Crew Requested ATC Assistance / Clarification
Contributing factors: Airspace Structure; Procedure
Primary problem: Ambiguous

Narrative: After leveling off at cruise and completing the cruise checklist; my FO noticed approximately 10 skydivers in close proximity to us at an altitude roughly 1;000 feet above us. We were on our assigned routine from ZZZ-ZZZ1; specially on V186 around TANNR.  After noticing the jumpers he disconnected the autopilot and initially nosed down the airplane; but I instructed him to stay at altitude and the jumpers seemed to maneuver around us. We reported the jumpers to ATC and maintained physical separation until well clear. Suggest having them jump off airway.




Synopsis: Air carrier Captain reported encountering jumpers while in level cruise on V186 airway near TANNR Intersection.
Date: 202002
Local time of day: 0001-0600
Location: PHX.Tower, AZ
Flight conditions: VMC
Weather elements / visibility: Turbulence
Light: Dusk
Aircraft: Regional Jet 900 (CRJ900)
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Climb
Airspace: Class B PHX
ATC / advisory: Tower PHX
Second aircraft: A321
Reporter organization: Air Carrier
Reporter function: Captain; Pilot Flying
Reporter qualification: Flight Crew Air Transport Pilot (ATP); Flight Crew Instrument; Flight Crew Multiengine
Anomaly: Inflight Event / Encounter Wake Vortex Encounter
Detector: Person Flight Crew
When detected: In-flight
Result: General None Reported / Taken
Contributing factors: Procedure; Environment - Non Weather Related
Primary problem: Ambiguous

Narrative: PHX Tower cleared us for takeoff on Runway 7L; and maintain visual separation from a departing Airbus 321. The takeoff roll was normal and we lifted off without any problems. On climb out; after acceleration altitude; with the aircraft cleaned up and climbing on climb thrust; the aircraft was rocked by wake turbulence from the Airbus ahead of us. The aircraft rolled to the right; passed 45 degrees bank; then lurched back to the left 45 degrees. The aircraft stabilized after the wake encounter without loss of altitude or directional control; and we continued without any further incident.




Synopsis: CRJ900 Captain reported that wake turbulence from a departing aircraft resulted in a momentary loss of aircraft control.
Date: 201203
Local time of day: 1201-1800
Location: ZZZ.Airport, US
Flight conditions: VMC
Weather elements / visibility: 10
Light: Daylight
Aircraft: P180 Avanti
Operator: Fractional
Operating under: Part 91
Flight plan: IFR
Mission: Ferry / Re-Positioning
Flight phase: Taxi
ATC / advisory: Ground ZZZ
Aircraft component: Hydraulic Main System - Regulator
Component problem: Improperly Operated
Reporter organization: Fractional
Reporter function: First Officer; Pilot Not Flying
Reporter qualification: Flight Crew Air Transport Pilot (ATP); Flight Crew Instrument; Flight Crew Multiengine
Human factors: Training / Qualification; Confusion; Human-Machine Interface; Situational Awareness
Anomaly: Deviation / Discrepancy - Procedural Published Material / Policy; Ground Excursion Taxiway
Detector: Person Flight Crew
When detected: Taxi
Result: Flight Crew Took Evasive Action
Contributing factors: Aircraft; Chart Or Publication; Human Factors
Primary problem: Aircraft

Narrative: After an uneventful flight; we landed on Runway 12R and cleared the runway to the right. Given taxi instructions by Ground to cross the next perpendicular taxiway and turn right on the next one to the FBO. As we turned right onto the taxiway; I (pilot not flying) then ran the after landing checklist. We were advised of conflicting traffic departing the ramp; a King Air and helicopter. Neither one was a factor for us. As we approached the left turn into the ramp; our steering and brakes (both hydraulically actuated with a pump) did not work. The Captain tried to turn and slow the plane but it continued forward. I tried my brakes and; upon learning that they did not work; I immediately grabbed the condition levers and pulled them back to cutoff. Additionally I turned off the fuel shutoff valves. We rolled from the taxiway at a VERY slow rate of speed into the grass. The grass was dry and on the same level as the taxiway and there was no drop off from the edge of the taxiway. The speed was a slow walk and very gentle. Upon coming to a stop we put on the parking brake and finished securing the aircraft. There was no damage to the airplane or airport property. We were pulled out of the grass by the FBO. Upon further inspection; we confirmed that there was no damage to airport property or the airplane. We later determined that the Captain; the pilot flying; had inadvertently turned off the right bleed and hydraulic switch instead of the left and right bleeds. All three switches are identical and on the same level; right next to each other. Pilot flying will now ONLY worry about taxiing. He will call for all switches to be turned off by the pilot not flying.




Synopsis: A P180's left and right engine bleed are identical and located next to the Hydraulic switch; so a Captain closed a bleed and turned off the hydraulics which caused a loss of steering and brakes followed by a taxiway excursion as the aircraft came to a stop undamaged.
Date: 202110
Local time of day: 1201-1800
Location: ZZZ.Airport, US
Aircraft: A319
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Descent
Aircraft component: Engine Oil Seals
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: Troubleshooting; Physiological - Other
Anomaly: Aircraft Equipment Problem Less Severe; Flight Deck / Cabin / Aircraft Event Smoke / Fire / Fumes / Odor
Detector: Person Flight Attendant; Person Flight Crew
When detected: In-flight
Result: Flight Crew Overcame Equipment Problem; General Maintenance Action
Contributing factors: Human Factors; Aircraft
Primary problem: Aircraft

Narrative: During descent as power went back to idle aircraft filled with strong odor suspected to be fumes. Flight attendants showed symptoms of headaches; soar throats and Metallic taste.Lack of maintenance accountability for poor procedures and FAA overlook of them. Third fume event on the same aircraft in less than 30 days. Better and more accountable maintenance procedures [recommended].




Synopsis: Air Carrier First Officer reported a fume event during initial descent resulting in flight attendants experiencing physiological symptoms.
Date: 201812
Local time of day: 1801-2400
Location: ZZZ.Tower, US
Aircraft: EMB ERJ 170/175 ER/LR
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Flight phase: Final Approach
Airspace: Class C ZZZ
ATC / advisory: Tower ZZZ
Second aircraft: Amateur/Home Built/Experimental
Reporter organization: Government
Reporter function: Ground
Reporter qualification: Air Traffic Control Fully Certified
Human factors: Communication Breakdown; Confusion; Situational Awareness
Anomaly: ATC Issue All Types; Inflight Event / Encounter Weather / Turbulence
Detector: Person Air Traffic Control
When detected: In-flight
Result: Air Traffic Control Provided Assistance
Contributing factors: Human Factors
Primary problem: Human Factors

Narrative: I was working Ground Control so I wasn't directly involved with the coordination. Runway XX was in use; but the wind had shifted to approximately 300/12. The Flight Line Manager called TRACON to coordinate a runway change. What I overheard was that the arrival controller wasn't interested in a change at the moment and was going to continue to send aircraft to RWY XXL which is exactly what I observed over the next few minutes. Our Local Controller was holding a Cessna taildragger that was airborne and needed to land on RWY XYL due to the wind and sent the E75 around. The GLST was #2 on final for XXL and was able to land despite the tailwind.




Synopsis: Ground Controller reported when the Tower Manager wanted to switch runways; the Approach controller did not want to and ran more traffic in despite the tailwind.
Date: 202103
Local time of day: 1801-2400
Aircraft: A321
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Cruise
Airspace: Class A ZZZ
ATC / advisory: Center ZZZ
Aircraft component: Air Conditioning and Pressurization Pack
Component problem: Malfunctioning
Reporter organization: Air Carrier
Reporter function: Captain; Pilot Not Flying
Reporter qualification: Flight Crew Air Transport Pilot (ATP); Flight Crew Instrument; Flight Crew Multiengine
Human factors: Distraction; 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 cruise one of the flights attendants called me up and said they could smell something like burning paper around Row 33. No smoke was observed. As the flight attendants searched for the source of the smell; we started the smoke; fumes checklist in the QRH. The smell dissipated after 5 minutes and before any configuration changes were made in the flight deck. I decided to continue on since there were [no] indications of smoke anymore. There were no complaints or reports of any injuries to passengers or crew members. A smoke fumes report was filled and an AML entry of the event followed by a company report.No smoke was seen; only the odor of smoke smelt. The FA (Flight Attendant) said it was like burning paper. Before I completed our smoke checklist; the smell had completely dissipated.




Synopsis: A321 Captain reported a Flight Attendant notified them of burning fumes in the cabin which dissipated within five minutes. Flight continued to destination for an uneventful landing. Maintenance action was requested.
Date: 201302
Local time of day: 1201-1800
Location: ZZZ.Airport, US
Flight conditions: VMC
Weather elements / visibility: Snow; Icing
Light: Daylight
Aircraft: Skyhawk 172/Cutlass 172
Operator: Personal
Operating under: Part 91
Flight plan: None
Mission: Personal
Flight phase: Takeoff / Launch
Reporter organization: Personal
Reporter function: Single Pilot
Reporter qualification: Flight Crew Private
Human factors: Situational Awareness; Training / Qualification
Anomaly: Ground Event / Encounter Ground Strike - Aircraft; Ground Event / Encounter Loss Of Aircraft Control
Detector: Person Flight Crew
When detected: In-flight
Result: Aircraft Aircraft Damaged; General Evacuated
Contributing factors: Weather; Environment - Non Weather Related; Human Factors
Primary problem: Ambiguous

Narrative: I departed flying VFR on a pleasure flight with one of my daughters. We headed north to land on one of the several plowed ice roads. I have done this on earlier occasions as it is commonplace in the winter. I did a low pass over the road I selected that was away from people; ice houses; traffic; to allow for a landing into the wind (210 at 4 knots when I departed) and to check the condition of the road. I went back around in a normal left hand pattern and landed intending to do a touch and go. I configured the plane for a soft field takeoff; reapplied power and began accelerating. Shortly before rotating I ran over a bump in the road causing the plane to veer left slightly. I applied full right rudder; and attempted to rotate as I had reached 55-60 knots. At that point the left main wheel contacted the snow and pulled the plane to the left into the snow. It immediately slowed down and then nosed over onto its back. I shut off both masters; the mags; the fuel and pulled the throttle and mixture out after making sure my daughter was fine. We then exited the airplane. Having done landings like this before I was prepared for it and was focused on staying away from people and the traffic. In hindsight I believe there were other; wider roads that would have been a better option and would have led to a different outcome.




Synopsis: A C172 pilot lost control of his aircraft following a touch and go landing on an ice road when a wheel struck a snow bank and the aircraft flipped over on its back.
Date: 201905
Location: ZZZ.Airport, US
Aircraft: B737-800
Operator: Air Carrier
Operating under: Part 121
Mission: Passenger
Flight phase: Climb
Airspace: Class B ZZZ
Reporter organization: Air Carrier
Reporter function: Flight Attendant In Charge
Human factors: Physiological - Other; Situational Awareness
Second reporter function: Flight Attendant (On Duty)
Anomaly: Flight Deck / Cabin / Aircraft Event Illness / Injury; Flight Deck / Cabin / Aircraft Event Smoke / Fire / Fumes / Odor
Detector: Person Flight Attendant; Person Flight Crew; Person Passenger
When detected: In-flight
Result: Air Traffic Control Provided Assistance; Flight Crew Diverted; Flight Crew Landed As Precaution; Flight Crew Returned To Departure Airport; General Maintenance Action
Contributing factors: Environment - Non Weather Related; Aircraft; Human Factors
Primary problem: Aircraft

Narrative: Everything was fine until we took off and the entire plane started to smell like something was burning. The smell was extremely strong. I checked the lavatories and checked my surrounding areas; but there was no smoke or indications that something was on fire. The smell was a burning smell; ironically mixed with a scent of wet dog or pee. Flight Attendant #2 called Flight Attendant #1 to ask if she could come back to see if she smelt it but she confirmed it was smelling like that throughout the cabin.  I wasn't on the phone; but to my knowledge; the Captain over heard the conversation and said he was smelling the same. He originally said we were going to continue on our way to ZZZ1 but the smell never subsided. Not much longer; the Captain called and said we will be diverting back to ZZZ. I felt extremely nauseous when he prepared us for landing; but I didn't think much of it until I found myself sick in the restroom after we landed. I also felt very dizzy and my skin feels like it's on fire. Others on my crew felt symptoms as well.


Second narrative: After take-off; [Flight Attendant] #1 and I started smelling something foul. [Flight Attendant] #2 called the [Flight Attendant] #1 to see if all crew was smelling the same thing and the cockpit pitched in saying they were smelling something pungent as well. At first; the pilots wanted to continue on; but when the smell kept coming back; they decided to head back to ZZZ. [Flight Attendant]  #4 felt nauseous and threw up; [Flight Attendant] #1 had a headache; and the cockpit had a headache along with itchy and dry eyes. I felt nauseous and had a severe headache with heat flashes. As a team; we have decided to go to the ER to check ourselves out.


Synopsis: B737-800 flight attendants reported strong burning odor in passenger cabin resulting in health issues. Odor was reported to Captain who confirmed the odor and stated they were returning to departure airport.
Date: 201905
Local time of day: 1201-1800
Location: PDX.Airport, OR
Flight conditions: VMC
Aircraft: B737 Undifferentiated or Other Model
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Final Approach
Airspace: Class C PDX
ATC / advisory: Tower PDX
Second aircraft: Any Unknown or Unlisted Aircraft Manufacturer
Reporter organization: Air Carrier
Reporter function: First Officer; Pilot Flying
Reporter qualification: Flight Crew Air Transport Pilot (ATP); Flight Crew Multiengine; Flight Crew Instrument
Human factors: Distraction; Situational Awareness
Anomaly: ATC Issue All Types; Conflict Airborne Conflict; Deviation / Discrepancy - Procedural Published Material / Policy
Detector: Automation Aircraft TA; Person Air Traffic Control; Person Flight Crew
When detected: In-flight
Result: General None Reported / Taken
Contributing factors: Airspace Structure
Primary problem: Airspace Structure

Narrative: On approach to Runway 10L at PDX; Tower advised of traffic in the pattern at Pearson Field (VUO). This airport is directly in line with the approach path of 10L. On final; TCAS gave out three TA warnings.




Synopsis: B737 First Officer reported three TA alerts while on approach to Runway 10L at PDX due to pattern work at VUO.
Date: 201901
Local time of day: 1801-2400
Location: ZBW.ARTCC, NH
Aircraft: Embraer Undifferentiated or Other Model
Operator: Air Carrier
Flight plan: IFR
Mission: Passenger
Flight phase: Descent
ATC / advisory: Center ZBW
Second aircraft: Any Unknown or Unlisted Aircraft Manufacturer
Reporter organization: Government
Reporter function: Approach
Reporter qualification: Air Traffic Control Fully Certified
Human factors: Distraction; Situational Awareness
Anomaly: ATC Issue All Types; Conflict Airborne Conflict; Deviation / Discrepancy - Procedural Published Material / Policy
Detector: Person Air Traffic Control
When detected: In-flight
Contributing factors: Human Factors
Primary problem: Human Factors

Narrative: Aircraft X was issued a vector to descend to meet the ZUL LOA altitude with an opposite direction departure off of YOW. After issuing the vector and descent at the same time (15L and descent) I continued to work at the south side of the airspace. When I looked up to rescan to the north it was too late to take any further action. I was also distracted internally with the lingering thoughts of the government shutdown and the added stresses of not receiving a paycheck this week. Between the added thoughts in my head with the busy traffic scenario as well as the conversations going on around the building and area; there was numerous factors. More staffing; Less CIC time; less government shutdown.




Synopsis: Boston Center Controller reported an unsafe operation relating to an opposite direction operation; and being distracted by the government shutdown.
Date: 201706
Local time of day: 1801-2400
Location: LVK.Airport, CA
Flight conditions: VMC
Light: Daylight
Aircraft: Champion Citabria Undifferentiated
Operator: Personal
Operating under: Part 91
Flight plan: None
Mission: Training
Flight phase: Final Approach
Airspace: Class D LVK
ATC / advisory: Tower LVK
Second aircraft: Cessna 150
Reporter organization: Personal
Reporter function: Pilot Flying; Trainee
Reporter qualification: Flight Crew Instrument; Flight Crew Private
Human factors: Situational Awareness
Anomaly: Conflict NMAC
Detector: Person Flight Crew
When detected: In-flight
Result: General None Reported / Taken
Contributing factors: Airport; Human Factors
Primary problem: Human Factors

Narrative: Parallel runways. I was cleared for the option right traffic for 25R. Cessna 150 for left traffic for 25L; over shot their base to final turn and came close to the final approach path for 25R.




Synopsis: Citabria pilot landing Runway 25R experienced a NMAC with a C150 landing Runway 25L that overshot the base to final turn at LVK.
Date: 201604
Local time of day: 0601-1200
Location: ZZZ.Airport, US
Flight conditions: Mixed
Weather elements / visibility: Rain; 7
Light: Daylight
Aircraft: SR22
Operator: Personal
Operating under: Part 91
Flight plan: IFR
Mission: Personal
Flight phase: Climb
Airspace: Class E ZZZ
ATC / advisory: TRACON ZZZ
Reporter organization: Personal
Reporter function: Captain; Pilot Flying
Reporter qualification: Flight Crew Multiengine; Flight Crew Air Transport Pilot (ATP); Flight Crew Flight Instructor
Human factors: Troubleshooting
Anomaly: Aircraft Equipment Problem Less Severe; Deviation / Discrepancy - Procedural Maintenance
Detector: Person Flight Crew
When detected: In-flight
Result: Air Traffic Control Provided Assistance; Flight Crew Returned To Departure Airport; General Flight Cancelled / Delayed; General Maintenance Action
Contributing factors: Aircraft
Primary problem: Aircraft

Narrative: Post maintenance (post annual) flight to check condition of aircraft. Upon initial climb out IFR in a left turn direct; my aircraft was receiving high engine oil temperature warnings on the Crew Alert System. Sitting right seat was an A&P who conducted the annual inspection of the aircraft. Oil temperature kept climbing to about 245F and my A&P and I both agreed that we should cut short the flight and return to base. At that time I requested a return and vectors for the RNAV runway 35. I was asked if I was declaring an emergency and I said that I was not but would like expedited vectors because I was starting to get concerned if the oil temperature went much higher; I would have an engine failure and thus a true emergency. After receiving vectors and a descent I got into VMC conditions (below the cloud deck) and cancelled IFR. At that time ATC informed me that they were [giving priority handling to me]. At this point I had the airport in visual contact and conducted a visual approach to runway 35. I was handed off to the airport tower and the rest of the flight was uneventful. My maintenance shop is currently troubleshooting and addressing the issue. No known cause yet as to what caused the high engine oil temperature but cylinders number 3 and number 4 were replaced during the annual inspection a week prior to the test flight. There was nothing additional I felt could be done to prevent this from happening as the whole point of the flight was to detect any issues post-maintenance that needed to be addressed.




Synopsis: The pilot of a Cirrus SR22T elected to return to the departure airport due to high engine oil temperature.
Date: 201601
Local time of day: 1201-1800
Location: SFO.Airport, CA
Light: Daylight
Aircraft: Light Transport; Low Wing; 2 Turbojet Eng
Operator: Fractional
Operating under: Part 91
Flight plan: IFR
Mission: Passenger
Flight phase: Taxi
ATC / advisory: Tower SFO
Aircraft component: Air/Ground Communication
Component problem: Design
Reporter organization: Government
Reporter function: Local
Reporter qualification: Air Traffic Control Fully Certified
Human factors: Time Pressure; Distraction; Communication Breakdown; Workload
Anomaly: ATC Issue All Types; Ground Event / Encounter Other / Unknown
Detector: Person Air Traffic Control
When detected: Taxi
Result: Air Traffic Control Issued Advisory / Alert; Flight Crew Became Reoriented
Contributing factors: ATC Equipment / Nav Facility / Buildings; Procedure
Primary problem: ATC Equipment / Nav Facility / Buildings

Narrative: Aircraft X was instructed to LUAW (Line Up and Wait) on RWY 10L. The crew acknowledged the instruction. The flight was then cleared for takeoff on RWY 10L. There was no acknowledgement and the aircraft didn't move. The instruction was issued again and again no response. Flight was then told to cancel takeoff clearance and hold in position. There was no response. We switched to the Standby Transmitter and told the crew to hold in position and ask how they heard and they reported loud and clear. There is a frequency dead zone on RWY 10L and portions of TWY S2 [and] S for aircraft of a certain height (Learjets; Challengers; Citations; etc.) where they are unable to receive the main transmitter for either LC or GC frequencies. This is a recurring problem at SFO. Move the main transmitters so that all aircraft receive the frequency at all points of the airfield. Especially on active runways.




Synopsis: SFO Local Controller reported that certain aircraft which taxi low to the ground have difficulty receiving transmissions in a Runway 10L dead zone along portions of Taxiways S and S2. Antenna location seems to be the problem.