elihoole/asrs-aviation-reports huggingface dataset:
Date: 201403
Local time of day: 1201-1800
Location: ZZZ.Airport, US
Flight conditions: VMC
Weather elements / visibility: 10
Light: Daylight
Aircraft: Light Sport Aircraft
Operator: FBO
Operating under: Part 91
Flight plan: None
Mission: Training
Flight phase: Landing
Airspace: Class D ZZZ
ATC / advisory: Tower ZZZ
Aircraft component: Nose Gear
Component problem: Failed
Reporter organization: FBO
Reporter function: Pilot Not Flying; Instructor
Reporter qualification: Flight Crew Flight Instructor; Flight Crew Commercial
Human factors: Training / Qualification; Human-Machine Interface
Anomaly: Aircraft Equipment Problem Critical; Ground Event / Encounter Ground Strike - Aircraft; Ground Event / Encounter Loss Of Aircraft Control
Detector: Person Flight Crew
When detected: In-flight
Result: General Maintenance Action
Contributing factors: Human Factors; Aircraft
Primary problem: Aircraft

Narrative: A student and I were landing on our second flight of the day together; one other person had flown the aircraft between our flights. It was our third and final landing of the flight. Before the incident both flights had been great with no abnormalities.On the last landing; which was a normal landing; the aircraft was drifting to the right after touchdown. I relieved the student of controls and noticed that the steering was not responding normally. I applied full left steering; confirmed that there was no throttle; and tried to correct the airplane to the left. It was slow; sluggish; and barely responsive although I managed to have the airplane turn off Runway XX and onto Runway XY. Once we cleared Runway XX I applied brakes; I felt (or heard) a snap and the nose wheel collapsed. We skidded for 100 feet or so to a stop. I then notified ATC and asked for assistance. A report was filed with the airport Sheriff's office and the airport fire department and the FSDO were contacted.No one was hurt.  The airplane was taken to a hanger for inspection at a later date by order of the FSDO.




Synopsis: When the student pilot appeared unable to control their LSA on the landing roll the instructor took the controls after which the nose wheel snapped off and the aircraft slid to a stop.  No one was injured.
Date: 201912
Local time of day: 1201-1800
Location: ZZZ.Airport, US
Aircraft: B737 Undifferentiated or Other Model
Operator: Personal
Flight phase: Parked
Aircraft component: Pneumatic Valve/Bleed Valve
Component problem: Design
Reporter organization: Personal
Reporter function: Technician
Reporter qualification: Maintenance Repairman
Anomaly: Aircraft Equipment Problem Critical; Deviation / Discrepancy - Procedural Published Material / Policy
Detector: Person Maintenance
Result: General None Reported / Taken
Contributing factors: Aircraft
Primary problem: Aircraft

Narrative: I would like to inform you that there is a system error in the precooler control system in the engine bleed system on Boeing 737 aircraft.The precooler control valve used in this system; when 390 F sensor remains open or if there is air leakage from the 390 F sensor control pressure sense line or wing thermal anti ice solenoid remains open; precooler control valve goes fully open with spring loaded. If Precooler control valve full open or hold any position; there is MEL restriction for icing condition As far as I know icing condition is a restriction required for wing anti ice.In the above mentioned cases (precooler control valve goes to full open position) engine bleed system does not give any malfunction or warning. This is a situation that conflicts with MEL item.An important restriction; such as icing condition; is that the system does not give a fault or warning under the conditions I have described above.However; many Boeing 737 aircraft may be flying in this condition. Any operator cannot be aware of this situation because no malfunction is seen. This situation create a dangerous situation; especially in winter.




Synopsis: Reporter stated that the precooler control valve on the B737 is poorly designed and subject to failures.
Date: 202110
Local time of day: 1801-2400
Location: ZZZ.Tower, US
Flight conditions: IMC
Aircraft: Commercial Fixed Wing
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Initial Approach
Airspace: Class D ZZZ
ATC / advisory: Tower ZZZ
Reporter organization: Air Carrier
Reporter function: Captain; Pilot Not Flying
Reporter qualification: Flight Crew Multiengine; Flight Crew Instrument; Flight Crew Air Transport Pilot (ATP)
Human factors: Workload; Distraction; Human-Machine Interface
Anomaly: Deviation - Altitude Excursion From Assigned Altitude; Deviation / Discrepancy - Procedural Clearance; Deviation / Discrepancy - Procedural Published Material / Policy; Inflight Event / Encounter CFTT / CFIT; Inflight Event / Encounter Unstabilized Approach; Inflight Event / Encounter Weather / Turbulence
Detector: Person Air Traffic Control; Person Flight Crew
When detected: In-flight
Result: Flight Crew Overcame Equipment Problem
Contributing factors: Human Factors
Primary problem: Human Factors

Narrative: While coming into ZZZ we checked the weather and the ceilings were not quite what we needed for the RNAV XX. We had plenty of gas and decided to ask for a hold. After holding we were informed of an aircraft that had broken out right at minimums. We decided to start the approach. We were cleared to cross the Initial Approach Fix at or above 3;000 ft. After crossing the fix the FO (First Officer) pilot flying; set the new altitude for 2;100 ft. which was the lowest altitude on the segment for the final app fix. After leveling off the First Officer then set 800 ft. for the MDA. Prior to the FAF I suggested flaps 45 instead of flaps 22 so we could get a lower deck angle and see the field better. He agreed so I was heads down while getting the new numbers. I was also told to contact Tower and after checking on he mentioned to check our altitude because he saw us low. At that point the FO was already correcting and we returned to the previous altitude promptly. This was corrected before the FAF so we didn't see a reason to terminate the approach. Not properly monitoring and heads down in a critical phase of flight. I shouldn't have suggested the late flap change. If I hadn't I could have noticed the FO descending early before ATC did. Next time I will keep what we have and after a missed approach I could change and try again.




Synopsis: Air carrier Captain reported altitude excursion during initial approach due to his failure to properly monitor flying pilot. Altitude excursion was corrected and flight completed a safe landing.
Date: 201711
Local time of day: 1201-1800
Location: BOS.Airport, MA
Light: Daylight
Aircraft: Small Transport; Low Wing; 2 Recip Eng
Operator: Air Taxi
Operating under: Part 135
Flight plan: IFR
Mission: Passenger
Flight phase: Climb
Airspace: Class B BOS
ATC / advisory: TRACON A90
Second aircraft: UAV - Unpiloted Aerial Vehicle
Reporter organization: Air Taxi
Reporter function: Captain; Pilot Flying
Reporter qualification: Flight Crew Air Transport Pilot (ATP)
Human factors: Situational Awareness
Anomaly: Airspace Violation All Types; Conflict NMAC; Deviation / Discrepancy - Procedural FAR; Inflight Event / Encounter Weather / Turbulence
Detector: Person Flight Crew
When detected: In-flight
Result: Air Traffic Control Provided Assistance; General Police / Security Involved
Contributing factors: Human Factors
Primary problem: Human Factors

Narrative: During climbout; I was about 2700 feet; 6-8 miles South-Southwest of Boston; I believe over the Quincy/Braintree area; I came within a couple hundred feet of drone. It was about 2 feet by 2 feet in size; black; four blade; and was rocking back and forth in the turbulence. I reported it to Boston Departure. The next controller followed up with more questions about it.




Synopsis: A Small Transport Captain reported a NMAC with a UAV operating in Boston Class B airspace without ATC knowledge.
Date: 201602
Local time of day: 0601-1200
Location: BWI.Tower, MD
Flight conditions: VMC
Light: Daylight
Aircraft: B737 Undifferentiated or Other Model
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Initial Approach
Airspace: Class B BWI
Reporter organization: Air Carrier
Reporter function: Captain; Pilot Not Flying
Reporter qualification: Flight Crew Air Transport Pilot (ATP)
Human factors: Situational Awareness
Second reporter function: First Officer; Pilot Flying
Anomaly: Deviation - Track / Heading All Types; Deviation / Discrepancy - Procedural Clearance
Detector: Person Air Traffic Control
When detected: In-flight
Result: Flight Crew Became Reoriented
Contributing factors: Human Factors
Primary problem: Human Factors

Narrative: At 6;000 feet AGL; we called BWI in sight. Approach told us we needed to be below 4;000 feet to be cleared for the approach to 10. I was Pilot Monitoring. The Pilot Flying configured the aircraft to landing configuration to execute a faster descent. While descending; we were vectored off the arrival. We focused on the descent more than our bearing to the airport due to a clear and a million day. We knew the airport was to our left. We were cleared for the visual to Runway 10. We turned toward the runway at BWI that we saw. As we got closer to BWI; we noticed the LOC wouldn't capture. As we were beginning discussion about this; Approach switched us to Tower. While trying to figure out why our NAV aids were off; Tower notified us immediately we were lined up for Runway 15. We were approximately six miles out. He asked if we would like 15R instead and cleared us to land. BWI Tower was amazing and professional in coming up with a solution fast. Our other option was to go-around (which we almost did; but Tower rectified the situation so fast). We landed 15R with no further issue.


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


Synopsis: Air Carrier flight crew on visual approach to BWI lines up on the wrong runway. Tower Controller notifies crew of this and offers them that runway which the crew accepts for landing.
Date: 202111
Local time of day: 1201-1800
Location: ZZZ.Airport, US
Flight conditions: VMC
Weather elements / visibility: 10
Aircraft: PA-28 Cherokee/Archer/Dakota/Pillan/Warrior
Operator: Personal
Operating under: Part 91
Flight plan: None
Mission: Personal
Flight phase: Taxi
ATC / advisory: Ground ZZZ
Second aircraft: Small Aircraft; Low Wing; 1 Eng; Retractable Gear
Reporter organization: Personal
Reporter function: Pilot Flying; Single Pilot
Reporter qualification: Flight Crew Instrument; Flight Crew Private
Human factors: Human-Machine Interface; Communication Breakdown; Situational Awareness; Workload
Anomaly: ATC Issue All Types; Conflict Ground Conflict; Critical; Deviation / Discrepancy - Procedural Clearance; Deviation / Discrepancy - Procedural Published Material / Policy; Ground Incursion Taxiway
Detector: Person Flight Crew
When detected: Taxi
Result: Flight Crew Took Evasive Action
Contributing factors: Human Factors
Primary problem: Human Factors

Narrative: I was cleared to taxi to parking; caution opposite direction traffic. Subsequently;  Aircraft Y was cleared to taxi; caution opposite direction traffic. While I was taxiing on [the] centerline; Aircraft Y exited the ramp approximately 1-200 feet in front of me; taxied across my path; and turned towards me with insufficient room to pass. I deviated off the centerline to avoid a collision and it passed with an estimated clearance of 3 feet between wingtips. After parking; I called Tower and reported it as an unsafe situation. In my judgment Aircraft Y should not have been cleared to taxi given the close distance between me and his ramp location; and he should not have crossed so close in front of me requiring a deviation to avoid a collision. It would have taken a small fraction of a minute for me to pass the ramp location of Aircraft Y and avoid the situation.




Synopsis: GA pilot reported a ground conflict with opposite direction traffic during taxi to parking. Pilot deviated off the centerline to avoid a collision. Pilot further stated ATC caused the conflict by issuing taxi clearance to opposite direction aircraft with insufficient room to pass safely.
Date: 201210
Local time of day: 0601-1200
Location: ZDC.ARTCC, VA
Flight conditions: IMC
Light: Dawn
Aircraft: Gulfstream IV / G350 / G450
Operator: Corporate
Operating under: Part 91
Flight plan: IFR
Mission: Passenger
Flight phase: Descent
Airspace: Class A ZDC
ATC / advisory: Center ZDC
Reporter organization: Corporate
Reporter function: Pilot Not Flying; First Officer
Reporter qualification: Flight Crew Multiengine; Flight Crew Flight Instructor; Flight Crew Instrument; Flight Crew Air Transport Pilot (ATP)
Human factors: Human-Machine Interface; Distraction; Communication Breakdown; Situational Awareness
Anomaly: Deviation - Speed All Types; Deviation / Discrepancy - Procedural Clearance; Deviation / Discrepancy - Procedural Published Material / Policy
Detector: Person Flight Crew
When detected: In-flight
Result: General None Reported / Taken
Contributing factors: Human Factors; Procedure
Primary problem: Procedure

Narrative: We were cleared to descend and maintain FL290 prior to beginning the GIBZZ RNAV STAR to IAD (not cleared to 'descend via'). I was the First Officer and non flying pilot. Just passed MGW; I left the number one radio to go over to number two; record the ATIS; and call the FBO to ensure passenger transportation was set up. While I was off the center frequency; the Captain queried ATC if we were to expect a 'descend via' clearance. The 'descend via' clearance was given just past the BRNDN Intersection. The Captain initiated a descent to comply with the crossing altitudes and speed restrictions. When I returned to the number one radio the Captain and I had a brief discussion about the changes that had occurred while I was off frequency. It soon became apparent that we would not be able to comply with the 280 KTS at JIMVE Intersection due to the late 'descend via' clearance. We advised ATC of this.This is a relatively new arrival with lots of crossing restriction and is very busy. The first few fixes are very close together. In the future; I will proactively begin a speed reduction and ensure both pilots are watching the arrival to avoid this situation.




Synopsis: A G-IV flight crew was unable to comply with the crossing speed restriction at JIMVE waypoint when they received their 'descend via the GIBZZ RNAV STAR' clearance late.
Date: 201710
Local time of day: 1801-2400
Location: ZZZ.Airport, US
Flight conditions: VMC
Light: Night
Aircraft: A300
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: Flap Control (Trailing & Leading Edge)
Component problem: Malfunctioning
Reporter organization: Air Carrier
Reporter function: Captain; Pilot Not Flying
Reporter qualification: Flight Crew Air Transport Pilot (ATP)
Human factors: Troubleshooting
Second reporter function: First Officer; Pilot Flying
Anomaly: Aircraft Equipment Problem Less Severe; Inflight Event / Encounter Fuel Issue
Detector: Person Flight Crew
When detected: In-flight
Result: Air Traffic Control Provided Assistance; Flight Crew Landed As Precaution; Flight Crew Overcame Equipment Problem
Contributing factors: Aircraft
Primary problem: Aircraft

Narrative: Burned more fuel than planned due to long taxi to [departure runway]; then change of arrival [STAR] from ZZZZ1 with Runway 27 to the ZZZZ2 and Runway 36R. We were also told to maintain best forward speed. Our arrival fuel became a concern; but we were still planning on arriving with about 10;000 lbs. Originally we would have arrived with better than 12;000 lbs. FO optimized flying the arrival as best as possible to conserve fuel. On approach to Runway 36R approximately at 1500 feet FO called for flaps 30/40. We received an ECAM of System 1 & 2 Flaps stuck. I called out the ECAM and completed the phase one of recycling the flap handle. The flaps remained stuck at 20 degrees. With a brief discussion we concurred that continuing in to land was the safest course of action considering the problem and our low fuel state. We completed the before landing checklist; bumped the approach speed up to 136 kts and selected the flap selector switch to 15/20. I [advised ATC] due to the problem with the flaps. Tower asked if we needed to roll the trucks; since we did have 20 degrees of flaps; which is normal for the windshear configuration; I felt we didn't need the fire rescue vehicles. Landing was uneventful. The malfunction was written up for maintenance; Operations; and the duty pilot were notified. There is a previous write up for this aircraft of the slats getting stuck.


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


Synopsis: A300 flight crew reported that during approach the flaps became stuck at 20 degrees.
Date: 201810
Local time of day: 0601-1200
Location: ZZZ.Airport, US
Aircraft: Small Aircraft; Low Wing; 1 Eng; Fixed Gear
Operator: Personal
Operating under: Part 91
Flight plan: IFR
Mission: Training
Aircraft component: Engine
Component problem: Failed
Reporter organization: Personal
Reporter function: Instructor; Pilot Flying
Reporter qualification: Flight Crew Flight Instructor; Flight Crew Commercial; Flight Crew Instrument
Human factors: Situational Awareness
Anomaly: Aircraft Equipment Problem Critical; Deviation / Discrepancy - Procedural Published Material / Policy
Detector: Person Flight Crew
When detected: In-flight
Result: Flight Crew Inflight Shutdown; Flight Crew Landed in Emergency Condition
Contributing factors: Aircraft; Human Factors
Primary problem: Ambiguous

Narrative: Engine failure on a three mile final; the cause of which is unknown; the airplane was successfully landed [off airport]. Better use of procedural flying could've restarted the airplane.




Synopsis: GA instructor pilot reported an off-field landing after experiencing an engine failure in flight.
Date: 201604
Local time of day: 1201-1800
Location: ZZZ.Airport, US
Flight conditions: VMC
Light: Daylight
Aircraft: Widebody; Low Wing; 2 Turbojet Eng
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Taxi
Reporter organization: Air Carrier
Reporter function: Captain; Pilot Flying
Reporter qualification: Flight Crew Air Transport Pilot (ATP)
Human factors: Distraction
Anomaly: Deviation / Discrepancy - Procedural Security; Flight Deck / Cabin / Aircraft Event Passenger Misconduct
Detector: Person Flight Attendant
When detected: Taxi
Result: General Police / Security Involved
Contributing factors: Human Factors
Primary problem: Human Factors

Narrative: Upon taxi into gate we had to stop short of gate to wait marshallers. Passengers were asked to remain seated until seat belt sign was turned off. Passenger left her seat and approached flight deck door. Flight attendant intervened and the passenger struck the flight attendant. Air Marshalls intervened at this time and handcuffed passenger. Purser informed me of the situation by inter phone and advised there was a level 2 incident in the cabin. We called the station on company radio and asked for police assistance. Police arrived and deplaned passenger. Flight Attendant who was struck by passenger was ok and we operated the return flight without incident.




Synopsis: Air carrier Captain reported being advised of an unruly passenger while taxiing to the gate. The passenger; who had struck a Flight Attendant; was handcuffed by air marshals and delivered to local airport police authorities at the gate.
Date: 201909
Local time of day: 0601-1200
Location: ATL.Airport, GA
Flight conditions: VMC
Light: Daylight
Aircraft: Regional Jet 200 ER/LR (CRJ200)
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Final Approach
Airspace: Class B ATL
ATC / advisory: Tower ATL
Second aircraft: UAV - Unpiloted Aerial Vehicle
Reporter organization: Air Carrier
Reporter function: Captain; Pilot Not Flying
Reporter qualification: Flight Crew Air Transport Pilot (ATP); Flight Crew Instrument; Flight Crew Multiengine
Human factors: Distraction; Situational Awareness
Anomaly: Conflict Airborne Conflict
Detector: Person Flight Crew
When detected: In-flight
Result: General None Reported / Taken
Contributing factors: Airspace Structure; Procedure; Human Factors; Aircraft
Primary problem: Aircraft

Narrative: I was Pilot Monitoring on our way into ATL. We were approximately at 1;500 or so feet on final into [Runway] 8L when I noticed a large white drone aircraft off to our lower left side moving west bound approximately 500 ft. below us. The best ground reference I could make was the large manufacturing warehouse with the 'BJ's' logo painted on the roof. It was white and had four props. I notified ATC of such which they passed on pilot reports and relayed into the ATIS. After landing; Tower requested a phone call for follow up. The [airliner] two aircraft back also saw the drone circling an apartment complex. I called ATC at the gate in which they took down basic information and asked if we took evasive action; which we had not. The event was caused by an individual or individuals illegally operating a UAS within 5nm of an airfield. I might suggest some guidance in a memo or CFM/FOM procedure on operations in these circumstances as drone encounters are becoming more and more frequent.




Synopsis: Captain reported encountering a drone while on approach to ATL.
Date: 202010
Local time of day: 0601-1200
Location: ZZZ.Tower, US
Weather elements / visibility: clear; 10
Aircraft: Balloon
Operator: Personal
Operating under: Part 91
Flight plan: VFR
Mission: Passenger
Flight phase: Landing
Airspace: Class D ZZZ
Reporter organization: Personal
Reporter function: Pilot Flying
Reporter qualification: Flight Crew Commercial
Human factors: Situational Awareness
Anomaly: Deviation / Discrepancy - Procedural Published Material / Policy; Ground Event / Encounter Loss Of Aircraft Control; Ground Event / Encounter Object; Inflight Event / Encounter Weather / Turbulence
Contributing factors: Human Factors; Weather
Primary problem: Weather

Narrative: On final approach at an altitude of approximately 50 feet AGL we experienced a sudden shift in horizontal wind speed that landed the balloon in the front yard of a residence at [Address]. The basket landed beside the front of the residence creating minor damage to a window ledge and downspout on a gutter. There were no injuries to passengers or pilot and none to people on the ground as it was early in the morning with no people outside. The police and fire department responded and a police report was submitted. The residence was inspected by the fire department and found to have minimal cosmetic damage. No structural damage was found. There was no damage to the balloon or it's structural components. Arrangements have been made to correct the cosmetic damage to the residence with the owners representative.




Synopsis: Hot air balloon pilot reports landing balloon in neighborhood yard.