elihoole/asrs-aviation-reports huggingface dataset:
Date: 202011
Local time of day: 1801-2400
Location: ZZZ.Airport, US
Flight conditions: VMC
Light: Night
Aircraft: Small Aircraft; Low Wing; 1 Eng; Fixed Gear
Operator: Personal
Operating under: Part 91
Flight plan: None
Mission: Personal
Flight phase: Final Approach
Aircraft component: Fuel System
Component problem: Improperly Operated
Reporter organization: Personal
Reporter function: Single Pilot
Reporter qualification: Flight Crew Air Transport Pilot (ATP); Flight Crew Multiengine; Flight Crew Instrument
Human factors: Time Pressure; Situational Awareness; Human-Machine Interface
Anomaly: Aircraft Equipment Problem Critical; Deviation / Discrepancy - Procedural Published Material / Policy; Ground Event / Encounter Ground Strike - Aircraft; Inflight Event / Encounter Fuel Issue
Detector: Person Flight Crew
When detected: In-flight
Result: Aircraft Aircraft Damaged; Flight Crew Landed in Emergency Condition
Contributing factors: Human Factors
Primary problem: Human Factors

Narrative: While flying [my aircraft]; I experienced an engine failure approximately 15 NM prior to the destination runway while flying at approximately 2;300 feet.  I had been experiencing extreme headwinds since a refueling stop and the leg had taken me longer than I'd planned. Because of the added flight time; I was thinking about fuel; but I thought I had enough fuel to make the intended destination with minimum reserves.  The engine failure was accompanied by a lack of fuel pressure that was not remedied by turning on an electric fuel pump.  I firmly believe it was due to fuel exhaustion.  With no airports within gliding distance; I angled the plane towards the interstate; and eventually lined up on a dark area parallel to the highway and attempted a landing onto an area about 100 yards from the highway. As I approached the field; I flared; and initially landed the main wheels successfully and rolled for a couple of seconds; probably 20 yards; but as soon as the nose wheel touched the recently plowed soft dirt; it dug in.  I did not suffer any serious injuries that I'm aware of and the plane had surprisingly minor damage.  Upon checking the fuel tanks after exiting the plane; they were indeed empty.




Synopsis: GA pilot reported making an off-airport landing that resulted from fuel exhaustion.
Date: 201602
Local time of day: 1801-2400
Location: ZZZ.TRACON, US
Flight conditions: VMC
Weather elements / visibility: 10
Light: Night
Aircraft: Cessna 152
Operator: FBO
Operating under: Part 91
Flight plan: None
Mission: Training
Flight phase: Cruise
Airspace: Class E ZZZ
ATC / advisory: TRACON ZZZ
Aircraft component: Engine
Component problem: Malfunctioning
Reporter organization: FBO
Reporter function: Pilot Flying; Instructor
Reporter qualification: Flight Crew Commercial; Flight Crew Instrument; Flight Crew Flight Instructor
Anomaly: Aircraft Equipment Problem Critical
Detector: Person Flight Crew
When detected: In-flight
Result: Flight Crew Landed As Precaution; General Evacuated; General Maintenance Action
Contributing factors: Aircraft; Human Factors
Primary problem: Ambiguous

Narrative: While enroute during a night cross country training flight; the power plant of the aircraft started sharing very rough and engine would provide only partial power. Immediately I started troubleshooting with the checklist to identify the possible cause. Only a reduction in power below 1500 RPM by the use of the throttle lever would minimize the vibration. I informed Approach of the situation; the nearest airport they mentioned was about 9 miles to the east. This power setting did not allow me to maintain altitude at the best glide speed of the aircraft; aircraft kept descending about 200 feet per minute. I directed the aircraft towards the road since it seemed it was the safest place to land. I followed the procedures on checklist for forced landing with engine power. Aircraft landed safe on the road. There was no property damage and no one was harmed. The aircraft was evacuated after it came to a complete stop; and after a few minutes the aircraft was pushed to the grassy area besides the road to prevent the aircraft from being damaged by local automobile traffic in the dark road. After emergency personnel left the area; I remained near the aircraft until mechanics and flight school representative arrived at the scene. Mechanics inspected the aircraft and mentioned that cylinder #2 was damaged and that the most likely cause was improper valve seating adjustment during maintenance. The aircraft had recently been released of 100 hour inspection according to maintenance logbooks. I aided in the removal of the wings and the aircraft was towed back to the airport.




Synopsis: A C152 pilot reported the loss of engine power that resulted in an off-field landing.
Date: 202110
Local time of day: 1201-1800
Location: ZZZ.Airport, US
Aircraft: Small Aircraft; High Wing; 1 Eng; Fixed Gear
Operating under: Part 91
Flight plan: IFR
Flight phase: Final Approach
Airspace: Class C ZZZ
ATC / advisory: TRACON ZZZ
Second aircraft: Military Trainer
Reporter organization: Government
Reporter function: Approach
Reporter qualification: Air Traffic Control Fully Certified
Human factors: Confusion; Situational Awareness; Time Pressure; Training / Qualification; Workload; Communication Breakdown
Anomaly: ATC Issue All Types; Conflict Airborne Conflict; Deviation / Discrepancy - Procedural Published Material / Policy; Deviation / Discrepancy - Procedural Clearance; Inflight Event / Encounter CFTT / CFIT
Detector: Person Air Traffic Control
When detected: In-flight
Result: Air Traffic Control Issued New Clearance; Air Traffic Control Provided Assistance
Contributing factors: Human Factors; Procedure
Primary problem: Procedure

Narrative: On Date at XA:10; the west side of the weekend split configuration was running approaches into ZZZ Runway XX. They had Aircraft X IFR doing the RNAV Runway XX approach and a flight of 2 Aircraft Y; come in for break traffic. I was working the east side of the weekend split. At XA:07 the Local Control at ZZZ Tower calls to ask what's the sequence between Aircraft X and the flight of 2 / Aircraft Y. West Controller told them that the 2 / Aircraft Y are going for the break; thus they call the sequence as they choose where the break point is.A minute or so later we see the IFR Aircraft X start a left-hand turn off the approach at 1;100 and proceeds to do a 360. Then another 360. At no point does the Local Controller call to APREQ (Approval Request) this. The TRACON CIC at the time calls the Tower CIC to ask what Aircraft X is doing / if he had canceled IFR and was told that there was nothing they could have done with him with the sequence we provided and that he was still IFR. This is very troubling to hear as it shows that the Tower Controller does not only [not] know how to work break traffic; but worse; they chose to spin an IFR aircraft on a 3-mile final below the MVA. This is plain unsafe and dangerous. ZZZ Tower has a culture of spinning VFR aircraft in all quadrants of their airspace when they get busy. This I believe; is a contributing factor as their tool box does not include; 'Extend your downwind; I'll call your base.' [I recommend] training for the Tower staff.




Synopsis: TRACON Controller reported a MVA violation when the Tower spun an arrival below the MVA.
Date: 202012
Local time of day: 1201-1800
Location: ZZZ.Airport, US
Aircraft: Commercial Fixed Wing
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Ferry / Re-Positioning
Flight phase: Parked
Reporter organization: Air Carrier
Reporter function: Captain; Pilot Flying
Reporter qualification: Flight Crew Air Transport Pilot (ATP); Flight Crew Multiengine; Flight Crew Instrument
Human factors: Confusion; Distraction; Troubleshooting; Time Pressure
Anomaly: Deviation / Discrepancy - Procedural Maintenance; Deviation / Discrepancy - Procedural Published Material / Policy; Ground Event / Encounter Fuel Issue
Detector: Person Flight Crew
When detected: Pre-flight
Result: Flight Crew Overcame Equipment Problem; General Flight Cancelled / Delayed
Contributing factors: Company Policy; Environment - Non Weather Related; Procedure; Human Factors
Primary problem: Procedure

Narrative: Upon doing cockpit pre-flight to ferry Aircraft X out of long-term storage from ZZZ to ZZZ1; I noticed the aircraft was fueled improperly. The wing tanks were not full and were imbalanced; there was no fuel in the center tank and there was fuel in the ACT (auxiliary) fuel tanks. This is not the proper configuration for fueling the aircraft. The wing tanks must be full before there can be any fuel in the center tank and certainly there cannot be fuel in the ACT tanks in this scenario. We notified the mechanics onboard who were assisting us to make sure everything was good prior to departure. What ensued was a three-hour debacle trying to figure out how to drain the fuel from the ACT tanks and ensure the only fuel was in the wing tanks. Planned release fuel was 25k; which in this scenario should result in fuel only in the wing tanks. After the fueling issue was finally resolved; we received two separate ECAMS after engine start. Shut down the engines and called the mechanics back to fix the new issues. SMOKE DET Fault and ANTI ICE STBY L STAT. MX fixed those two issues and we finally departed over four hours late.Someone in ZZZ is not making sure [aircraft company] aircraft coming out of storage are fueled properly. This is the second time I have caught a problem. Someone less vigilant may miss the problem.This is the second fueling issue I have had with an aircraft coming out of storage from ZZZ in the past two weeks.




Synopsis: Air carrier Captain reported having an aircraft that was fueled incorrectly for a ferry flight.
Date: 201409
Local time of day: 1801-2400
Location: ZDC.ARTCC, VA
Aircraft: Small Transport; Low Wing; 2 Turboprop Eng
Operator: Corporate
Operating under: Part 91
Flight plan: IFR
Mission: Passenger
Flight phase: Cruise
Airspace: Class A ZDC
ATC / advisory: Center ZDC
Reporter organization: Government
Reporter function: Enroute
Reporter qualification: Air Traffic Control Fully Certified
Human factors: Troubleshooting; Confusion; Distraction; Situational Awareness; Communication Breakdown
Anomaly: Deviation / Discrepancy - Procedural Clearance; Deviation / Discrepancy - Procedural Published Material / Policy; Inflight Event / Encounter Weather / Turbulence
Detector: Person Air Traffic Control
When detected: In-flight
Result: Air Traffic Control Provided Assistance
Contributing factors: Human Factors; ATC Equipment / Nav Facility / Buildings; Procedure
Primary problem: ATC Equipment / Nav Facility / Buildings

Narrative: I was working Sea Isle sector 59 with weather deviations and lots of transmissions.  I then noticed an aircraft showing FL320 with no information or track about 20 miles inside my airspace.  I advised the supervisor while I coordinated with Boston Center; HTO Hampton Sector who had worked the aircraft but no longer had the information on it and then they had to coordinate with Manta sector at New York Center to get the aircraft flight information.  HTO sector then coordinated Aircraft X flight plan information to me which is when I tracked the plane up; reissued routing; and continued to work.  We are in the process of transitioning to ERAM continuously and there was a problem with NY or Boston being able to flash the aircraft to me and then no manual hand off was made.Controllers should make manual hand offs as soon as feasible to avoid this type of situation.




Synopsis: ZDC Controller reports of an aircraft that was in his airspace without any track ID or hand off from the previous sector.
Date: 201904
Local time of day: 1801-2400
Location: ZZZ.Airport, US
Flight conditions: IMC
Light: Night
Aircraft: EMB ERJ 170/175 ER/LR
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Initial Climb
ATC / advisory: TRACON ZZZ
Reporter organization: Air Carrier
Reporter function: Pilot Not Flying; First Officer
Reporter qualification: Flight Crew Air Transport Pilot (ATP); Flight Crew Instrument; Flight Crew Multiengine
Anomaly: Flight Deck / Cabin / Aircraft Event Smoke / Fire / Fumes / Odor
Detector: Person Flight Crew
When detected: In-flight
Result: Flight Crew Overcame Equipment Problem
Contributing factors: Aircraft
Primary problem: Aircraft

Narrative: During initial climbout; at approximately 8;000 MSL; the Captain reported smelling the dirty sock odor. I noticed it as well; and donned my oxygen mask. I left the mask on for the next ten minutes. We called the flight attendants; who did not report any unusual odor in the cabin. The fumes subsided in about five minutes. I did not notice any physiological symptoms. We continued the flight with no further issues. Suggestions: provide training to flight crew; cabin crew; maintenance; and ground crew on the dirty sock odor - recognition; reporting; physiological effects; etc.; to raise awareness. Develop a checklist specifically for dirty sock fume events. Attempt to determine root cause of these events at [company] (oil over-servicing? etc.).




Synopsis: EMB-175 flight crew reported a dirty socks odor during initial climb.
Date: 202202
Local time of day: 1201-1800
Location: ZLC.ARTCC, UT
Aircraft: Single Engine Turboprop Undifferentiated
Flight plan: IFR
Flight phase: Final Approach
Airspace: Class E ZLE
ATC / advisory: Center ZLC
Reporter organization: Government
Reporter function: Enroute
Reporter qualification: Air Traffic Control Fully Certified
Human factors: Communication Breakdown
Anomaly: ATC Issue All Types; Deviation - Track / Heading All Types; Deviation / Discrepancy - Procedural Clearance; Deviation / Discrepancy - Procedural Published Material / Policy; Inflight Event / Encounter CFTT / CFIT; Inflight Event / Encounter Weather / Turbulence
Detector: Person Air Traffic Control
When detected: In-flight
Contributing factors: Airspace Structure; Chart Or Publication; Weather; Procedure; Human Factors
Primary problem: Human Factors

Narrative: I cleared Aircraft X for the ILS approach into IDA and informed the pilot of the 1200 RVR. 1 minute from WOTES the pilot told me he needed 2400 RVR and would need to hold. I issued holding at WOTES at 080 and the pilot read it back. No turn direction was issued as the pilot is expected to make standard right turns. 2 minutes later Aircraft X began a left turn and clipped a terrain box. A climb to 090 was issued.Recommendation - State turn directions if needed.




Synopsis: ZLC Center Controller reported an aircraft on the ILS approach to IDA airport entered holding with left turns instead of right turns and flew below the Minimum Vectoring Altitude.
Date: 201911
Local time of day: 0001-0600
Location: LAS.TRACON, NV
Flight conditions: VMC
Light: Daylight
Aircraft: Commercial Fixed Wing
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Initial Approach
Airspace: Class B LAS
ATC / advisory: TRACON L30
Reporter organization: Air Carrier
Reporter function: Pilot Not Flying; Captain
Reporter qualification: Flight Crew Instrument; Flight Crew Air Transport Pilot (ATP); Flight Crew Multiengine
Human factors: Situational Awareness; Confusion; Communication Breakdown
Anomaly: Deviation - Track / Heading All Types; Deviation / Discrepancy - Procedural Clearance; Deviation / Discrepancy - Procedural Published Material / Policy
Detector: Person Air Traffic Control
When detected: In-flight
Result: Air Traffic Control Issued New Clearance; Flight Crew Requested ATC Assistance / Clarification
Contributing factors: Procedure; Human Factors; Airspace Structure; Chart Or Publication; Company Policy
Primary problem: Chart Or Publication

Narrative: We had expected the RNAV Arrival. We were then told we would expect a different runway and were given a clearance that after a fix would be cleared for the RNAV Visual to the new runway. I pulled the approach out of the FMS and on my iPad and after asking my First Officer; used heading select to aim him on a dogleg left base to intercept the final. The weather was typically clear with unlimited visibility; and we had done a brief for a Visual Approach backed up with the RNAV Approach. The controller then gave us a heading to 245; which I answered but was probably blocked and I answered him again on the second call. He insisted that he had cleared us for the 'RNAV Visual' which we had both misinterpreted. Landing was uneventful and after we got to the gate I called the TRACON to talk to the chief and find out how the miscommunication evolved. In talking with ATC by phone; I learned that we were certainly not the first to make this mistake. He told me that the Charted Visual is to protect an underlying helicopter route among other things.I then found out that there is an actual RNAV Visual Approach listed as RNVV in the FMS database ; not page 12-3. There is an 'All Users' note on page 19-0 which we had missed as well. Unless you land on page 19-0-2 you will probably miss 19-0. When using the iPad I scrolled down to the RNAV page and did not know that there was more unseen below where I had put my finger. I do believe that there is a way to make sure that the term 'VISUAL' and 'RNAV-visual' remain unconfused. That would be to do; as is common at SFO for example. SFO has their visuals listed with names such as 'FMS Bridge visual'...'Tip Toe visual' and 'Quiet Bridge visual'. Thus the underlying RNAV GPS waypoints and altitudes remain intact but the possible confusion about being cleared for a generic visual approach is eliminated. This simple name change could then protect underlying routes.




Synopsis: Air Carrier Captain reported flying a standard visual approach to LAS when ATC had cleared them for a charted RNAV Visual Approach; resulting in a clearance deviation.
Date: 201605
Local time of day: 1201-1800
Location: ZZZ.Airport, US
Flight conditions: VMC
Weather elements / visibility: 10
Light: Daylight
Aircraft: Skylane 182/RG Turbo Skylane/RG
Operator: Personal
Operating under: Part 91
Flight plan: None
Mission: Personal
Flight phase: Landing
Aircraft component: Engine
Component problem: Malfunctioning
Reporter organization: Personal
Reporter function: Pilot Flying; Single Pilot
Reporter qualification: Flight Crew Commercial; Flight Crew Instrument
Anomaly: Aircraft Equipment Problem Critical
Detector: Person Flight Crew
When detected: In-flight
Result: Flight Crew Overcame Equipment Problem; General Maintenance Action
Contributing factors: Aircraft
Primary problem: Aircraft

Narrative: My plane was just out of annual with an engine overhaul. I had completed two one-hour break-in flights in the airport vicinity. This trip was to start the longer flight phase of breaking in the new engine. I flew uneventfully [for] a distance of about 200 nm. I refueled; took a short break; and returned to [home airport]. The cruise phase of the flight was uneventful.On short final I reduced power to about 16 inches; slightly above my normal final setting; to ensure that the engine was still powering the propeller since this is considered important for engine break-in. At an altitude of around 15 feet; I pulled the throttle back to reduce the engine to idle power. This however had no effect. I then tried to increase power for a go-around; intending to diagnose the problem in the air. This also had no effect.I then pulled the mixture control; which stopped the engine. I made a normal power-off landing and had enough momentum to taxi off the runway; where I stopped. I restarted the engine and confirmed that the throttle was ineffective and that the engine was producing significant power; too much to taxi safely.I notified Ground of the situation and waited for a tow-truck from the shop that had done the engine overhaul; for a period of about 30 minutes. The aircraft was then towed back to their hangar.




Synopsis: Cessna 182 pilot reported that during break-in following overhaul the engine became non-responsive to throttle inputs on short final.
Date: 202112
Local time of day: 1801-2400
Location: ZZZ.Airport, US
Flight conditions: VMC
Weather elements / visibility: Wind
Aircraft: Commercial Fixed Wing
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Initial Approach
Airspace: Class D ZZZ
ATC / advisory: Tower ZZZ
Reporter organization: Air Carrier
Reporter function: First Officer; Pilot Flying
Reporter qualification: Flight Crew Air Transport Pilot (ATP); Flight Crew Instrument; Flight Crew Multiengine
Human factors: Human-Machine Interface; Situational Awareness; Time Pressure; Troubleshooting
Anomaly: Inflight Event / Encounter CFTT / CFIT
Detector: Automation Air Traffic Control; Person Air Traffic Control
When detected: In-flight
Result: Air Traffic Control Issued Advisory / Alert; Flight Crew Became Reoriented
Contributing factors: Human Factors
Primary problem: Human Factors

Narrative: When we were cleared for the visual approach; we did a 3 NM runway extension; while descending on the base turn; ATC informed us of a low altitude alert. We leveled off momentarily to maintain altitude; we were configured properly and stable by 500 ft.; we continued our approach based on the path/angle provided by the PAPI and landed.Poor descent planning while on the visual approach.This low altitude situation could have been prevented if we extended our downwind 1-3 NM more while maintaining our altitude/pattern altitude.




Synopsis: Air Carrier First Officer reported a Terrain Warning issued by the Tower Controller while preparing for a visual approach. The FO stated the cause was poor descent planning and not following SOP's for the type of approach.
Date: 201703
Local time of day: 0601-1200
Location: ZLA.ARTCC, CA
Light: Dawn
Aircraft: Small Transport
Operator: Air Taxi
Operating under: Part 135
Flight plan: IFR
Mission: Passenger
Flight phase: Cruise
Airspace: Class A ZLA
ATC / advisory: Center ZLA
Reporter organization: Government
Reporter function: Enroute
Reporter qualification: Air Traffic Control Fully Certified
Anomaly: ATC Issue All Types; Deviation / Discrepancy - Procedural Clearance; Deviation / Discrepancy - Procedural Published Material / Policy
Detector: Person Air Traffic Control
When detected: In-flight
Result: Air Traffic Control Issued New Clearance
Contributing factors: Chart Or Publication; Procedure
Primary problem: Procedure

Narrative: OAPM (Optimization of Airspace and Procedures in the Metroplex) RNAV aircraft landing SBA are not receiving correct routing. Aircraft X had ZZZ-OCN-V208-VTU-KWANG-SBA. Needed PADRZ1-PADRZ-SXC-WEEZL-KWANG-SBA.


Second narrative: NEW OAPM PROCEDURES. INTERIM LINE SHOULD BE 15000 FEET; NOT 14000 FEET. SAN M;P; Q CATEGORY AIRCRAFT 140 SHOULD BE TURNED 'OFF' FOREVER AND  DELETED.


Synopsis: ZLA Center Controller working airspace with new OAPM arrival and departure procedures reported an aircraft received by him had incorrect routings.