elihoole/asrs-aviation-reports huggingface dataset:
Date: 201905
Local time of day: 0601-1200
Location: GAI.Airport, MD
Flight conditions: VMC
Light: Daylight
Aircraft: Small Transport
Flight phase: Taxi
ATC / advisory: UNICOM GAI
Reporter function: Captain
Reporter qualification: Flight Crew Commercial; Flight Crew Instrument
Human factors: Confusion; Distraction; Situational Awareness
Anomaly: Deviation / Discrepancy - Procedural Published Material / Policy
Detector: Person Flight Crew
When detected: Taxi
Result: General None Reported / Taken
Contributing factors: Airport; Chart Or Publication
Primary problem: Chart Or Publication

Narrative: Flying into GAI I noted several potentially hazardous airport operations activities with no NOTAM published. There were certain taxiways which were barricaded and unavailable for aircraft use and many airport Maintenance Personnel (I would estimate around 20 people) were conducting work on active taxiways; both within and outside of the blocked-off areas. Different areas of the airport were effected on our two different visits and at one point the approach end of Runway 32 was inaccessible requiring a back-taxi if full length was required. The Maintenance Personnel seemed very aware and acted safely at all times; however it did impact airport operations at a busy non-towered airport and is certainly the type of event that should have been published in a NOTAM. Additionally; possibly due to the work being done; there were discrepancies between the taxiway signage on the airport and the depictions on the chart. This could potentially cause a safety issue due to miscommunication between aircraft if one was using the taxiway designation on a sign and another was using the chart. Specifically; I recall that Taxiway A4 on the chart was signed as A3. A NOTAM should be published when this type of work is being conducted at an airport. If this is not possible; perhaps the AWOS recording could have some mention to the work being conducted.




Synopsis: Small Transport aircraft Captain reported there are no NOTAMs at GAI airport with regards to the current unavailable taxiways and work in progress. Discrepancies between signage and taxiway charts were also cited.
Date: 201603
Local time of day: 1201-1800
Location: ZZZ.Tower, US
Flight conditions: VMC
Weather elements / visibility: 10
Light: Daylight
Aircraft: PC-12
Operator: Air Carrier
Operating under: Part 135
Flight plan: IFR
Mission: Passenger
Flight phase: Takeoff / Launch
Airspace: Class B ZZZ
Aircraft component: Turbine Engine
Component problem: Malfunctioning
Reporter organization: Air Carrier
Reporter function: Captain; Pilot Flying
Reporter qualification: Flight Crew Air Transport Pilot (ATP); Flight Crew Multiengine; Flight Crew Instrument
Anomaly: Aircraft Equipment Problem Critical
Detector: Person Flight Crew
When detected: In-flight
Result: Flight Crew Landed in Emergency Condition; Flight Crew Requested ATC Assistance / Clarification; Flight Crew Returned To Departure Airport
Contributing factors: Aircraft
Primary problem: Aircraft

Narrative: [We] lined up for takeoff. After setting power at 43 PSI Torque; a standard takeoff occurred. At approximately 300 ft. AGL; the Master Caution illuminated and I saw the Torque gauge surging back and forth from 35-51 PSI (above max limitations); without anyone touching the throttle. I tried adjusting the throttle lower; to no avail. I did not feel the engine itself surge; but being so close to the ground and concentrating on flying; I could not check all the other gauges and diagnose the problem properly. I asked the copilot (who had just switched to departure frequency) to advise we needed to remain in the pattern and return to land immediately. The copilot relayed that to ATC; who asked if we were [requesting] for priority (they were busy at the time). We remained left closed traffic and ran the appropriate check lists. Once the power was pulled back to about 30 PSI; the torque surging stopped. Two aircraft on final were given go around/vectors as a result of our [situation]. We made an uneventful landing and taxied in. No emergency services were used or ever seen.




Synopsis: PC-12 Captain reported returning to departure airport after noticing the torque gauge surging shortly after takeoff.
Date: 201910
Local time of day: 1801-2400
Location: RDU.Airport, NC
Flight conditions: VMC
Aircraft: A320
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Taxi
ATC / advisory: Tower RDU
Reporter organization: Air Carrier
Reporter function: Captain; Pilot Flying
Reporter qualification: Flight Crew Instrument; Flight Crew Multiengine; Flight Crew Air Transport Pilot (ATP)
Human factors: Distraction; Situational Awareness
Second reporter function: First Officer; Pilot Not Flying
Anomaly: Deviation / Discrepancy - Procedural Published Material / Policy; Ground Event / Encounter Object; Ground Excursion Taxiway
Detector: Person Other Person
When detected: Taxi
Result: General None Reported / Taken
Contributing factors: Human Factors; Procedure; ATC Equipment / Nav Facility / Buildings; Airport
Primary problem: Procedure

Narrative: It was reported to me that we hit a taxi way light last week during our 3 day trip. We were given a push clearance off of the gate and instructions were for push crew to give way to an aircraft under tow and then push us tail north but push us far enough north that we would exit ramp at the assigned taxiway. We pushed as directed and ground crew disconnected. We contacted Ground Control and were issued taxi instructions. I started to make the right turn and the First Officer said 'we have a taxi light right here. I straightened out and taxied thanking my First Officer for stopping me from turning to soon; unaware that we had hit anything. I had cleared the right turn with the First Officer before taxiing but started my turn toward the taxiway without realizing I was so close to the edge of the taxiway. I should have looked at the angle of the taxiway more carefully on the airport diagram before beginning the turn and I also would recommend that Ramp Control not use this taxiway for taxi out when aircraft are facing the opposite direction as it makes for a bad situation where hitting a taxi way light is more probable.


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


Synopsis: A320 flight crew reported that ATC instructions combined with a loss of situational awareness caused them to hit a taxiway light.
Date: 201907
Local time of day: 1801-2400
Location: MWH.Airport, WA
Light: Daylight
Aircraft: Fighter
Operator: Military
Operating under: Part 91
Flight plan: IFR
Mission: Tactical
Flight phase: Final Approach
Airspace: Class D MWH
ATC / advisory: TRACON MWH
Reporter organization: Government
Reporter function: Approach
Reporter qualification: Air Traffic Control Fully Certified
Human factors: Situational Awareness; Communication Breakdown
Anomaly: Deviation - Altitude Excursion From Assigned Altitude; Deviation / Discrepancy - Procedural Clearance; Inflight Event / Encounter CFTT / CFIT
Detector: Person Air Traffic Control
When detected: In-flight
Result: Air Traffic Control Provided Assistance; Flight Crew Returned To Clearance
Contributing factors: Human Factors
Primary problem: Human Factors

Narrative: Aircraft X inbound for an IFR approach then RTB to ZZZ. Aircraft was level at 6;000 then issued a descent to 4;000. The aircraft read back 'out of 6;000 for 4;000'. They descended to roughly 3;000. I; the Controller noticed this as they entered a 4;000 MVA. Controller issued a climb to 4;000 and heading to turn back into a 3;000 MVA. Controller asked if they could maintain their own terrain and obstruction clearance up to 4;000. The aircraft responded the first time with something similar to 'say again'. Controller reissued the instruction and they answered in the affirmative.The aircraft had omitted part of their return clearance and I had to reissue the specific instructions to them. If I had to guess I would say the pilot had low experience in an [type].




Synopsis: Moses Lake TRACON Controller reported an aircraft below the MVA and related issues.
Date: 201707
Local time of day: 0601-1200
Location: ZZZ.Airport, US
Flight conditions: VMC
Light: Daylight
Aircraft: MD-11
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Cargo / Freight / Delivery
Flight phase: Cruise
Airspace: Class A ZZZ
ATC / advisory: Center ZZZ
Aircraft component: Hydraulic Main System
Component problem: Failed
Reporter organization: Air Carrier
Reporter function: Captain; Pilot Flying
Reporter qualification: Flight Crew Air Transport Pilot (ATP)
Anomaly: Aircraft Equipment Problem Critical
Detector: Person Flight Crew
When detected: In-flight
Result: Air Traffic Control Provided Assistance; Flight Crew Landed in Emergency Condition; Flight Crew Overcame Equipment Problem
Contributing factors: Aircraft
Primary problem: Aircraft

Narrative: During cruise experienced HYD3 PRES HI LVL 2 Alert and HYD3 OFF LVL 1 Alerts. On checking the display; I noticed HYD 3 PRES was 3270 psi and HYD3 temperature was 120C. Soon after that quantity on HYD 3 went to 0. We then received HYD 3 FAIL LVL 2 Alert. Followed QRH For HYD 3 FAIL. Performed Manual Gear Extension. Proceeded to land. [Advised ATC]; received very good handling from them and coordination from Operations.




Synopsis: MD-11 Captain reported landing safely after the #3 hydraulic system failed during cruise.
Date: 202112
Local time of day: 0601-1200
Location: ZZZ.Airport, US
Flight conditions: VMC
Weather elements / visibility: 10
Light: Daylight
Aircraft: Cessna 340/340A
Operator: Personal
Operating under: Part 91
Flight plan: None
Mission: Personal
Flight phase: Landing
Airspace: Class D ZZZ
ATC / advisory: Tower ZZZ
Aircraft component: Landing Gear
Component problem: Failed
Reporter organization: Personal
Reporter function: Single Pilot; Pilot Flying
Reporter qualification: Flight Crew Multiengine; Flight Crew Commercial; Flight Crew Instrument
Anomaly: Aircraft Equipment Problem Critical; Ground Event / Encounter Other / Unknown
Detector: Person Flight Crew
When detected: In-flight
Result: General None Reported / Taken
Contributing factors: Aircraft
Primary problem: Aircraft

Narrative: I went out for a local flight; I proceeded to the practice area. Returning back to the airport and after completing the before landing checklist 3 green lights indicated that gear was down and locked.I called the Tower to confirm my landing gear was down. Tower confirmed the gear was down. Landing was smooth and during the roll out of the runway; the right main gear collapsed. No airport property was damaged or fluids spilled from the aircraft.




Synopsis: Cessna 340 pilot reported the landing gear collapsed on landing.
Date: 201305
Local time of day: 1201-1800
Location: ZZZ.Airport, US
Flight conditions: VMC
Weather elements / visibility: Windshear; GUSTING CONDITIONS
Aircraft: Light Sport Aircraft
Operator: Personal
Operating under: Part 91
Flight plan: None
Mission: Training
Flight phase: Landing
ATC / advisory: Tower ZZZ
Reporter organization: Personal
Reporter function: Instructor; Pilot Not Flying
Reporter qualification: Flight Crew Commercial; Flight Crew Flight Instructor; Flight Crew Multiengine; Flight Crew Instrument
Human factors: Human-Machine Interface
Anomaly: Ground Event / Encounter Ground Strike - Aircraft; Ground Excursion Runway; Inflight Event / Encounter Loss Of Aircraft Control; Inflight Event / Encounter Weather / Turbulence
Detector: Person Flight Crew
When detected: In-flight
Result: Aircraft Aircraft Damaged; Flight Crew Regained Aircraft Control; General Maintenance Action
Contributing factors: Human Factors; Weather
Primary problem: Ambiguous

Narrative: Upon landing rollout in a wheel landing configuration; a wind direction change caused the tail of the aircraft to veer. The instructor could not react fast enough to prevent the aircraft from departing the runway. The right wing tip contacted the ground and minimal damage was done. Upon inspection the aircraft was returned to its hangar for further inspection by the owner and Mechanic. The Mechanic then placed a temporary patch on the right wing tip and returned the aircraft to service.




Synopsis: Sport Cub instructor pilot reports his student losing control due to a wind gust during a wheel landing. The instructor cannot react quickly enough and the aircraft departs the runway with the right wing tip contacting the ground.
Date: 201502
Local time of day: 1201-1800
Location: ZZZ.TRACON, US
Flight conditions: IMC
Aircraft: Large Transport; Low Wing; 2 Turbojet Eng
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Climb
Aircraft component: Turbine Engine
Component problem: Malfunctioning
Reporter organization: Air Carrier
Reporter function: Captain; Pilot Not Flying
Reporter qualification: Flight Crew Commercial
Human factors: Workload
Second reporter function: Pilot Flying; First Officer
Anomaly: Aircraft Equipment Problem Critical; Inflight Event / Encounter Weather / Turbulence
Detector: Person Flight Crew
When detected: In-flight
Result: Aircraft Aircraft Damaged; Flight Crew Inflight Shutdown; Flight Crew Returned To Departure Airport; General Declared Emergency
Contributing factors: Aircraft; Weather
Primary problem: Aircraft

Narrative: Climbing through 2;000 feet; right engine began banging with associated oscillations of engine instruments. Flight leveled at 3;000 feet. Throttle was brought to idle and banging stopped. Vector back to our departure airport requested. Right engine was idling at 10% N1; 10% N2. Right engine was then shut down IAW QRH. First Officer flew while Captain ran checklist and communicated with Flight attendants. Air and Rescue Fire Fighters (ARFF) requested. Icing was encountered during descent. Flight landed uneventfully 19 minutes after takeoff. ARFF reported bullet cone of right engine was detached and lying at the bottom of cowling.


Second narrative: The regular bangs seemed like 'compressor stalls' as we leveled. At this point we both were extremely busy. I was flying the aircraft with the right engine at idle; at night; in icing conditions; and talking with ATC to give them the fuel and souls on board. Interestingly; I remember them asking for the fuel quantity in pounds!!!! Although we were extremely busy inflight trying to accomplish checklists; we were able to do so in a timely manner and turned final at 10 miles from the airport. Time compression at the time made it seem like the flight lasted longer than it actually did. The Captain did an outstanding job of running multiple checklists making PA's to keep passengers informed and keeping Flight Attendants in the loop as to our intentions. Plus he kept an eye on me to be sure we were doing the right things at the right times.


Synopsis: When the right engine started making continuous loud banging sounds similar to compressor stalls shortly after takeoff; a flight crew advised ATC; performed an inflight shut down of the engine and returned to their departure airport.
Date: 201901
Local time of day: 1201-1800
Location: ZZZ.Airport, US
Flight conditions: VMC
Weather elements / visibility: 10
Light: Daylight
Aircraft: PA-28 Cherokee/Archer/Dakota/Pillan/Warrior
Operator: Personal
Operating under: Part 91
Flight plan: None
Mission: Personal
Flight phase: Landing
Airspace: Class C ZZZ
ATC / advisory: TRACON ZZZ
Reporter organization: Personal
Reporter function: Pilot Flying
Reporter qualification: Flight Crew Private
Human factors: Training / Qualification; Situational Awareness
Second reporter function: Pilot Not Flying
Anomaly: Ground Event / Encounter Object; Ground Excursion Runway; Inflight Event / Encounter Weather / Turbulence
Detector: Person Flight Crew
When detected: In-flight
Result: Aircraft Aircraft Damaged
Contributing factors: Human Factors
Primary problem: Human Factors

Narrative: I was cleared to land. Conditions were windy; and I handled the approach for landing from the right seat. My approach was faster than what it should have been. The aircraft then landed further down the runway than expected. Upon touchdown I lost control of the aircraft and could not get the plane stopped in time. The aircraft veered off of the runway shortly after striking into a runway light.


Second narrative: There were four people on board; I was in the left seat and a friend; also a private pilot; was in the right seat and two passengers in the back. I was PIC of the flight and my friend was the pilot flying the aircraft from cruise down to landing. We filed a VFR flight plan and received flight following upon departure. The winds were calm when we departed but as we got closer to the airport of intended landing the winds were variable and gusty. Approach vectored us around for [the] runway (3;500 feet long). I was tuning frequencies and getting my taxiways diagram ready since he had control of the aircraft.The pilot flying misjudged the length of the runway and overran the runway and hit a runway threshold light and stopped about 100ft on the grass. While we were 2 miles from the runway our airspeed was 110kts and the aircraft was slowing down. As we were over the runway there was slight gust of wind that bumped our speed from 80kts back to 100kts. He reduced the power to idle and tried to complete the landing; and with the short runway there wasn't enough time to decide to go around; he landed and hit the brakes to slow the airplane down but it was already too late and within a few seconds later overran the runway onto the grass. There was no substantial damage to the aircraft; and [ground personnel] pushed the airplane back to the runway and they advised me to contact ground and taxi back to the FBO.


Synopsis: PA28 flight crew reported the aircraft ran off the end of the runway following a fast; long landing.
Date: 201506
Local time of day: 0601-1200
Location: ZZZ.Airport, US
Flight conditions: VMC
Light: Daylight
Aircraft: A319
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Final Approach; Initial Approach
Airspace: Class B ZZZ
ATC / advisory: Tower ZZZ
Reporter organization: Air Carrier
Reporter function: Pilot Not Flying; Captain
Reporter qualification: Flight Crew Air Transport Pilot (ATP)
Human factors: Distraction; Fatigue; Situational Awareness; Workload
Anomaly: Deviation / Discrepancy - Procedural Published Material / Policy; Inflight Event / Encounter Unstabilized Approach
Detector: Person Flight Crew
When detected: In-flight
Result: Flight Crew Took Evasive Action; Flight Crew Returned To Clearance; Flight Crew Became Reoriented
Contributing factors: Human Factors; Procedure
Primary problem: Procedure

Narrative: First Officer (FO) flying. Approach turned us high on base leg and cleared us for a visual to Runway X. FO disconnected all automation (including autothrust). He had previously briefed me that he was going to do that for proficiency. He began to slow to final approach speed and called for gear and flaps on schedule. I saw we were high and requested S-turns from the tower which was approved. We slowed to final approach speed all configured for landing and completed the landing checklist. We continued the S-turns to lose altitude but had a high sink rate due to the altitude. We both discussed deviations and corrections during the approach and communicated well to get the approach stabilized with plenty of time for a normal landing in the touchdown zone at the appropriate speed. Event occurred because of a high turn to base and all automation being disconnected which is a little out of the ordinary in this aircraft. Potential additional factor is that this was the fourth 'stand-up' overnight in a row for me and the third for the first officer. Although we were running on schedule this trip; the accumulated fatigue; short rest time; and [early morning] departure could possibly slow reaction time and affect decision-making.I think probably a wider turn to final or a longer downwind to lose altitude would have been the best option. After the sink rate did not improve a go-around would have been prudent. An earlier intercept of the VASI or electronic glide path would have prevented the high sink rate. Also thinking a little more ahead and maybe leaving some of the automation on for better vertical guidance.




Synopsis: An A319 First Officer disconnected all automation including autothrust to practice a manual visual approach; but got high on profile. S-turns along with a high sink rate were required to attain a normal profile before landing on speed in the landing zone. Fatigue was an issue.
Date: 202101
Local time of day: 1201-1800
Location: AFW.Airport, TX
Aircraft: Small Aircraft; High Wing; 1 Eng; Fixed Gear
Operating under: Part 91
Flight plan: IFR
Flight phase: Final Approach
Airspace: Class D AFW
ATC / advisory: Tower AFW
Second aircraft: Any Unknown or Unlisted Aircraft Manufacturer
Reporter function: Local
Reporter qualification: Air Traffic Control Fully Certified
Human factors: Situational Awareness
Anomaly: ATC Issue All Types; Conflict Airborne Conflict
Detector: Person Air Traffic Control
When detected: In-flight
Result: Air Traffic Control Issued Advisory / Alert; Air Traffic Control Provided Assistance; Flight Crew Took Evasive Action
Contributing factors: Aircraft; Airspace Structure; Human Factors
Primary problem: Airspace Structure

Narrative: Aircraft X was on an ILS Approach to Runway 16L. A VFR aircraft was skirting around AFW's Class D airspace; not in communication with AFW or D10. The VFR aircraft was eastbound then turned north and crossed over WIGZU the FAF for ILS RWY 16L at 2;600 FT MSL. Aircraft X was at the same altitude. The Local Controller called the traffic and Aircraft X reported the traffic in sight. Aircraft X reported that they had to turn off the ILS then turn back once they were clear of the traffic. The two aircraft were less than 1/2 mile apart at the same altitude head on to each other. This area is dangerous and this continues to be an issue. The airspace design is outdated. AFW airport has grown and is continuing to grow. The facility has recently been upgraded from a Level 5 Tower to a Level 6 Tower. In the last year three new air carriers have all started operating at AFW.  A contractor for the US military has relocated their maintenance base to AFW. Aerospace company X has also begun construction at their new facility here as well. Both runways were extended from 9;000 feet to 11;000 feet in the last few years. Everything at this airport has been growing and expanding except the airspace. The Class Bravo airspace should be expanded to include WIGZU the FAF for RWY 16L. This would allow us the ability to talk to VFR aircraft that constantly cross this area around 2;500 feet. We have conducted pilot outreach at surrounding airports. It has not been successful. We just want the ability to talk to these VFR aircraft to provide traffic advisories. The airspace needs to be updated.




Synopsis: AFW Tower Controller reported an airborne conflict and cited airspace design as a contributing factor.