FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

WPR10LA393 · Piper PA18A

10 Aug 2010 · Billings, MT, United States

Piper PA18A · Accident: loss of control in flight during landing

From Laurel Municipal Airport (6S8) to Billings Logan International Airport (BIL)

Report a problem

Event

NTSB case
WPR10LA393
Event typeAccident: someone killed or seriously injured, or the aircraft substantially damaged (NTSB definition). Incident: an occurrence that affected or could have affected safety, short of that. Glossary
Accident
InvestigationHow far the investigation had got when the record was published: preliminary, ongoing, final or completed. Unknown where the source does not say. Glossary
Completed
API-reported fatalities
0 · all aircraft and ground
Ground fatalities
Unknown
OperationWhat kind of flying it was, grouped by the rules it flew under: airline (US Part 121), air taxi and commuter (Part 135), general aviation (Part 91 and similar), military or government. Glossary
General aviation
WeatherVisual meteorological conditions (VMC): good enough to fly by looking outside. Instrument conditions (IMC): cloud or low visibility, flying by instruments. Glossary
Visual Meteorological Cond

Piper PA18A

Aircraft type
Piper PA18
Category
Airplane
RegistrationThe aircraft's tail number, such as N12345 or G-ABCD. Registrations are reissued, so the same one years apart can be a different aircraft. Glossary
N2660A
Operator
Unknown
Onboard fatalities
Unknown
Route
From Laurel Municipal Airport (6S8), Laurel, MTTo Billings Logan International Airport (BIL), Billings, MT
Aircraft age
Not recorded
Flight rulesThe regulations the flight operated under: in the US, Part 91 (general aviation), Part 121 (airlines), Part 135 (air taxi and commuter) and others; for flights abroad, the NTSB's coarser commercial or non-commercial code. Glossary
Part 91: General Aviation
Phase of flightThe stage of the flight when things started to go wrong: standing, taxi, takeoff, initial climb, en route, maneuvering, approach or landing. Glossary
Landing
Defining eventThe single coded event the NTSB judges best describes what happened (records from 2008 on). Older records name the first occurrence in the sequence instead. Glossary
Loss of control in flight
DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
Substantial

Cause areas

  • Aircraft › Aircraft oper/perf/capability
  • Environmental issues › Conditions/weather/phenomena
  • Personnel issues › Task performance

Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.

NTSB narrative

As the airplane approached the airport, the pilot was given clearance to land on runway 28L. The pilot reported that he also heard the tower controller tell an inbound helicopter to follow him. Review of a recording of the tower communications revealed that the controller actually instructed the helicopter to pass behind the airplane and cleared the helicopter to land on taxiway H in the opposite direction of the airplane. (Taxiway H was south of and parallel to runway 28L with a taxiway centerline to runway centerline distance of about 200 feet.) About 1 1/2 minutes later, the tower controller told the airplane pilot that there was a helicopter on his left side and that it would be landing on the taxiway adjacent to the runway. The airplane pilot did not acknowledge the transmission.

The airplane pilot said that he was planning to fly the airplane low over the runway and land long to expedite his ground taxi. As the airplane pilot flew low over the approach end of the runway, he was surprised to see the helicopter flying towards him. He thought it was flying over the edge of his runway and that its rotor wash would impact his airplane. However, radar data from an antenna located on the airport indicated that the two aircraft were horizontally separated by about 300 feet when they passed each other at a point about 885 feet from the approach end of the runway. Additionally, the helicopter pilot reported that his landing on taxiway H was accomplished about 300 feet from the airplane.

The airplane pilot stated that just as he was passing the helicopter, his left wing tip was violently slammed down. The airplane veered right about 30 to 40 degrees, stalled, and impacted the ground. A witness observed the airplane's left wing strike the runway before the airplane veered right off the runway and over the grass. Airport operations personnel located a yellow paint transfer mark on the runway surface about 1,616 feet from the approach end of the runway. The location and paint color of the transfer mark were consistent with the airplane's left wing tip impacting the runway when the airplane's fuselage was over the runway's right edge. Radar data indicated that, at the time the airplane produced the mark, the helicopter was more than 1,350 feet away.

At the time, the airplane was landing with a direct crosswind of about 6 knots from the left.

The FAA Aeronautical Information Manual states that "Pilots of small aircraft should avoid operating within three rotor diameters of any helicopter in a slow hover taxi or stationary hover." Since this helicopter's main rotor disc diameter was about 33.5 feet, the recommended distance to maintain from small airplanes in order to prevent downwash encounters was about 100 feet. Additionally, a representative from the helicopter manufacturer's safety department said that a helicopter descending during air taxiing and with a forward speed of about 58 mph, the helicopter's ground speed when it passed the airplane, would produce significantly less downwash relative to what it would produce when static hovering or hover taxiing.

Probable cause

The pilot's inadequate compensation for the wind conditions and failure to maintain lateral and directional control of the airplane during landing.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record WPR10LA393
Event ID
20100810X20446
Case number
WPR10LA393
Dataset
full-current
Source SHA-256
5cf380f0061817c0331a6b2d8cc7e0ee3a79bea469a1001dc5c10e56f35f5ab3
Source notes (4)
  • Unreviewed is an editorial label, not an investigation status. API-sourced is not report-checked or human-reviewed. Explicit event totals are used without summing aircraft injury tables; onboard allocation is withheld. Unknown values remain unknown. The operation category is mapped from the NTSB-reported FAR part and has not been reviewed.
  • Filled from the NTSB case API where the bulk record had no value: investigation status. Values present in the bulk record are kept.
  • The date is the local date, which is the same as the UTC date the NTSB stores.
  • API snapshot SHA-256: 203e00c410602ffd95147502ca8f605e35a72d02781d7126055b4f1f174c159d; retrieved 2026-09-15T14:49:13.124Z.