elihoole/asrs-aviation-reports huggingface dataset:
Date: 202003
Local time of day: 0601-1200
Location: ZBW.ARTCC, NH
Flight conditions: VMC
Light: Daylight
Aircraft: PA-28 Cherokee/Archer/Dakota/Pillan/Warrior
Operator: Personal
Operating under: Part 91
Flight plan: None
Mission: Personal
Flight phase: Cruise
Airspace: Class E ZBW
ATC / advisory: CTAF LEW
Reporter organization: Personal
Reporter function: Pilot Flying; Single Pilot
Reporter qualification: Flight Crew Commercial; Flight Crew Instrument
Human factors: Distraction; Situational Awareness
Anomaly: Conflict NMAC
Detector: Person Flight Crew
When detected: In-flight
Result: General None Reported / Taken
Contributing factors: Environment - Non Weather Related
Primary problem: Environment - Non Weather Related

Narrative: Flying over the city of Lewiston; Maine I caught a glimpse of an object pass off the right wingtip and lost sight of it quickly as it passed beyond the rearmost window. This all happened very quickly and for a split second I was concerned whatever the object was might strike the tail or elevator. As I recalled the image of the object it can be described as black in color and the shape was unlike that of a bird or child's balloon. From memory I can describe the shape as having extremities which I interpreted as possibly being a drone.Hearing a Skylane announce departure from LEW toward my position I advised the pilot over CTAF of a possible drone over the city to which he acknowledged.




Synopsis: PA28 pilot reported a NMAC with a UAV.
Date: 201304
Local time of day: 1201-1800
Location: ZZZ.Airport, US
Flight conditions: VMC
Weather elements / visibility: 10
Light: Daylight
Aircraft: Duchess 76
Operator: Personal
Operating under: Part 91
Flight plan: VFR
Mission: Training
Flight phase: Cruise
Airspace: Class D ZZZ
ATC / advisory: TRACON ZZZ
Aircraft component: Engine
Component problem: Malfunctioning
Reporter organization: Personal
Reporter function: Instructor; Pilot Flying
Reporter qualification: Flight Crew Commercial; Flight Crew Flight Instructor; Flight Crew Multiengine; Flight Crew Instrument
Anomaly: Aircraft Equipment Problem Critical
Detector: 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: During a multi-engine training flight I was unable to restart the right engine after the student performed a full engine shut down at 4;500 FT. We went through the checklist three times and made several attempts to restart the engine but were unable to successfully bring the engine back to a windmilling condition. After losing 2;000 FT in altitude the decision was made to discontinue the air restart and land the plane with one engine. We contacted Approach Control to advise them of our situation and request priority [handling.] We were cleared direct to YYY and given priority as an aircraft in distress. After contacting the Tower we were cleared to land and landed with only the left engine. Because of the momentum of the aircraft we were able to exit the runway safely onto a taxiway. There were 3 people on board; the CFI; and two students. We took off with 80 gallons of fuel (40 each side) and burned approximately 25 gallons in flight.




Synopsis: A multi-engine flight instructor and two student pilots were unable to restart the right engine of a Beechcraft Duchess after practicing in-flight shutdown and restart operations. They declared an emergency and successfully performed a single engine approach and landing at a nearby airport.
Date: 202201
Location: MCO.Airport, FL
Flight conditions: VMC
Aircraft: Commercial Fixed Wing
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Final Approach
Airspace: Class B MCO
ATC / advisory: TRACON F11
Aircraft component: Autoflight System
Component problem: Malfunctioning
Reporter organization: Air Carrier
Reporter function: Pilot Flying; First Officer
Reporter qualification: Flight Crew Instrument; Flight Crew Multiengine; Flight Crew Air Transport Pilot (ATP)
Anomaly: Aircraft Equipment Problem Less Severe
Detector: Person Flight Crew
When detected: In-flight
Result: Aircraft Equipment Problem Dissipated
Contributing factors: Aircraft; Environment - Non Weather Related
Primary problem: Environment - Non Weather Related

Narrative: On a visual approach to Runway 35R in Orlando; the glide slope did not capture initially. Once on the ground we got a takeoff config warning when clearing the runway with the power barley pushed up. This was reported to ATC; Dispatch and Maintenance. All tests from Maintenance are successful; they think it was a possible 5G anomaly.




Synopsis: Air carrier First Officer reported glide slope and takeoff configuration warning anomalies on arrival into MCO; citing possible 5G interference as the cause of the issues.
Date: 201508
Local time of day: 0601-1200
Location: ZZZ.Airport, US
Flight conditions: VMC
Weather elements / visibility: Turbulence
Light: Daylight
Aircraft: A320
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Climb
Airspace: Class E ZZZ
ATC / advisory: Center ZZZ
Aircraft component: Turbine Engine
Component problem: Malfunctioning
Reporter organization: Air Carrier
Reporter function: Captain; Pilot Not Flying
Anomaly: Aircraft Equipment Problem Critical
Detector: Automation Aircraft Other Automation; Person Flight Crew
When detected: In-flight
Result: Flight Crew Landed As Precaution; Flight Crew Landed in Emergency Condition; Flight Crew Returned To Departure Airport
Contributing factors: Aircraft
Primary problem: Aircraft

Narrative: Climbing out of FL150; we felt a bump followed by erratic engine 1 indications. ECAM showed ENG 1 SYSTEM fault; and ECAM ENG 1 FADEC B fault. We had to bring ENG 1 to idle stabilize the engine. Returned to [departure airport] and made a normal overweight landing.




Synopsis: An A320 Captain reported problems with the #1 engine on climbout; requiring reduced thrust to idle to stabilize engine. The flight returned to departure airport.
Date: 201504
Local time of day: 0601-1200
Location: ZZZ.Airport, US
Flight conditions: VMC
Weather elements / visibility: 10
Light: Daylight
Aircraft: Cessna 188 (Ag Wagon/Ag Truck/Ag Husky)
Operator: Other 137 operations
Operating under: Part 137
Mission: Other 137 operations
Flight phase: Other 137 operations
Second aircraft: Helicopter
Reporter organization: Other 137 operations
Reporter function: Pilot Flying
Reporter qualification: Flight Crew Commercial; Flight Crew Flight Instructor; Flight Crew Instrument
Human factors: Situational Awareness; Workload; Confusion; Communication Breakdown
Anomaly: Conflict NMAC; Deviation / Discrepancy - Procedural Published Material / Policy
Detector: Person Flight Crew
When detected: In-flight
Result: General None Reported / Taken
Contributing factors: Human Factors; Airport; Environment - Non Weather Related; Procedure
Primary problem: Procedure

Narrative: Conducting Part 137 operations on South part of airport. Did not see or hear communications from Helicopter approaching airport. After Helicopter made his initial call to the unicom; the FBO responded that ag operations we being conducted on the South part of airport.




Synopsis: A CE-188 conducting AG spray operations near a Midwest airport had a near miss after a helicopter pilot approaching the airport did not make CTAF position reports.
Date: 202103
Local time of day: 1201-1800
Location: 7F3.Airport, TX
Flight conditions: VMC
Light: Daylight
Aircraft: Small Aircraft
Operator: FBO
Operating under: Part 91
Flight plan: None
Mission: Training
Flight phase: Landing; Descent
Airspace: Class E ZFW
ATC / advisory: CTAF ZZZ; UNICOM ZZZ
Second aircraft: Amateur/Home Built/Experimental
Reporter organization: Personal
Reporter function: Instructor; Pilot Flying
Reporter qualification: Flight Crew Flight Instructor; Flight Crew Multiengine; Flight Crew Instrument; Flight Crew Air Transport Pilot (ATP)
Human factors: Situational Awareness; Communication Breakdown
Anomaly: Conflict NMAC
Detector: Person Flight Crew
Result: Flight Crew Executed Go Around / Missed Approach; Flight Crew Took Evasive Action
Contributing factors: Human Factors; Airport
Primary problem: Airport

Narrative: While returning to 7F3 on a student training flight I was informed on the CTAF that there were numerous powered parachutes(PPC) in the vicinity of the airport. One pilot stated that 2 PPC were at 1;500 ft. on downwind to Runway 18; the runway in use. Another pilot had to abort his landing because of 2 PPC over the runway as he was approaching the runway on a simulated engine out pattern. There were approximately 12 PPC's in the air and I could see that they were interfering with approaches; upwind legs and on downwind. After maneuvering to avoid them I changed the pattern to a non standard right pattern and still encountered them on that side of the airport at different altitudes. They do not have radios; and being slow are hard to see; especially the light of a low; soon to be setting sun.This is a very unsafe airport ; especially for training; when these PPC's are operating. 7F3 is a high student pilot training facility and this needs to be addressed ASAP.




Synopsis: An instructor pilot returning to land reported numerous powered parachutes fly in the vicinity of this airport causing conflictions with aircraft arriving and departing the VFR pattern.
Date: 201407
Location: SJU.Airport, PR
Aircraft: Commercial Fixed Wing
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Reporter organization: Air Carrier
Human factors: Confusion
Anomaly: No Specific Anomaly Occurred All Types
Detector: Person Flight Crew
Result: General None Reported / Taken
Contributing factors: Chart Or Publication
Primary problem: Chart Or Publication

Narrative: For TJSJ/SJU; the [Briefing Page] states under departures (Note 3) that taxiway restrictions and taxiway holding position information are located on the [Parking Gate Chart].  Similarly; the [Airport Diagram] shows an area on the west side of the airport bounded by a thin dashed line with a note stating; 'For Taxiway Restrictions See [the Parking Gate Chart].'However; the most current [Parking Gate Chart]; as found in the EFB and also on the company intranet has nothing of the sort.  It is only a list parking gate coordinates and a diagram showing their location on the terminal.  No information on this page describes any taxiway restrictions; and no information on the diagram or the text depicts any taxiway holding positions. The 'changes' information at the bottom of the current [Parking Gate Chart] states; 'Changes: Parking gates; chart reindexed.'  Perhaps in the re-indexing process this chart became the [Parking Gate Chart]; without any corresponding update to the notes on the [Airport Diagram] and the [Briefing Page].  Since no other chart in the current section on SJU appears to contain the missing information; it seems possible that the relevant chart has been omitted entirely. To the extent that Aircrews operating into SJU; particularly for the first time; need to be aware of the 'restrictions' contained on the now-missing page; this omission compromises the Safety of operations at SJU.




Synopsis: Air carrier pilot reports that the Airport Diagram for SJU has a note on the left side of the chart indicating that taxiway restrictions for this area can be found on the Gate Diagram; but there is nothing there.
Date: 201409
Local time of day: 0601-1200
Location: ABQ.Airport, NM
Flight conditions: VMC
Light: Dawn
Aircraft: B737-300
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Flight phase: Climb
Airspace: Class C ABQ
ATC / advisory: TRACON ABQ
Reporter organization: Air Carrier
Reporter function: Captain
Anomaly: Deviation / Discrepancy - Procedural Published Material / Policy; Inflight Event / Encounter CFTT / CFIT
Detector: Person Air Traffic Control
When detected: In-flight
Result: Air Traffic Control Issued New Clearance; Air Traffic Control Issued Advisory / Alert; Flight Crew Returned To Clearance
Contributing factors: Aircraft; Human Factors; Procedure
Primary problem: Ambiguous

Narrative: Departing ABQ under VFR conditions cleared to depart via the MNZNO TWO RNAV Departure off of Runway 08. Engaged LNAV at 400 feet. Leveled off at YUGLU at 9000 feet per the SID. Selected the assigned altitude of FL200 and engaged VNAV. All selections were verified by the pilot monitoring and myself. Within a minute; ATC assigned us a heading off of the SID for 'terrain avoidance.' We complied with the heading. NO GPWS warnings or cautions were issued. I don't know if ATC was nervous because we did not start climbing immediately after the YUGLU intersection; or other issues. The F/O and I were both surprised by the clearance and thought it was a little early to be issued by ATC. The flight proceeded without further incident. We both had good situational awareness of where we were and had good Crew communications. We complied with FOM and AOM procedures. It was the first time I had flown a -300 in a while and I don't know if it was a little slow to climb or not. The correct annunciations were displayed as appropriate for the commanded selection.




Synopsis: B737 Captain reported being vectored off the MNZNO 2 RNAV after YUGLU for terrain when the aircraft does not immediately start climbing out of 9;000 FT.
Date: 201209
Local time of day: 0601-1200
Location: MEM.Airport, TN
Flight conditions: VMC
Light: Daylight
Aircraft: A300
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Cargo / Freight / Delivery
Flight phase: Initial Approach
Airspace: Class B MEM
ATC / advisory: TRACON M03
Aircraft component: FMS/FMC
Component problem: Design; Malfunctioning
Reporter organization: Air Carrier
Reporter function: Pilot Not Flying; Captain
Reporter qualification: Flight Crew Air Transport Pilot (ATP)
Second reporter function: First Officer; Pilot Flying
Anomaly: Aircraft Equipment Problem Less Severe; Deviation - Altitude Crossing Restriction Not Met; Deviation - Altitude Overshoot; Deviation - Speed All Types; Deviation / Discrepancy - Procedural Published Material / Policy; Deviation / Discrepancy - Procedural Clearance
Detector: Person Flight Crew
When detected: In-flight
Result: Flight Crew Returned To Clearance
Contributing factors: Aircraft; Procedure
Primary problem: Aircraft

Narrative: Flying LTOWN 6 into Memphis; aircraft was not going to make speed restriction at CLARK. We added more drag via spoilers at which time the nose abruptly pitched down (at 8;400 FT approximately). Selected ALT Hold on FCP. Aircraft would not level off so pilot flying (First Officer) disengaged autopilot and hand flew aircraft back to 8;000 FT. Note we went approximately 275 FT low. It needs to be noted that the A300 FMS is incapable of flying these STARS with any consistency. When it appears they may stay on profile they will always surprise you at the last second with some new exotic maneuver. Quite frankly; I'm tired of being set up for failure with procedures that are developed by someone who doesn't know anything about flying. Release the A300 from the requirement for flying these arrivals. Workload is increased exponentially and safety is reduced in kind.


Second narrative: Flying LTOWN 6 into MEM. Descending out of 9;000 FT for 8;000 FT; aircraft unable to maintain 210 KTS speed restriction. Extended speed brakes to slow down which resulted in a nose down pitch. Aircraft did not honor the 8;000 FT restriction at CLARK. As it approached 8;000 FT; I engaged ALT HOLD. Aircraft reacted too slowly and continued descent. I disconnected the autopilot and brought the aircraft back to 8;000 FT. Maximum deviation noted approximately 275 FT. Tighten up the tolerances the FMS allows before it reacts. Manually fly the autopilot (level change) and take the FMS out of the loop.


Synopsis: A300 flight crew laments the ability of the FMS to comply with RNAV arrival procedures.
Date: 201308
Local time of day: 1801-2400
Location: ZZZ.Airport, US
Flight conditions: VMC
Light: Daylight
Aircraft: Regional Jet 700 ER/LR (CRJ700)
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Landing
ATC / advisory: Tower ZZZ
Aircraft component: Turbine Engine
Component problem: Failed
Reporter organization: Air Carrier
Reporter function: Pilot Not Flying; Captain
Reporter qualification: Flight Crew Air Transport Pilot (ATP)
Human factors: Human-Machine Interface
Anomaly: Aircraft Equipment Problem Critical
Detector: Automation Aircraft Other Automation; Person Flight Crew
When detected: Other Landing Roll
Result: Flight Crew Overcame Equipment Problem
Contributing factors: Aircraft
Primary problem: Aircraft

Narrative: Upon landing we received a R ENG FLAMEOUT message right after thrust reverser deployment. After decelerating; I took the controls from the First Officer and called for the checklist. While exiting the runway; I saw that right engine ITT exceeded limits which led me to shut the engine down. We then completed the R ENG FLAMEOUT abnormal and then reviewed single engine procedures. After completing the after landing and taxi shutdown checklists the aircraft was taxied normally to the gate. The engine malfunction was the main threat. Possible loss of directional control; increased stopping distance; potential of fire; and distracting the crew are the main problems that arose from the engine malfunction. Glare from the setting sun made it more difficult for the crew to see the displays while on Runway XX.Stopping the aircraft on the runway instead of taking the time to exit may have helped lessen the time it took to shut the engine down. Doing so may have also reduced the time that the ITT was above limits. However; controlling the aircraft and ensuring that the passengers; crew and cargo remained safe are the main priorities before the aircraft. Having better sun visors or screens would aid in reducing glare on the displays during the day.




Synopsis: While reversing after landing the flight crew of a CRJ-700 experienced a right engine flame out and noted high ITT as they turned off the runway.  The shut the engine down; completed checklists; and taxied to their gate.
Date: 201202
Local time of day: 1801-2400
Location: ZZZ.Airport, US
Flight conditions: VMC
Light: Night
Aircraft: B767-300 and 300 ER
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Climb
Airspace: Class A ZZZ
ATC / advisory: Center ZZZ
Aircraft component: Pneumatic Valve/Bleed Valve
Component problem: Failed
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 Critical
Detector: Automation Aircraft Other Automation; Person Flight Crew
When detected: In-flight
Result: Flight Crew Landed in Emergency Condition; Flight Crew Returned To Departure Airport; General Declared Emergency; General Flight Cancelled / Delayed; General Maintenance Action
Contributing factors: Aircraft
Primary problem: Aircraft

Narrative: During climb; an EICAS message came up 'L ENG HPSOV.' [We] completed QRH checklist; declared an emergency and returned to the departure airport. A normal approach and landing was made.


Second narrative: [We] extended the landing pattern so the aircraft would be under the maximum landing weight; normal landing and checklists.


Synopsis: A B767-300 EICAS alerted LT ENG HPSOV at cruise shortly after takeoff so an emergency was declared. The aircraft returned to the departure airport where repairs were made and flight continued to its scheduled destination.
Date: 201910
Local time of day: 1801-2400
Location: ZZZ.Airport, US
Flight conditions: VMC
Light: Night
Aircraft: PA-28 Cherokee/Archer/Dakota/Pillan/Warrior
Operator: FBO
Operating under: Part 91
Flight plan: None
Mission: Training
Flight phase: Takeoff / Launch
Airspace: Class D ZZZ
ATC / advisory: Tower ZZZ
Aircraft component: AC Generator/Alternator
Component problem: Malfunctioning
Reporter organization: FBO
Reporter function: Instructor
Reporter qualification: Flight Crew Commercial; Flight Crew Flight Instructor; Flight Crew Instrument; Flight Crew Multiengine
Human factors: Troubleshooting; Workload
Anomaly: Aircraft Equipment Problem Critical
Detector: Person Flight Crew
When detected: In-flight
Result: Air Traffic Control Provided Assistance; Flight Crew Diverted; Flight Crew Requested ATC Assistance / Clarification
Contributing factors: Aircraft
Primary problem: Aircraft

Narrative: Performing a night cross country flight with a student pilot. 'Alternator INOP' annunciator illuminated and ammeter displayed after takeoff. IP (Instructor Pilot) performed checklist by noting the position of the circuit breaker - In. IP turned alternator switch off; pulled circuit breaker and then reset; turned alternator switch back to the 'on' position and annunciator was extinguished. IP radioed Tower that aircraft had alternator failure indications and would like to return to ZZZ. As the radio call was being made 'Alternator INOP' annunciator illuminated again. IP told Tower that Aircraft X would like to land and park the aircraft at the FBO. Tower acknowledged and offered any assistance. Conditions were unlimited VMC at night. IP completed the Master Checklist and opted to 'land as soon as practical' as stated in the NOTE for ALTERNATOR FAILURE WITHOUT STANDBY. Aircraft X was also practicing landings at ZZZ and IP asked them to pick up the IP and Student at the FBO once they were completed with their training and had burned off fuel to accommodate added weight. This conversation of Aeronautical Decision Making was performed over ZZZ Tower frequency and should have been recorded. IP texted Chief Instructor; Chief Mechanic; and Chief Dispatcher to notify them of the situation and let them know that IP was leaving Aircraft X at the FBO at ZZZ overnight to be retrieved in Day VMC. No response or acknowledgment was received until the next day.




Synopsis: PA-28 instructor reported an alternator failure during a night flight that resulted in a precautionary landing.
Date: 201601
Local time of day: 1801-2400
Location: SBP.Airport, CA
Weather elements / visibility: Rain; 3
Aircraft: PA-24 Comanche
Operator: Personal
Operating under: Part 91
Flight plan: IFR
Mission: Personal
Flight phase: Final Approach
Airspace: Class D SBP
ATC / advisory: Tower SBP
Reporter organization: Personal
Reporter function: Single Pilot; Pilot Flying
Reporter qualification: Flight Crew Air Transport Pilot (ATP); Flight Crew Instrument; Flight Crew Multiengine
Human factors: Distraction; Situational Awareness
Anomaly: Deviation - Altitude Excursion From Assigned Altitude; Deviation - Track / Heading All Types; Deviation / Discrepancy - Procedural Clearance; Inflight Event / Encounter CFTT / CFIT; Inflight Event / Encounter Unstabilized Approach
Detector: Person Air Traffic Control
When detected: In-flight
Result: Air Traffic Control Issued Advisory / Alert
Contributing factors: Human Factors
Primary problem: Human Factors

Narrative: While on the ILS 11 Approach into SBP I deviated from both the localizer and glide slope. At one point I was low enough on the glide slope that I was advised by the Control Tower that I set off a low altitude alert. I corrected and landed uneventfully. I was distracted by a passenger which was a contributing factor.




Synopsis: PA-24 pilot reported receiving a low altitude alert from ATC on approach to SBP; citing cockpit distractions as contributing.