elihoole/asrs-aviation-reports huggingface dataset:
Date: 202110
Local time of day: 0601-1200
Location: IMS.Airport, IN
Flight conditions: VMC
Weather elements / visibility: Haze / Smoke
Light: Daylight
Aircraft: Small Aircraft
Operator: FBO
Operating under: Part 91
Mission: Training
Flight phase: Cruise
Airspace: Class E LOU
Second aircraft: Small Aircraft
Reporter function: Instructor
Reporter qualification: Flight Crew Flight Instructor; Flight Crew Instrument; Flight Crew Multiengine; Flight Crew Commercial
Human factors: Communication Breakdown; Other / Unknown; Situational Awareness
Anomaly: Conflict NMAC; Inflight Event / Encounter Bird / Animal
Detector: Person Flight Crew
When detected: In-flight
Result: Flight Crew Took Evasive Action
Contributing factors: Environment - Non Weather Related; Human Factors
Primary problem: Human Factors

Narrative: Climbing from ZZZ; birds passed overhead; leaving droppings on our windscreen. Once in level flight about 15 miles SSW of IMS; we noticed Aircraft Y in the distance; seemingly well above us (we were at 2;300-2;400 feet MSL). Because of a combination of hazy conditions and the bird droppings on our windshield; we lost sight of Aircraft Y; when we noticed it; it was less than a mile from us; 100-200 feet above us; traveling opposite direction. We nosed over and to the right in an evasive maneuver as Aircraft Y passed over us.In that situation; we could have stayed in the pattern at ZZZ; returning to clean the windshield before commencing our training flight to IMS. The student and I reacted appropriately once we realized the potential accident developing; but if we had been able to maintain visual on the opposing aircraft; we could have maneuvered to evade much sooner. The student and I will revisit the FAA Safety Team literature/presentations on aircraft safety in flight and VFR collisions in 'practice areas' (as we were crossing the ZZZ/IMS/LOU practice area when the near-miss occurred).




Synopsis: GA Flight Instructor with student reported an NMAC with an aircraft traveling in opposite direction near IMS airport.
Date: 202107
Local time of day: 0601-1200
Location: ZKC.ARTCC, KS
Flight conditions: VMC
Weather elements / visibility: 100
Light: Daylight
Aircraft: Commercial Fixed Wing
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Cruise
Airspace: Class A ZKC
ATC / advisory: Center ZKC
Reporter organization: Air Carrier
Reporter function: First Officer
Reporter qualification: Flight Crew Air Transport Pilot (ATP); Flight Crew Multiengine; Flight Crew Instrument
Human factors: Distraction
Anomaly: Conflict Airborne Conflict; Deviation / Discrepancy - Procedural Published Material / Policy
Detector: Person Flight Crew
When detected: In-flight
Result: Flight Crew Requested ATC Assistance / Clarification
Contributing factors: Equipment / Tooling; Human Factors
Primary problem: Equipment / Tooling

Narrative: All of a sudden; the Captain stopped mid-sentence and said; 'Look at that!'  He pointed to the 1:00 right position; and we passed by a large; round; unknown object to the right at our altitude.  Based on the speed of passing; it seemed to be stationary.  It was large (much larger than a Mylar balloon); dark gray and silver/shiny; stripes (stripes of its form/shape) from top to bottom.  It seemed to have a pinch point at the bottom.  I didn't see anything attached; but the Captain said he saw a rope or something dangling behind it.  Soon after our shock; ATC gave us a handoff and we reported the object.  He was unaware of its presence. I reached out to the [nearby]  pilots to see if anyone knew anything.  One pilot responded: 'We got a message from our chief pilot this morning - balloon off SWO 100 radial 12.4nm & tethered balloon by Company.' The message the pilots in SWO received correlates with the location of our event.  I've never known of a tethered balloon at 32;000 feet.  Makes one wonder if this balloon got loose; especially given the rope the Captain saw.  If so; shouldn't ATC have been notified?  A bit more right today; and I may not have been able to write this report; along with the more than 200 people we had onboard.




Synopsis: An Air Carrier pilot reported a close encounter with an unidentified object which the reporter researched and believed it may have been an untethered balloon.
Date: 201709
Local time of day: 1201-1800
Location: ZZZ.Airport, US
Light: Daylight
Aircraft: Q400
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Climb
Airspace: Class A ZZZ
ATC / advisory: Center ZZZ
Aircraft component: Pressurization System
Component problem: Malfunctioning
Reporter organization: Air Carrier
Reporter function: Captain; Pilot Not Flying
Reporter qualification: Flight Crew Air Transport Pilot (ATP)
Second reporter function: First Officer; Pilot Flying
Anomaly: Aircraft Equipment Problem Less Severe; Deviation / Discrepancy - Procedural Published Material / Policy
Detector: Automation Aircraft Other Automation; Person Flight Crew
When detected: In-flight
Result: Air Traffic Control Provided Assistance; Flight Crew Requested ATC Assistance / Clarification; Flight Crew Overcame Equipment Problem
Contributing factors: Aircraft
Primary problem: Aircraft

Narrative: We departed ZZZ with all operations normal. As we continued our climb we had a master warning CABIN PRESS at FL230 and leveled off at FL232. We verified the cabin altitude which read 10;000 and decided to don our masks. We notified ATC immediately that we needed a descent to 10;000 so we started down. We pulled out the immediate action card checklist and the checklist stated is the aircraft above FL180 or is rapid descent required; we had a discussion that our cabin was partially pressurized and slowly changing and our flight attendants and passengers had already started a service so a rapid descent would have had a high risk for injury; so we continued a descent at 2000 fpm. We divided up tasks and one person flew and talked with ATC while the other ran checklists and spoke with maintenance; dispatch; and the flight attendants (we verified if any doors were squealing and if anything was abnormal they said everything was fine). We continued our descent and ran the pressurization fail checklist; which did not allow us to pressurize the aircraft. As we passed through 15;000 ft we decided to take our masks off to continue our checklist and verified that the cabin altitude only reached a max altitude of 12;500. We finished with the unpressurized flight checklist and continued our flight at 10;000 ft with normal operations.Every passenger received a comment card which they were not notified of the situation because the flight flew as if it were a normal flight. There should have been some communication with the ground agent before they came up and asked if all the masks had dropped and if everyone was ok.


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


Synopsis: Q400 flight crew reported during climb they received a 'CABIN PRESS' warning.
Date: 201201
Local time of day: 1201-1800
Location: ZZZ.Airport, US
Light: Daylight
Aircraft: B767 Undifferentiated or Other Model
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Landing
Airspace: Class B ZZZ
ATC / advisory: Tower ZZZ
Aircraft component: AC Generator/Alternator
Component problem: Malfunctioning
Reporter organization: Air Carrier
Reporter function: Captain; Pilot Not Flying
Reporter qualification: Flight Crew Air Transport Pilot (ATP)
Human factors: Distraction; Situational Awareness; Time Pressure
Anomaly: Aircraft Equipment Problem Critical
Detector: Automation Aircraft Other Automation; Person Flight Crew
When detected: Taxi; In-flight
Result: Flight Crew FLC complied w / Automation / Advisory; Flight Crew Inflight Shutdown; General Maintenance Action
Contributing factors: Aircraft
Primary problem: Aircraft

Narrative: On approximately 6 mile final to 9R the right engine generator dropped off line. After a short time the generator came back on then once again tripped off. The APU was started and the landing was accomplished. While taxiing in the oil pressure dropped to 7 PSI. The engine was shutdown and the QRH procedure was accomplished. At first it appeared the problem was with the right generator but when power was reduced after landing and waiting for a runway crossing the right engine low pressure light illuminated and the oil pressure was noted to be in the red. Oil quantity was 20.




Synopsis: While on final approach a B767 right generator dropped off line but returned to normal. After landing engine oil pressured dropped to 7 PSI; the right engine was then shut down using the QRH.
Date: 202003
Local time of day: 0001-0600
Aircraft: A320
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Descent
Aircraft component: Pneumatic System
Component problem: Malfunctioning
Reporter organization: Air Carrier
Reporter function: Captain; Pilot Flying
Reporter qualification: Flight Crew Air Transport Pilot (ATP); Flight Crew Instrument; Flight Crew Multiengine
Anomaly: Aircraft Equipment Problem Less Severe; Flight Deck / Cabin / Aircraft Event Smoke / Fire / Fumes / Odor
Detector: Person Flight Crew
When detected: In-flight
Result: Flight Crew Overcame Equipment Problem; General Maintenance Action
Contributing factors: Aircraft
Primary problem: Aircraft

Narrative: I started the trip in ZZZ the crew that brought Aircraft X in had a fume event on descent at 3;000 ft.; it was determined by Maintenance that the problem was with Pack 1 so; Pack 1 was deactivated; during boarding we smelled it again with Pack 2 running and APU; Maintenance was called and the APU was deactivated.During descent through FL 210 we smelled it again with both engines running; both bleeds open; Pack 1 off; APU off; Pack 2 on.




Synopsis: A320 Captain reported a fumes event during boarding and also during descent at destination.
Date: 201408
Local time of day: 1201-1800
Location: ZZZ.Airport, US
Aircraft: B767-300 and 300 ER
Operator: Air Carrier
Operating under: Part 121
Flight phase: Takeoff / Launch
ATC / advisory: TRACON ZZZ
Aircraft component: Turbine Engine
Component problem: Malfunctioning
Reporter organization: Air Carrier
Reporter function: Pilot Not Flying; Relief Pilot
Anomaly: Aircraft Equipment Problem Less Severe
Detector: Person Flight Crew
When detected: In-flight
Result: Flight Crew Returned To Departure Airport; Flight Crew Landed As Precaution; General Declared Emergency; General Maintenance Action
Contributing factors: Aircraft
Primary problem: Aircraft

Narrative: Engine vibration on T/O with wind 100 at 5 KTS / Max Power T/O; rain showers in area. After gear retract there was a slight vibration noticed. Right engine was producing less N1 than the left. At approximately 3;000 FT we matched the N1's; the right throttle was a full knob forward of the left; fuel flow on R was about 4;000 pounds above the left. R.E. LPT vibration was 5.0 (max on scale); temps split between engines. Decision was made to return. Radio calls made to Maintenance; Dispatch; Ramp Tower; ATC; for coordination and advice. Flight attendants notified. Emergency was declared with approach as we were to make an overweight landing (336.0 pounds.) Flight attendants were made aware and kept abreast of the situation. Landing was uneventful. Returned to gate. All applicable log book entries made. The vibration on T/O felt to me as if a cargo container slid aft in the cargo bay at about gear retraction; or shortly thereafter. The vibration was only about 2 seconds in duration with no other vibration felt after that. There were no reports from the cabin; FA's or passengers; about any major vibrations; smoke; oil; or pieces of engine exiting the right engine.




Synopsis: B767-300 flight crew detects a rumbling vibration from the right engine shortly takeoff. With N1 low; N2 near the limit; fuel flow high and LPT vibration at 5.0 the decision is made to return to the departure airport. Maintenance discovers a turbine failure.
Date: 201304
Local time of day: 1201-1800
Location: BTV.Airport, VT
Flight conditions: VMC
Weather elements / visibility: 10
Light: Daylight
Aircraft: Citation V/Ultra/Encore (C560)
Operator: Fractional
Operating under: Part 135
Flight plan: IFR
Flight phase: Takeoff / Launch
Airspace: Class C BTV
ATC / advisory: TRACON BTV
Aircraft component: Aileron Control System
Component problem: Malfunctioning
Reporter organization: Fractional
Reporter function: Captain; Pilot Flying
Reporter qualification: Flight Crew Air Transport Pilot (ATP)
Human factors: Situational Awareness; Human-Machine Interface
Second reporter function: Pilot Flying; Captain
Anomaly: Aircraft Equipment Problem Critical
Detector: Person Flight Crew
When detected: In-flight
Result: General None Reported / Taken
Contributing factors: Aircraft
Primary problem: Aircraft

Narrative: After departing and executing a left hand turn as directed by ATC; I heard and felt a 'pop' noise in the control yoke. I was hand flying at the time and an additional amount of control 'play' was noted. No other vibration or anomaly was detected other than while in level cruise flight with the autopilot engaged; the first officer control yoke listed in a slight left turn direction. Due to gusty crosswind conditions that existed at the departure airport and aircraft gross weight; we elected to continue to the destination airport where runway alignment and prevailing surface winds required less control input.


Second narrative: No additional information was provided in the secondary narrative.


Synopsis: Despite experiencing an unusual popping noise and feeling some slack in the ailerons the flight crew of a CE-560 elected to continue to their destination as superior prevailing wind direction and velocity predicted less exposure to possible handling problems than did those existing at their departure airport.
Date: 201203
Local time of day: 1201-1800
Location: ZZZ.Airport, US
Flight conditions: VMC
Light: Daylight
Aircraft: Amateur/Home Built/Experimental
Operator: Personal
Operating under: Part 91
Flight plan: None
Mission: Personal
Flight phase: Landing
ATC / advisory: Tower ZZZ
Aircraft component: Nose Gear
Component problem: Failed
Reporter organization: Personal
Reporter function: Single Pilot; Pilot Flying
Reporter qualification: Flight Crew Air Transport Pilot (ATP)
Anomaly: Aircraft Equipment Problem Critical
Detector: Person Flight Crew
When detected: In-flight
Result: Aircraft Aircraft Damaged
Contributing factors: Aircraft
Primary problem: Aircraft

Narrative: Upon normal landing nose wheel strut broke. Aircraft slid to a stop. There was no further damage and no injuries.




Synopsis: The pilot of a pusher canard homebuilt suffered a nose gear strut failure on landing.
Date: 201909
Local time of day: 0001-0600
Location: OAK.Airport, CA
Light: Daylight
Aircraft: B737-700
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Taxi
Reporter organization: Air Carrier
Reporter function: First Officer; Pilot Not Flying
Reporter qualification: Flight Crew Air Transport Pilot (ATP)
Human factors: Situational Awareness
Second reporter function: Pilot Flying; Captain
Anomaly: Deviation / Discrepancy - Procedural Clearance; Ground Event / Encounter Other / Unknown; Ground Incursion Taxiway
Detector: Person Ground Personnel
When detected: Taxi
Contributing factors: Airport; Human Factors; Procedure
Primary problem: Airport

Narrative: While taxiing into the gate; the Pilot Flying and Pilot Monitoring elected to continue to the gate while an aircraft that had pushed from another gate was in position with ground crew approximately 120 feet and 30 degrees off center of our Gate J-line; aligned with the eastern taxi-in line at the terminal. The Pilot Monitoring noticed Pilot Flying was proceeding past our gate and called that that was the correct Gate. The Pilot Flying stopped the aircraft and made a left turn with brake to align on the Gate J-line; however 40 feet inside the top of J-line due to the 30 feet overshoot. Winds at the time were approximately 280 degrees at 20 kts; or approximately 60 degrees off the Gate J-line axis blowing towards the eastern taxi-in line at the Terminal. After engine shutdown; both Pilot Flying and Pilot Monitoring were met by a Ramp Supervisor who stated that the engine exhaust was creating a hazard for the ramp crew that had pushed the aircraft from an adjacent gate.


Second narrative: [Narrative contained no additional information.]


Synopsis: B737 flight crew reported a Ramp Supervisor advised them their exhaust created a hazard for a ramp crew at an adjacent gate.
Date: 201407
Location: ZZZ.Airport, US
Light: Daylight
Aircraft: B737-700
Operator: Air Carrier
Operating under: Part 121
Mission: Passenger
Flight phase: Parked
Reporter organization: Air Carrier
Reporter function: Flight Attendant (On Duty); Flight Attendant In Charge
Reporter qualification: Flight Attendant Current
Human factors: Time Pressure; Workload
Anomaly: Deviation / Discrepancy - Procedural Security; Deviation / Discrepancy - Procedural Published Material / Policy
Detector: Person Flight Crew
When detected: Pre-flight
Result: General None Reported / Taken
Contributing factors: Human Factors; Company Policy
Primary problem: Ambiguous

Narrative: Another day....another safety related issue. Upon arrival at gate; about 32 minutes before departure; I informed the Ops Agent we would need 5-minutes before boarding could begin to do our required safety/equipment checks. He looked at his watch and gave me a puzzled/confused look; almost in shock that he wouldn't have enough time to push on time. I repeated we would need 5-minutes. About 2-minutes later; while involved with my required checks -- the first wheelchair customer came walking onboard. I didn't have time to stop the flow or address this early boarding with the Agent before the other wheelchair customers were lined-up; unloading etc.... The originating flight security check document had not been signed yet either. Just before the door shut; I addressed the Ops Agent telling him his early boarding was not right and that we had not even finished our required checks. He said; '.....well; I have a supervisor up-top and everything; so we had to get boarding....' I told him it was wrong and that despite that fact; we needed to fully complete our pre-boarding equipment checks and security sweep before boarding was to start. I informed the agent I was going to write a report on the incident. Stop the pressure to push early. Give flight crews 5-10 minutes guaranteed to perform our required duties without being rushed; hovered-over or made to feel guilty that we will be the cause for a delay.




Synopsis: A B737 Flight Attendant reports that agents are not honoring requests by the cabin crew to hold off boarding until required security and cabin checks are complete and the crew is ready to board.
Date: 201901
Local time of day: 1201-1800
Location: ZZZ.Airport, US
Flight conditions: VMC
Light: Daylight
Aircraft: Cessna 402/402C/B379 Businessliner/Utiliner
Operator: Air Taxi
Operating under: Part 135
Mission: Passenger
Flight phase: Cruise
ATC / advisory: Center ZZZ
Aircraft component: Engine
Component problem: Failed
Reporter organization: Air Taxi
Reporter function: Captain; Pilot Flying
Reporter qualification: Flight Crew Instrument; Flight Crew Commercial; Flight Crew Multiengine
Anomaly: Aircraft Equipment Problem Critical
Detector: Person Flight Crew
When detected: In-flight
Result: Flight Crew Overcame Equipment Problem
Contributing factors: Aircraft
Primary problem: Aircraft

Narrative: In cruise my right engine failed. There was a shutter; than another shutter and the engine was completed stopped. On the second shutter I began the Engine Failure in Flight flow. Upon reaching fuel pump on high; in the flow; the engine was stopped. I continued the flow to completion; secured the engine; referenced the QRH; and called ATC. I was able to maintain level flight to I decided to continue to [the destination] airport. I briefed the passengers and they appeared to be alright. I followed the in-range and before landing checklist per the QRH and landed without further incident. I was greeted by fire trucks and taxied to the gate.




Synopsis: C402 Captain reported an engine failure in cruise.
Date: 201511
Local time of day: 1801-2400
Location: RNO.Airport, NV
Flight conditions: VMC
Light: Night
Aircraft: B737-800
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Initial Approach
Airspace: Class C RNO
ATC / advisory: TRACON NCT
Reporter organization: Air Carrier
Reporter function: First Officer; Pilot Flying
Reporter qualification: Flight Crew Air Transport Pilot (ATP)
Human factors: Situational Awareness
Anomaly: Inflight Event / Encounter CFTT / CFIT
Detector: Automation Aircraft Terrain Warning
When detected: In-flight
Result: Flight Crew Became Reoriented; Flight Crew Took Evasive Action
Contributing factors: Human Factors
Primary problem: Human Factors

Narrative: While on the visual approach at night using the ILS 16R as a backup I was intercepting the localizer between DICEY and TAKLE and set the altitude to 6400 feet to cross DICEY. We received a terrain alert while in the descent in the process of leveling off the GPWS terrain pull up alert sounded. I executed the escape maneuver to a safe altitude and continued the visual approach. The approach plate does show a 6200 ft hill on the approach which I did not notice. I had the runway clearly insight and everything appeared to be a normal visual approach. Next time I will cross TAKLE at 8500 and follow the glide slope. Until I am more familiar with Reno I will always intercept the glide slope and localizer for guidance.




Synopsis: B737 First Officer reported receiving a terrain alert followed by a GPWS pull up alert caused by a 6200 ft hill while on a night visual approach to Runway 16R at RNO.
Date: 202101
Local time of day: 0601-1200
Flight conditions: VMC
Weather elements / visibility: 10
Light: Daylight
Aircraft: PA-28 Cherokee/Archer/Dakota/Pillan/Warrior
Operator: Other unknown
Operating under: Part 91
Flight plan: None
Flight phase: Takeoff / Launch
ATC / advisory: Tower ZZZ
Aircraft component: Wing Leading Edge
Component problem: Malfunctioning
Reporter organization: Personal
Reporter function: Instructor
Reporter qualification: Flight Crew Instrument; Flight Crew Commercial; Flight Crew Flight Instructor
Anomaly: Aircraft Equipment Problem Less Severe; Ground Event / Encounter Person / Animal / Bird
Detector: Person Flight Crew
When detected: In-flight
Result: Aircraft Aircraft Damaged; Flight Crew Rejected Takeoff
Contributing factors: Environment - Non Weather Related
Primary problem: Environment - Non Weather Related

Narrative: During ground roll; prior to rotation; a bird flew in front of us and impacted the left wing. Resulting in a dent to the left leading edge. We immediately informed tower and turned on to a taxiway.




Synopsis: GA pilot reported that just before rotation a bird impacted the left wing and the pilot then rejected the takeoff.