elihoole/asrs-aviation-reports huggingface dataset:
Date: 201306
Local time of day: 0001-0600
Location: ZOA.ARTCC, CA
Aircraft: B737-800
Operator: Air Carrier
Operating under: Part 121
Mission: Passenger
Flight phase: Cruise
Airspace: Class A ZOA
ATC / advisory: Center ZOA
Reporter organization: Air Carrier
Reporter function: First Officer; Pilot 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: General Maintenance Action
Contributing factors: Human Factors
Primary problem: Human Factors

Narrative: During cruise flight; I was replacing the batteries in my headset and dropped a 3 pack of AAA batteries wrapped in a rubber band. The batteries bounced off the cockpit floor; hit the toe of my boot; and bounced into the [underfloor area] under the First Officer's left rudder pedal. Notified Dispatch and put a write-up in the logbook. I met the Mechanic after landing and spent the next hour with flashlight trying to find missing batteries. Watch when you drop stuff on cockpit floor; it could go anywhere. Right now; no batteries found.




Synopsis: B737-800 First Officer reported he dropped some AAA batteries that went under the floor in the rudder pedal area.
Date: 202002
Flight conditions: VMC
Aircraft: B737 Next Generation Undifferentiated
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Takeoff / Launch
ATC / advisory: Ground ZZZ; Tower ZZZ
Aircraft component: Speedbrake/Spoiler
Component problem: Malfunctioning
Reporter organization: Air Carrier
Reporter function: Pilot Not Flying; Captain
Reporter qualification: Flight Crew Instrument; Flight Crew Multiengine; Flight Crew Air Transport Pilot (ATP)
Human factors: Confusion; Human-Machine Interface; Troubleshooting
Second reporter function: First Officer; Pilot Flying
Anomaly: Aircraft Equipment Problem Critical
Detector: Person Flight Crew
When detected: Other Takeoff
Result: Flight Crew Rejected Takeoff; General Flight Cancelled / Delayed
Contributing factors: Aircraft
Primary problem: Aircraft

Narrative: As we taxied out I saw the Speed Brake Do Not Arm light flicker once as we taxied out of the ramp area and once about halfway to the runway. I pressed the speed brake forward to make sure again that it was [in the] down detent. It was in the correct position. The light did not come on again. We ran all of the checklists and there was nothing unusual. We ran the final items on the before take off checklist. Everything was operation normal. We were cleared for take off. The First Officer was flying. He said check thrust and I took the throttles for take off. As we rolled down the runway around 60 To 70 kts.; I saw the speed brake do not arm light flicker then turn on steady. I also heard the configuration horn go off. I called reject; I have the aircraft around 75 to 80 kts. I pressed the manual brakes around 60 kts. to prevent the violent stop.The First Officer made the calls to Tower and remain seated calls. I slowly taxied off the runway. We called to the back to make sure everyone was seated and ok. The Purser said everything was fine. We did not ask for assistance since we were in the low speed regime. We ran the rejected Take Off checklist from the QRC. The First Officer ran his after landing flows. We asked Ground for a spot to work the problem. I called Maintenance with Operations.  I talked with [someone] who said this was a known anomaly (which I did not know about). He had me set the flaps to one then he had me activate the number two stick shaker. He said that we were good to go. The light never came on again. I made a call to the Flight Attendants and the passengers. We ran all of our checklists again and taxied back to the runway for take off. We took off without incident and landed [at our destination].


Second narrative: Shortly after applying power for takeoff; the SPEED BRAKE DO NOT ARM light came on twice. It came on briefly a first time; went away and turned back on and the Captain initiated the Rejected Takeoff. The decision to reject was performed around 80 kts. and we followed company procedures.


Synopsis: Flight Crew reported a rejected takeoff due to a Speed Brake Do Not Arm light coming on.
Date: 201406
Local time of day: 1801-2400
Location: OAK.Airport, CA
Light: Dusk
Aircraft: Small Aircraft; Low Wing; 2 Eng; Retractable Gear
Flight plan: IFR
Flight phase: Initial Climb
Airspace: Class C OAK
ATC / advisory: Tower OAK
Reporter organization: Government
Reporter function: Instructor; Local
Reporter qualification: Air Traffic Control Fully Certified
Human factors: Communication Breakdown; Confusion; Distraction
Anomaly: ATC Issue All Types; Airspace Violation All Types; Deviation / Discrepancy - Procedural Clearance; Deviation / Discrepancy - Procedural Published Material / Policy
Detector: Person Air Traffic Control
When detected: In-flight
Contributing factors: Airspace Structure; Procedure
Primary problem: Procedure

Narrative: Aircraft X was about to depart IFR and NCT Coordinator called us about his beacon code. This led us to forget to obtain IFR departure release because I did not remember that Diablo Sector is open. Normally; when Diablo is not open we have auto releases on prop departures on NIMI or H315 departures. It was not until we had the next IFR departure that I inquired to the trainee if we got a release on Aircraft X and she said she just launched him.We should have been using the CFR placard when Diablo is open to avoid forgetting.




Synopsis: OAK Tower Controller describes situation where an aircraft departed without a release.  Controller also states there is a placard to remind them to obtain the release that they weren't using.
Date: 202001
Location: ZZZ.Airport, US
Light: Daylight
Aircraft: B737-700
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Landing
Airspace: Class B ZZZ
Reporter organization: Air Carrier
Reporter function: Flight Attendant (On Duty)
Reporter qualification: Flight Attendant Current
Anomaly: Aircraft Equipment Problem Less Severe; Deviation / Discrepancy - Procedural Published Material / Policy; Flight Deck / Cabin / Aircraft Event Smoke / Fire / Fumes / Odor
Detector: Person Flight Attendant
When detected: In-flight
Result: Air Traffic Control Provided Assistance; Flight Crew Requested ATC Assistance / Clarification; Flight Crew Diverted; Flight Crew Landed in Emergency Condition; General Flight Cancelled / Delayed
Contributing factors: Aircraft
Primary problem: Aircraft

Narrative: Diversion in ZZZ due to flaps and loss of hydraulics. For safety Flight Attendants remained seated. A couple of passenger call lights went off after [the] Captain's announcement during flight . Flight Attendants made several announcements that for safety we would remain seated for the short duration of the flight. Upon landing; [there was a] burning smell of rubber odor in [the] aft galley. Once we came to a stop [we] verified that smoke was not visible and passengers were requesting to use the lavatory. Informed them to remain seated until we received further directives from the Captain and initially communicated with other Cabin Crew Members. For Safety and Regulatory Requirements; [we] continued to adhere to International Regulatory Requirements until we arrived at [the] gate with forward cabin door(s) opened.




Synopsis: B737-700 Flight Attendant reported 'burning smell of rubber' upon diversion landing due to a hydraulic malfunction.
Date: 201409
Local time of day: 1801-2400
Location: ATL.Airport, GA
Light: Daylight
Aircraft: Medium Transport; Low Wing; 2 Turbojet Eng
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Descent
Airspace: Class E ZTL
ATC / advisory: Center ZTL
Second aircraft: Medium Transport; Low Wing; 2 Turbojet Eng
Reporter organization: Government
Reporter function: Enroute
Reporter qualification: Air Traffic Control Fully Certified
Human factors: Confusion; Communication Breakdown; Distraction; Troubleshooting; Situational Awareness
Anomaly: Conflict Airborne Conflict; Deviation - Altitude Excursion From Assigned Altitude; Deviation / Discrepancy - Procedural Published Material / Policy
Detector: Person Air Traffic Control
When detected: In-flight
Result: Air Traffic Control Separated Traffic
Contributing factors: ATC Equipment / Nav Facility / Buildings; Aircraft; Human Factors
Primary problem: ATC Equipment / Nav Facility / Buildings

Narrative: I was working aircraft out of a holding pattern for ATL.  I thought I had used proper vertical separation.  I was certain Aircraft X was out of 150 and assigned Aircraft Y 160 and a reverse heading of 340 to sequence them behind Aircraft X.  There was a jet that had just diverted to HSV; and I was in a conversation with them about going to ATL since we had just started running aircraft into ATL.  The next thing I knew; conflict alert was going off and Aircraft Y was asking me to verify their assigned altitude.  I saw Aircraft Y leaving descending through 169 and Aircraft X at 165 right on top of each other.  I told Aircraft Y to level off at whatever altitude they were at; and turned them 40 degrees left.  The next update showed Aircraft Y at 163 and Aircraft X's altitude was Xed out.  At that point I just wanted to make sure everyone was separated.  Pilots were stepping on transmissions and I could not get replies right away.  I then saw Aircraft X out of 150. I think I may have told them to expedite their descent at some point; but I don't remember for certain.  I could not think straight at this point and asked the CIC to get me out.  I have since heard it was a Mode C swap.  I don't know if anything can be done about them; but it was an extremely upsetting experience to go through. Anything that can be done about Mode C swaps.




Synopsis: ZTL Controller reports of an incident where he is trying to separate two aircraft in a conflict due to altitude separation.  The Mode C's of the aircraft swap and cause the Controller problems.
Date: 201902
Local time of day: 1801-2400
Location: ZZZ.Airport, US
Aircraft: PA-28 Cherokee/Archer/Dakota/Pillan/Warrior
Operator: Personal
Operating under: Part 91
Flight plan: None
Mission: Personal
Flight phase: Parked
Reporter organization: Personal
Reporter function: Pilot Flying; Single Pilot
Reporter qualification: Flight Crew Commercial; Flight Crew Flight Instructor; Flight Crew Instrument; Flight Crew Multiengine
Anomaly: Aircraft Equipment Problem Critical
Detector: Person Flight Crew
When detected: Aircraft In Service At Gate
Result: Air Traffic Control Provided Assistance; Flight Crew Requested ATC Assistance / Clarification
Contributing factors: Aircraft; Human Factors
Primary problem: Ambiguous

Narrative: Tried to start the aircraft but it didn't want to start. I let it cool down then tried again. Then I smelled a burning smell. I told my friend to exit the aircraft; then I went to check the engine. When I opened [the cowling] I noticed that there was [a] fire. I told my friend to get as far as possible from the aircraft because we had no time to try to [extinguish] the fire. It was next to the fuel tanks. Then I called [ATC and] told them to send the fire people because the aircraft engine is on fire. [A] few minutes later they came and [extinguished] the fire.




Synopsis: PA-28 pilot reported experiencing an engine fire during a start attempt.
Date: 201310
Local time of day: 1201-1800
Location: ZZZ.ARTCC, US
Flight conditions: VMC
Light: Daylight
Aircraft: Cessna Citation Sovereign (C680)
Operator: Fractional
Operating under: Part 91
Flight plan: IFR
Mission: Passenger
Flight phase: Takeoff / Launch
Airspace: Class A ZZZ
ATC / advisory: Center ZZZ
Aircraft component: Hydraulic System
Component problem: Failed
Reporter organization: Fractional
Reporter function: First Officer
Reporter qualification: Flight Crew Air Transport Pilot (ATP)
Human factors: Workload
Anomaly: Aircraft Equipment Problem Critical; Ground Excursion Runway
Detector: Automation Aircraft Other Automation; Person Flight Crew
When detected: In-flight
Result: Flight Crew Diverted; Flight Crew Landed in Emergency Condition; General Declared Emergency
Contributing factors: Aircraft
Primary problem: Aircraft

Narrative: Shortly after landing gear retraction; the amber CAS message Hydraulic Volume Low illuminated. The EICAS indicator showed 0 volume in the hydraulic reservoir. We climbed to a safe altitude and ran the checklist for the malfunction and continued toward the mainland to determine a suitable landing site. The company was contacted regarding the problem and requested we land at an isolated field. We determined a larger airport had more suitable runways and informed ATC we would be making an emergency landing there. Based on the landing numbers per the checklist criteria; Runway XX was suitable. We rehearsed the landing sequence prior to touchdown to ensure we were coordinated in our efforts. Upon touchdown; the emergency braking system was applied; but seemed to have little effect. The airplane coasted to a stop.  All passengers and crew were OK.




Synopsis: A CE680 EICAS alerted HYDRAULIC VOLUME LOW after landing gear retraction so the flight diverted and after landing when the aircraft's braking systems failed; the aircraft rolled safely to a stop.
Date: 201311
Local time of day: 1201-1800
Location: ZZZ.ARTCC, US
Flight conditions: VMC
Weather elements / visibility: 10
Light: Daylight
Aircraft: Citationjet (C525/C526) - CJ I / II / III / IV
Operator: Personal
Operating under: Part 91
Flight plan: IFR
Mission: Personal
Flight phase: Cruise
Airspace: Class A ZZZ
ATC / advisory: Center ZZZ
Aircraft component: Pressurization System
Component problem: Malfunctioning
Reporter organization: Personal
Reporter function: Single Pilot; Pilot Flying
Reporter qualification: Flight Crew Air Transport Pilot (ATP)
Anomaly: Aircraft Equipment Problem Critical
Detector: Person Flight Crew
When detected: In-flight
Result: Flight Crew Took Evasive Action; General Declared Emergency
Contributing factors: Aircraft
Primary problem: Aircraft

Narrative: Cruising at FL410; sudden sound of air and loss of pressurization. Called Center to declare an emergency and given FL210. Told them I would need emergency descent. All seemed carried out without problem. (I had immediately followed the well trained drills of emergency descent.) Requested and given altitude of 10;000 FT to complete flight without problem.




Synopsis: A C525 lost pressurization at FL410; so the single pilot declared an emergency and descended to 10;000 FT.
Date: 202003
Location: ZZZ.Airport, US
Light: Daylight
Aircraft: Commercial Fixed Wing
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Cruise
Airspace: Class A ZZZ
ATC / advisory: Ramp ZZZ
Reporter organization: Air Carrier
Reporter function: Flight Attendant (On Duty)
Reporter qualification: Flight Attendant Current
Human factors: Other / Unknown
Anomaly: Deviation / Discrepancy - Procedural FAR; Deviation / Discrepancy - Procedural Published Material / Policy
Detector: Person Flight Attendant
When detected: In-flight; Aircraft In Service At Gate
Result: General None Reported / Taken
Contributing factors: Environment - Non Weather Related; Human Factors
Primary problem: Environment - Non Weather Related

Narrative: Past 3 days have been very trying. Passengers are able to board the planes ill. Coughing; sneezing; even having the appearance of being ill. I am at the end of my 3 Day and instead of looking forward to going home; I am reluctant in that I may be bringing the virus home to my family. Please see if the company can have CDC (Center for Disease Control) come out and have crew members tested in base. Crew members are around hundreds of people a day and could very well be transmitting the virus to others. Please let me know when and how this necessary procedure could be implemented to best serve our customers and each other. Thank you.




Synopsis: Flight Attendant reported ill passengers on the flight and was concerned regarding lack of COVID-19 testing for the crew.
Date: 201208
Local time of day: 0601-1200
Location: ZZZ.Airport, US
Light: Daylight
Aircraft: Regional Jet 200 ER/LR (CRJ200)
Operator: Air Carrier
Operating under: Part 121
Mission: Passenger
Flight phase: Parked
Aircraft component: Minimum Equipment List (MEL)
Reporter organization: Air Carrier
Reporter function: Other / Unknown
Reporter qualification: Maintenance Airframe; Maintenance Powerplant
Human factors: Situational Awareness; Training / Qualification; Confusion; Troubleshooting; Communication Breakdown
Anomaly: Aircraft Equipment Problem Critical; Deviation / Discrepancy - Procedural Published Material / Policy
Detector: Person Maintenance
When detected: Pre-flight
Result: General Maintenance Action
Contributing factors: Aircraft; Chart Or Publication; Human Factors; MEL; Manuals
Primary problem: Human Factors

Narrative: I opened an MEL 73-31-3 for a Fuel Pressure Indication System. I thought that the switch was at fault based on the Fault Isolation Manual (FIM) task for the 'FUEL LO PRESS' caution message. My Supervisor informed me today that the Standy Fuel Check Valve could also cause the problem. My Supervisor informed me that we need to do more troubleshooting to find root cause of problem. Based on the information that I had at the time; I believed that the pressure switch was reading incorrectly. We scheduled Maintenance to look at problem. [Recommend] creating a flow chart for this particular message.




Synopsis: A Maintenance Controller reports he deferred a fuel pressure switch on a CRJ-200 aircraft based on their Fault Isolation Manual (FIM) procedures for a 'FUEL LO PRESS' caution message. He was later informed that a Standby Fuel Check Valve could have been the problem and the importance of better troubleshooting to find root causes.
Date: 201808
Local time of day: 1801-2400
Location: ZZZ.Airport, US
Flight conditions: VMC
Weather elements / visibility: Rain; 5
Light: Night
Aircraft: Super King Air 300
Operator: Corporate
Operating under: Part 91
Flight plan: IFR
Mission: Passenger
Flight phase: Landing
Airspace: Class G ZZZ
Reporter organization: Corporate
Reporter function: Pilot Flying; Single Pilot
Reporter qualification: Flight Crew Air Transport Pilot (ATP); Flight Crew Multiengine; Flight Crew Instrument
Human factors: Situational Awareness
Anomaly: Ground Event / Encounter Object; Ground Event / Encounter Loss Of Aircraft Control; Ground Excursion Runway
Detector: Person Flight Crew
Result: Flight Crew Regained Aircraft Control
Contributing factors: Airport; Weather; Human Factors
Primary problem: Weather

Narrative: Upon landing; aircraft hydroplaned as was evident by the photographs that were taken the following morning. There were rain showers in the area; and the runway appeared wet on landing. The left main and nose landing gear slid off the side of the runway and became stuck in the mud. After touchdown; the aircraft felt like it was on ice; and started drifting left. With the power levers at idle; I applied right rudder to try to realign the aircraft on the centerline of the runway.In conclusion; had the runway been grooved this incident would not have occurred. There was minor damage to the aircraft from hitting a runway edge light.




Synopsis: Super King Air pilot reported hydroplaning on landing and hitting a runway light.
Date: 201909
Local time of day: 1201-1800
Aircraft: B737-800
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Cruise
Airspace: Class A ZZZ
ATC / advisory: Center ZZZ
Aircraft component: Recirculation Fan
Component problem: Malfunctioning
Reporter organization: Air Carrier
Reporter function: First Officer; Pilot Not Flying
Reporter qualification: Flight Crew Instrument; Flight Crew Air Transport Pilot (ATP); Flight Crew Multiengine
Human factors: Situational Awareness
Anomaly: Aircraft Equipment Problem Less Severe; Deviation / Discrepancy - Procedural Published Material / Policy; Flight Deck / Cabin / Aircraft Event Smoke / Fire / Fumes / Odor
Detector: Person Flight Crew; Person Flight Attendant
When detected: In-flight
Result: Aircraft Equipment Problem Dissipated; Flight Crew Overcame Equipment Problem; General Maintenance Action
Contributing factors: Aircraft
Primary problem: Aircraft

Narrative: At FL370; flight attendants notified us of an electrical smelling odor mid cabin from exit rows to aft lavatories. No visible smoke only fumes: they walked the cabin several times searching for a source but found none. Captain asked them to check for overheating PED (Passenger Electronic Device). None found. Meanwhile we began the QRH for fumes in cabin through step 11. Turned off recirculating fans; fumes no longer present. Turned off bus transfer switch; IFE power; CAB/Utility power; fumes no longer present. Long [satellite] call with [Chief Pilot]; decided to continue to destination. Rest of flight was uneventful. Left all equipment 'OFF' that was turned off as directed by QRH.




Synopsis: B737 First Officer reported fumes in the cabin; prompting successful in flight troubleshooting and uneventful landing.
Date: 201910
Local time of day: 0001-0600
Location: ZZZ.Airport, US
Aircraft: B737-800
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Climb
Aircraft component: Pressurization System
Component problem: Failed
Reporter organization: Air Carrier
Reporter function: Captain; Pilot Flying
Reporter qualification: Flight Crew Air Transport Pilot (ATP)
Second reporter function: Pilot Not Flying; First Officer
Anomaly: Aircraft Equipment Problem Less Severe; Deviation / Discrepancy - Procedural Published Material / Policy
Detector: Person Flight Crew
When detected: In-flight
Result: Flight Crew Diverted; Flight Crew Returned To Departure Airport; Flight Crew Landed in Emergency Condition
Contributing factors: Aircraft
Primary problem: Aircraft

Narrative: On departure passing approximately 11;000 feet; we had cabin pressure failure and got a CABIN ALTITUDE WARNING light and horn. I was flying; disconnected the autopilot and immediately reversed climb to get down to 10;000 feet cabin. We [advised ATC] and got vectors back to ZZZ for an uneventful landing on Runway XXC.According to maintenance in ZZZ; problem may have been caused by rapid change of temperature gradient overnight on the ground. I have never heard of this issue. They ran 4 tests on both pressure units and we pressurized the cabin at the gate to approximately 3.0 differential. Log book signed off and an uneventful takeoff and flight to ZZZ1.


Second narrative: On climbout from ZZZ passing through 11;000 feet; we had a cabin pressure failure and got a CABIN ALTITUDE warning light and horn. Captain was flying and I was the pilot monitoring. Captain disconnected the autopilot and immediately reversed climb and descended back to 10;000 feet. We [advised ATC] and got vectors back to ZZZ for an uneventful landing on Runway XXC.According to Maintenance in ZZZ; the problem may have been caused by a rapid change of temperature gradient overnight on the ground. Maintenance performed 4 tests on both pressure units and we also pressurized the cabin at the gate to approximately 3.0 differential. Log book was signed off and an uneventful flight to ZZZ1 was performed.


Synopsis: B737-800 flight crew reported a pressurization problem during climb that resulted in a diversion.