elihoole/asrs-aviation-reports huggingface dataset:
Date: 201902
Local time of day: 0001-0600
Location: ZZZZ.ARTCC, FO
Aircraft: B767-300 and 300 ER
Operator: Air Carrier
Operating under: Part 121
Mission: Cargo / Freight / Delivery
Flight phase: Climb
Airspace: Class A ZZZZ
ATC / advisory: Center ZZZZ
Reporter organization: Air Carrier
Reporter function: Pilot Not Flying; Captain
Reporter qualification: Flight Crew Air Transport Pilot (ATP); Flight Crew Multiengine; Flight Crew Instrument
Human factors: Situational Awareness
Anomaly: Aircraft Equipment Problem Critical
Detector: Automation Aircraft Other Automation; Person Flight Crew
When detected: In-flight
Result: Flight Crew Overcame Equipment Problem; Flight Crew Returned To Departure Airport
Contributing factors: Aircraft
Primary problem: Aircraft

Narrative: L ENGINE FUEL FILTER EICAS (Engine Indicating and Crew Alerting System) MESSAGE CAME ON DURING CLIMB. EICAS MESSAGE CAME ON AND OFF SEVERAL TIMES AND REMAINED ON THROUGHOUT MOST OFF THE FLIGHT. LEFT ENGINE VIBRATED AND VIBRATION INCREASED DURING DESCENT COMPLIED WITH NON-NORMAL AND NORMAL CHECKLISTS [REQUESTED PRIORITY HANDLING] AND RETURNED TO ZZZZ. (Out of maintenance log.)We did not want to proceed over water with a possibility of fuel contamination. I was the monitoring pilot and completed the non-normal and normal checklists while FO (First Officer) was flying and handling ATC; I assumed the controls for the landing. We returned safely to ZZZZ. Excellent assistance from my FO.System malfunction.




Synopsis: B767 Captain reported an L Engine Fuel Filter EICAS message that was intermittent during a flight which made them return to departure airport.
Date: 201505
Local time of day: 1201-1800
Flight conditions: VMC
Light: Daylight
Aircraft: Commercial Fixed Wing
Operator: Air Carrier
Operating under: Part 121
Mission: Passenger
Flight phase: Landing
Reporter organization: Air Carrier
Reporter function: Passenger
Human factors: Confusion
Anomaly: Deviation / Discrepancy - Procedural Published Material / Policy; Flight Deck / Cabin / Aircraft Event Other / Unknown
Detector: Person Passenger
When detected: In-flight; Taxi
Result: Flight Crew Became Reoriented
Contributing factors: Company Policy; Environment - Non Weather Related
Primary problem: Company Policy

Narrative: Although I appreciate a jovial cabin crew; I suggest the theatrics be limited to non-critical portions of the flight. As among the flight crew; non-essential and distracting banter should be limited to sterile cockpit rules in the cabin; too.Upon touchdown; cabin crew used PA system to create noises which; once I figured it out; were imitations of a horse. Although this appeared to delight some passengers; it frightened me for a moment as I thought one of the flight deck crew had a stuck mic on the PA and was expressing fear. As this was a rather non-normal occurrence to an otherwise uneventful touchdown; I truly thought something had gone wrong.I believe cabin crews should observe a more appropriate use of PA during critical phases.




Synopsis: A passenger reported being initially startled by a Flight Attendant PA banter on landing until he realized the theatrics were not aircraft related noise.
Date: 201408
Location: LVJ.Airport, TX
Aircraft: No Aircraft
Reporter function: Pilot Flying; Single Pilot
Human factors: Situational Awareness
Anomaly: No Specific Anomaly Occurred All Types
Detector: Person Flight Crew
When detected: In-flight
Result: General None Reported / Taken
Contributing factors: Equipment / Tooling
Primary problem: Equipment / Tooling

Narrative: A 1200 foot broadcast tower near the Pearland Regional Airport (LVJ) in the Houston; TX area has been partially to totally unlit for the past several years.  It has been totally unlit for at least the last four months.  It is located approximately 3 miles south of the airport and within approximately 1.5 miles of the instrument approach to Runway 32.  NOTAM's are repeatedly issued for the tower; but it seems to never get fixed.  As evidenced by the Army helicopter crash into a NOTAM'ed unlit tower near Waco that killed seven people; the NOTAM solution really isn't a solution.  It would seem that the tower operator is abdicating his responsibility to maintain working lights at the expense of safety.  A check of the NOTAM history will reveal how long this situation has persisted. I contacted the FAA; who replied that they had no enforcement powers and that this function was governed by the FCC.  I've filed a complaint with the FCC and received a response that since the tower owner was maintaining NOTAM's; there was no violation (email from local FCC enforcement officer pasted at bottom).  I find this to be an incredible situation. A tower owner can skate by for years using the NOTAM system; effectively negating any incentive to spend the money to light his tower; while putting the rest of the flying public at risk.  This is a tall tower near a busy airport in the metropolitan area of the fourth largest city in the US and it has been totally dark.  Unbelievable. I also find the FCC's response to this issue to be unacceptable.  They seem to be in no rush to force the tower owner to meet their established lighting requirements.  There is no reason in the world that it should take this long for a tower to get a lighting system installed. It's done every day on towers all over the world.  At the very least; he could put temporary strobes on it. Email response from FCC;  'I received your complaint concerning the light outage on Tower number 1052126 near the airport in Pearland; TX.  The owner is maintaining a NOTAM so there is no FCC Rule violation.  The owner has had the lighting repaired multiple times; but the lighting kept going out.  He finally realized that the entire lighting system must be replaced.  He is in the process of purchasing the necessary equipment and working with a tower company to have the lighting repaired.  I'll be staying in touch with the owner to ensure the lighting is repaired.    Communications Commission Enforcement Bureau South Central Region Houston Office. '




Synopsis: Pilot reports that a communication tower (1052126) three miles south of LVJ has been unlighted or partially lighted for years and needs to be repaired instead of just issuing Notam's.
Date: 201707
Location: ZZZ.ARTCC, US
Aircraft: Citation Excel (C560XL)
Operator: Air Taxi
Operating under: Part 135
Flight plan: IFR
Flight phase: Climb
Airspace: Class E ZZZ
Reporter organization: Air Taxi
Reporter function: Captain; Pilot Flying
Reporter qualification: Flight Crew Air Transport Pilot (ATP)
Anomaly: Deviation / Discrepancy - Procedural Published Material / Policy; Inflight Event / Encounter Fuel Issue
Detector: Person Flight Crew
When detected: In-flight
Result: Air Traffic Control Issued New Clearance; Flight Crew Requested ATC Assistance / Clarification
Contributing factors: Company Policy; Procedure
Primary problem: Company Policy

Narrative: The Company routinely flight plans with a planned altitude on a departure fix in order to account for the higher fuel consumption when departing a satellite airport.However; when such processes are used in the Company's flight planning it ends up filing such initial lower altitude as the requested final altitude to ATC. Unfortunately; the FAA's ATC system does not seem to recognize the subsequent altitude changes included in the ICAO flight plan.The issue with such a lower altitude being filed is that it may lead to a different route than the one that would be received for the higher altitudes. This presents a number of risk factors -- E.g. Not enough fuel; multiple full route clearance changes; etc.Today's flight was planned for FL400; however; we were cleared with a planned final altitude of 16000 FT. Clearance delivery was not able to change the planned altitude and we had to ask one of the subsequent ARTCC controllers to change the altitude.




Synopsis: Cessna 560XLS Captain reported that the FAA's ATC system does not seem to recognize the subsequent altitude changes included in the ICAO flight plan.
Date: 201807
Local time of day: 0601-1200
Weather elements / visibility: Turbulence; +10
Light: Daylight
Aircraft: Aeronca Champion
Operator: Personal
Operating under: Part 91
Flight plan: VFR
Mission: Personal
Flight phase: Landing
Airspace: Class G Y
Reporter organization: Personal
Reporter function: Single Pilot
Reporter qualification: Flight Crew Sport / Recreational
Human factors: Situational Awareness
Anomaly: Ground Event / Encounter Object; Ground Event / Encounter Loss Of Aircraft Control; Ground Event / Encounter Ground Strike - Aircraft; Inflight Event / Encounter Weather / Turbulence
Detector: Person Flight Crew
When detected: Other landing
Result: Aircraft Aircraft Damaged; General Evacuated
Contributing factors: Weather; Human Factors
Primary problem: Human Factors

Narrative: As I approached my landing at the airport a crosswind developed. I had checked AWOS on my downwind which stated winds were calm. As the plane touched the pavement the wind blew the plane sideways. The landing gear broke and ripped the left wheel off the plane. The propeller then broke and control of the plane was lost. The plane collided with 2 runway lights causing them to fall. The plane came to a stop. My passenger and I departed the plane without injury.




Synopsis: GA pilot reported a loss of control during landing due to a crosswind encounter.
Date: 202004
Local time of day: 1201-1800
Location: ZZZ.TRACON, US
Flight conditions: VMC
Light: Daylight
Aircraft: Beechcraft Single Piston Undifferentiated or Other Model
Operator: Corporate
Operating under: Part 91
Flight plan: None
Mission: Passenger
Flight phase: Cruise
Airspace: Class B ZZZ
ATC / advisory: TRACON ZZZ
Aircraft component: AC Generator/Alternator
Component problem: Failed
Reporter organization: Corporate
Reporter function: Pilot Flying
Reporter qualification: Flight Crew Commercial; Flight Crew Instrument; Flight Crew Multiengine
Anomaly: Aircraft Equipment Problem Critical; Deviation / Discrepancy - Procedural Published Material / Policy
Detector: Person Flight Crew
When detected: In-flight
Result: Air Traffic Control Provided Assistance; Flight Crew Diverted; Flight Crew Landed in Emergency Condition; General Flight Cancelled / Delayed; General Maintenance Action
Contributing factors: Aircraft
Primary problem: Aircraft

Narrative: Alternator bracket failure causing alternator failure; diverted to land; ATC [advised] on my behalf.




Synopsis: Pilot reported an alternator mounting bracket failure resulted in a diversion and a precautionary emergency landing.
Date: 201604
Local time of day: 1201-1800
Location: ZZZ.Airport, US
Flight conditions: VMC
Weather elements / visibility: 10
Light: Daylight
Aircraft: Cessna 210 Centurion / Turbo Centurion 210C; 210D
Operator: Personal
Operating under: Part 91
Flight plan: IFR
Mission: Personal
Flight phase: Cruise
Airspace: Class E ZZZ
ATC / advisory: Center ZZZ
Second aircraft: Cessna Single Piston Undifferentiated or Other Model
Reporter organization: Personal
Reporter function: Single Pilot
Reporter qualification: Flight Crew Commercial; Flight Crew Instrument
Human factors: Communication Breakdown; Situational Awareness
Anomaly: ATC Issue All Types; Conflict NMAC; Deviation / Discrepancy - Procedural Published Material / Policy; Flight Deck / Cabin / Aircraft Event Other / Unknown
Detector: Automation Aircraft TA; Person Air Traffic Control
When detected: In-flight
Result: Air Traffic Control Issued Advisory / Alert
Contributing factors: Airspace Structure; Human Factors
Primary problem: Human Factors

Narrative: We were cleared direct to [destination airport] at 3000 feet and my traffic system sounded an alert showing a target almost directly ahead and 100 feet higher. I identified the traffic about 500 feet to my left as it went by. I asked the controller if he had noticed the target and he stated that he had been trying to call me and the pilot of the target plane but neither of us answered. I told him that I never heard his call. The other pilot said he had heard the call and had responded.Since I'm not sure why I didn't hear the call; I can only assume that perhaps I was focused on other tasks or there was a communications problem. In the future I will try even harder to make sure that one ear is always listening. Perhaps the controllers should re-transmit if an alert is not acknowledged quickly.The Traffic Avoidance System was an important factor in this case and well worth the investment.




Synopsis: The pilot of a C210 was alerted to a near-mid-air-collision by the onboard traffic system. ATC was reported to have tried to contact both aircraft; but an unknown communication problem existed.
Date: 202201
Local time of day: 0601-1200
Location: ZZZ.Airport, US
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 Climb
Aircraft component: Elevator Trim System
Component problem: Failed
Reporter organization: Air Carrier
Reporter function: Pilot Flying
Reporter qualification: Flight Crew Multiengine; Flight Crew Instrument; Flight Crew Air Transport Pilot (ATP)
Human factors: Troubleshooting
Anomaly: Aircraft Equipment Problem Critical; Deviation / Discrepancy - Procedural Published Material / Policy
Detector: Person Flight Crew
When detected: In-flight
Contributing factors: Aircraft
Primary problem: Aircraft

Narrative: Auto Trim Fail to Autopilot Failure on climb out.




Synopsis: ERJ 145 First Officer reported auto trim fail and autopilot failure on climb out.
Date: 202101
Local time of day: 1201-1800
Location: HDN.Airport, CO
Aircraft: Small Transport
Operating under: Part 91
Flight phase: Takeoff / Launch
Airspace: Class E ZDV; Class G HDN
ATC / advisory: CTAF HDN; Center ZDV
Second aircraft: Light Transport
Reporter function: Other / Unknown; Unicom Operations
Human factors: Communication Breakdown
Second reporter function: Captain; Pilot Flying
Anomaly: Conflict Ground Conflict; Critical; Deviation / Discrepancy - Procedural Published Material / Policy; Deviation / Discrepancy - Procedural FAR; Ground Incursion Runway
Result: Flight Crew Took Evasive Action; Flight Crew Executed Go Around / Missed Approach
Contributing factors: Human Factors; Airspace Structure
Primary problem: Human Factors

Narrative: During heavy traffic with inbound and outbound traffic Aircraft X was on short final. Aircraft Y was in line with several other aircraft for a [Runway] 28 departure. Aircraft X was calling position inbound for [Runway] 28. When Aircraft Y was number one in line to depart; the aircraft advanced on to the Runway 28 without any radio traffic and departed. This caused Aircraft X to go missed to avoid a collision. Aircraft Y never responded to any radio traffic.


Second narrative: Event happened at Yampa Valley Colorado. Contributing factors were a weather pause for both incoming and outgoing traffic. As we were trying to take off Denver Center was trying to sequence arrivals and departures. The aircraft in front of us was cleared to take off by Denver Center. We were asked if we could take off and be airborne within 90 seconds due to an inbound aircraft. We had an aircraft in sight and believed that to be the aircraft which we were cleared in front of. Contributing factor was Pilot in command was on ATC frequency but not on CTAF frequency. First officer was on both frequencies; but VFR aircraft was not transmitting position in pattern. As we took the runway and began our takeoff roll; chatter on the CTAF frequency alerted us to the traffic conflict. First Officer began giving vectors to Pilot Flying to avoid possible conflict. Due to being on takeoff roll we did not have visual on conflict aircraft. After getting airborne and getting in a safe flight configuration we took a slight left turn to displace ourselves from the TCAS information. We did not receive an RA likely because we were too low.Situational Awareness of Pilot Flying was increased dramatically once on both frequencies. Both pilots were under the impression clearance to depart was given with the aircraft we had in view to be the called traffic.


Synopsis: Pilot and ground employee reported that an aircraft did not communicate their intentions on CTAF; taxied onto the runway and departed in front of an inbound aircraft causing that aircraft to go-around.
Date: 201407
Local time of day: 0001-0600
Location: ZZZ.Airport, CA
Flight conditions: VMC
Weather elements / visibility: 10
Light: Daylight
Aircraft: PA-44 Seminole/Turbo Seminole
Operator: FBO
Operating under: Part 91
Flight plan: None
Mission: Training
Flight phase: Landing
Airspace: Class G ZZZ
ATC / advisory: CTAF ZZZ
Aircraft component: Landing Gear
Component problem: Improperly Operated
Reporter organization: FBO
Reporter function: Instructor; Pilot Not Flying
Reporter qualification: Flight Crew Commercial; Flight Crew Flight Instructor; Flight Crew Instrument; Flight Crew Multiengine
Human factors: Situational Awareness; Distraction
Anomaly: Deviation / Discrepancy - Procedural FAR; Deviation / Discrepancy - Procedural Published Material / Policy; Ground Event / Encounter Gear Up Landing
Detector: Person Flight Crew
When detected: In-flight
Result: Aircraft Aircraft Damaged; General Maintenance Action
Contributing factors: Human Factors
Primary problem: Human Factors

Narrative: I was training my Multi-Commercial course student in a PA44-180. The weather condition was wind 290 at 12 knots; sky is clear; visibility is more than 10 SM. We were practicing single engine circling instrument approach to prepare the check ride of my student at a non-towered airport. During the final approach course; the landing gear was down with simulated single engine. At 200 FT above MDA; we raised the landing gear for the circle; otherwise we can not maintain MDA for circling due to drag. However; we had a strong head wind so I changed my mind to make a straight in landing at the 2.5 mile final. Until that time student and I misunderstood that we had lowered the landing gear. Unfortunately landing gear warning horn was not activated at that time. We just continued to approach and landed without landing gear down. After the propeller hit the ground; we noticed that we did not lower the landing gear. Airplane stopped on the runway near the center line and there was no damage to airport facilities. Student and I were not hurt and we evacuated from the airplane. I requested the help from local airplane mechanics at the field and we lifted up the airplane and moved it from the runway within an hour. I also had a handheld transceiver to communicate with any inbound traffic just in case. Through this incident; I learned how each procedure is important during the whole flight and I promised to myself that I am going to double check every single critical procedure during the flight in the future. I couldn't emphasize enough about the landing gear double check.




Synopsis: PA44 instructor pilot describes the events leading up to a gear up landing after a simulated engine out approach.
Date: 201606
Local time of day: 0601-1200
Location: ZHU.ARTCC, TX
Light: Daylight
Aircraft: Military Transport
Operator: Military
Operating under: Part 91
Flight plan: IFR
Mission: Training
Flight phase: Cruise
Airspace: Class A ZHU
ATC / advisory: Center ZHU
Reporter organization: Government
Reporter function: Enroute
Reporter qualification: Air Traffic Control Fully Certified
Human factors: Situational Awareness; Distraction; Workload
Anomaly: ATC Issue All Types; Airspace Violation All Types; Deviation / Discrepancy - Procedural Published Material / Policy
Detector: Person Air Traffic Control
When detected: In-flight
Result: Air Traffic Control Issued New Clearance; Flight Crew Exited Penetrated Airspace
Contributing factors: Environment - Non Weather Related; Staffing; Human Factors
Primary problem: Human Factors

Narrative: Mid shift configuration. Aircraft X enroute at 15000 feet. Entered R4401 which was active up to 18000 feet. I was reading and failed to realize that the route took the aircraft through the restricted area. When I observed the aircraft inside the restricted area I issued an immediate turn to take the aircraft out of the area on the shortest route then resumed normal operations. I personally will play closer attention during midshift operations.




Synopsis: ZHU Controller reported they allowed an aircraft to enter a restricted area.
Date: 202001
Local time of day: 0601-1200
Location: ZZZ.Airport, US
Flight conditions: IMC
Weather elements / visibility: Cloudy; Turbulence
Light: Daylight
Aircraft: Regional Jet 200 ER/LR (CRJ200)
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Descent
Airspace: Class B ZZZ
Aircraft component: Fuel Quantity-Pressure Indication
Component problem: Malfunctioning
Reporter organization: Air Carrier
Reporter function: Captain; Pilot Not Flying
Reporter qualification: Flight Crew Air Transport Pilot (ATP); Flight Crew Multiengine; Flight Crew Instrument
Anomaly: Aircraft Equipment Problem Critical; Deviation / Discrepancy - Procedural Published Material / Policy; Inflight Event / Encounter Fuel Issue; Inflight Event / Encounter Weather / Turbulence
Detector: Person Flight Crew
When detected: In-flight
Result: Air Traffic Control Provided Assistance; Aircraft Equipment Problem Dissipated; Flight Crew Landed in Emergency Condition; Flight Crew Overcame Equipment Problem; General Maintenance Action
Contributing factors: Aircraft; Weather
Primary problem: Aircraft

Narrative: We were in the descent into ZZZ on the arrival.  Once we reached 13;000 feet we began to encounter moderate chop.  I then noticed we had a fuel crossflow inhibit status message on ED-2.  After seeing that message I noticed the fuel imbalance.  There was 2;000 lbs in the left tank and 1;600 lbs in the right tank.  As Captain; I then began to search a QRH procedure for the imbalance.  As I opened the QRH; the right fuel gauge and total fuel gauge showed amber.  After the loss of the gauges; the left tank began to rise.  The First Officer and I could not determine whether or not fuel was transferring or just burning from the right tank.  Because of this we elected to advise ATC and land as soon as possible.  The gauges did return on short final with a balanced fuel load.




Synopsis: CRJ-200 Captain reported a fuel imbalance on approach; causing a precautionary landing.