elihoole/asrs-aviation-reports huggingface dataset:
Date: 202110
Aircraft: B737 MAX 9
Operator: Air Carrier
Operating under: Part 121
Flight phase: Parked
Aircraft component: Wheels/Tires/Brakes
Component problem: Malfunctioning
Reporter organization: Air Carrier
Reporter function: Technician
Anomaly: Aircraft Equipment Problem Less Severe
Detector: Person Maintenance
When detected: Aircraft In Service At Gate
Result: General Maintenance Action
Contributing factors: Aircraft
Primary problem: Aircraft

Narrative: The B737 MAX 9 has a chronic problem with tire pressures dropping considerably and I have found brake brackets cracked. This is just one aircraft. This needs to be looked at ASAP.




Synopsis: Maintenance Technician reported chronic low tire pressures as well as cracked brake brackets on multiple B737 MAX 9 aircraft.
Date: 201907
Local time of day: 1201-1800
Location: ZZZ.Airport, US
Flight conditions: VMC
Weather elements / visibility: 10
Light: Daylight
Aircraft: Aerobatic
Operator: Personal
Operating under: Part 91
Flight plan: None
Mission: Personal
Flight phase: Landing
Airspace: Class E ZZZ; Class G ZZZ
ATC / advisory: UNICOM ZZZ
Reporter organization: Personal
Reporter function: Single Pilot; Pilot Flying
Reporter qualification: Flight Crew Private
Human factors: Training / Qualification; Situational Awareness
Anomaly: Ground Event / Encounter Ground Strike - Aircraft; Ground Event / Encounter Loss Of Aircraft Control; Inflight Event / Encounter Weather / Turbulence
Detector: Person Flight Crew
When detected: In-flight
Result: Aircraft Aircraft Damaged
Contributing factors: Aircraft; Human Factors; Weather
Primary problem: Weather

Narrative: After carrying out 3 prior landings; [I made a] normal approach on center line. Normal landing made and as plane slowed to walking pace it began to ground loop. Aircraft controlled by rudder/braking inputs; [but the] aircraft nosed over [and] came to stop just right of runway center line and parallel to runway direction. Suspected wind shear. Pilot shut down systems and fuel system and exited aircraft. No injuries to pilot. Minimal damage to prop and spinner - no structural damage; weather was CAVOK.




Synopsis: Great Lakes 2T pilot reported a ground loop occurred late in the landing roll when he encountered suspected wind shear.
Date: 201907
Local time of day: 0001-0600
Location: ZZZ.Airport, US
Weather elements / visibility: Lake Effect; 10
Light: Dusk
Aircraft: Balloon
Operator: Personal
Operating under: Part 91
Flight plan: None
Mission: Personal
Flight phase: Final Approach
Reporter organization: Personal
Reporter function: Single Pilot
Reporter qualification: Flight Crew Private
Human factors: Situational Awareness; Time Pressure; Workload
Anomaly: Ground Event / Encounter Object; Inflight Event / Encounter Loss Of Aircraft Control
Result: Aircraft Aircraft Damaged; Flight Crew Took Evasive Action
Contributing factors: Environment - Non Weather Related; Weather; Human Factors
Primary problem: Ambiguous

Narrative: Approximately .5 mile from the attended landing area (approach end of runway 01) I descended to 100 ft. AGL and leveled off preparing for final approach. Before the descent our speed was at 11mph; at 100 ft. AGL the wind had increased to 14 mph. At 0.24 mi from our intended landing point 500 ft. from the power lines we started an unexpected decent (roller/ down draft). I started burning to arrest the decent (Approximately 20 second). The Balloon did not start to climb until just before the power lines. One power line caught on the bottom of the basket then released as we climbed out. Climbing at a high rate I vented to slow it down and must have got caught in the down draft again and started another fast-decent into a tree. Due to the high rate of burn I lifted out of the tree were I must have been hit by wind shear (at 100 ft. the winds were at 14mph and on the ground ZZZ showing calm) knocking the air out of the envelope as we were on our final descent closing the throat of the balloon causing some fabric to get burnt in the lower gore area during final decent.




Synopsis: A pilot reported losing control of his balloon due to gusty winds; which resulted in a brief contact with power lines.
Date: 202107
Local time of day: 1801-2400
Location: ZZZ.Airport, US
Flight conditions: VMC
Light: Night
Aircraft: A320
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: Oil Contents Indication
Component problem: Malfunctioning
Reporter organization: Air Carrier
Reporter function: First Officer
Reporter qualification: Flight Crew Multiengine; Flight Crew Air Transport Pilot (ATP); Flight Crew Instrument
Anomaly: Aircraft Equipment Problem Critical; Deviation / Discrepancy - Procedural Clearance
Detector: Person Flight Crew
When detected: In-flight
Result: Air Traffic Control Provided Assistance; Flight Crew Requested ATC Assistance / Clarification; Flight Crew Returned To Departure Airport; Flight Crew Landed As Precaution; General Flight Cancelled / Delayed; General Maintenance Action
Contributing factors: Aircraft
Primary problem: Aircraft

Narrative: On climb out from ZZZ; we noticed engine oil quantity on engine #2 had gone to 0. We notified ATC and returned to ZZZ. All other indications were normal. The landing was uneventful and we taxied to the gate.




Synopsis: First Officer reported loss of #2 engine oil quantity caused them to make an air turn back to a precautionary landing.
Date: 201903
Local time of day: 0601-1200
Location: UUWV.ARTCC, FO
Flight conditions: VMC
Light: Daylight
Aircraft: Falcon 900
Operator: Corporate
Operating under: Part 91
Flight plan: IFR
Mission: Passenger
Flight phase: Cruise
ATC / advisory: Center UUWV
Aircraft component: GPS & Other Satellite Navigation
Component problem: Malfunctioning
Reporter organization: Corporate
Reporter function: Pilot Flying; Captain
Reporter qualification: Flight Crew Multiengine; Flight Crew Instrument; Flight Crew Air Transport Pilot (ATP)
Human factors: Troubleshooting; Confusion
Anomaly: Aircraft Equipment Problem Less Severe
Detector: Automation Aircraft Other Automation; Person Flight Crew
When detected: In-flight
Result: General None Reported / Taken
Contributing factors: Aircraft
Primary problem: Aircraft

Narrative: After Departing UUWW for ZZZZ while cruising at FL380 approximately 200 miles NW of UUWW GPS 1 and GPS 2 both failed for about 1 minute then returned to service and then again failed for about 1 minute and again returned to service.No GPS failures occurred prior to or after this specific event. As stated both GPS units failed simultaneously. The airplane's navigational performance did not appear to be degraded by these momentary failures as the airplane is equipped with dual IRS (Internal Reference System) which were unaffected.No known atmospheric interference occurred and no known GPS satellite outages occurred. In retrospect there may have been some sort of interference associated with the GPS receivers which caused these failure messages. The actual cause is unknown.




Synopsis: DA50-900EX Captain reported GPS 1 and GPS 2 both failed at the same time then returned to service and then again failed and again returned to service.
Date: 201910
Local time of day: 1201-1800
Location: ZZZ.Tower, US
Flight conditions: VMC
Light: Daylight
Aircraft: Commercial Fixed Wing
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Cargo / Freight / Delivery
Flight phase: Final Approach
Airspace: Class B ZZZ
ATC / advisory: Tower ZZZ
Aircraft component: Autothrottle/Speed Control
Component problem: Improperly Operated
Reporter organization: Air Carrier
Reporter function: First Officer; Pilot Flying
Reporter qualification: Flight Crew Air Transport Pilot (ATP); Flight Crew Instrument; Flight Crew Multiengine
Human factors: Communication Breakdown
Anomaly: ATC Issue All Types; Aircraft Equipment Problem Less Severe; Deviation - Speed All Types; Deviation / Discrepancy - Procedural Published Material / Policy
Detector: Person Flight Crew
When detected: In-flight
Result: Air Traffic Control Provided Assistance; Flight Crew Overcame Equipment Problem; General Flight Cancelled / Delayed
Contributing factors: Aircraft; Procedure
Primary problem: Procedure

Narrative: On short final into ZZZ; Tower told us to go around; it was an unexpected clearance and in the process I thought I had reengaged the Autopilot but had not; and did not call for Go around flaps fast enough to keep the aircraft from over speeding the flaps by about 7 knots.  Had I engaged the autopilot or pulled the power back from the TOGA (Takeoff Go Around) setting the issue would not have occurred.  After being vectored around Tower informed us that they had a false indication of a vehicle or other object entering the runway area.  I attempted to submit this [Report] a few days after the incident when it was fresh in my mind; but I used the Company app and after having several issues; I thought it submitted but only realized it didn't submit when I received notification from the [Report] committee.Refreshing Go around procedures more often and verifying that the autopilot is engaged.




Synopsis: First Officer reported not reengaging the autopilot on a go around; resulting in a flap overspeed.
Date: 201508
Local time of day: 1801-2400
Location: ZZZ.Airport, US
Flight conditions: VMC
Weather elements / visibility: 10
Light: Night
Aircraft: Duke 60
Operator: Personal
Operating under: Part 91
Flight plan: None
Mission: Training
Flight phase: Landing
ATC / advisory: Tower ZZZ
Aircraft component: Nose Gear
Component problem: Failed
Reporter organization: Personal
Reporter function: Instructor; Pilot Not Flying
Reporter qualification: Flight Crew Instrument; Flight Crew Air Transport Pilot (ATP); Flight Crew Flight Instructor; Flight Crew Multiengine
Human factors: Troubleshooting; Workload
Anomaly: Aircraft Equipment Problem Critical
Detector: Person Flight Crew
When detected: In-flight
Result: Aircraft Aircraft Damaged; Flight Crew Landed in Emergency Condition; General Maintenance Action
Contributing factors: Aircraft; Procedure
Primary problem: Aircraft

Narrative: On landing left main landing gear collapsed. Shortly after the nose wheel collapsed. Aircraft came to rest on left side off runway. There were 5 occupants in the aircraft; no injuries. The landing was a normal touchdown; no side loading on the gear. Winds were 270 at 5 knots.On a previous landing had an indication that nose landing gear was not down and locked. Completed POH procedure and did receive an indication of nose gear being down and locked. Landed without incident; nose gear down and locked light illuminated after touchdown.Had the aircraft inspected by a mechanic at the FBO. Was advised the gear was down and locked and the likely issue was the gear motor. Was recommended to fly the aircraft back to its home field with gear down and have maintenance performed.




Synopsis: A BE-60 nose gear indicated not down and locked on the previous approach but did lock after landing. A mechanic recommended gear down ferry to home base. The next landing the left main collapsed followed by the nose gear. No injuries resulted.
Date: 201910
Local time of day: 1801-2400
Location: FLL.Airport, FL
Light: Night
Aircraft: B737 Next Generation Undifferentiated
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Takeoff / Launch
Airspace: Class C FLL
ATC / advisory: Tower FLL
Second aircraft: Caravan Undifferentiated
Reporter organization: Government
Reporter function: Ground
Reporter qualification: Air Traffic Control Fully Certified
Human factors: Confusion; Distraction; Situational Awareness
Anomaly: ATC Issue All Types; Conflict Ground Conflict; Critical; Deviation / Discrepancy - Procedural Clearance; Deviation / Discrepancy - Procedural Published Material / Policy; Ground Incursion Runway
Detector: Person Air Traffic Control
When detected: Taxi
Result: Air Traffic Control Issued Advisory / Alert
Contributing factors: Airport; Human Factors
Primary problem: Airport

Narrative: I told Aircraft X; who landed on Runway 28L to taxi via [Taxiway] E and B5; and hold short of Runway 28R to get to parking. The pilot read back that he would hold short of Runway 28R. There was moderate traffic volume and it was nighttime. There were numerous taxiway closures due to construction; creating an unsafe situation in my opinion. I taxied several other aircraft that called for taxi. When I scanned back to observe Aircraft X; he had taxied past the hold short bars and was on the south edge of Runway 28R. At the same time; Aircraft Y had just rotated on Runway 28R. A collision was narrowly averted. I believe that the lack of the runway safety hold lights being on; combined with a very confusing runway crossing point due to poor planning for the runway being opened with so many taxiway closures were contributing factors to the event. The pilot also advised that one of the Runway 28R hold signs were unlit. Serious and swift safety steps should be taken to prevent a future safety event or disaster from happening. Runway 28R should not have been opened with so many associated taxiways closed. The Runway occupancy safety lights must be swiftly returned to service. Runway lights and signs that are unlit should be fixed as quickly as possible.




Synopsis: FLL Tower Controller reported that taxiway closures and unlit runway and taxiway signs resulted in a runway incursion and a critical ground conflict.
Date: 202109
Local time of day: 0001-0600
Location: ZZZ.Airport, US
Aircraft: A300
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Cargo / Freight / Delivery
Flight phase: Taxi
Airspace: Class D ZZZ
ATC / advisory: Tower ZZZ
Aircraft component: Gear Extend/Retract Mechanism
Component problem: Malfunctioning
Reporter organization: Air Carrier
Reporter function: Dispatcher
Reporter qualification: Dispatch Dispatcher
Anomaly: Aircraft Equipment Problem Critical; Deviation / Discrepancy - Procedural Clearance; Deviation / Discrepancy - Procedural Published Material / Policy
Detector: Person Flight Crew
When detected: In-flight
Result: Air Traffic Control Provided Assistance; Flight Crew Requested ATC Assistance / Clarification; Flight Crew Returned To Departure Airport; Flight Crew Landed As Precaution; General Maintenance Action; General Flight Cancelled / Delayed
Contributing factors: Aircraft
Primary problem: Aircraft

Narrative: The crew conducted an air return due to the landing gear not retracting.




Synopsis: Dispatcher reported Flight Crew conducted an air turn back after landing gear would not retract.
Date: 201512
Local time of day: 1201-1800
Location: ZZZ.TRACON, US
Flight conditions: Marginal
Aircraft: No Aircraft
Reporter organization: Government
Reporter function: Supervisor / CIC; Approach
Reporter qualification: Air Traffic Control Fully Certified
Human factors: Training / Qualification; Workload
Anomaly: ATC Issue All Types; Inflight Event / Encounter Other / Unknown
Detector: Person Air Traffic Control
When detected: Routine Inspection
Result: Air Traffic Control Provided Assistance
Contributing factors: Staffing; Weather; Manuals; Airspace Structure; Human Factors
Primary problem: Human Factors

Narrative: The weather that morning was IFR and RVR's were relevant. After losing the minimums for Runway XYL the operation then swung to Runway XXL. The forecast was from continued improvement in the weather but that obviously did not occur. My objective that morning was to accomplish as many ELMS (computer based supplemental training) as possible. We have several ELMS due by the end of this month. I made a decision to consolidate the operation to 2 radar scopes. We had just put 8 arrivals down in the first 15 minutes and in my judgment other than the last of the morning departure push we were in a significant lull. My intention at this point was to give people a break before assigning additional people ELMS. I had 2 Controllers returning shortly from their ELMS to reopen those positions and 1 other due back shortly from break. Two sectors were very busy but very much in control. I looked again at the timeline to ensure the string from ZZZZZ Intersection was drying up. At approximately XA40Z an aircraft went around. I immediately paged a controller to the TRACON as I knew I was losing RVR to continue to land Runway XYL. He opened a sector but at this point the departure controller was way behind with the volume and complexity of his traffic. There was no runway to land due to closures which immediately doubled the volume and complexity for the controllers. Another controller also returned to the TRACON and I asked him to relieve a sector. It took him 5 minutes until he was able to take the position. I then had another controller open another sector. The controller was unable to give her the position due to their volume. I made numerous mistakes and lacked sound judgment during this event. First and foremost I compromised my people for trying to accomplish an administrative task. I also had no safety net in place in the event that I lost the runway. Had I kept another sector open I believe much of what transpired would have still occurred but I was wrong to take away another set of eyes from the operation. I also should have had a returning controller open another sector instead of relieving an already open sector. I also did not consider the lack of open runways and that should have been one of the firs things to consider.




Synopsis: An ATC Supervisor did not open enough sectors in the facility to manage the traffic workload.
Date: 201404
Local time of day: 0001-0600
Location: ZZZZ.Airport, FO
Aircraft: B777 Undifferentiated or Other Model
Operator: Air Carrier
Operating under: Part 121
Flight phase: Parked
Reporter organization: Air Carrier
Reporter function: Captain; Pilot Not Flying
Reporter qualification: Flight Crew Air Transport Pilot (ATP)
Human factors: Communication Breakdown; Workload
Second reporter function: Relief Pilot; First Officer; Pilot Not Flying
Anomaly: Deviation / Discrepancy - Procedural Published Material / Policy; Deviation / Discrepancy - Procedural FAR
Detector: Person Flight Crew
When detected: Routine Inspection
Result: General None Reported / Taken
Contributing factors: Chart Or Publication; Procedure; Company Policy
Primary problem: Ambiguous

Narrative: Dispatch and flight crew failed to notice that ZZZZ was no longer a suitable ETOPS alternate based on the information provided.After flight during company audit. Multiple flights; multiple companies.


Second narrative: NOTAM indicated that the automated weather was unable to provide altimeter visibility and density. ZZZZ SVC AUTOMATED WEATHER BROADCAST SYSTEM VIS; ALT AND DENSITY ALT NOT AVBL.Nowhere does it say the automated weather was the only weather source on the island. I have personally been to Midway and know that there are airport personnel out there. I would like to believe that one of those people can actually read a barometer; anemometer and tell me what the visibility is; when I contact them on 126.2 per the Pacific 1/2 chart prior to the approach. 'The local altimeter is required per the commercial chart notes for all approaches into ZZZZ (Use local altimeter setting; if not received; procedure not authorized); thereby rendering the approaches useless. Without any useable approaches; ZZZZ could not be applied as an alternate per our Ops Specs.' If the approach is unauthorized; the NOTAM should state 'APPROACH UNAUTHORIZED' not some ambiguous comment about an automated device.


Synopsis: A B777 crew flew an oceanic flight with ZZZZ as an ETOPS alternate; but it was not legal because of inadequate weather information.
Date: 202108
Local time of day: 1201-1800
Location: ZZZ.Airport, US
Flight conditions: VMC
Weather elements / visibility: 10
Light: Daylight
Aircraft: Cessna 210 Centurion / Turbo Centurion 210C; 210D
Operator: Personal
Operating under: Part 91
Flight plan: IFR
Mission: Personal
Flight phase: Initial Climb
Airspace: Class D ZZZ1
ATC / advisory: TRACON ZZZ1
Aircraft component: Reciprocating Engine Assembly
Component problem: Malfunctioning
Reporter organization: Personal
Reporter function: Pilot Flying; Single Pilot
Reporter qualification: Flight Crew Instrument; Flight Crew Private
Human factors: Situational Awareness; Troubleshooting; Communication Breakdown
Anomaly: Aircraft Equipment Problem Critical; Deviation / Discrepancy - Procedural Published Material / Policy
Detector: Person Flight Crew
When detected: In-flight
Result: Air Traffic Control Provided Assistance; Flight Crew Requested ATC Assistance / Clarification; Flight Crew Returned To Departure Airport; General Maintenance Action; General Flight Cancelled / Delayed
Contributing factors: Aircraft
Primary problem: Aircraft

Narrative: Departed ZZZ on Runway XX at XA01. Engine ran smoothly on run-up and during takeoff roll; all cylinder temperatures normal. Assigned climb to 5;000 ft. via radar vector 200 heading by ZZZ Tower. After departure; handed off to ZZZ1 Approach. Checked in with ZZZ1 Approach at approximately 2;200 ft. MSL; after which the engine started to run very roughly and cylinder head temperatures started to rise above normal levels. [Requested priority handling] with ZZZ1 Approach and stated that I needed to return immediately to ZZZ. ZZZ1 Approach asked if we needed assistance; to which I replied negative. Switched back to ZZZ Tower; requested priority handling with them again; and stated that we would be returning to the airport and landing on Runway XY.ZZZ Tower cleared out other traffic and cleared us to land on Runway XX; in response to which I restated that [we] would be landing on Runway XY. This back-and-forth transmission was repeated a couple of times; but eventually [we] were cleared to land on Runway XY by ZZZ Tower. Completed 270-degree turn; extended landing gear; and landed on Runway XY without further incident. [We] were able to taxi back to ramp with no further issue. Problem hasn't been verified; but suspect water contaminated fuel that sloshed to fuel pickup on rotation. Will analyze engine logs to check for proper fuel flow.




Synopsis: C210 pilot reported engine power loss on climb-out and elected to perform an air turn back and precautionary landing.