elihoole/asrs-aviation-reports huggingface dataset:
Date: 201407
Local time of day: 1801-2400
Location: ZLC.ARTCC, UT
Light: Night
Aircraft: Any Unknown or Unlisted Aircraft Manufacturer
Airspace: Class A ZLC
ATC / advisory: Center ZLC
Reporter organization: Government
Human factors: Confusion; Communication Breakdown; Distraction; Troubleshooting; Situational Awareness; Other / Unknown
Anomaly: ATC Issue All Types
Detector: Person Air Traffic Control
Contributing factors: ATC Equipment / Nav Facility / Buildings
Primary problem: ATC Equipment / Nav Facility / Buildings

Narrative: For the second time today and 3rd time (that I know of) in last two months; the Voice Switching System malfunctioned on a sector; leaving the Controller no way to communicate for 2 min and 35 sec.  I was CIC when the Controller called me over and said that he had lost communications on Sector 8.  I had the same problem a few hours earlier while I was working the sector (See report #).  The transmitter sites were selected properly.  The 'RCVR ON' font in the middle of the green field that shows the receiver and transmitters were selected were flashing alternately from black to red.  The Controller tried the BUEC [Back up radio] with no success. The Controller unplugged and tried transmitting from the D-Side with no success.  Shortly after 2 minutes the problem resolved itself and communication resumed.I do not know of any recommendations.




Synopsis: ZLC Controller reports of Voice Switch System malfunctioning for the third time in three months that he knows about.  The equipment then it resets itself and works fine.
Date: 201709
Local time of day: 0601-1200
Location: ZZZ.Airport, US
Flight conditions: Mixed
Weather elements / visibility: 8
Light: Daylight
Aircraft: B737-700
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Initial Climb
Airspace: Class B ZZZ
ATC / advisory: Tower ZZZ
Aircraft component: Turbine Engine
Component problem: Malfunctioning
Reporter organization: Air Carrier
Reporter function: Captain; Pilot Flying
Reporter qualification: Flight Crew Air Transport Pilot (ATP)
Second reporter function: First Officer; Pilot Not Flying
Anomaly: Aircraft Equipment Problem Less Severe; Inflight Event / Encounter Bird / Animal
Detector: Person Flight Crew
When detected: In-flight
Result: Aircraft Aircraft Damaged; Flight Crew Landed in Emergency Condition; Flight Crew Returned To Departure Airport
Contributing factors: Environment - Non Weather Related
Primary problem: Environment - Non Weather Related

Narrative: After takeoff; we had just retracted the landing gear and were accelerating when; at the last second; I saw a black dot ahead of us in our turn left to a 200 heading. It appeared to be a bird. I tried to pull the nose up to climb above it; but it wheeled up; put its brakes on by pulling its wings back and then dropped off to the right. It entered our right engine and we immediately had a loud buzzing noise along with engine vibration at about 3.5 to 4 on the number 2 engine. I checked the engine N1s and N2s and the engine was still rotating; but the vibration continued unchecked. My First Officer and I discussed the parameters as I initially thought to call for the severe damage checklist; but instead elected to call for the engine vibration checklist as the engine was still running.After retarding the throttle to idle; the vibrations subsided. I elected to keep the engine running; but land configured for a single engine landing with flaps at 15 just in case the engine failed at any point. Landing and rollout were uneventful. I shut down number 2 engine after landing and had the fire trucks check out our number 2 engine for leaks or damage and clear us to taxi. At the gate; the damage to the fan blades on the rotor was apparent.


Second narrative: We elected to return to the airport for landing.


Synopsis: B737-700 flight crew reported a bird strike after takeoff which resulted in damage to the right engine and return to departure airport.
Date: 201408
Local time of day: 0001-0600
Location: ZZZ.Airport, US
Flight conditions: IMC
Light: Daylight
Aircraft: Q400
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Initial Approach
Airspace: Class D ZZZ
ATC / advisory: Tower ZZZ
Aircraft component: Autoflight System
Component problem: Malfunctioning
Reporter organization: Air Carrier
Reporter function: Pilot Flying; Captain
Reporter qualification: Flight Crew Air Transport Pilot (ATP)
Human factors: Distraction; Confusion; Human-Machine Interface; Troubleshooting; Situational Awareness; Fatigue
Anomaly: Aircraft Equipment Problem Less Severe; Deviation / Discrepancy - Procedural Published Material / Policy; Inflight Event / Encounter Unstabilized Approach; Inflight Event / Encounter CFTT / CFIT
Detector: Automation Aircraft Other Automation; Person Flight Crew
When detected: In-flight
Result: Flight Crew Took Evasive Action; Flight Crew Became Reoriented
Contributing factors: Human Factors; Aircraft; Procedure
Primary problem: Procedure

Narrative: RNAV approach; at a fix inside the IF; lost VNAV and LNAV coupling. Instructed pilot not flying to engage NAV and VNAV; twice; all the while descending and not monitoring glidepath guidance. Was confused by the unexplained loss of coupling and distracted by trying to get it back. Although I knew the corrective action (missed approach or climb up closer to the Vpath so it will capture); for some reason; it did not occur to me at the time. I then realized that we were below glidepath; (possibly full scale; not sure now) just as we were breaking out of the clouds. No deviation calls or missed approach call from pilot not flying. Requested and received visual approach clearance; and landed. Might have been 2 previous nights of sub-optimal sleep; leading to some degree of degradation of alertness.




Synopsis: A Q400 VNAV and LNAV coupling disengaged on an RNAV approach inside the IF and while troubleshooting; the Captain lost situational awareness and descended more than one dot below the glidepath and fortunately became VMC for landing.
Date: 201709
Local time of day: 1201-1800
Location: ZZZ.Airport, US
Flight conditions: VMC
Light: Daylight
Aircraft: Regional Jet 700 ER/LR (CRJ700)
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Climb
Airspace: Class E ZZZ
ATC / advisory: TRACON ZZZ
Aircraft component: Autopilot
Component problem: Malfunctioning
Reporter organization: Air Carrier
Reporter function: Captain; Check Pilot; Pilot Not Flying
Reporter qualification: Flight Crew Air Transport Pilot (ATP)
Anomaly: Aircraft Equipment Problem Less Severe; Deviation - Altitude Excursion From Assigned Altitude
Detector: Person Flight Crew
When detected: In-flight
Result: Flight Crew Diverted; Flight Crew Landed As Precaution; Flight Crew Returned To Departure Airport
Contributing factors: Aircraft
Primary problem: Aircraft

Narrative: On climb out passing through approximately 7;000 FT; we received an 'EFIS COMP MON' caution message immediately followed by an AP TRIM IS ND (Autopilot Trim is Nose Down) caution message. I instinctively looked at the elevator trim display and observed the trim running nose down. I immediately pushed the stab trim disconnect and instructed the First Officer to do the same. I assumed control of the aircraft and told the First Officer to request a level off at 10;000 FT from ATC. As he was doing that I disconnected the Autopilot and found it to be excessively out of trim to the point that it was very difficult to control. I instructed him to run the Stab Trim Runaway checklist. Although we never heard the trim clacker; it seemed at the time the more prudent checklist to run.I had the First Officer request a turn back towards [departure airport] as a precaution although we had not committed yet to a return. During this turn I lost some altitude due to the excessive nose down trim as the primary cause but was able to gain it back. Upon further reflection; I decided to run the AP TRIM IS ND checklist because I felt that the Autopilot was the more probable cause. I reengaged the trim and trimmed the aircraft for level flight. We did not experience any trim runaway.After briefing the First Officer about the Autopilot possibly driving the trim nose down; a reengaged the Autopilot per the checklist. Immediately the trim started moving nose down so I once again disconnected the trim and the Autopilot. I reengaged the trim and left the Autopilot off. I determined the Autopilot had malfunctioned and since at this time we had full control of the aircraft; I elected to not [get priority handling]. I had the First Officer request a return to [departure airport] and instructed him to notify the flight attendants and to ACARS dispatch. We returned and landed uneventfully.




Synopsis: CRJ-700 Captain reported returning to departure airport after experiencing an autopilot malfunction that drove the stabilizer trim to a nose-down position.
Date: 202005
Location: ZZZ.Airport, US
Flight conditions: IMC
Weather elements / visibility: 10
Light: Daylight
Aircraft: RV-10
Operator: Personal
Operating under: Part 91
Flight plan: IFR
Mission: Personal
Flight phase: Cruise
Airspace: Class E ZZZ
ATC / advisory: Center ZZZ; TRACON ZZZ; Tower ZZZ
Aircraft component: AC Generator/Alternator
Component problem: Failed
Reporter organization: Personal
Reporter function: Single Pilot; Pilot Flying
Reporter qualification: Flight Crew Multiengine; Flight Crew Instrument; Flight Crew Flight Engineer; Flight Crew Air Transport Pilot (ATP); Flight Crew Flight Instructor
Human factors: Time Pressure
Anomaly: Aircraft Equipment Problem Critical; Deviation / Discrepancy - Procedural Published Material / Policy
Detector: Person Flight Crew
When detected: In-flight
Result: Flight Crew Landed in Emergency Condition; General Maintenance Action
Contributing factors: Aircraft
Primary problem: Aircraft

Narrative: While at cruise level at 9000 ft. on Radar Vector with Approach I experienced a complete electrical failure with a loss of single and only altenator. Backup instruments were available with battery power only. Available power was dependent on state of battery.I [advised ATC]. but was not sure transmission was received due to loss of VHF 1 and VHF 2. I had ground contact and remained clear of clouds and descended to 1500 ft. and landed without incident at ZZZ.After landing I telephoned Approach Control and reported my emergency; and that I had landed safely without incident at ZZZ. The [Approach] Controller assured me that he would notify Center and that I had landed safely at ZZZ. Weather conditions at time of electrical remained VFR and allowed me to land safely without incident.




Synopsis: RV-10 pilot reported complete electrical failure; causing a diversion and emergency landing.
Date: 202009
Local time of day: 1801-2400
Location: CMH.Airport, OH
Aircraft: Commercial Fixed Wing
Reporter function: Technician
Reporter qualification: Maintenance Airframe; Maintenance Powerplant
Anomaly: Deviation / Discrepancy - Procedural Published Material / Policy
Detector: Person Maintenance
Contributing factors: Equipment / Tooling; Human Factors
Primary problem: Equipment / Tooling

Narrative: While procuring a nitrogen cart to perform aircraft servicing I noticed that the nitrogen bottles loaded into the cart were painted green whereas they are usually an off white color. I immediately suspected that the cart was loaded with oxygen bottles and had to do a quick search to determine that the bottles were in fact nitrogen but they were painted green. The bottles were labeled with a small nitrogen sticker that was on the underside of the bottle. Please see the attached picture. This is a very dangerous condition that would lead to extreme aircraft damage and or human injury/death. A technician could accidentally mistake the nitrogen cart for oxygen and service and oxygen system with nitrogen. Also; a technician could become used to green nitrogen bottles and accidentally service a tire or strut with oxygen. I recommend that these bottles either be taken out of service and repainted; or wrapped with a 360 degree label stating its contents.




Synopsis: Aircraft technician reported nitrogen bottles improperly painted as oxygen bottles.
Date: 201409
Local time of day: 0601-1200
Location: ZZZ.Airport, US
Flight conditions: VMC
Light: Daylight
Aircraft: Champion Citabria 7ECA
Operating under: Part 91
Flight plan: None
Mission: Utility / Infrastructure
Flight phase: Cruise
Airspace: Class E ZZZ
Aircraft component: Exterior Pax/Crew Door
Reporter function: Pilot Flying; Single Pilot
Reporter qualification: Flight Crew Commercial; Flight Crew Instrument
Human factors: Other / Unknown
Anomaly: Aircraft Equipment Problem Less Severe
Detector: Person Flight Crew
When detected: In-flight
Result: Flight Crew Diverted; Flight Crew Landed As Precaution
Contributing factors: Human Factors; Aircraft
Primary problem: Ambiguous

Narrative: About 4 miles north east of [the airport] Citabria lost door inflight. Landing was made [the airport] after determining it was closest practical airport and normal landing was made successfully. Event occurred over unpopulated area.




Synopsis: Citabria pilot experiences the loss of the cabin door in flight over an unpopulated area. Pilot diverts to a suitable airport.
Date: 201510
Location: ZZZ.ARTCC, US
Flight conditions: VMC
Light: Daylight
Aircraft: Regional Jet 700 ER/LR (CRJ700)
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Descent
ATC / advisory: Center ZZZ
Reporter organization: Air Carrier
Reporter function: Captain; Pilot Not Flying
Reporter qualification: Flight Crew Air Transport Pilot (ATP)
Human factors: Confusion; Situational Awareness; Workload
Anomaly: ATC Issue All Types; Deviation - Altitude Crossing Restriction Not Met; Deviation / Discrepancy - Procedural Clearance
Detector: Person Flight Crew
When detected: In-flight
Result: Flight Crew Became Reoriented; Flight Crew Returned To Clearance
Contributing factors: Human Factors
Primary problem: Human Factors

Narrative: Center assigned (not charted) crossing restriction with inadequate time to prepare. To the best of my recollection; we were given about 10 miles to program a relatively complicated restriction into the FMS which then indicated an unacceptably high rate of descent would be necessary. I made two radio calls informing ATC that we would be unable to comply prior to reaching the problematic fix. No response was received.




Synopsis: The CRJ-700 Captain was unable to comply with a crossing restriction which was issued late by ATC.
Date: 201304
Local time of day: 1201-1800
Location: ZZZ.Airport, US
Aircraft: B737-800
Operator: Air Carrier
Operating under: Part 121
Mission: Passenger
Flight phase: Cruise
Airspace: Class A ZZZ
ATC / advisory: Center ZZZ
Aircraft component: Fuel Distribution System
Component problem: Malfunctioning
Reporter organization: Air Carrier
Reporter function: Pilot Not Flying
Anomaly: Aircraft Equipment Problem Critical
Detector: Person Flight Crew
When detected: In-flight
Result: Flight Crew Landed As Precaution; Flight Crew Diverted; General Declared Emergency
Contributing factors: Aircraft
Primary problem: Aircraft

Narrative: During Cruise flight the aircraft had an uncommanded fuel imbalance that could not be controlled. Referred to the QRH. Declared an emergency and diverted.




Synopsis: B737-800 crew discovers a fuel imbalance during cruise flight that cannot be corrected with QRH procedures. Crew diverts to the nearest suitable airport.
Date: 202004
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
Human factors: Other / Unknown
Anomaly: Deviation / Discrepancy - Procedural Published Material / Policy
Detector: Person Flight Attendant
Result: General None Reported / Taken
Contributing factors: Company Policy; Environment - Non Weather Related; Human Factors
Primary problem: Human Factors

Narrative: Purser brought a passenger along on her trip during the Coronavirus outbreak. She stated they are traveling together all month long during her work trips. She is potentially exposing other crew members [with] an extra person during this time. He joined us on a shuttle. Didn't wear a mask. Poor decision as a safety professional.




Synopsis: Flight Attendant reported concerns with another Flight Attendant bringing a passenger on the shuttle bus and flight during the COVID-19 pandemic.
Date: 202110
Local time of day: 1201-1800
Location: ZZZ.TRACON, US
Aircraft: Commercial Fixed Wing
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Descent; Initial Approach
Airspace: Class B ZZZ; Class E ZZZ
ATC / advisory: TRACON ZZZ
Aircraft component: Air Conditioning and Pressurization Pack
Component problem: Malfunctioning
Reporter organization: Air Carrier
Reporter qualification: Flight Crew Air Transport Pilot (ATP); Flight Crew Instrument; Flight Crew Multiengine
Human factors: Physiological - Other
Anomaly: Aircraft Equipment Problem Less Severe; Flight Deck / Cabin / Aircraft Event Smoke / Fire / Fumes / Odor
Detector: Person Flight Crew
When detected: In-flight
Result: Flight Crew Overcame Equipment Problem
Contributing factors: Aircraft
Primary problem: Aircraft

Narrative: Upon descent into ZZZ we noticed the distinct smell of an odor event. It started about 15;000 feet on descent and continued until after landing. Just about the time we noticed it; we got a call from inflight that it was strongest at the back around the row 20 area. Following the odor isolation guide we turned Pack 2 off and left it off for the duration of the flight. That seemed to help; but it didn't eliminate the odor. As of right now; about 4 hours post event; I have a sore throat and a slight headache that I attribute to the fume event.




Synopsis: Air Carrier flight crew reported a fume event during descent. Flight crew completed odor isolation procedures and continued to a safe landing at destination.
Date: 202110
Local time of day: 1801-2400
Location: ZZZ.Airport, US
Flight conditions: Marginal
Light: Night
Aircraft: EMB ERJ 170/175 ER/LR
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Parked
Airspace: Class B ZZZ
ATC / advisory: Tower ZZZ
Aircraft component: Main Gear Wheel
Component problem: Failed
Reporter organization: Air Carrier
Reporter function: Pilot Not Flying; Captain
Reporter qualification: Flight Crew Air Transport Pilot (ATP); Flight Crew Instrument; Flight Crew Multiengine
Second reporter function: Pilot Flying; First Officer
Anomaly: Aircraft Equipment Problem Critical; Ground Event / Encounter Other / Unknown
Detector: Person Flight Crew
When detected: Aircraft In Service At Gate
Result: Aircraft Aircraft Damaged; General Maintenance Action
Contributing factors: Aircraft
Primary problem: Aircraft

Narrative: After landing; left main gear showed abnormal brake temperatures. The outboard brakes were at 400 degrees and increasing while the inboard brakes were at 21 degrees. The right main landing gears showed normal temperatures expected after a normal landing. BRK OVERHEAT and LG NO DISPATCH caution messages populated on EICAS. FO (First Officer) and I discussed it and thought it was most likely was a faulty indication. I asked FO to perform a post flight walk around and report back what he finds. FO came back and said the inboard wheel was missing on the landing gear.


Second narrative: After landing parking at the gate; both pilots noticed that the left main gear outboard brake temp was unusually high to over 450C while inboard brake remained at around 22C. The brake overtemp EICAS msg popped out couple seconds after following with LG no Dispatch message after the flight crew shut down the engine. First Officer noticed right away the left side inboard landing gear the wheel was missing during post flight walk around


Synopsis: Flight Crew reported finding the left hand inboard main tire and wheel assembly missing.
Date: 202101
Location: ZZZ.Airport, US
Aircraft: No Aircraft
Reporter organization: Air Carrier
Reporter function: Gate Agent / CSR
Human factors: Other / Unknown
Anomaly: Deviation / Discrepancy - Procedural Published Material / Policy; Ground Event / Encounter Other / Unknown
Result: General None Reported / Taken
Contributing factors: Environment - Non Weather Related; Human Factors; Company Policy
Primary problem: Environment - Non Weather Related

Narrative: We all have been complying with mask use at ZZZ to 'Stop the spread' and for public image.  I see the policy becoming more and more restrictive; and gets interpreted differently by people.  Yes; we must wear a face covering while in the public. Yes; if we are unable to maintain social distance; we should also be wearing a covering outside of public area.  What this does not address is the long term health effects of wearing a face covering every day of the week for hours at a time.  Extended mask use can cause and is not limited to:1.Shortness of Breath and Light headedness2. Headaches3. Dermatitis4. A weakened Immune System ( your body is unable to rid toxic cell normally because they wind up staying in your face covering which causes bacteria to stay in your mouth. Having bacteria stay in your mouth leads to health issues such as dental issues (root canals; infections; etc.) Healthy oral hygiene is a necessity for heart health and overall health.5.Chronic Respiratory Issues




Synopsis: Customer Service Representative reported health related concerns with wearing face masks at work for extended periods of time.
Date: 202105
Local time of day: 1201-1800
Location: FAI.TRACON, AK
Aircraft: Commercial Fixed Wing
Operator: Air Taxi
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Descent
Airspace: Class E FAI
ATC / advisory: TRACON FAI
Reporter organization: Government
Reporter function: Supervisor / CIC; Approach
Reporter qualification: Air Traffic Control Fully Certified
Human factors: Time Pressure; Workload; Situational Awareness
Anomaly: ATC Issue All Types; Airspace Violation All Types; Deviation - Track / Heading All Types; Deviation / Discrepancy - Procedural Published Material / Policy
Detector: Person Air Traffic Control
When detected: In-flight
Result: Air Traffic Control Issued New Clearance
Contributing factors: Procedure; Human Factors; Company Policy; Chart Or Publication; Airspace Structure
Primary problem: Procedure

Narrative: Aircraft X was filed on the HRDNG STAR into FAI. The pilot checked onto approach passing 17;000 feet in the descent to 8;000 feet. Lightning Group airspace was called HOT by Anchorage Center sector 15/16. This airspace includes the Viper B MOA / ATCAA that is within 3 miles from the STAR fight path. Anchorage Center is required to remove the aircraft off of the STAR prior to switching them to FAI Approach. This was not accomplished; the Approach Controller had to vector the aircraft away from that airspace. This is a known issue; inside and outside of FAI ATCT; with that SID. Multiple training scenarios as well as in-person briefings have been completed over this issue.If one fix is moved 1 mile south; this will alleviate all headaches and route changes. Anchorage Center previously stated in a response awhile back; that there was no issue with this arrival because they are required to remove the aircraft from the STAR. With this not occurring; Anchorage Center changing the aircraft frequency; and FAI Approach now responsible allows too much possibility into a system that needs assurances.




Synopsis: FAI TRACON Controller reported ZAN Center was not complying with established procedures to route aircraft away from military special use airspace. Reporter stated this is a routine occurrence.