elihoole/asrs-aviation-reports huggingface dataset:
Date: 201310
Local time of day: 0601-1200
Location: AVQ.Airport, AZ
Flight conditions: VMC
Light: Daylight
Aircraft: Light Transport; Low Wing; 2 Turbojet Eng
Operator: Air Taxi
Operating under: Part 135
Flight plan: IFR
Mission: Passenger
Flight phase: Takeoff / Launch
ATC / advisory: CTAF AVQ
Second aircraft: Mooney Aircraft Undifferentiated or Other Model
Reporter organization: Air Taxi
Reporter function: Captain; Pilot Flying
Reporter qualification: Flight Crew Air Transport Pilot (ATP); Flight Crew Instrument; Flight Crew Multiengine
Human factors: Time Pressure; Communication Breakdown; Situational Awareness
Anomaly: Conflict Ground Conflict; Critical; Deviation / Discrepancy - Procedural Published Material / Policy
Detector: Person Flight Crew
When detected: Taxi
Result: General None Reported / Taken
Contributing factors: Procedure; Human Factors; Environment - Non Weather Related
Primary problem: Human Factors

Narrative: After taking the Runway 12 for departure; a previous aircraft on a touch and go continued on runway heading until approximately 1;500 FT AGL. We held in takeoff position to wait for that aircraft to turn since our speed on takeoff would have been much greater than his. We had to hold for approximately 1 minute and 30 seconds to avoid a conflict with the previous aircraft. While holding in position; an unidentified Mooney aircraft that had been on a wide base when we took the runway; continued a visual approach to Runway 12; and executed a go-around at approximately 20 feet AGL. The unidentified Mooney missed our aircraft vertically by about 100 FT. As we were static on the runway; we had no way to avoid the conflict with the Mooney.




Synopsis: An air taxi jet holding in position on AVQ Runway 12; had a near miss with a Mooney which executed a go around after passing about twenty feet over head.
Date: 201304
Local time of day: 1801-2400
Location: ZNY.ARTCC, NY
Aircraft: B737-800
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Cruise
Airspace: Class A ZNY
ATC / advisory: Center ZNY
Reporter organization: Government
Reporter function: Enroute
Reporter qualification: Air Traffic Control Fully Certified
Human factors: Situational Awareness
Anomaly: ATC Issue All Types
Detector: Person Air Traffic Control
Result: General None Reported / Taken
Contributing factors: Procedure
Primary problem: Procedure

Narrative: There is a major issue with the way the Bermuda Sector; a RADAR sector unless the RADAR fails is operated. We are using ATOP to control the traffic in an out of Bermuda as well as overflights. As far as overflights go the system works. As far as the transition to the airport; this system is inadequate. It was a fairly moderate traffic flow into the Bermuda Sector. There was a core track exiting the sector. Most aircraft were on the track. Some fix to fix direct; and others from the entry fix to BDA then to the exit fix; which added to the complexity. The sector was split out HI and LOW. There was a departure climbing to FL290. There were 2 inbounds to BDA at FL300 and FL310. There were multiple aircraft on the track above FL310. Air Carrier X a frequent arrival into BDA was entering at FL370 which is in violation of our agreement unless APREQed. I was unable to descend this flight due to the fact that we cannot use radial DME separation until 130 miles from the VOR. When I probed the flight down to FL310 ATOP showed conflicts with more than 5 aircraft. I had to hold the flight for almost 20 minutes at FL370 at a fix and then send the flight over 100 miles off their route of flight to descend the aircraft. This is a major issue due to the limitations of the system.




Synopsis: ZNY Controller voiced concern regarding the Bermuda Sector operations when RADAR is not available.
Date: 202012
Aircraft: Any Unknown or Unlisted Aircraft Manufacturer
Flight phase: Parked
Reporter organization: Contracted Service
Reporter function: Inspector
Reporter qualification: Maintenance Inspection Authority; Maintenance Airframe; Maintenance Powerplant
Human factors: Communication Breakdown
Anomaly: Aircraft Equipment Problem Less Severe; Deviation / Discrepancy - Procedural Published Material / Policy; Deviation / Discrepancy - Procedural Maintenance
When detected: Routine Inspection
Result: General Work Refused
Contributing factors: Environment - Non Weather Related; Company Policy; Aircraft; Human Factors
Primary problem: Company Policy

Narrative: I have been working for a Part XXX operator this year.  At the beginning of the season; when I was hired; I noted aggressive corrosion in multiple areas of the aircraft.  I also noted that some components were missing documentation from the logbooks; and other components were 'time expired.'When I made mention of these items to the certificate holder; I was told that the aircraft is 'public use' and that the airworthiness requirements do not apply.I was also told that if I don't like the way they operate; I can find a different job.  Well; I left a good job to come to this operation and it is too difficult to find decent jobs with the COVID employment downturn in general aviation; so I was stuck.I still refused to sign off an annual inspection so the operator had a different Inspector Authority (IA) sign it off.  The other IA never inspected the aircraft...just signed the logbooks.The aircraft operated all season in this condition.Now that the season is over; I was again told to do an annual inspection; so that it is ready for next season.  Instead; I turned in my notice.  I don't feel the aircraft is necessarily a danger to the public; however I also don't feel the aircraft is necessarily 'legal.'Maybe all this is acceptable in the Part XXX world.




Synopsis: Maintenance Inspector reported concerns with company signing off of annual inspections of aircraft with several known maintenance issues and discrepancies.
Date: 201903
Location: ZZZ.Airport, US
Aircraft: Commercial Fixed Wing
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Parked
Reporter organization: Air Carrier
Reporter function: Ramp
Human factors: Situational Awareness
Anomaly: Ground Event / Encounter Vehicle
Detector: Person Ground Personnel
When detected: Aircraft In Service At Gate
Result: Aircraft Aircraft Damaged
Contributing factors: Equipment / Tooling
Primary problem: Equipment / Tooling

Narrative: Setting up departure flight with the lead; picked up push tractor from [another] gate. I drove to gate ZZ; made left and drove on VSR (vehicle service road) of co-pilot side making sure to stay outside OSZ (operations service zone); then made left hand turn to position tractor in front of 737-700. As I approached aircraft; had to slow down to make sharp turn and avoid tow bars in the way. Got past those and then tried to stop [tractor] and the brakes failed to stop and it coasted toward plane and scratched bottom part of nose cone.




Synopsis: Ramp employee reported the tractor brakes failed while approaching the aircraft resulted in minor damage to the aircraft.
Date: 202010
Local time of day: 0001-0600
Aircraft: Commercial Fixed Wing
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Cruise
Airspace: Class A ZZZ
Reporter organization: Air Carrier
Reporter function: Flight Attendant (On Duty)
Reporter qualification: Flight Attendant Current
Human factors: Communication Breakdown
Second reporter function: Flight Attendant (On Duty)
Anomaly: Deviation / Discrepancy - Procedural Published Material / Policy; Flight Deck / Cabin / Aircraft Event Passenger Misconduct
Detector: Person Flight Attendant
When detected: In-flight
Result: General None Reported / Taken
Contributing factors: Environment - Non Weather Related; Human Factors
Primary problem: Human Factors

Narrative: Uniformed crew member was reminded by both flight attendants multiple times to comply with our mask policy and keep her mask over both her nose and mouth. At one point FA B walked by her and reminded her politely to wear her mask; it was off at this point; and the employee responded 'clearly I'm drinking this water; thank you.' Unfortunately the passenger was not drinking water when she was reminded or else FA B would have not said anything to her. The employee was given a warning at this point; after both FAs reminded her at least one more time. Totaling 6 times she was kindly reminded. The Flight Deck was notified after the warning was given and the passenger complied after the warning was given.


Second narrative: A uniformed flight crew passenger would not comply with our company mask policy for either FA's. We both asked her three times to comply with our mask policy. And our next step was to check one last time to see without asking her again if she complied on her own; and she had not. We then issued her a warning; a fresh mask and ask if she had any more questions or excuses. Then she complied the rest of the flight.


Synopsis: Air Carrier flight attendants reported a uniformed passenger company employee was non-compliant with face mask policy.
Date: 201504
Local time of day: 0601-1200
Location: HOU.Tower, TX
Weather elements / visibility: Windshear; Thunderstorm
Light: Daylight
Aircraft: Any Unknown or Unlisted Aircraft Manufacturer
Airspace: Class B HOU
ATC / advisory: Tower HOU
Reporter organization: Government
Reporter qualification: Air Traffic Control Fully Certified
Human factors: Distraction
Anomaly: ATC Issue All Types; Inflight Event / Encounter Weather / Turbulence
Detector: Person Air Traffic Control
Result: Air Traffic Control Issued Advisory / Alert
Contributing factors: ATC Equipment / Nav Facility / Buildings
Primary problem: ATC Equipment / Nav Facility / Buildings

Narrative: Major thunderstorms with tornado warnings and high winds with wind shear again come through Houston; Texas; with major airlines landing and taking off from HOU.  Tower crew is having to listen to the ASOS on the telephone; distracting the controllers from their jobs because the wind indicators are down still. Low level wind shear and wind shifts accompany the extreme weather over the weekend and the wind indicators are still down. Fix the wind indicators and have a better system in place; and why isn't there someone working on this issue over the weekend until it's fixed.  This is a safety of flight issue.




Synopsis: A Houston Controller reports of having to listen to the ASOS on the telephone because the wind indicators are out of service. The Controller reports this is a distraction. There was severe weather in the area.
Date: 202110
Local time of day: 1801-2400
Location: PHX.Airport, AZ
Aircraft: B737-800
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Landing
Airspace: Class B PHX
ATC / advisory: Tower PHX
Second aircraft: Airbus Industrie Undifferentiated or Other Model
Reporter organization: Air Carrier
Reporter function: Captain; Pilot Not Flying
Reporter qualification: Flight Crew Air Transport Pilot (ATP)
Anomaly: Inflight Event / Encounter Wake Vortex Encounter; Inflight Event / Encounter Unstabilized Approach
Detector: Person Flight Crew
When detected: In-flight
Result: Flight Crew Executed Go Around / Missed Approach; Flight Crew Took Evasive Action
Contributing factors: Environment - Non Weather Related; Procedure
Primary problem: Procedure

Narrative: Landing behind an Airbus aircraft on runway 26 in Phoenix with a 6 knot wind from the north we encountered wing tip vortex turbulence and induced roll.  The copilot made an excellent choice and performed at aborted landing/go-around.  We re-entered the pattern on downwind and received vectors for an uneventful landing.  Approach Control apologized for vectoring us too close behind the Airbus and Tower had asked them to expedite off the runway.  We were at least 2 minutes behind the preceding aircraft. If the wind hadn't been from the north; I don't think we would have had any problem; but the copilot did a great job!  Many passengers thanked [us] for being safe.  Thought that the copilot made an excellent early decision to go around instead of trying to 'save' it.




Synopsis: B737-800 Captain reported executing a go-around after encountering wake turbulence in trail of an Airbus just before landing at PHX.
Date: 202005
Local time of day: 1201-1800
Location: ZZZ.Airport, US
Flight conditions: IMC
Weather elements / visibility: Rain
Light: Night
Aircraft: MD-11
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Flight phase: Parked
Airspace: Class B ZZZ
Aircraft component: Main Gear Wheel
Component problem: Improperly Operated
Reporter organization: Air Carrier
Reporter function: Technician
Reporter qualification: Maintenance Powerplant; Maintenance Airframe
Human factors: Distraction
Anomaly: Aircraft Equipment Problem Less Severe; Deviation / Discrepancy - Procedural Maintenance; Deviation / Discrepancy - Procedural Published Material / Policy
Detector: Person Maintenance
When detected: Aircraft In Service At Gate
Result: Aircraft Aircraft Damaged; General Maintenance Action
Contributing factors: Incorrect / Not Installed / Unavailable Part; Procedure; Weather
Primary problem: Procedure

Narrative: I was changing 3 main tires and a nose tire on a MD-11. It was raining; dark and pretty windy. I was just informed today that apparently on one of the tires I changed (#6); that the axle sleeve (which should not come off) did slide off with the old tire and all I can say is that I simply did not notice that it stuck in the tire or noticed when I packaged up the old tire that it was in the tire assembly. The aircraft departed my station the next day to ZZZ. There it had a #6 anti-skid issue and they had to change the transducer as it had been damaged. It flew to ZZZ1 next and when it arrived to the gate; the hubcap was broken; the anti-skid transducer again was damaged; tire pressure connector mangled and it was discovered the axle sleeve was missing. I knew the aircraft had been down in ZZZ1 for the incident; but it was not known to me until a few weeks later that the axle sleeve had been found at the vendor in the tire that I had changed in ZZZ2.Well; AMM 32-XX-XX-X-X does tell you to inspect the axle sleeve to ensure that the tab at the outboard end is not broken and is bent into the axle slot to prevent sleeve rotation. I obviously did not do that. To prevent this form of event from happening again; I need to slow down and examine my work more closely when I am doing repetitive jobs.




Synopsis: Technician reported overlooking the axle sleeve being removed with the old tire and wheel assembly and not reinstalled; causing repetitive damage to the aircraft at other stations.
Date: 202112
Aircraft: B737-800
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Parked
Aircraft component: AC Generator/Alternator
Component problem: Malfunctioning
Reporter organization: Air Carrier
Reporter function: Technician
Reporter qualification: Maintenance Powerplant; Maintenance Airframe
Human factors: Time Pressure; Situational Awareness; Troubleshooting
Anomaly: Aircraft Equipment Problem Critical; Deviation / Discrepancy - Procedural Published Material / Policy; Deviation / Discrepancy - Procedural FAR; Deviation / Discrepancy - Procedural Maintenance
Detector: Person Flight Crew
When detected: In-flight
Result: Flight Crew Returned To Departure Airport; General Maintenance Action
Contributing factors: Procedure; Human Factors; Aircraft
Primary problem: Aircraft

Narrative: Aircraft X air return for Engine 2 issue. [Aircraft] had IDG checks on both engines. Had engine cowls open; no faults noted at time.




Synopsis: Technician reported an air turn back for engine #2 issues and performed IDG oil level checks with both engine cowls open. No defects were noted.
Date: 201402
Local time of day: 1201-1800
Location: S56.TRACON, UT
Flight conditions: VMC
Light: Daylight
Aircraft: Small Aircraft; Low Wing; 1 Eng; Fixed Gear
Operator: Other Flight School
Operating under: Part 91
Flight plan: None
Mission: Training
Flight phase: Cruise
Airspace: Class E ZLC
ATC / advisory: TRACON S56
Second aircraft: Small Aircraft; Low Wing; 1 Eng; Retractable Gear
Reporter organization: Other Flight School
Reporter function: Instructor
Reporter qualification: Flight Crew Commercial; Flight Crew Flight Instructor; Flight Crew Instrument; Flight Crew Multiengine
Human factors: Communication Breakdown; Distraction; Workload; Time Pressure
Anomaly: ATC Issue All Types; Conflict NMAC; Deviation / Discrepancy - Procedural Published Material / Policy
Detector: Person Flight Crew
When detected: In-flight
Result: Flight Crew Took Evasive Action
Contributing factors: Procedure; Environment - Non Weather Related
Primary problem: Ambiguous

Narrative: This was a training flight for an instrument flight. We were reviewing DME holds from the FFU VOR to the east. Altitude was 7;500 FT MSL. Also we were on Salt Lake Approach receiving traffic advisories. We initially got a call out for the other traffic; ATC advised us of the traffic south of our position we were a heading of roughly 270. The other traffic was also on radar with Salt Lake Approach talking. The next call from ATC; he recommended a turn to the south to avoid the traffic. I continued to look for the traffic and turned south bound. The next call from ATC was to turn to the South West to avoid the traffic. Once we reached a heading of roughly 220 a traffic alert from my TWAS system inside the aircraft came up for the first time for this aircraft; the target was directly on my position and indicating 0 feet of difference. At that same moment I spotted the aircraft to my left side same altitude less than 100 feet horizontally opposite direction. By the time I had seen the traffic their wing was slightly ahead mine; because of that there was no time to react and turn to the right. The other aircraft had seen me at the last moment and started a hard turn to there right to avoid. The other traffic advised ATC that they saw me and that we were very close. In my opinion if the other aircraft did not see me at the last moment there would have been a collision.




Synopsis: Two aircraft near FFU had a near miss at 7;500 FT after Salt Lake Approach Control pointed out their mutual traffic and issued suggest headings but still neither aircraft saw the other until the last second.
Date: 201712
Local time of day: 1801-2400
Location: ZZZZ.Airport, FO
Light: Night
Aircraft: MD-11
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Cargo / Freight / Delivery
Flight phase: Takeoff / Launch
ATC / advisory: Tower ZZZ
Aircraft component: Hydraulic System
Component problem: Malfunctioning
Reporter organization: Air Carrier
Reporter function: Captain; Pilot Not Flying
Reporter qualification: Flight Crew Air Transport Pilot (ATP)
Human factors: Situational Awareness
Anomaly: Aircraft Equipment Problem Less Severe
Detector: Person Flight Crew
When detected: In-flight
Result: Air Traffic Control Provided Assistance; Flight Crew Returned To Departure Airport; Flight Crew Landed in Emergency Condition
Contributing factors: Aircraft
Primary problem: Aircraft

Narrative: After rotation; had level 2 HYD1 FAIL. Checking hydraulic page; HYD1 quantity 0.3. Elected to return to [departure airport]. Accepted vectors to runway. Landed without incident. Obtained a tow to the gate. [There was] hydraulic leak in elevator actuator.




Synopsis: MD-11 Captain reported returning to departure airport when Hydraulic System 1 quantity dropped after takeoff.
Date: 201401
Local time of day: 0601-1200
Location: ABQ.Airport, NM
Flight conditions: VMC
Aircraft: Commercial Fixed Wing
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Flight phase: Initial Approach
Airspace: Class C ABQ
ATC / advisory: TRACON ABQ
Aircraft component: GPWS
Component problem: Malfunctioning
Reporter organization: Air Carrier
Reporter function: Captain; Pilot Flying
Human factors: Distraction
Anomaly: Aircraft Equipment Problem Less Severe; Inflight Event / Encounter CFTT / CFIT
Detector: Automation Aircraft Terrain Warning; Person Flight Crew
When detected: In-flight
Result: General None Reported / Taken
Contributing factors: Aircraft
Primary problem: Aircraft

Narrative: During approach in visual conditions to Runway 21 in ABQ was cleared from STAR arrival procedure to descend in for visual approach. Terrain was clearly in sight; and briefed. During base to final GPWS alerted with 'Pull Up' command. Crew coordination was excellent during arrival and approach and both pilot not flying and pilot flying (Captain) confirmed NO Conflict with terrain; GPWS then quickly announced Clear of Conflict and we landed without incident.




Synopsis: An Air Carrier flight crew in VMC conditions during descent for landing quickly determined a GPWS 'Pull up' warning was erroneous and continued their approach and landing without further event.
Date: 202001
Local time of day: 1201-1800
Location: ZLA.ARTCC, CA
Flight conditions: VMC
Light: Daylight
Aircraft: Cessna 150
Operator: Personal
Operating under: Part 91
Flight plan: VFR
Mission: Personal
Flight phase: Cruise
Aircraft component: Engine Air
Component problem: Failed
Reporter organization: Personal
Reporter function: Single Pilot
Reporter qualification: Air Traffic Control Fully Certified; Flight Crew Instrument; Flight Crew Multiengine; Flight Crew Commercial
Human factors: Workload; Time Pressure
Anomaly: Aircraft Equipment Problem Critical
Detector: Person Flight Crew
When detected: In-flight
Result: Air Traffic Control Provided Assistance; Flight Crew Landed in Emergency Condition; Flight Crew Overcame Equipment Problem; Flight Crew Diverted; General Maintenance Action
Contributing factors: Aircraft
Primary problem: Aircraft

Narrative: I was VFR at 8500 when my aircraft experienced a sudden loss of power. I immediately applied carburetor heat and slightly enriched the mixture; which kept the engine running. Continuously tried a variety of settings with mixture; throttle; and carb heat. When carb heat was removed; the engine seemed to die. After a few minutes and a few hundred feet of descent; I definitively determined this was not carburetor icing and elected to divert to ZZZ airport and [advised ATC]. I suspected some sort of blockage; either to airflow or possible contaminated fuel (though I had sampled the fuel at the last point of departure with negative results). I was able to control the descent and land at ZZZ without incident; where I informed the Controller of my safe arrival. A&P on field inspected the aircraft and found the intake air filter was clogged and replaced the filter which solved the problem; aircraft performed satisfactorily on further runup and was returned to service.




Synopsis: C150 pilot reported that a loss of engine power in cruise resulted in a diversion.