elihoole/asrs-aviation-reports huggingface dataset:
Date: 202112
Local time of day: 0001-0600
Location: ZZZ.ARTCC, US
Flight conditions: VMC
Aircraft: B737 Undifferentiated or Other Model
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: Fuel
Component problem: Malfunctioning
Reporter organization: Air Carrier
Reporter function: Captain; Pilot Flying
Reporter qualification: Flight Crew Instrument; Flight Crew Multiengine; Flight Crew Air Transport Pilot (ATP)
Human factors: Troubleshooting
Anomaly: Aircraft Equipment Problem Critical; Deviation / Discrepancy - Procedural Weight And Balance; Deviation / Discrepancy - Procedural Published Material / Policy; Deviation / Discrepancy - Procedural Clearance; Inflight Event / Encounter Fuel Issue
Detector: Automation Aircraft Other Automation; Person Flight Crew
When detected: In-flight
Result: Flight Crew Diverted; General Maintenance Action
Contributing factors: Aircraft
Primary problem: Aircraft

Narrative: At cruise I noticed a fuel imbalance; with the right tank being 1500 lbs lower than the left. Had the amber alert with no fuel in the center tank. Turned both right side pumps off and opened the cross feed. Then I noticed the fuel over destination being lower than normal; 7.2 was on the flight plan and it was showing 6.0. CI was planed at 120 and was not changed. The fuel over destination kept going down at approximately 500 lbs every 10 min. Also the right side tank kept losing gas with the pumps shut off; it did slow down but never stopped. Ran the FUEL LEAK-ENGINE QRH then talked to Dispatch on ARINC and advised about the idea of diverting. We both agreed ZZZ1 was a good choice. As we were getting farther away from land at this point; when the fuel over destination reached 5.7 and still falling we decided to divert to ZZZ1. Advised ATC; the flight attendants were briefed as well as the passengers on our situation and diversion. On downwind the tanks were in balance. At the marker the Left side now showed 1500 lbs low. No action was taken and we landed safely. Emergency vehicles inspected our aircraft and found no signs of leakage; so we taxied to the gate with vehicles following.




Synopsis: B737 Captain reported fuel imbalance due to possible fuel leak resulting in a diversion.
Date: 201409
Local time of day: 0601-1200
Location: NCT.TRACON, CA
Flight conditions: VMC
Weather elements / visibility: 10
Light: Daylight
Aircraft: Small Aircraft; Low Wing; 1 Eng; Retractable Gear
Operator: Personal
Operating under: Part 91
Flight plan: None
Mission: Personal
Flight phase: Initial Climb
Airspace: Class B SFO; Class E NCT
ATC / advisory: TRACON NCT
Reporter organization: Personal
Reporter function: Pilot Flying; Single Pilot
Reporter qualification: Flight Crew Commercial; Flight Crew Instrument
Human factors: Situational Awareness; Time Pressure
Anomaly: Airspace Violation All Types; Conflict NMAC; Deviation - Altitude Overshoot
Detector: Automation Aircraft RA; Person Flight Crew
When detected: In-flight
Result: Flight Crew Took Evasive Action; Flight Crew Returned To Clearance
Contributing factors: Environment - Non Weather Related
Primary problem: Environment - Non Weather Related

Narrative: I took off from San Carlos Airport; Bay Meadows departure.  Normal climb out to the Pacific Coast; and I had just leveled off at 3;700 to stay under the San Francisco Class B airspace that starts at 4;000 feet in that area. No sooner than I was level; both my Garmin GTN 750; and Garmin 650 (both driven by a Garmin GDL 88 TIS B for Traffic) lit up for a traffic conflict. I switched the GTN 650 to the 2 mile ring display; and saw that another aircraft was in direct conflict with my airplane. That aircraft was moving very fast relative to me; and if I did not take some evasive action; it was absolutely apparent that a mid-air was probable. That aircraft display was showing him to be 100 to 200 feet below me. The convergence was so fast that I had very little time to fully analyze the complete picture; but I needed to make a change in altitude and direction NOW. I immediately went to full throttle and climbed at my maximum rate of climb until I could see from the traffic displays that he had passed virtually directly under me; at a separation of about 400 to 500 feet. For the moment I kept climbing until I was absolutely sure that he had passed under me. I never did see that aircraft visually. In the process of evading the threat; I had climbed to 4;100 feet; or 100 feet into the SFO Class B airspace. I immediately descended back down to my previous 3;700 foot altitude. I regard my (minor) intrusion into the Class B airspace as necessary for safety.  I am convinced that had I not climbed away from the converging aircraft; a midair was all too likely.  I am also glad that I spent a very considerable amount of money rebuilding my avionics to include the GTN 750/GTN 650/GDL 88 equipment.  The traffic warnings alone are worth the price. In the last several months; I have 'seen' traffic via the avionics that I have not seen at all; or only when very close via 'eyeballs'.




Synopsis: A pilot departed SQL West bound; climbed to 3;700 feet and there took evasive action from GTN 750/650 TIS alerted traffic 400 feet below. During the climb he momentarily entered SFO Class B.
Date: 201703
Local time of day: 1201-1800
Location: ZZZ.Airport, US
Light: Daylight
Aircraft: B737-300
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Final Approach; Landing
Airspace: Class D ZZZ
ATC / advisory: Tower ZZZ
Aircraft component: Landing Gear Indicating System
Component problem: Malfunctioning
Reporter organization: Air Carrier
Reporter function: Pilot Flying; Captain
Reporter qualification: Flight Crew Air Transport Pilot (ATP)
Second reporter function: Pilot Not Flying; First Officer
Anomaly: Aircraft Equipment Problem Less Severe
Detector: Person Flight Crew
When detected: In-flight
Result: Flight Crew Overcame Equipment Problem
Contributing factors: Aircraft
Primary problem: Aircraft

Narrative: On approach at the FAF we lowered the gear but had no Landing Gear Indication lights. With no time to trouble shoot; we elected a low approach while leaving the landing gear handle down and asking the Tower to give us their opinion of our gear status. The Tower confirmed what we believed. Our gear was in fact down. After the low approach and establishing ourselves on downwind we began an analysis and found [a] circuit breaker was popped.The First Officer found the breaker and after a discussion that his shoulder harness may have popped the CB; I directed him to reset the breaker. We regained two of the three gear lights. However the left gear light remained extinguished. We swapped the right gear light for the left light and it illuminated down. So we swapped it back and replaced the bulbs in the left gear indicator. One of the bulbs illuminated in the left gear and we elected to land with no further incident.


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


Synopsis: B737 flight crew reported an issue with the landing gear indicating light system that was traced to a popped circuit breaker. Flight crew surmised the popped breaker could have been caused by the shoulder harness.
Date: 202107
Local time of day: 1201-1800
Location: ZZZ.Airport, US
Flight conditions: VMC
Weather elements / visibility: 10
Light: Daylight
Aircraft: PA-28 Cherokee/Archer/Dakota/Pillan/Warrior
Operator: Personal
Operating under: Part 91
Flight plan: None
Mission: Personal
Flight phase: Other Traffic Pattern; Downwind
Airspace: Class G ZZZ
ATC / advisory: CTAF ZZZ
Second aircraft: Small Aircraft
Reporter organization: Personal
Reporter function: Pilot Flying; Single Pilot
Reporter qualification: Flight Crew Flight Instructor; Flight Crew Instrument; Flight Crew Commercial
Human factors: Situational Awareness; Communication Breakdown
Anomaly: Conflict NMAC; Deviation / Discrepancy - Procedural Published Material / Policy
Detector: Person Flight Crew
When detected: In-flight
Result: Flight Crew Took Evasive Action
Contributing factors: Human Factors; Procedure
Primary problem: Procedure

Narrative: I received flight following enroute to ZZZ. After ATC approved my frequency change and squawk code change to 1200. I switched to CTAF frequency and AWOS. I made radio calls that I was approaching airport from several miles away and would be doing a 45 degree entry for [Runway] XX; full stop. I then made my radio call for a 45 degree entry on the 45 degree entrance for Runway XX right traffic. Preceding traffic did an entry via base leg and landed on Runway XX without incident. I proceeded to enter via 45 degree entry and made my turn to downwind right traffic at about 1;006ft MSL. I continued to make radio calls that I was right turn downwind XX for ZZZ. I heard nor saw no other traffic in the pattern nor making radio calls for ZZZ. No traffic appeared on my ADS-B in Stratus 2I unit either. Abeam numbers of Runway XX; I reduced power and start about a 500/min descent and was scanning for traffic and scanning for proper distance for a turn to base. As I descended a silver high wing banner towing aircraft came into view coming from the opposite direction slightly above me on downwind (maybe 35 feet above me) and was transitioning through the traffic pattern of ZZZ towing a banner. There was no time for a radio call at the closing rate of the two aircraft and I abruptly made a descending right turn to avoid a head on collision. The banner tow plane did not turn initially but made a right turn after I called on the radio letting him know he flew through the downwind leg of in the opposite of the pattern at ZZZ and nearly collided with me. He then made a right turn and proceeded to fly west toward the bay to avoid the pattern. He said he had no idea what I was talking about and was cursing on the radio. I then realized that he never saw me. I continued to make my base leg radio call and final approach radio call and landed without any other problems. This collision was avoided.




Synopsis: Pilot reported a Near Mid Air Collision with a banner tow aircraft that flew through the airport traffic pattern; causing them to take evasive action.
Date: 201909
Local time of day: 1801-2400
Location: ZZZ.Airport, US
Flight conditions: VMC
Aircraft: B727-200
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Cargo / Freight / Delivery
Flight phase: Cruise
ATC / advisory: Center ZZZ
Aircraft component: Air Conditioning Distribution Ducting; Clamps; Connectors
Component problem: Malfunctioning
Reporter organization: Air Carrier
Reporter function: Flight Engineer / Second Officer
Reporter qualification: Flight Crew Flight Engineer; Maintenance Powerplant; Maintenance Airframe
Human factors: Situational Awareness
Anomaly: Aircraft Equipment Problem Critical; Deviation / Discrepancy - Procedural Published Material / Policy; Deviation / Discrepancy - Procedural Maintenance
Detector: Person Flight Crew
When detected: In-flight
Result: Air Traffic Control Provided Assistance; Flight Crew Overcame Equipment Problem; General Maintenance Action
Contributing factors: Equipment / Tooling; Human Factors; Procedure
Primary problem: Procedure

Narrative: During cruise flight I heard a pop sound; flight level 310. I noticed the cabin rate of climb indicating 1;000 ft. [per] minute climb. I closed off the cargo heat outflow; cabin rate decreased to 500 ft. [per] minute. Unable to control the cabin rate using the manual cabin pressure control; the Captain called ATC to request a descent and called for the appropriate checklist as the cabin altitude reached 7;000 ft. Review of the Failure of Automatic Pneumatic Pressurization Controller checklist didn't help our situation. We leveled off at flight level 270; cabin kept climbing; at this time we donned our oxygen masks. Captain requested another descent to flight level 230 as the cabin reached 11;000 ft. Another request to descend was made; we leveled off at flight level 210 and the cabin decreased to 10;000 ft. The cabin settled at 10;000 ft. for a short while; but then it started to climb again. We descended to flight level 190 where the cabin finally settled at 10;000 ft. A short time later it was time for us to descend into ZZZ. We had to keep engines 1 and 3 at a higher setting in order to maintain a level cabin from climbing above 10;000 ft. Throughout our situation; ATC was very accommodating. We had an uneventful landing into ZZZ. The mechanic inspection revealed that the water separator coalescer unit clamp had become undone and the unit separated from its ducting allowing the air to leak out.




Synopsis: Flight Engineer reported a progressive loss of cabin pressure as the result of a water separator unit clamp coming undone.
Date: 201709
Local time of day: 0601-1200
Location: MCO.Airport, FL
Flight conditions: VMC
Light: Daylight
Aircraft: Cessna Citation Sovereign (C680)
Operator: Corporate
Operating under: Part 91
Flight plan: IFR
Mission: Passenger
Flight phase: Initial Approach
Airspace: Class B MCO
ATC / advisory: TRACON F11
Second aircraft: A321
Reporter organization: Corporate
Reporter function: Pilot Flying; Captain
Reporter qualification: Flight Crew Instrument; Flight Crew Multiengine; Flight Crew Air Transport Pilot (ATP)
Anomaly: Inflight Event / Encounter Wake Vortex Encounter
Detector: Person Flight Crew
When detected: In-flight
Result: Flight Crew Took Evasive Action
Contributing factors: Environment - Non Weather Related; Procedure
Primary problem: Ambiguous

Narrative: While being vectored we were sequenced 6 miles in trail of an A321. On the descent at 6500 feet while on a downwind vector for a visual approach to runway 36L into the MCO airport we experienced wake turbulence. We slowed our rate of descent to avoid any further wake encounter. We referenced the ILS glideslope by staying a dot high to continue avoiding any potential further wake encounter. We encountered no further wake turbulence.




Synopsis: CE680 Captain reported encountering wake turbulence on arrival into MCO 6 miles in trail of an A321.
Date: 201305
Local time of day: 1201-1800
Location: ZZZ.Airport, US
Aircraft: Regional Jet 700 ER/LR (CRJ700)
Operator: Air Carrier
Operating under: Part 121
Mission: Passenger
Flight phase: Climb
Aircraft component: Main Gear Tire
Component problem: Failed
Reporter organization: Air Carrier
Reporter function: Dispatcher
Reporter qualification: Dispatch Dispatcher
Human factors: Confusion; Communication Breakdown; Workload
Anomaly: Aircraft Equipment Problem Critical; Deviation / Discrepancy - Procedural Published Material / Policy
Detector: Person Flight Crew
When detected: In-flight
Result: Flight Crew Diverted; Flight Crew Landed in Emergency Condition; General Declared Emergency
Contributing factors: Procedure; Aircraft
Primary problem: Aircraft

Narrative: Was made [aware] of the emergency landing into the station by Operations. I asked Operations if they knew why they diverted with an emergency. Operations didn't know. I quickly sent information Operation to flight talked to Captain when on ground and found out flight on takeoff blew a tire; ingested some of the tire into the engine. Flight was able to keep engine running. Landing safely with no problem with passengers. Since the flight landed so quickly after takeoff and wasn't made aware of the emergency until almost on ground. I wasn't able to send fuel numbers to flight. Busy with putting in the diversion entry forgot to amend release. Aircraft landed and couldn't amend release since it was already on the ground. I did file a record history explaining what happen with the diversion.Found out in my case that if the flight is already on ground I could put the amendment in the file.




Synopsis: A CRJ-700 tire failed on takeoff FOD'ing an engine so the crew declared an emergency and diverted to a nearby airport. The Dispatcher was not made aware of the divert reason until the crew was on the ground because of the short flight.
Date: 201312
Local time of day: 1201-1800
Location: ZZZ.Airport, US
Flight conditions: VMC
Weather elements / visibility: 10
Light: Daylight
Aircraft: P180 Avanti
Operator: Air Taxi
Operating under: Part 135
Flight plan: IFR
Mission: Passenger
Flight phase: Takeoff / Launch
Reporter organization: Air Taxi
Reporter function: Captain
Reporter qualification: Flight Crew Flight Instructor; Flight Crew Air Transport Pilot (ATP); Flight Crew Instrument; Flight Crew Multiengine
Human factors: Situational Awareness
Anomaly: Aircraft Equipment Problem Critical; Ground Excursion Runway
Detector: Person Flight Crew
When detected: In-flight
Result: Flight Crew Rejected Takeoff
Contributing factors: Aircraft; Human Factors; Weather
Primary problem: Aircraft

Narrative: Aircraft was about to depart the airport; acclerating down runway and upon reaching takeoff speed; pull back on control yoke and aircraft failed to rotate and become airborne. Soon there after; I elected to abort the takeoff using maximum reverse and braking. Aircraft came to rest as it exited the runway approximately 200 FT from the end of Runway 32. Cause of problem unknown; possible weather related with airport reporting below freezing temperatures. Done to prevent situation or recurrence. Receive more infomation regarding runway and airport conditions.




Synopsis: P180 pilot reports rejecting the takeoff after discovering the aircraft will not rotate at takeoff speed. The aircraft is stopped 200 FT beyond the end of the runway.
Date: 201409
Local time of day: 0601-1200
Location: ZZZ.TRACON, US
Weather elements / visibility: Fog; Rain; 10
Light: Daylight
Aircraft: RV-7
Operator: Personal
Operating under: Part 91
Flight plan: VFR
Mission: Personal
Flight phase: Descent
Airspace: Class E ZZZ
ATC / advisory: TRACON ZZZ
Reporter organization: Personal
Reporter function: Single Pilot; Pilot Flying
Reporter qualification: Flight Crew Private
Human factors: Physiological - Other; Training / Qualification
Anomaly: Deviation / Discrepancy - Procedural FAR; Inflight Event / Encounter Weather / Turbulence; Inflight Event / Encounter VFR In IMC
Detector: Person Flight Crew
When detected: In-flight
Result: Flight Crew Landed As Precaution; Flight Crew Diverted
Contributing factors: Weather; Human Factors; Procedure
Primary problem: Procedure

Narrative: The clouds had broken...and while the ceiling was still only around 3;000; I launched; confident I'd at least be able to get to [an intermediate stop]; less than an hour away; at which time I could re-evaluate the weather. I was planning a flight to [destination]; but not long after launching...I ran into showers and zigged and zagged along; until I saw broken sky. I then headed for it. Being on top seemed a better option than trying to cross the mountains running scud. A half hour or so later; the buildup seemed to grow ahead (I realized later this was an optical illusion); and [the intermediate stop] was now reporting overcast. Now; keep in mind; just several days earlier; I'd gone to [a safety seminar] on weather. So I knew better than to let myself get stuck on top; and yet -- here I was: unwilling to turn around and too stupid to check the weather ahead to see if it had afforded me any options. Instead; I circled the field as judged by my GPS; and then descended through 2;000 feet of clouds; somewhat confident than the ATIS reporting 3;900 broken; was correct. It was.It was illegal. It was stupid. And I apologized to the plane and; upon landing; went straight to the mirror and promised myself I'd never do such a stupid thing again. There were so many options -- better options -- I could have made and didn't.




Synopsis: RV-7 pilot continued VFR flight into worsening weather until becoming VFR On Top then descended through the overcast based on GPS position and was able to land in VMC.
Date: 201903
Location: ZZZ.Airport, US
Flight conditions: VMC
Aircraft: A320
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Takeoff / Launch
Reporter organization: Air Carrier
Reporter function: Pilot Not Flying; Captain
Reporter qualification: Flight Crew Multiengine; Flight Crew Instrument; Flight Crew Air Transport Pilot (ATP)
Second reporter function: First Officer; Pilot Flying
Anomaly: Deviation / Discrepancy - Procedural Hazardous Material Violation; Deviation / Discrepancy - Procedural Published Material / Policy; Deviation / Discrepancy - Procedural Weight And Balance
Detector: Person Dispatch
When detected: In-flight
Result: General None Reported / Taken
Contributing factors: Human Factors; Procedure
Primary problem: Procedure

Narrative: We were told after takeoff that we had dry ice in cargo pit 2; we did not get any notification by way of a DG form; [and] it was not noted on the final weights or on the service form. We were told it was less than 4 lbs; but might have been listed as less than 1lb. We had no animals in the pit.


Second narrative: After takeoff we were informed via ACARS that we had dry ice in cargo pit 2. We received no prior notification on a DG form; it was not noted on the final weights or on the aircraft service form. We were told it was less than 4 lbs but might have been listed as less than 1 lb. There were no animals in cargo pit 2. There were no issues as a result of this.


Synopsis: A320 flight crew reported receiving Dispatch notification during cruise of Hazmat [Dry Ice] loaded on aircraft without providing NOTOC [Notice to Captain] prior to departure.
Date: 201203
Local time of day: 0001-0600
Location: ZZZ.Airport, US
Flight conditions: VMC
Weather elements / visibility: 10
Aircraft: Dash 8-400
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Flight phase: Climb
Airspace: Class B ZZZ
ATC / advisory: Tower ZZZ
Aircraft component: Gear Extend/Retract Mechanism
Component problem: Malfunctioning
Reporter organization: Air Carrier
Reporter function: Captain; Pilot Flying
Reporter qualification: Flight Crew Air Transport Pilot (ATP)
Anomaly: Aircraft Equipment Problem Critical
Detector: Automation Aircraft Other Automation; Person Flight Crew
When detected: In-flight
Result: Flight Crew Overcame Equipment Problem; Flight Crew Returned To Departure Airport; General Declared Emergency
Contributing factors: Aircraft
Primary problem: Aircraft

Narrative: After takeoff the landing gear master caution warning sounded; landing gear failed To retract correctly. We notified ATC; were vectored to a safe airspace; ran the QRH; declared an emergency and returned to our deparature airport.




Synopsis: A DHC-8 declared and emergency and returned to their departure airport when the landing gear failed to retract normally.