elihoole/asrs-aviation-reports huggingface dataset:
Date: 201512
Local time of day: 1801-2400
Location: ZZZ.Airport, US
Light: Night
Airspace: Class C ZZZ
ATC / advisory: Tower ZZZ
Aircraft component: Transponder
Component problem: Improperly Operated
Reporter organization: Government
Reporter function: Local
Reporter qualification: Air Traffic Control Fully Certified
Human factors: Communication Breakdown; Distraction; Troubleshooting; Workload
Anomaly: ATC Issue All Types; Deviation / Discrepancy - Procedural FAR; Deviation / Discrepancy - Procedural Published Material / Policy
Detector: Person Air Traffic Control
Result: General Maintenance Action
Contributing factors: ATC Equipment / Nav Facility / Buildings; Human Factors; Procedure
Primary problem: Procedure

Narrative: There are facilities for offices; maintenance and assembly many airports.  There has been an ongoing issue with a beacon code (transponder) apparently emanating from the ramp or facilities. This creates clutter on the radar scope for the controllers and located adjacent to Runway with departures; arrivals and over flights. Additionally there is the risk of an aircraft receiving a TCAS alert. Normally a 1200 code at field elevation (900) feet radiates but on other occasions at 7700 code and a 0600 code has radiated. The facility has contacted a maintenance facility numerous times to resolve such a situation.  A flight was cleared for takeoff. The stationary target over a local facility was squawking 0600 and rapidly climbing and descending from 900 feet to 9;700 feet. The departure was advised of the target by local control. A collision alert alarmed on the radar scope. The traffic was not a factor (could not playback situation on the falcon).  The south radar controller asked the pilot if he received a TCAS RA and the pilot stated no.  I was working another position and saw the situation take place. The overall FLM in charge of the shift attempted to call the contacts at the facility and got voice mail. He filed an MOR on the situation. Tech Ops was shown the target on one occasion and stated it appeared to be an aircraft squawking a beacon code on the ramp. If these are transponder equipment tests; they are not coordinated with tower.  This target clutters up the scope and has the potential to cause TCAS RA's to occur. This appears to be an issue with the local maintenance facility.  Flight standards should contact the operator and resolve the issue and follow up to ensure it is eliminated. Tech Ops should also examine the issue to ensure it is not radar related.




Synopsis: An ATC Tower Controller reported an aircraft maintenance facility located on airport tests transponders without coordinating with ATC which can interfere with normal flight operations.
Date: 201507
Local time of day: 0001-0600
Location: ZZZ.Airport, US
Light: Dawn
Aircraft: B737-900
Operator: Air Carrier
Operating under: Part 121
Mission: Passenger
Flight phase: Parked
Reporter organization: Air Carrier
Reporter function: Inspector
Reporter qualification: Maintenance Airframe; Maintenance Powerplant
Human factors: Communication Breakdown; Situational Awareness; Time Pressure
Anomaly: Deviation / Discrepancy - Procedural FAR; Deviation / Discrepancy - Procedural Maintenance; Deviation / Discrepancy - Procedural Published Material / Policy
Detector: Person Maintenance
When detected: In-flight
Result: General None Reported / Taken
Contributing factors: Human Factors; Company Policy; Procedure
Primary problem: Human Factors

Narrative: Aircraft supervisor approached me in my office and said he needed the inspector slot on log page for the #1 engine change signed for. I asked him if all the paper work was complete and the job was complete and his reply was yes and that the aircraft was at the terminal being loaded for its [next] trip. After I signed the log book I went to review the engine change paper work package when I discovered the Engine change installation task was not completed. By the time this discovery took place the aircraft already [departed].




Synopsis: A Maintenance Inspector discovered that the Maintenance Supervisor was incorrect when he reported that all of the engine change paperwork was completed when he requested the final signoff.
Date: 201606
Local time of day: 1201-1800
Location: ZZZ.Airport, US
Flight conditions: VMC
Light: Daylight
Aircraft: B737-700
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Climb
Airspace: Class B ZZZ
ATC / advisory: TRACON ZZZ
Aircraft component: Powerplant Lubrication System
Component problem: Failed
Reporter organization: Air Carrier
Reporter function: Captain
Reporter qualification: Flight Crew Air Transport Pilot (ATP)
Human factors: Distraction; Workload
Second reporter function: First Officer
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: Flight Crew Inflight Shutdown; Flight Crew Took Evasive Action; Flight Crew Returned To Departure Airport; Flight Crew Landed in Emergency Condition; General Maintenance Action
Contributing factors: Aircraft
Primary problem: Aircraft

Narrative: During climb out departing at approximately 4;500 feet; the number two engine oil quantity decreased to zero. Shortly after; the oil pressure also plunged to zero. The associated Low Oil Pressure light illuminated; and we proceeded to the QRH; referencing the Low Oil Pressure Procedure; and then the Engine Shutdown Procedure. We notified ATC of the problem; and requested vectors for a return to [departure airport]; as well as requested Fire Rescue to be notified. Fuel and souls onboard were given to ATC. The Flight Attendant (FA) were notified and briefed. The Passengers were briefed on the reason for the return.Ground Ops was notified; and asked to relay a message to Dispatch of the circumstances. The flight plan was amended at (time) for the return to the departure airport. All QRH procedures were followed to completion; to the best of our ability. The [flight computer] was used to run flaps 15; single engine; landing dry runway. Landing weight was approximately 124;000 pounds; maximum landing gross weight for our aircraft was 128;000 pounds. Thus overweight conditions were not a factor. Only one item was omitted by accident. Due to the high task loading; there was the failure to [notify] ATC. I simply got busy and forgot.I do believe ATC was under the assumption that we were an aircraft [in distress]; as they provided expedited service in every manner. After landing we proceeded to the large ramp just off of the Runway; and had Airport Fire Rescue inspect the number two engine for abnormal signs of debris or high heat signatures. None were found; so we proceeded to the gate. The entire Crew did a professional job of taking care of this situation. The Passengers seemed to be of normal conditions as they exited the aircraft.


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


Synopsis: A B737-700 lost oil quantity and pressure shortly after takeoff. The crew followed the QRH; shut the engine down and returned to the departure airport for an uneventful single engine landing.
Date: 202105
Local time of day: 1801-2400
Location: ZZZ.ARTCC, US
Flight conditions: VMC
Aircraft: B737-800
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Cruise
Airspace: Class A ZZZ; Class B ZZZ2
ATC / advisory: Center ZZZ
Aircraft component: Autoflight System
Component problem: Failed
Reporter organization: Air Carrier
Reporter function: Captain; Pilot Flying
Reporter qualification: Flight Crew Air Transport Pilot (ATP); Flight Crew Instrument; Flight Crew Multiengine
Human factors: Fatigue; Distraction; Human-Machine Interface
Anomaly: ATC Issue All Types; Aircraft Equipment Problem Critical; Conflict Airborne Conflict; Deviation / Discrepancy - Procedural Published Material / Policy; Deviation / Discrepancy - Procedural FAR
Detector: Person Flight Crew
When detected: In-flight
Result: Air Traffic Control Provided Assistance; Air Traffic Control Separated Traffic; Flight Crew Overcame Equipment Problem; Flight Crew Landed As Precaution; Flight Crew Requested ATC Assistance / Clarification; General Flight Cancelled / Delayed; General Maintenance Action
Contributing factors: Aircraft; Software and Automation; Procedure
Primary problem: Aircraft

Narrative: At XA:55Z the master caution light; auto pilot disconnect aural  warning and IRS annunciation light activated. The FO was the PF and immediately began to hand fly the aircraft. As PM; I verified the aircraft was stable and performed QRH XX.X IRS fault. After completing the required items and discussing all of the impact items; I sent ATC a CPDLC message as to our loss of navigation equipment and inability to remain in RVSM airspace due to the loss of the auto pilot. ATC instructed to remain at FL370 due to traffic. We called dispatch via SATCOM and relayed our current situation and reiterated our need to use the ILS RWY XX into ZZZ due to the loss of RNAV capabilities. After a conference call with Operations and Maintenance; we continued to ZZZ and landed uneventfully via the ILS RWY XX.We split the flying duties to avoid fatigue (30 minute intervals). ATC was given 2 hours to plan our arrival to the opposite runway; and they did an exemplary job. ZZZ1 was built in route 2 as our primary divert airport.




Synopsis: Captain reported total loss of the autoflight systems required close coordination with ATC for traffic separation and special flight handling due to loss of RVSM and RNAV capabilities.
Date: 201407
Local time of day: 1801-2400
Location: ZMA.ARTCC, FL
Light: Night
Aircraft: B747 Undifferentiated or Other Model
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Flight phase: Climb
Airspace: Class A ZMA
ATC / advisory: Center ZMA
Reporter organization: Government
Reporter function: Handoff / Assist; Enroute
Reporter qualification: Air Traffic Control Fully Certified
Human factors: Communication Breakdown; Other / Unknown; Confusion
Second reporter function: Enroute; Trainee
Anomaly: ATC Issue All Types; Inflight Event / Encounter Weather / Turbulence
Detector: Person Air Traffic Control
When detected: In-flight
Result: Air Traffic Control Provided Assistance
Contributing factors: ATC Equipment / Nav Facility / Buildings
Primary problem: ATC Equipment / Nav Facility / Buildings

Narrative: We were working a day involving a lot of weather resulting in numerous point outs to other sectors/facilities and coordination.  My R side and I were both on and off the line coordinating.  At one of these times I had just turned my receiver back on and my R side was coordinating with another controller and I heard Aircraft X was calling.  When my R side finished coordinating I told him I heard Aircraft X calling. My R side then climbed Aircraft X and we both continued working.  A few minutes later sector 23 that owns below our altitude stratum called asking if we were showing we had track control of Aircraft X. I said that we did and she asked if he was climbing and I said he was. She then said that they must have skipped her and he was our control. I didn't understand what she meant at the time and the CIC from her area later came over and explained that they were having an automation area with Orlando Approach.  The CIC explained this was a systemic issue they had had in the past and ERAM had caused it to start happening again where we auto acquire the aircraft.  I do not know how he was shipped to us because I know Orlando Approach wouldn't have our frequency or if any other sectors worked him after Orlando and prior to us acquiring the hand off. This situation definitely should be further investigated and I believe all employees should be briefed of the possibility of it happening again if this is truly a systematic error that may or has happened before/again. Also we as a radar team were wrong by not verifying Aircraft X's assigned altitude at check in.


Second narrative: My sector did not have track control or approve a point-out of Aircraft X when the aircraft entered our airspace. My understanding is that the aircraft was auto-flashed by the computer in F11 (Orlando Approach).Make sure the computer does not auto flash aircraft to the wrong sectors.


Synopsis: ZMA controllers describe situation where the sector has an aircraft that they have control of that never talked to the lower sector and are wondering how the aircraft got on his frequency.
Date: 202011
Local time of day: 1801-2400
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: Flight Attendant (On Duty)
Reporter qualification: Flight Attendant Current
Anomaly: Deviation / Discrepancy - Procedural Published Material / Policy
Detector: Person Flight Attendant
When detected: Taxi
Contributing factors: Company Policy; Environment - Non Weather Related
Primary problem: Environment - Non Weather Related

Narrative: I did not remove my mask to during demo to show oxygen mask use because passenger in X1; was eating and I cannot socially distance while he was not wearing a mask. I did not feel safe removing my mask because of risk of COVID exposure.  He wasn't wearing a mask while I was in close proximity to him.I recommend not removing face mask during oxygen demo. We touch shared safety cards in the seat back for the demo and then directly touch our masks to remove to demo the oxygen mask. There is no opportunity to sanitize in between touching dirty; shared items before touching our masks which are supposed to be done with clean hands. This is unsafe during a pandemic and can spread COVID.




Synopsis: Flight Attendant reported not removing the face mask during the safety demonstration due to the close proximity of a passenger with face mask off while eating.
Date: 201207
Local time of day: 1201-1800
Location: ZZZ.Airport, US
Flight conditions: VMC
Weather elements / visibility: 15
Light: Daylight
Aircraft: RV-8
Operator: Personal
Operating under: Part 91
Flight plan: None
Mission: Personal
Flight phase: Landing
ATC / advisory: CTAF ZZZ
Aircraft component: Nosewheel Steering
Component problem: Malfunctioning
Reporter organization: Personal
Reporter function: Pilot Flying; Single Pilot
Reporter qualification: Flight Crew Air Transport Pilot (ATP); Flight Crew Flight Instructor; Flight Crew Multiengine
Human factors: Confusion; Distraction; Time Pressure; Training / Qualification; Troubleshooting
Anomaly: Inflight Event / Encounter Loss Of Aircraft Control
Detector: Person Flight Crew
When detected: Other Landing Roll
Result: Aircraft Aircraft Damaged; General Maintenance Action
Contributing factors: Aircraft
Primary problem: Aircraft

Narrative: I was landing on Runway 26. It was day time VMC; the winds were pretty much down the runway at less than 10 KTS. I executed a normal 3 point landing; the aircraft rolled straight for just a few seconds and then veered hard to the right and departed the runway. I had applied full left rudder; left brake; and right aileron to stop the aircraft without effect. When the aircraft departed the runway; it slid sideways in dirt until hitting a ridge where the damage occurred. No personal injuries and the aircraft was slightly damaged. I have over 2;000 hours in conventional gear aircraft and have never seen one veer so hard without some sort of either impute or external force. I really have no idea what happened. Subsequent web posts lead me to believe that there is a main gear toe issue that leads to such a problem. Having had my wheel pants off and visually inspecting the main tires; I did not notice any abnormal wear on the tires. But I will have the repair facility check the toe in/out and the tailwheel steering.




Synopsis: A RV8's nose wheel is suspected of causing the aircraft to depart the runway after landing when it veered hard right and neither braking; rudder nor aileron inputs could counter the turn.
Date: 201512
Local time of day: 1801-2400
Location: NCT.TRACON, CA
Flight conditions: Mixed
Weather elements / visibility: Thunderstorm; Rain; Turbulence; 1
Light: Night
Aircraft: B737 Undifferentiated or Other Model
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Descent
Airspace: Class B SFO
ATC / advisory: TRACON NCT
Aircraft component: Tablet
Component problem: Malfunctioning
Reporter organization: Air Carrier
Reporter function: Captain; Pilot Flying
Reporter qualification: Flight Crew Air Transport Pilot (ATP)
Human factors: Situational Awareness; Distraction
Anomaly: Aircraft Equipment Problem Less Severe; Deviation - Altitude Undershoot; Deviation / Discrepancy - Procedural Clearance
Detector: Person Air Traffic Control
When detected: In-flight
Result: Flight Crew Returned To Clearance; Flight Crew Became Reoriented
Contributing factors: Human Factors; Aircraft
Primary problem: Human Factors

Narrative: Arriving from the oceanic sector into the SF Bay Area. I was both Pilot Flying (PF) and PIC. My iPad; used for approach chart data; froze. I could not scale or change charts. OAK (destination) had originally reported calm wind and 10 sm visibility and I was going to use the RNAV-Y 28L. The updated weather placed TRW over the airport and the wind was 15 gusting to 35; visibility 1 sm in heavy rain; so I was trying to shift to the ILS 30. As it was a round trip to OAK; we had three pilots in the cockpit and the other 2 had functioning iPads. I switched with the third pilot in the jump seat and had a functioning iPad quickly. This is our home base; we are all VERY familiar with the approach; but wanted it displayed to follow proper SOP's.As we crossed the OSI VOR; the Pilot Monitoring (PM)/SIC pointed to the altitude alerter which he had set to 6;000 feet per received NORMAL clearance. I did not realize that we were still at 7;000' and ATC had called a second time telling us to descend. There was no immediate conflict. No evasive maneuvering was taken or noted by any aircraft or ATC. We descended as instructed but may have delayed our descent by 30 seconds due to my distraction with the iPad.Subsequent to this; I contacted Jeppesen; the manufacturer of the software used in the iPad. They noted it was a known problem; they were working on a revision and provided a workaround in the meantime. The workaround was transmitted that evening to all company pilots to prevent further problems until a software fix is released.




Synopsis: B737 Captain reported undershooting his altitude clearance when he was distracted by a malfunctioning iPad.
Date: 202007
Location: ZZZ.Airport, US
Flight conditions: VMC
Aircraft: Commercial Fixed Wing
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Flight phase: Taxi
ATC / advisory: Ground ZZZ
Reporter organization: Air Carrier
Reporter function: Captain; Pilot Flying
Reporter qualification: Flight Crew Air Transport Pilot (ATP)
Human factors: Situational Awareness
Second reporter function: Pilot Not Flying; First Officer
Anomaly: Deviation / Discrepancy - Procedural Clearance; Ground Incursion Taxiway
Detector: Person Air Traffic Control
When detected: Taxi
Result: Air Traffic Control Issued New Clearance; Air Traffic Control Provided Assistance
Contributing factors: Environment - Non Weather Related; Human Factors
Primary problem: Human Factors

Narrative: First flight in over 6 weeks only second time in ZZZ in over 5 years. Have flown only 3 other legs since CQMV in March and those were in May. Missed the turn to [Taxiway] R from [Taxiway] B had to turn around and use new taxi route to get to runway.  I was under the impression R was further down B. We also had a runway change from plan. I may have still had that route in mind when I missed the turn.


Second narrative: On taxi out we received [an] unexpected runway for departure. Taxi instructions were A; AX; B; R ; [Runway] XR. The FMC was reprogrammed accordingly and we got our new takeoff data. As we were on B I asked the Captain if I could begin the before takeoff checklist. As I was doing the checklist we passed the right turn to R. Ground advised us of the error and gave us new taxi instructions. No other problems were noted and taxied out the rest of the way to XR.


Synopsis: Air carrier flight crew reported a taxiway incursion.  Captain cited lack of recent flying.
Date: 201503
Local time of day: 1201-1800
Location: N07.Airport, NJ
Flight conditions: VMC
Weather elements / visibility: 20
Light: Daylight
Aircraft: Commander 112/A/B/TC
Operator: Personal
Operating under: Part 91
Flight plan: None
Mission: Ferry / Re-Positioning
Flight phase: Landing
Aircraft component: Nose Gear
Component problem: Malfunctioning
Reporter organization: Personal
Reporter function: Single Pilot
Reporter qualification: Air Traffic Control Fully Certified; Flight Crew Multiengine; Flight Crew Air Transport Pilot (ATP); Flight Crew Flight Instructor; Flight Crew Instrument
Anomaly: Aircraft Equipment Problem Critical; Ground Event / Encounter Ground Strike - Aircraft
Result: Aircraft Aircraft Damaged; General Maintenance Action
Contributing factors: Aircraft
Primary problem: Aircraft

Narrative: I departed delivering an AC11 after maintenance on landing gear. Everything seemed normal. Approaching the pattern from the West I lowered the landing gear. I had initially not seen a green nose gear indication. While on the downwind I recycled the gear and got a positive indication 3 green and conducted a low approach requesting others on the ground to advise the status of the gear. Numerous responses were in the affirmative that it was down. I landed normally while coasting and decelerating; I gently applied brake pressure and felt the nose come down slightly; thinking the oleo strut must be settling after been serviced. I applied a tad more brake pressure and then the nose fell; the prop hit the ground and aircraft slid.The AC11 had just completed service on the oleo struts and oil change as far as I know. I was well rested.




Synopsis: The pilot of a Rockwell Commander experienced a nose landing gear collapse during landing rollout. The aircraft had just had the landing gear serviced.