elihoole/asrs-aviation-reports huggingface dataset:
Date: 202106
Local time of day: 1201-1800
Location: ZZZ.TRACON, US
Aircraft: A330
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Flight phase: Initial Climb
ATC / advisory: TRACON ZZZ
Reporter organization: Government
Reporter function: Departure
Reporter qualification: Air Traffic Control Fully Certified
Human factors: Communication Breakdown
Anomaly: ATC Issue All Types; Deviation / Discrepancy - Procedural Published Material / Policy; Inflight Event / Encounter CFTT / CFIT
Detector: Automation Air Traffic Control
When detected: In-flight
Result: Air Traffic Control Issued New Clearance; Flight Crew Returned To Clearance
Contributing factors: Human Factors; Procedure
Primary problem: Human Factors

Narrative: Tower requested release on Aircraft X; IFR; filed ZZZ.ZZZZZ.ZZZ with a requested altitude of FL230; runway heading. The remarks stated that they were requesting to follow the ZZZZZ2 SID; but the routing was not filed that way. When Aircraft X checked on; the language barrier hindered me from properly understanding what they were requesting to do. I asked a few times what their intent was. In the final exchange; I was able to understand that they were level at 1;500 MSL in a 2;300 MVA (Minimum Vectoring Altitude). I immediately said; '...negative; climb and maintain 080.' No further issues were experienced and I was able to get them on their requested routing.




Synopsis: TRACON Controller reported that an aircraft was at an altitude below the minimum vectoring altitude for the area and directed an immediate climb.
Date: 201809
Location: MMFR.ARTCC, FO
Flight conditions: IMC
Weather elements / visibility: Turbulence
Aircraft: B737 Undifferentiated or Other Model
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Cruise
ATC / advisory: Center MMFR
Reporter organization: Air Carrier
Reporter function: First Officer; Pilot Not Flying
Reporter qualification: Flight Crew Commercial; Flight Crew Multiengine; Flight Crew Instrument
Human factors: Communication Breakdown; Distraction; Other / Unknown
Anomaly: Flight Deck / Cabin / Aircraft Event Illness / Injury; Inflight Event / Encounter Weather / Turbulence
Detector: Person Flight Crew
When detected: In-flight
Result: Flight Crew Regained Aircraft Control; General Physical Injury / Incapacitation
Contributing factors: Weather
Primary problem: Weather

Narrative: I was the Pilot monitoring on flight to ZZZ when we encountered moderate turbulence enroute at FL340 in Monterey airspace over the gulf of Mexico over the fix of XOTUG. It went from completely smooth air to moderate turbulence with a couple of jolts and rolls to where it caused several injuries to passengers and flight attendants where we had paramedics meet the aircraft upon arrival in ZZZ. We did not have any indications on RADAR nor from ATC that it was moderate level turbulence and we were completely startled ourselves. It only lasted about 10-15 seconds while the autopilot remained on and smoothed out afterwards. We checked on the cabin status and were told of the injuries incurred by the passengers who one happened to be in the lavatory and one who had coffee spilled on her lap. The Flight Attendant also hurt her wrist and hip as well from what we were told. Prior to this; the seat belt sign was off as we were experiencing smooth air and we turned it on as soon as we encountered the turbulence. We also made the PA announcement for the flight attendants to remain seated.




Synopsis: B737 First Officer reported moderate turbulence with minor injuries to passengers and flight attendants.
Date: 201905
Local time of day: 1801-2400
Location: EWR.Airport, NJ
Flight conditions: VMC
Weather elements / visibility: Thunderstorm
Aircraft: B787 Dreamliner Undifferentiated or Other Model
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Climb
Airspace: Class B EWR
ATC / advisory: TRACON N90
Aircraft component: Cockpit Window
Reporter organization: Air Carrier
Reporter function: Captain; Pilot Flying
Reporter qualification: Flight Crew Air Transport Pilot (ATP); Flight Crew Multiengine; Flight Crew Instrument
Human factors: Situational Awareness
Anomaly: Aircraft Equipment Problem Less Severe; Inflight Event / Encounter Weather / Turbulence
Detector: Person Flight Crew
When detected: In-flight
Contributing factors: Aircraft; Weather; Human Factors; Company Policy
Primary problem: Aircraft

Narrative: While climbing out of approximately 7;500 feet; the aircraft received a lightning strike. Primarily forward left side window heat and primary First Officer side window heat inop illuminated. I flew the aircraft; the First Officer ran the appropriate checklist; contacted Dispatch with a patch through to [Chief Pilot]. The First Officer reviewed all systems pages; all normal. CB (Circuit Breaker) check indicated CB condition unknown for items related to inoperative systems. The crew openly discussed the situation together with [Chief Pilot] and Dispatch and concurred that the aircraft was and enroute weather was safe to continue to destination. Operations were normal and systems operated as expected throughout the remainder of the flight.




Synopsis: Air carrier pilot reported a lightning strike rendered their window heat inoperative; but they were able to continue to their destination.
Date: 201810
Location: ZZZ.Airport, US
Aircraft: B787-800
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Parked
ATC / advisory: Ramp ZZZ
Reporter organization: Air Carrier
Reporter function: Technician
Reporter qualification: Maintenance Airframe; Maintenance Powerplant
Human factors: Situational Awareness
Anomaly: Deviation / Discrepancy - Procedural Published Material / Policy; Ground Event / Encounter Other / Unknown
Detector: Person Ground Personnel; Person Maintenance
When detected: Taxi
Contributing factors: Company Policy; Equipment / Tooling; Procedure
Primary problem: Equipment / Tooling

Narrative: A787-800 was being prepared for a tow operation out of a hangat to the taxiway due to hangar construction and equipment congestion. The tow bar was attached to [the] 787-800 and a Tow Tractor GT350. The pavement was dry and the B787 had 30;000 pounds of fuel. The wheel chocks were pulled; TTWS active; and entry stair removed. The Tow Tractor parking brake was set and was shutoff. I exited the Tow Tractor to establish cockpit communication. After establishing cockpit communication; the wingwalkers; guideman and I; met at the Tow Tractor. We discussed clearance issues due to hangar construction and that we would not follow the lead out line because of construction equipment. Prior to entering the Tow Tractor; I instructed the taxi crew to release the brakes. Immediately upon release of brakes; the B787 began rolling backwards pulling the Tug with it. A Maintenance Technician noticed the B787 and Tow Tractor moving; entered the Tow Tractor; and brought it to a stop. The aircraft and tug rolled 3 feet before coming to a stop.I strongly feel Company has over rated the GT350's braking capability for wide body aircraft. The mechanical brake on the GT350 may have sufficient holding strength on a flat dry surface; but has proven to fail on a surface with a grade and is not able to hold the aircraft weight. I assume that a Tow Tractor would be able to under any situation provide sufficient braking pressure and prevent an aircraft from rolling.[Procedures Manual] states 'If you get out of the Tow Tractor set the parking brake and turn off the ignition.' Is the intent of that statement only apply when not attached to an aircraft? I feel any Tow Tractor that I use should be capable of stopping an aircraft from moving. The applicability and rating of the GT350 breaking force and stopping force on a grade needs to be reevaluated and updated.




Synopsis: Maintenance Technician reported an unmanned Tow Tractor; coupled to a B787; began rolling on the ramp even though the brakes on the Tow Tractor were set.
Date: 202010
Local time of day: 1801-2400
Location: ZZZ.Tower, US
Flight conditions: VMC
Light: Night
Aircraft: SR20
Operating under: Part 91
Mission: Training
Flight phase: Landing
Aircraft component: Main Gear Tire
Component problem: Failed
Reporter function: Instructor
Reporter qualification: Flight Crew Flight Instructor
Anomaly: Aircraft Equipment Problem Critical
Detector: Person Flight Crew
Result: Air Traffic Control Provided Assistance; Flight Crew Requested ATC Assistance / Clarification; General Evacuated; General Maintenance Action
Contributing factors: Aircraft
Primary problem: Aircraft

Narrative: Coming in on a stable approach the student landed on Runway XL and the student landed on the centerline of the runway nicely; but started drifting to the left then I told the student; 'Centerline put in some right rudder' after seeing that the student didn't corrected I told him;' my controls and tried to put the aircraft back on centerline; but couldn't then the air aircraft started to shake from the left side and immediately I realized we have a possible blown out tire and came in to a complete stop. After that I contacted ZZZ Tower and told them that we have a blown out tire and they responded 'Roger are you able exit off the runway.' I responded that we are unable to exit out the runway. Then I told them if I can get a frequency change to contact company and they said approve and report back. Then I contacted flight Supervisor and told them about the situation and he sent out maintenance for us. Then I switched back to Tower and let them know that I contacted company and they are going to send out maintenance. Tower responded; 'Roger; I sent out Airport Operations as well they will be on the way.' Then I asked Tower if I can shutdown the aircraft and evacuated on the runway. Tower responded;'that's approved.' I said; 'Roger we will shutdown the aircraft here and this is our final call.' Then maintenance came by and replace the tire and then after that we taxied back to the ramp.




Synopsis: An instructor reported  during landing rollout his SR20 suffered a tire failure requiring him to take control from his student.
Date: 201706
Local time of day: 0001-0600
Location: BTR.Airport, LA
Flight conditions: VMC
Light: Night
Aircraft: Light Transport; Low Wing; 2 Turbojet Eng
Operator: Fractional
Operating under: Part 91
Mission: Ferry / Re-Positioning
Flight phase: Takeoff / Launch
ATC / advisory: CTAF BTR
Reporter organization: Fractional
Reporter function: First Officer; Pilot Not Flying
Reporter qualification: Flight Crew Air Transport Pilot (ATP)
Human factors: Communication Breakdown
Anomaly: Conflict Ground Conflict; Less Severe; Deviation / Discrepancy - Procedural Published Material / Policy; Ground Incursion Runway
Detector: Person Flight Crew
When detected: In-flight
Result: General None Reported / Taken
Contributing factors: Procedure; Human Factors
Primary problem: Human Factors

Narrative: After starting engines on the ramp; I announced on the CTAF frequency (118.45) that we were taxiing out for takeoff to Rwy 4L (tower closed). I noticed that all airport lights were extinguished; so I activated all lighting on 118.45 using PCL procedures. No vehicular/aircraft traffic was observed on the surface of the airport; and no movements of same were heard on the CTAF. Just prior to taking the selected runway for departure (4L); I announced that we were taking the runway for departure. After brake release; I announced on the CTAF that we were commencing takeoff roll on 4L. All aircraft / taxi lights were on full bright. Just after the aircraft began to accelerate; I heard on the CTAF; 'Airport maintenance one is crossing all airport taxiways/ runways at Baton Rouge; use caution for vehicle.' Apparently this was an inspection vehicle for the airport prior to the tower opening. After the aircraft accelerated through approximately 90 knots; I noticed the silhouette of a vehicle crossing our active runway (4L) right to left approximately 3;000 ft in front of the aircraft; most likely the vehicle was crossing the runway on taxiway G. There was never a conflict with the aircraft and vehicle; and we were airborne well prior to where the vehicle crossed the runway; and the vehicle was clear of the runway when we passed that position.




Synopsis: Light Transport First Officer reported an airport vehicle crossing the departure runway after the crew had announced several times that they were taxiing to and departing from Runway 4L; on the CTAF frequency. The crew had also activated the airport lighting prior to taxi.
Date: 202112
Local time of day: 1201-1800
Location: ZZZ.Airport, US
Flight conditions: VMC
Weather elements / visibility: 10
Light: Daylight
Aircraft: Any Unknown or Unlisted Aircraft Manufacturer
Operator: Personal
Operating under: Part 91
Flight plan: None
Mission: Personal
Flight phase: Cruise
Airspace: Class G ZZZ
ATC / advisory: CTAF ZZZ
Reporter organization: Personal
Reporter function: Pilot Flying; Single Pilot
Reporter qualification: Flight Crew Flight Instructor
Anomaly: Aircraft Equipment Problem Critical; Deviation / Discrepancy - Procedural Published Material / Policy
Detector: Person Flight Crew
When detected: In-flight
Result: Flight Crew Took Evasive Action; Flight Crew Landed As Precaution
Contributing factors: Aircraft
Primary problem: Aircraft

Narrative: I was flying the gyroplane north bound over highway; going back to the airport at an altitude of 800 feet MSL; around 70 MPH; and I was probably 4.2 miles from the airport. As I was getting close the gyroplane started moving the nose left and right; my reaction was to lower the engine RPM and slow down; and the nose of the gyroplane stop moving. I continued to go toward the airport; and about a minute later the same movement of the nose going left and right started again but more pronounced. I again reduced the engine power to a lower engine rpm; but this time the nose movement did not stop or slow down; instead started to increase. I decided I would not make it back to the airport safely and made a precautionary landing on the shoreline.




Synopsis: Gyro-copter pilot reported the nose of the aircraft began to move side to side becoming unsafe to fly resulting in an off-airport landing.
Date: 202103
Local time of day: 1801-2400
Location: 39N.Airport, NJ
Light: Daylight
Aircraft: Small Aircraft; High Wing; 1 Eng; Fixed Gear
Operator: Personal
Operating under: Part 91
Mission: Personal
Flight phase: Taxi
Reporter organization: Personal
Reporter function: Pilot Flying; Single Pilot
Reporter qualification: Flight Crew Instrument; Flight Crew Private
Human factors: Communication Breakdown
Anomaly: Conflict Ground Conflict; Critical; Deviation / Discrepancy - Procedural FAR; Deviation / Discrepancy - Procedural Published Material / Policy; Ground Event / Encounter Object; Ground Event / Encounter Vehicle
Detector: Person Flight Crew
When detected: Taxi
Result: Flight Crew Took Evasive Action
Contributing factors: Procedure; Human Factors; Environment - Non Weather Related
Primary problem: Environment - Non Weather Related

Narrative: I was taxiing from the parking area to the active runway via the Taxiway at 39N [Princeton Airport]. Active was Runway 28. I noticed a car parked on the grass along the runway behind the PAPI lights. As I taxied down I noticed a person runway along the runway with orange cones on the runway. As I taxied down I noticed a white sports like 'race car' approaching me on the taxiway. They veered into the grass as I taxied down and I have to veer steer my aircraft to the right of the taxiway to avoid them passing underneath my wing. As I approached the run up area I noticed two cars; various tripods with equipment and one of the cars was behind the threshold in grass of the active runway with two people outside the car. I stopped at the runway hold short lines; and had to shut down as they weren't moving. I got out of plane and had to explain to them that they have cars; equipment and cones on an active runway. The person said he worked there and had permission from his boss to be there. I had to state repeatedly that I cannot take the runway safely with people; cars; and equipment on the active runway; which they didn't seem to understand. I reviewed showed them the runway hold short lines and reviewed that anything on the runway side of these lines has to be moved. I asked what they would do about an approaching aircraft; he indicated he had a radio- but this airport doesn't technically require radio use to land there. I reviewed what they are doing is dangerous. After they cleared their cars; equipment; cones; and people I was able to start back up and obtain my departure clearance and depart uneventfully. The field was NOT NOTAM'ed closed for race car activity in my briefings. Monitoring CTAF during my previous landing; parking; then later restarting and taxiing did not indicate any of this activity.I should have notified NY Approach Controllers after establishing contact with them but I didn't. The Controller was very busy but it was my mistake not to notify them in hindsight.




Synopsis: Pilot reported airport was being used for car racing without NOTAMs being posted.
Date: 201712
Local time of day: 0001-0600
Location: EUG.Tower, OR
Flight conditions: IMC
Aircraft: Small Aircraft; Low Wing; 2 Eng; Retractable Gear
Operator: Air Taxi
Operating under: Part 135
Flight plan: IFR
Mission: Ambulance
Flight phase: Final Approach
Airspace: Class D EUG
ATC / advisory: TRACON EUG
Reporter organization: Government
Reporter function: Approach
Reporter qualification: Air Traffic Control Fully Certified
Human factors: Communication Breakdown; Human-Machine Interface; Training / Qualification
Anomaly: ATC Issue All Types; Deviation / Discrepancy - Procedural Published Material / Policy
Detector: Person Air Traffic Control
When detected: In-flight
Result: Air Traffic Control Provided Assistance
Contributing factors: Company Policy; ATC Equipment / Nav Facility / Buildings
Primary problem: Company Policy

Narrative: Aircraft X was being vectored for the ILS. Tower lighting panel for airport lights was out of service due to a power outage the day before. The airport management decided; in their infinite wisdom; to just have ATC call their representative to have them change the airport lighting when needed. The night airport management person on duty was not properly trained in how to use the lighting panel; and with the visibility dropping rapidly; the runway lights needed to be on step 5. Airport management was unable to turn the lights up to step 5 with the visibility dropping to less than 1/4SM. Their electrician called the tower; and was extremely unhelpful and obstructive. Luckily the medevac was able to land safely.Airport management and their electrician are NOT reliable when it comes to having control of airport lighting. They are not properly trained; and when weather moves in like this; they cannot be relied upon to make the changes to the airport lighting in a timely manner. This cannot go on [further] while we wait for a new lighting panel to be acquired and installed. It extremely unsafe.




Synopsis: Eugene air traffic control Tower operator reported Tower lighting panel out of service; hindering IFR operations.
Date: 202111
Aircraft: A320
Operator: Air Carrier
Operating under: Part 121
Flight phase: Parked
Aircraft component: Horizontal Stabilizer Trim
Component problem: Improperly Operated
Reporter organization: Air Carrier
Reporter function: Technician
Reporter qualification: Maintenance Airframe; Maintenance Powerplant
Human factors: Situational Awareness; Troubleshooting
Anomaly: Aircraft Equipment Problem Critical; Deviation / Discrepancy - Procedural FAR; Deviation / Discrepancy - Procedural Maintenance; Deviation / Discrepancy - Procedural Published Material / Policy
Detector: Person Maintenance
When detected: Routine Inspection
Result: General Maintenance Action
Contributing factors: Human Factors; Aircraft; Procedure
Primary problem: Human Factors

Narrative: THSA (Trimmable Horizontal Stabilizer Assembly) Master Spline threaded bushing    (G1) was found missing safety wire during unrelated THSA general visual inspection. See AMM 27-44-00-710-001-A for safety wire installation requirements and Figure 27-44-00-991-00300-A test procedure of jamming simulation tool: Sheet 1. See log page XXXXXXX. This safety wire is removed and installed during THSA jamming tests; usually scheduled with some A checks. There is an  inspection of the installed safety wire on the task card.




Synopsis: A320 technician reported required safety wire missing on THSA master spline threaded bushing discovered during an unrelated general visual inspection.
Date: 201903
Local time of day: 0601-1200
Aircraft: EMB ERJ 190/195 ER/LR
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Initial Climb
Reporter organization: Air Carrier
Reporter function: Flight Attendant (On Duty)
Human factors: Physiological - Other
Anomaly: Flight Deck / Cabin / Aircraft Event Illness / Injury; Flight Deck / Cabin / Aircraft Event Smoke / Fire / Fumes / Odor
Detector: Person Flight Attendant; Person Flight Crew
When detected: In-flight
Result: Air Traffic Control Provided Assistance; Flight Crew Landed As Precaution; Flight Crew Returned To Departure Airport; General Maintenance Action
Contributing factors: Aircraft
Primary problem: Aircraft

Narrative: On climbout; strong burning/acrid fumes burned my eyes and throat and I started coughing and could not breathe. Passengers also could smell the strong fumes. I donned a portable 02 bottle and strapped into the empty jumpseat Number 3. I told the Number 1 that I was incapacitated. This was a Fume event. This is a very serious issue and makes crew incapacitated. The Number 1 and the Captain also smelled the fumes.FAA needs to fine airlines thousands of dollars every time a fume event is found. Potential irreversible brain and physical disabilities could occur because of smelling toxic TCP (Tricresyl Phosphate) fumes from the engine oil.




Synopsis: EMB-190 Flight Attendant reported fume event had incapacitated them during initial climb.
Date: 202102
Local time of day: 1201-1800
Location: ZZZ.ARTCC, US
Flight conditions: VMC
Weather elements / visibility: 10
Light: Daylight
Aircraft: Small Aircraft
Operator: Personal
Operating under: Part 91
Flight plan: VFR
Mission: Personal
Flight phase: Cruise
Airspace: Class E ZZZ
ATC / advisory: Center ZZZ
Aircraft component: Oil Filter
Component problem: Improperly Operated
Reporter organization: Personal
Reporter function: Single Pilot; Pilot Flying
Reporter qualification: Flight Crew Instrument; Flight Crew Private
Human factors: Time Pressure; Troubleshooting; Situational Awareness
Anomaly: Aircraft Equipment Problem Critical; Deviation / Discrepancy - Procedural Maintenance; Deviation / Discrepancy - Procedural Published Material / Policy; Flight Deck / Cabin / Aircraft Event Smoke / Fire / Fumes / Odor
Detector: Person Flight Crew
When detected: In-flight
Result: Air Traffic Control Provided Assistance; Flight Crew Took Evasive Action; Flight Crew Landed in Emergency Condition; Flight Crew Requested ATC Assistance / Clarification
Contributing factors: Procedure; Aircraft; Human Factors
Primary problem: Ambiguous

Narrative: During cruise; a smoke smell was detected. We attempted to trace the smell and quickly found smoke to be coming out of the foot wells. We proceeded to descend to the nearest airport where we found oil spattered inside of the cowling. The local Mechanic traced the leak to the oil filter which was installed by a different Mechanic who we contracted for a pre-buy. The Mechanic in question had used a pair of pliers to torque the oil filter; punching a small hole in the exterior which started leaking in flight and dripping on the heater; creating the smoke. The local Mechanic fixed our issue with a new oil filter and we proceeded to our destination the following day.




Synopsis: GA pilot reported the oil filter was installed improperly and caused smoke in the aircraft.