elihoole/asrs-aviation-reports huggingface dataset:
Date: 201703
Local time of day: 0601-1200
Location: ZZZ.Airport, US
Flight conditions: VMC
Light: Daylight
Aircraft: SR20
Operator: FBO
Operating under: Part 91
Flight plan: None
Mission: Training
Flight phase: Taxi
ATC / advisory: Ground ZZZ
Aircraft component: Engine
Component problem: Malfunctioning
Reporter organization: FBO
Reporter function: Instructor; Pilot Not Flying
Reporter qualification: Flight Crew Commercial; Flight Crew Flight Instructor
Anomaly: Aircraft Equipment Problem Less Severe
Detector: Person Flight Crew
When detected: Taxi
Result: Flight Crew Returned To Gate
Contributing factors: Aircraft
Primary problem: Aircraft

Narrative: While taxing; aircraft engine sputtered and shutdown. I contacted ground on and informed them we were stuck in the middle of the taxiway and advised we would attempt restart and if successful request amended clearance from. ATC advised us to advise them. After conducting successful hot start we taxied with clearance from ground back to ramp and contacted ops and asked for maintenance to come out to aircraft. Maintenance arrived and advised writing up aircraft due to prior similar incident.




Synopsis: SR20 flight instructor reported the engine sputtered and shutdown on taxi out. The aircraft restarted and returned to the ramp.
Date: 201502
Flight conditions: Mixed
Weather elements / visibility: Windshear
Light: Daylight
Aircraft: Commercial Fixed Wing
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Initial Approach
Airspace: Class B P50
Reporter organization: Air Carrier
Reporter function: Captain; Pilot Flying
Reporter qualification: Flight Crew Air Transport Pilot (ATP)
Human factors: Situational Awareness
Second reporter function: Pilot Not Flying; First Officer
Anomaly: Deviation - Altitude Excursion From Assigned Altitude; Inflight Event / Encounter Weather / Turbulence
Detector: Person Air Traffic Control; Person Flight Crew
When detected: In-flight
Result: Air Traffic Control Issued Advisory / Alert; Flight Crew Returned To Clearance
Contributing factors: Weather
Primary problem: Weather

Narrative: I received an altitude deviation inquiry on the arrival of [our] flight to IWA and subsequently was asked to call PHX Tracon after landing. While on an assigned heading near the northwest valley of the Superstition Mountains; we experienced turbulence and windshear (with a subsequent loss of airspeed and altitude). Recovery procedures were applied; and altitude and airspeed were regained. Upon recovery of our assigned altitude of 6;000 ft; ATC did query us on our assigned altitude. We lost approximately 20 knots and approximately 200 feet of altitude. We became quite busy at this point and did not make a PIREP on the windshear.


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


Synopsis: Flight crew reported an altitude excursion on arrival into IWA when they encountered turbulence and windshear.
Date: 202011
Local time of day: 0601-1200
Location: ZZZ1.Airport, US
Flight conditions: VMC
Weather elements / visibility: 10
Light: Daylight
Aircraft: Small Aircraft; High Wing; 1 Eng; Retractable Gear
Operator: Personal
Operating under: Part 91
Flight plan: None
Mission: Ferry / Re-Positioning
Flight phase: Initial Approach
Airspace: Class G ZZZ
Aircraft component: Reciprocating Engine Assembly
Component problem: Failed
Reporter organization: Personal
Reporter function: Pilot Flying; Single Pilot
Reporter qualification: Flight Crew Air Transport Pilot (ATP); Flight Crew Multiengine; Flight Crew Instrument; Flight Crew Flight Instructor; Other ATP
Human factors: Situational Awareness
Anomaly: Aircraft Equipment Problem Critical; Deviation / Discrepancy - Procedural Published Material / Policy; Ground Event / Encounter Ground Strike - Aircraft; Inflight Event / Encounter Fuel Issue; Inflight Event / Encounter Loss Of Aircraft Control
Detector: Person Flight Crew
When detected: In-flight
Result: Flight Crew Diverted; Flight Crew Inflight Shutdown
Contributing factors: Aircraft
Primary problem: Aircraft

Narrative: Intended flight was from my home base at ZZZ; to ZZZ1. Flight time was calculated to be about 20 minutes. Approximately 4 miles from ZZZ1 the engine power suddenly rolled back. I immediately looked for a landing field while at the same time trying to adjust the mixture and the throttle to regain power.As I was setting up to land on a field; the engine power came back up again. I deducted that the partial power failure was due to either water on the fuel tank or a clog in the fuel line. I decided to abandon the forced landing and try to land at the airport; which was only about 3 miles away. I lowered the landing gear; execute my Before Landing Checklist and set to land. The engine quit shortly after that. I had to quickly pick another forced landing spot because there were trees all around. The aircraft impacted hard; 1.2 SM from the airport. I sustained injuries.




Synopsis: Pilot flying RC-3 aircraft reports engine failure inflight.
Date: 201512
Local time of day: 1801-2400
Location: ZZZ.Airport, US
Flight conditions: VMC
Light: Night
Aircraft: MD-11
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Cargo / Freight / Delivery
Flight phase: Parked
Reporter organization: Air Carrier
Reporter function: First Officer; Pilot Not Flying
Reporter qualification: Flight Crew Air Transport Pilot (ATP)
Human factors: Workload
Anomaly: Aircraft Equipment Problem Less Severe; Deviation / Discrepancy - Procedural MEL / CDL; Deviation / Discrepancy - Procedural Maintenance
Detector: Person Flight Crew
When detected: Pre-flight
Result: General None Reported / Taken
Contributing factors: MEL
Primary problem: MEL

Narrative: Assigned this aircraft and saw that it had 12 MEL's with one additional open item forthcoming according to ramp maintenance. Capt and I reviewed the MEL's and could comply with each MEL on the flight tonight. Concern was at what number of MEL's does it become too much and the jet become down until they are fixed. Capt had flown with an FAA maintenance inspector previously who informed him that generally speaking it would be 5 to 6. We consulted with our dispatcher and the Duty Officer over our concerns. We knew we could safely execute the flight while satisfying all MEL requirements so we proceeded to fly the aircraft as scheduled without any incidents other than identifying the right hand turn off light while working appeared to be misaligned and of little use to the Captain but did assist myself looking out to the right side of the aircraft. During flight the Captain sent an ACARS message to Maintenance and wrote this up making the total MELs now at 13.




Synopsis: MD11 First Officer reported accepting the aircraft and flew with 13 listed MELs.
Date: 201704
Local time of day: 0001-0600
Location: ADW.Airport, MD
Aircraft: Military
Operator: Military
Flight plan: VFR
Mission: Training
Flight phase: Initial Climb
Airspace: Class B DCA
ATC / advisory: Tower ADW
Second aircraft: Military
Reporter organization: Government
Reporter function: Local
Reporter qualification: Air Traffic Control Fully Certified
Human factors: Time Pressure; Situational Awareness; Communication Breakdown; Workload
Anomaly: ATC Issue All Types; Airspace Violation All Types; Conflict Airborne Conflict; Deviation / Discrepancy - Procedural Clearance; Deviation / Discrepancy - Procedural Published Material / Policy
Detector: Person Air Traffic Control
When detected: In-flight
Result: Flight Crew Requested ATC Assistance / Clarification
Contributing factors: Company Policy; Airspace Structure; Aircraft; Procedure
Primary problem: Company Policy

Narrative: Helicopter X called me at Local Control for a practice departure scramble launch from their flight line. I was trying to resolve a transponder issue with the two previous helicopters that departed shortly before helicopter X called. At the same time; a MEDEVAC aircraft which was a higher priority called ready for departure which I was trying to coordinate a release for with the departure controller. Helicopter X departed and entered Class B airspace without a clearance. I radar identified helicopter X and allowed them to continue their mission. A Brasher Warning was not issued.Shortly after helicopter Y called me for a practice departure scramble launch from their flight line. I issued helicopter Y the MEDEVAC aircraft traffic that was cleared for takeoff and departing Runway 1L; but not clearance into the Washington Bravo Airspace. Helicopter Y entered the Bravo airspace without clearance. I radar identified helicopter Y and they continued on their mission. A Brasher Warning was not issued.Helicopter X and helicopter Y's flight line is on the west side of the airport. Helicopter Y departed his flight line north bound while aircraft Z was rotating. Aircraft Z was on a SID that states he must turn to a 270 heading within 3 DME of ADW. As aircraft Z started his turn; helicopter Y was underneath him and separation was not ensured.When the helicopters are practicing their scramble missions they must obtain a clearance from Local Control before entering Class-B airspace. If we are unable to answer their initial call right away they depart without a clearance. This type of event happens on a daily basis at ADW and is a huge safety concern in the Tower. The Tower has called their flight line on numerous occasions; however this event continues to happen.




Synopsis: ADW Tower Local Controller reported two helicopters departed without a clearance conflicting with departing traffic.  The helicopters also entered Class B airspace without clearance.
Date: 202101
Local time of day: 0601-1200
Location: ZZZ.Airport, US
Flight conditions: VMC
Light: Daylight
Aircraft: EMB ERJ 145 ER/LR
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Landing
Airspace: Class B ZZZ
ATC / advisory: Tower ZZZ
Aircraft component: Horizontal Stabilizer Trim
Component problem: Malfunctioning
Reporter organization: Air Carrier
Reporter function: Captain; Pilot Flying
Reporter qualification: Flight Crew Air Transport Pilot (ATP); Flight Crew Instrument; Flight Crew Multiengine
Anomaly: Aircraft Equipment Problem Critical
Detector: Automation Aircraft Other Automation
When detected: In-flight
Result: Flight Crew Overcame Equipment Problem; General Maintenance Action
Contributing factors: Aircraft
Primary problem: Aircraft

Narrative: ZZZ to ZZZ1; visual approach into Runway XX; VMC weather conditions. At approximately 300 feet AGL two messages populated on the EICAS; PTRIM (Pitch Trim) MAIN INOP and PTRIM BACKUP INOP. Both crew members initially looked to see if half of the trim control on either side yolk had been accidentally held; which would cause the effected main control to become INOP; neither side was observed being pressed or stuck. The crew then quickly tested each main control and back up control; one at a time; each control switch failed to activate/ control the elevator trim. The airspeed was 145 KTS IAS. The crew briefed that the controls were trimmed for landing speed; 145 KTS; and due to the short final; now near 200 feet AGL; the landing would be continued. The crew also quickly briefed that in the event of a go-around special attention would need to be paid attention to airspeed due to the INOP trim and the traffic pattern and second landing would be flown at/near 145 KTS. The flight terminated safely and maintenance was called. Maintenance investigation found that when the autopilot disconnect button was pressed to disengage the autopilot it became stuck in the pressed position. This stuck position lead to the dual; main and backup; trim inoperative condition.I would very much like to know if this is a replicable condition with the AP disconnect button or if this failure was an anomaly. If this is a programming fail safe designed into the system; then awareness training might be beneficial to the rest of the group.




Synopsis: Air carrier Captain reported PITCH TRIM FAIL EICAS messages during short final approach.
Date: 201503
Local time of day: 1201-1800
Location: JAC.Airport, WY
Flight conditions: VMC
Light: Daylight
Aircraft: Small Aircraft; High Wing; 1 Eng; Retractable Gear
Operator: Personal
Operating under: Part 91
Flight plan: IFR
Mission: Personal
Flight phase: Final Approach
Airspace: Class D JAC
ATC / advisory: Center ZLC; Tower JAC
Reporter organization: Personal
Reporter function: Instructor; Pilot Not Flying
Reporter qualification: Flight Crew Air Transport Pilot (ATP); Flight Crew Flight Instructor; Flight Crew Multiengine
Human factors: Communication Breakdown; Confusion; Distraction; Situational Awareness; Time Pressure
Anomaly: ATC Issue All Types; Airspace Violation All Types; Deviation / Discrepancy - Procedural Published Material / Policy
Detector: Person Air Traffic Control
When detected: In-flight
Contributing factors: Human Factors; Procedure
Primary problem: Procedure

Narrative: We were on an IFR flight plan to JAC inbound from OLNUE intersection.  Approximately 15 miles from the airport ATC advised us that there was a King Air at our 6 o'clock position.  We acknowledged and continued; staying with Center.  About 7 miles from the airport ATC was going to hand us over to Tower but said 'No stay with me as I want to keep an eye on the King Air'. We had been setting up for a left downwind entry.  At abeam the end of the runway we were told to switch to Tower.  When we switched Tower was not happy and wanted to know where we had been.  There was no delay from the time we switched from Center to Tower.  Tower informed us we had entered class D airspace without communicating to them.Since Center had told us to stay with them we thought tower would know this and that it was coordinated between the both of them.  In the future we will ask if we should continue into class D airspace or stay outside of it if a similar situation arises.  Also pay closer attention as to how close the airspace is and ask ahead of time to make sure we are not in airspace that we aren't supposed to be in.




Synopsis: Pilot reports of Center telling them to stay with him; because of traffic in close proximity. Center switches aircraft over to Tower and Tower complains that they had violated the Class Delta airspace and should have called them sooner.
Date: 201910
Local time of day: 0601-1200
Location: SYR.Tower, NY
Aircraft: EMB ERJ 145 ER/LR
Operator: Fractional
Operating under: Part 135
Flight plan: IFR
Mission: Passenger
Flight phase: Final Approach
Airspace: Class C SYR
ATC / advisory: Tower SYR
Second aircraft: Airbus Industrie Undifferentiated or Other Model
Reporter organization: Fractional
Reporter function: Pilot Not Flying; First Officer
Reporter qualification: Flight Crew Air Transport Pilot (ATP)
Human factors: Situational Awareness; Time Pressure
Anomaly: ATC Issue All Types; Conflict Ground Conflict; Critical
Detector: Person Flight Crew
When detected: In-flight
Result: Flight Crew Requested ATC Assistance / Clarification; Flight Crew Executed Go Around / Missed Approach
Contributing factors: Human Factors; Procedure
Primary problem: Procedure

Narrative: During the final approach at approximately 1;000 feet; Tower cleared Aircraft Y for takeoff. Aircraft Y had just lined up and initiated the takeoff when we approached 500 feet. At 200 feet we initiated the go-around because Aircraft Y had still not rotated. Tower then gave us a left heading to reinterpret the pattern and we landed without issue. Tower should not have cleared Aircraft Y for takeoff while we were on the final approach and Aircraft Y should have requested to hold position instead of cutting it that close should they have had an issue on the roll and had we committed to land.




Synopsis: EMB-145 pilot reported a loss of spacing on final approach that resulted in a go-around.
Date: 201811
Local time of day: 1201-1800
Location: ZZZ.Airport, US
Flight conditions: VMC
Weather elements / visibility: 10
Light: Daylight
Aircraft: SR22
Operator: Personal
Operating under: Part 91
Flight plan: None
Mission: Personal
Flight phase: Landing
Reporter organization: Personal
Reporter function: Pilot Flying; Single Pilot
Reporter qualification: Flight Crew Multiengine; Flight Crew Commercial; Flight Crew Instrument
Human factors: Situational Awareness
Anomaly: Ground Event / Encounter Ground Strike - Aircraft; Ground Event / Encounter Loss Of Aircraft Control; Ground Excursion Runway
Detector: Person Flight Crew
When detected: In-flight
Result: Aircraft Aircraft Damaged; Flight Crew Regained Aircraft Control
Contributing factors: Weather; Human Factors; Environment - Non Weather Related
Primary problem: Ambiguous

Narrative: I was executing a practice VOR A approach to ZZZ in VFR weather and was inbound from the ZZZ VOR. My initial plan was to land on Runway XX. As I approached Runway XX I saw the runway appeared to have some snow on it. Therefore I decided to land on Runway XY which appeared to have much less snow on it. The landing seemed normal but as I applied brakes the aircraft did not slow down. I suspect that there may have been ice on the runway that I did not identify in the air. As a result the aircraft overran the runway by about 30 ft. (my estimate is only approximate) and came to a stop without hitting anything. Initially I did not see any damage but after a more careful examination I saw damage to a propeller blade which had struck a runway light located at the departure threshold. I think two contributing factors were that I may have been too fast and too high but could have successfully landed if the runway had been dry. Failure to properly compensate for icy conditions was a factor in the overrun.




Synopsis: SR22 Pilot reported a runway excursion and ground damage due to the loss of control on a potentially ice covered runway.
Date: 202105
Local time of day: 0601-1200
Location: ZZZ.TRACON, US
Flight conditions: VMC
Aircraft: Large Transport; Low Wing; 2 Turbojet Eng
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Climb
Airspace: Class E ZZZ
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 Commercial; Flight Crew Instrument; Flight Crew Multiengine
Human factors: Situational Awareness; Distraction
Anomaly: Airspace Violation All Types; Conflict NMAC; Deviation / Discrepancy - Procedural FAR; Deviation / Discrepancy - Procedural Published Material / Policy; Deviation / Discrepancy - Procedural Unauthorized Flight Operations (UAS)
Detector: Person Flight Crew
When detected: In-flight
Result: General None Reported / Taken
Contributing factors: Environment - Non Weather Related; Human Factors; Procedure
Primary problem: Ambiguous

Narrative: FO (First Officer) observed a black and white object roughly 2 feet in diameter passed extremely close to aircraft left during climb passing 13;500 feet on the ZZZZZ2 [SID] prior to ZZZZZ [fix]. The object was close enough that he expected an impact. As Pilot Monitoring; I was heads down attending to FMS programming and did not see the object. FO did not see wings or recognize the object as a balloon; nor could he confirm the object to be a drone.




Synopsis: Air carrier flight crew was flying a published SID and climbing above 10;000 feet when an object; possibly a UAS; passed by the aircraft.
Date: 201812
Local time of day: 0601-1200
Location: ZJX.ARTCC, FL
Flight conditions: VMC
Weather elements / visibility: 10
Light: Daylight
Aircraft: Skyhawk 172/Cutlass 172
Operator: Personal
Operating under: Part 91
Flight plan: None
Mission: Personal
Flight phase: Cruise
Airspace: Class E ZJX
Second aircraft: UAV - Unpiloted Aerial Vehicle
Reporter organization: Personal
Reporter function: Pilot Flying; Single Pilot
Reporter qualification: Flight Crew Private
Human factors: Situational Awareness
Anomaly: Conflict NMAC
Detector: Person Flight Crew
When detected: In-flight
Result: General None Reported / Taken
Contributing factors: Procedure; Airspace Structure
Primary problem: Ambiguous

Narrative: We encountered a drone at our cruise altitude of 4500 feet. It was clearly identifiable as an unmanned aerial vehicle with a white/red top and black bottom. No evasive action taken because the time between seeing the drone and the drone passing about 150 feet from our left wing was too short (estimate between 0.5 and 1 second).




Synopsis: C-172 pilot reported sighting a drone close by during cruise flight.
Date: 201606
Local time of day: 0001-0600
Location: EWR.Airport, NJ
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: Descent
Airspace: Class E N90
ATC / advisory: TRACON N90
Reporter organization: Air Carrier
Reporter function: Captain; Pilot Flying
Reporter qualification: Flight Crew Air Transport Pilot (ATP)
Human factors: Communication Breakdown; Situational Awareness
Anomaly: ATC Issue All Types; Inflight Event / Encounter Weather / Turbulence
Detector: Person Air Traffic Control; Person Flight Crew
When detected: In-flight
Result: Air Traffic Control Issued New Clearance; Flight Crew Became Reoriented
Contributing factors: Company Policy
Primary problem: Company Policy

Narrative: Yesterday while flying to EWR there were THREE of us with similar call signs...all [my airline]. The controllers were having a tough time keeping us straight and spent a lot of time correcting themselves. During descent; one controller kept telling us to level off at 10;000 feet when we were already at 8;400 and descending to 8;000. We were SURE we'd busted an altitude. We were in heavy rain and IMC; immediately stopped the descent until we could verify OUR clearance. After we queried the controller she apologized several times that she'd mixed up the call signs; but it WASN'T HER FAULT! When controllers are so busy this is setting us up for a MAJOR ACCIDENT or violation!




Synopsis: B737 Captain reported there were three company aircraft on the same frequency with similar call signs; which caused problems for both the flights and ATC.
Date: 202111
Local time of day: 1201-1800
Location: PHL.Airport, PA
Flight conditions: VMC
Weather elements / visibility: 10
Light: Daylight
Aircraft: Small Aircraft
Operator: FBO
Operating under: Part 91
Flight plan: None
Mission: Training
Flight phase: Climb
Airspace: Class B PHL
Reporter organization: FBO
Reporter function: Instructor; Pilot Not Flying
Reporter qualification: Flight Crew Commercial; Flight Crew Flight Instructor; Flight Crew Instrument; Flight Crew Multiengine; Flight Crew Private
Human factors: Confusion; Fatigue; Situational Awareness
Anomaly: Airspace Violation All Types; Deviation / Discrepancy - Procedural FAR; Deviation / Discrepancy - Procedural Published Material / Policy
Detector: Person Flight Crew
When detected: In-flight
Result: Flight Crew Exited Penetrated Airspace
Contributing factors: Airspace Structure; Environment - Non Weather Related; Human Factors
Primary problem: Human Factors

Narrative: Student pilot climbed to 4;500 feet where Class B started at 4;000 feet. Instructor did not catch the error in time and airspace was busted. The instructor had [the] student pilot descend in altitude immediately once she realized airspace was busted.Fatigue and stress were involved with student pilot. It was the last flight before the student's checkride and he was not prepared and frustrated. Instructor did not pick up on the student busting the airspace until after the airspace was busted.Instructor and student talked about this error and reviewed airspace after the flight. This was the student's first flight under the Philadelphia Class Bravo and they are now more knowledgeable of the precautions of busting airspace. Instructor also learned from this error and knows to not let it happen again.




Synopsis: GA instructor with a student pilot reported they flew into Class B airspace without a clearance.