elihoole/asrs-aviation-reports huggingface dataset:
Date: 202105
Local time of day: 1201-1800
Location: ZZZ.TRACON, US
Flight conditions: VMC
Weather elements / visibility: 10
Light: Daylight
Aircraft: Texan T6/Harvard (Antique)
Operator: Military
Operating under: Part 91
Flight plan: VFR
Mission: Training
Flight phase: Cruise
Airspace: Class E ZZZ
ATC / advisory: Center ZZZ
Second aircraft: Small Aircraft; Low Wing; 2 Eng; Retractable Gear
Reporter organization: Military
Reporter function: Instructor
Reporter qualification: Flight Crew Commercial; Flight Crew Flight Instructor; Flight Crew Instrument; Flight Crew Rotorcraft
Human factors: Communication Breakdown; Situational Awareness
Anomaly: ATC Issue All Types; Airspace Violation All Types; Conflict NMAC; Deviation / Discrepancy - Procedural FAR; Deviation / Discrepancy - Procedural Published Material / Policy
Detector: Automation Aircraft TA
When detected: In-flight
Result: Flight Crew Took Evasive Action
Contributing factors: Human Factors; Procedure
Primary problem: Human Factors

Narrative: Training flight working in the MOA. In comms with ZZZ Center; but operating VFR within the bounds of our assigned MOA block. We were executing a variety of contact maneuvers between 12;000-17;999 MSL; including basic air work; out of control flight; and unusual attitudes. We were monitoring the assigned ZZZ center frequency; but were not able to pay close attention due to focus on the training maneuvers. At one point I heard a civilian aircraft being advised that they were filing a flight plan through an active MOA; but did not hear the aircraft's response. I heard multiple company aircraft checking in for the MOA; including blocks adjacent to mine. Immediately before the NMAC; I set up my student for a nose-low unusual attitude recovery maneuver. I noted a TCAS contact; but it was on a depicted section line for the MOA; so I dismissed the contact as company traffic with the expectation they would be deconflicted through SOP adherence. As we entered a significant nose-low descent for training; we received another traffic advisory; very close to us. We executed a 5G pull and turn for avoidance. Our indicated altitude dropped below the contact. I'd estimate we came within 100 feet of the conflict; though I did not get visual on the other aircraft. Center called us and asked if we had to execute a significant evasive maneuver; and advised that the conflict had been a civilian multi engine aircraft. The controller was apologetic for not providing a traffic call to us; though due to how dynamic our training maneuver was; I don't believe the controller could have anticipated the severity of the conflict.




Synopsis: Texan T6/Harvard pilot reported taking evasive action during a training flight in response to a NMAC with a aircraft that entered their MOA block.
Date: 202201
Local time of day: 0001-0600
Location: IND.TRACON, IN
Aircraft: Large Transport; Low Wing; 2 Turbojet Eng
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Cargo / Freight / Delivery
Flight phase: Initial Approach
Airspace: Class C IND
ATC / advisory: TRACON IND
Aircraft component: Autothrottle/Speed Control
Component problem: Failed
Reporter organization: Air Carrier
Reporter function: Captain; Pilot Flying
Reporter qualification: Flight Crew Air Transport Pilot (ATP)
Anomaly: Aircraft Equipment Problem Less Severe
Detector: Person Flight Crew
When detected: In-flight
Result: General None Reported / Taken
Contributing factors: Aircraft; Environment - Non Weather Related
Primary problem: Aircraft

Narrative: While on approach about 7 miles out our autothrottles failed. Only reporting because of recent 5G concerns. Flight continued without incident.




Synopsis: Air carrier Captain reported failure of autothrottles on approach into IND; citing possible 5G interference as contributing.
Date: 202002
Local time of day: 0601-1200
Location: PWT.Airport, WA
Flight conditions: VMC
Weather elements / visibility: 10
Light: Daylight
Aircraft: Cessna 152
Operator: Personal
Operating under: Part 91
Mission: Training
Flight phase: Climb
Airspace: Class E ZSE
Reporter organization: Personal
Reporter function: Instructor; Pilot Not Flying
Reporter qualification: Flight Crew Flight Instructor; Flight Crew Commercial; Flight Crew Instrument
Human factors: Situational Awareness
Anomaly: Conflict NMAC
Detector: Person Flight Crew
When detected: In-flight
Result: Flight Crew Took Evasive Action
Contributing factors: Human Factors
Primary problem: Human Factors

Narrative: While enroute to PWT my student and I were climbing to 2;500 ft. on a heading of approximately 250. An aircraft was flying north at what looked like 2;500 ft. We were at about 2;200 ft. when we spotted the aircraft and made maneuvers to avoid a collision. I would say we were about a hundred or so feet below the aircraft when we leveled off to avoid. Our view was obstructed by our wing and we weren't able to see the aircraft in our climb. In the future we will check aircraft blind spots before initiating a climb or directional change in the aircraft. No traffic alerts were available in our airplane.




Synopsis: C172 instructor pilot reported an NMAC while enroute to PWT.
Date: 201705
Local time of day: 1201-1800
Location: ZZZ.Airport, US
Flight conditions: VMC
Weather elements / visibility: 10
Light: Daylight
Aircraft: Gulfstream G200 (IAI 1126 Galaxy)
Operator: Personal
Operating under: Part 91
Flight plan: IFR
Mission: Ferry / Re-Positioning
Flight phase: Initial Climb
Airspace: Class E ZZZ
ATC / advisory: TRACON ZZZ
Aircraft component: Autopilot
Component problem: Malfunctioning
Reporter organization: Personal
Reporter function: Captain; Pilot Flying
Reporter qualification: Flight Crew Commercial; Flight Crew Multiengine
Human factors: Troubleshooting
Second reporter function: First Officer; Pilot Not Flying
Anomaly: Aircraft Equipment Problem Less Severe; Deviation - Altitude Excursion From Assigned Altitude; Deviation / Discrepancy - Procedural Clearance; Deviation / Discrepancy - Procedural Published Material / Policy
Detector: Person Flight Crew
When detected: In-flight
Result: Flight Crew Overcame Equipment Problem; Flight Crew Regained Aircraft Control
Contributing factors: Aircraft
Primary problem: Aircraft

Narrative: I was Pilot in Command and the Pilot Flying after a normal takeoff climbing out from ZZZ. Gear was up and we were turning to a heading of 320 with the auto-pilot (AP) engaged set to level at 3000 feet. Almost immediately after leveling at 3000 feet the plane pitched aggressively up and started climbing. I immediately disconnected the autopilot and pitched down and trimmed down but there was real resistance (felt like a runaway trim). I believe the highest we climbed was 4000-4500 feet. My copilot pushed down with me to adjust altitude and he requested a heading and block altitude from ATC while we evaluated the situation. We hand-flew the plane.Having three options of landing overweight (we were above max landing weight); dump fuel or continue; as we were going to a Maintenance Facility we opted to continue to our destination and trouble shoot/monitor closely the situation.I advised my copilot to couple the AP to his side and try to re-engage the AP. We had enough fuel to fly to our destination at an altitude below 28;000 feet but since the AP was operating normally on the right side we continued flight with it operating uneventfully in that position in RVSM (FL400-FL410). We reacted immediately and advised ATC immediately after taking rapid corrective action. We train for this and will continue to do so. I am sorry if we caused aggravation and we appreciate the immediate assistance provided to us by ATC.


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


Synopsis: G200 flight crew reported a malfunction with one autopilot shortly after level off from climb. Crew switched to other autopilot and continued to the destination.
Date: 201706
Local time of day: 0601-1200
Location: ZZZ.Airport, US
Flight conditions: VMC
Weather elements / visibility: Clear; 10
Light: Daylight
Aircraft: Bonanza 35
Operator: Personal
Operating under: Part 91
Flight plan: None
Mission: Personal
Flight phase: Takeoff / Launch
Airspace: Class D ZZZ
ATC / advisory: Tower ZZZ
Aircraft component: Engine
Component problem: Malfunctioning
Reporter organization: Personal
Reporter function: Pilot Flying; Single Pilot
Reporter qualification: Flight Crew Instrument; Flight Crew Multiengine
Human factors: Situational Awareness; Time Pressure
Anomaly: Aircraft Equipment Problem Critical; Ground Excursion Runway
Detector: Person Flight Crew
When detected: In-flight
Result: Flight Crew Inflight Shutdown; Flight Crew Landed in Emergency Condition; Flight Crew Returned To Departure Airport; Flight Crew Took Evasive Action; General Maintenance Action
Contributing factors: Aircraft; Environment - Non Weather Related
Primary problem: Aircraft

Narrative: After being cleared for takeoff I taxied the aircraft; held the brake; applied full throttle; reviewed the gauges; released the brake; became airborne; retracted the gear; then loss power. I redeployed the gear; assessed the amount of remaining runway as gear was extending and landed the aircraft when gear locked. On roll out I applied brakes and guided the plane toward the maintenance road at the end of the runway. I brought the aircraft to a stop approximately 50-75 feet past the end of the runway on the maintenance road. After a few tries I restarted the aircraft and attempted to taxi clear of the runway. As I was turning around the aircraft became stuck in the soft sand. Airport personnel assisted me getting the aircraft unstuck and I taxied it back to the hangar.There were no injuries; no aircraft damage; and no damage to the airport.




Synopsis: A BE-35 pilot reported a power loss on takeoff and landed just beyond the runway end. While attempting to taxi back to the runway; the aircraft became stuck in sand but was freed with assistance.
Date: 201308
Local time of day: 0601-1200
Location: ZZZ.Tower, US
Light: Daylight
Aircraft: EMB ERJ 170/175 ER/LR
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Cruise
Airspace: Class B ZZZ
ATC / advisory: Tower ZZZ
Aircraft component: Hydraulic System Lines; Connectors; Fittings
Component problem: Failed
Reporter organization: Air Carrier
Reporter function: Captain; Pilot Not 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 Diverted; Flight Crew Landed in Emergency Condition; General Declared Emergency
Contributing factors: Aircraft
Primary problem: Aircraft

Narrative: Enroute at cruise altitude; we got a caution message for Hydraulic 1 low quantity followed by Hydraulic 1 low pressure. We confirmed hydraulic fluid lost from hydraulic system page on MFD. Entire fluid leaked within 90 sec. After performing the QRH procedure and talking to Maintenance; we confirmed that complete Hydraulic 1 system lost.  We declared an emergency got out of RVSM and hand flew the airplane as directed by QRH. Performance calculation from QRH required longer finals and longer runway since braking was now reduced to 50% with only one thrust reverser available and multifunction spoilers compromised. After discussing with Company we were directed to change our destination to ZZZ. Passengers and cabin crew were briefed and informed regarding the plan. Airplane flew fine minus the speed brakes. After landing the wheel brakes were sluggish but deceleration was positive. After clearing the runway we had Fire and Rescue give us a visual inspection for any active leaks or smoke. Once cleared and all okay from Fire and Rescue we decided to be towed back to the gate; since brakes were getting hotter by the minute. Passengers were given a bus ride. Except for Hydraulic system 1; all other systems worked exceptionally.




Synopsis: EMB-170 captain reports loss of Hydraulic system 1 in cruise due to loss of hydraulic system fluid. Crew diverts to a suitable airport with a long runway due to loss of some systems. A safe landing ensues.
Date: 201403
Local time of day: 0601-1200
Location: EHAM.Airport, FO
Aircraft: B767 Undifferentiated or Other Model
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Other Preflight Planning
Aircraft component: Electronic Flt Bag (EFB)
Component problem: Malfunctioning
Reporter organization: Air Carrier
Reporter function: Pilot Flying; First Officer
Human factors: Troubleshooting; Time Pressure; Human-Machine Interface; Distraction
Anomaly: Aircraft Equipment Problem Critical
Detector: Person Flight Crew
When detected: Pre-flight
Result: General None Reported / Taken
Contributing factors: Manuals; Human Factors; Equipment / Tooling; Aircraft; Chart Or Publication; Company Policy
Primary problem: Ambiguous

Narrative: Many times the iPad WSI function freezes on the last route that was loaded in before flight. The only way to fix the problem is to delete WSI and reinstall it. The problem with that is it takes time; you need an internet connection; and you have to reinstall your charts that you want saved or you will not get the information.




Synopsis: A B767 First Officer reported frequent failures of their iPad EFBs to delete the previous flight data and display data appropriate for the current operation.
Date: 202201
Local time of day: 0001-0600
Location: , AZ
Flight conditions: VMC
Weather elements / visibility: 10
Light: Night
Aircraft: Large UAS; Fixed Wing
Operator: Government
Operating under: Public Aircraft Operations (UAS)
Flight plan: IFR
Mission: Public Safety / Pursuit (UAS)
Flight phase: Cruise
Airspace: Class A ZZZ
Reporter organization: Government
Reporter function: Person Manipulating Controls (UAS)
Reporter qualification: Flight Crew Instrument; Flight Crew Flight Instructor; Flight Crew Commercial; Flight Crew Multiengine
Human factors: Communication Breakdown; Situational Awareness
Anomaly: Airspace Violation All Types; Deviation / Discrepancy - Procedural Clearance
Detector: Person UAS Crew
When detected: In-flight
Result: Air Traffic Control Issued New Clearance; Flight Crew Exited Penetrated Airspace; Flight Crew Requested ATC Assistance / Clarification
Contributing factors: Procedure; Human Factors
Primary problem: Human Factors

Narrative: Slightly flew outside of cleared section of X; immediately turned around and requested the sectors we wanted. ATC cleared us for the sectors with no issues.

Callback: Reporter was unable to provide any further information.



Synopsis: UAS pilot reported the UAS flew outside of the authorized operations area. Pilot continued flight after receiving ATC clearance into additional airspace.
Date: 202104
Local time of day: 0601-1200
Weather elements / visibility: 10
Light: Daylight
Aircraft: LA-4-200 Buccaneer
Operator: Personal
Operating under: Part 91
Flight plan: None
Mission: Personal
Flight phase: Cruise
Airspace: Class E ZZZ
Aircraft component: Engine
Component problem: Failed
Reporter organization: Personal
Reporter function: Pilot Flying; Single Pilot
Reporter qualification: Flight Crew Instrument; Flight Crew Multiengine; Flight Crew Private
Anomaly: Aircraft Equipment Problem Critical; Deviation / Discrepancy - Procedural Published Material / Policy; Ground Event / Encounter Other / Unknown
Detector: Person Flight Crew
When detected: In-flight
Result: Flight Crew Landed in Emergency Condition; General Flight Cancelled / Delayed; General Maintenance Action
Contributing factors: Aircraft
Primary problem: Aircraft

Narrative: The engine in my Lake Amphibian lost power and I had to conduct a forced landing on a dirt road.




Synopsis: Lake LA4-200EP pilot reported a forced landing on a dirt road due to engine loss of power.
Date: 201708
Location: TA79.Airport, TX
Aircraft: No Aircraft
Reporter function: Observer
Anomaly: Other Obstacle Hazard
Detector: Person Observer
When detected: Routine Inspection
Result: General None Reported / Taken
Contributing factors: Chart Or Publication; Equipment / Tooling; Environment - Non Weather Related; Airport
Primary problem: Chart Or Publication

Narrative: New crane (over 100 ft tall) installed at Texas Tech University Health Sciences Center at 3601 4th Street Lubbock; TX in late July. Crane is approximately 120 ft tall and has a single warning light on top of mast. Boom is over 100 ft long and does not have a light on either end. As it stands right now; the boom is closer to the University Medical Center (602 Indiana Ave Lubbock; TX) Emergency Room Helipad than any of the well-marked buildings.This appears to be a potential problem. With multiple helicopters using pad at all hours of the day and night; approaching from several directions; this movable boom could be struck by an incoming or outgoing flight very easily; especially at night.




Synopsis: An Observer near Texas Tech University Medical Center (TA79) reported a new crane 120 ft high is lighted but its boom; over 100 ft long horizontally; is not lighted and presents a hazard for helicopters taking off and landing at the adjacent helipad.
Date: 202110
Local time of day: 0001-0600
Location: ZZZ.Airport, US
Flight conditions: IMC
Weather elements / visibility: Rain
Aircraft: B737 Undifferentiated or Other Model
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Taxi
Reporter organization: Air Carrier
Reporter function: First Officer
Reporter qualification: Flight Crew Instrument; Flight Crew Multiengine; Flight Crew Air Transport Pilot (ATP)
Human factors: Other / Unknown
Anomaly: Ground Event / Encounter Weather / Turbulence; Ground Event / Encounter Loss Of Aircraft Control
Detector: Person Flight Crew
When detected: Taxi
Result: Flight Crew Regained Aircraft Control; Flight Crew Took Evasive Action
Contributing factors: Weather; Human Factors
Primary problem: Weather

Narrative: Wet taxiway upon arrival into ZZZ on short flight from ZZZ1-ZZZ.  Conditions were light rain; no puddling.  Long taxi from Runway XL into terminal.  Aircraft slid back and forth across taxiway centerline during the turn on the XX curve of Taxiway 1. Difficult to regain control on slick taxiway surface. Perhaps we should have been taxiing slower; given the conditions.  Aircraft did not leave prepared surface nor make contact with any taxiway lights.




Synopsis: B737 First Officer reported momentary loss of aircraft control while taxiing in light rain conditions.  First Officer stated taxi speed could have been too high for the conditions.
Date: 201712
Local time of day: 1201-1800
Location: ZZZ.Airport, US
Flight conditions: VMC
Light: Daylight
Aircraft: EMB ERJ 170/175 ER/LR
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Descent
Airspace: Class A ZZZ
ATC / advisory: Center ZZZ
Aircraft component: Position Computing System
Component problem: Malfunctioning
Reporter organization: Air Carrier
Reporter function: Captain; Pilot Flying
Reporter qualification: Flight Crew Air Transport Pilot (ATP)
Human factors: Human-Machine Interface
Anomaly: Aircraft Equipment Problem Less Severe; Deviation - Track / Heading All Types; Deviation / Discrepancy - Procedural Clearance; Deviation / Discrepancy - Procedural Published Material / Policy
Detector: Automation Aircraft Other Automation; Person Flight Crew
When detected: In-flight
Result: Air Traffic Control Provided Assistance; Flight Crew FLC Overrode Automation; Flight Crew Overcame Equipment Problem; Flight Crew Returned To Clearance
Contributing factors: Aircraft
Primary problem: Aircraft

Narrative: On the arrival into ZZZ we were past ZZZZZ and approaching ZZZZZ1 when the FMS seemed to lose its position. It displayed amber dashed lines on the distance remaining location on the pilot flying PFD and the vertical profile displayed the aircraft prior to ZZZZZ even though we had just passed it. As we approached ZZZZZ1; the FMS did not sequence and the aircraft continued the previous course without making the turn. Both the Pilot Flying and Pilot Monitoring FMS needles on the HSI displayed previous course information and did not sequence for the turn. I immediately disconnected the autopilot and autothrottles and hand flew the depicted turn while the Pilot Monitoring informed ATC of the FMS malfunction. We were subsequently issued vectors and an assigned heading. During the course deviation; we remained within 3 miles of the depicted course on the MFD. This event appears to be caused by a navigation anomaly in the FMS and is unlike any other known FMS issues. Usually when an error like this is noted with and HSI being 'frozen'; the pilot flying HSI still functions normally. In this case; both PFD needles were frozen and the error occurred during descent; whereas previous cases the error has normally occurred on climb or departure. I recommend further research be conducted to see if this type of error has been occurring throughout the fleet and try to pinpoint a cause. This type of event could have been very dangerous had we been on another arrival and if the deviation would have occurred in the other direction nearer to other arrival corridors.




Synopsis: ERJ-175 Captain reported that during descent the FMS lost its position with both pilots needles on the HSI displaying previous flight information.
Date: 201204
Local time of day: 0601-1200
Location: ZZZ.Airport, US
Light: Daylight
Aircraft: Dash 8-300
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Taxi
ATC / advisory: Ground ZZZ
Aircraft component: Air Conditioning Distribution System
Component problem: Malfunctioning
Reporter organization: Air Carrier
Reporter function: First Officer; Pilot Flying
Reporter qualification: Flight Crew Air Transport Pilot (ATP)
Human factors: Distraction; Situational Awareness; Time Pressure; Training / Qualification
Anomaly: Flight Deck / Cabin / Aircraft Event Smoke / Fire / Fumes / Odor
Detector: Person Flight Crew
When detected: Taxi
Result: Flight Crew FLC complied w / Automation / Advisory; Flight Crew Returned To Gate; General Declared Emergency
Contributing factors: Aircraft
Primary problem: Aircraft

Narrative: As we taxied out from Bravo short of Kilo; we smelled something that smelled like burnt rubber and that was followed by smoke in the flight deck. The First Officer declared an emergency to Ground Control and we stopped the aircraft on Taxiway Bravo. We ran the Aircraft Fire or Smoke Checklist and then followed that down to the suspected source of bleed or air conditioning. Smoke began to subside a little when the bleeds were shut off. We shut down the engines and had fire rescue check the airplane for smoke or fire outside of the aircraft. They determined no signs of smoke or fire so we restarted the airplane; kept bleeds off and were followed back to the gate. On the way back; the smell worsened and stayed in the aircraft once we shutdown but the smoke never returned.




Synopsis: A DHC8-300 developed a burnt rubber smell with smoke during taxi out so an emergency was declared; the engines shut down; and after Airfield Rescue and Fire Fighter inspections the aircraft restarted for a return to the gate.