# NTSB WPR10LA393: Piper PA18A, N2660A, Billings, MT, August 10, 2010

- Type: NTSB accident investigation
- Classification: Accident · Minor injuries · Limited investigation · Final report
- Date: August 10, 2010, 08:18 local (14:18 UTC)
- Place: Billings, MT
- Coordinates: 45.807498, -108.553886
- Nearby events: https://openairdocs.org/map.md?lat=45.8075&lon=-108.5539&mi=10
- Phase of flight: [Landing](https://openairdocs.org/ntsb-phases/550) (OpenAirDocs' grouping)
- Defining event: [Landing: Loss of control in flight](https://openairdocs.org/ntsb-events/240)
- Highest injury: Minor injuries
- Injuries: 2 minor
- Status: Completed, report July 21, 2011
- Report: Approved by Office Director
- NTSB office: Western Pacific Region
- Parties: FAA FSDO
- NTSB case key (mKey): 76921
- NTSB case page: https://web.ntsb.gov/investigations/?ntsbnumber=WPR10LA393
- NTSB report (PDF, downloads): https://data.ntsb.gov/carol-repgen/api/Aviation/ReportMain/GenerateNewestReport/76921/pdf
- NTSB docket: https://data.ntsb.gov/Docket?ProjectID=76921
- Page: https://openairdocs.org/ntsb/WPR10LA393

## Probable cause

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

## Findings

NTSB's coded findings; those marked are part of the probable cause.

- [Performance/control parameters: directional control](https://openairdocs.org/ntsb-findings/01062020): Aircraft › Aircraft oper/perf/capability · Not attained/maintained (probable cause); cases with it: [Piper PA-18A, 6 cases](https://openairdocs.org/ntsb-findings/01062020/cases.md?model=7101804), [All aircraft, 3,958 cases](https://openairdocs.org/ntsb-findings/01062020/cases.md)
- [Wind: crosswind](https://openairdocs.org/ntsb-findings/03034040): Environmental issues › Conditions/weather/phenomena · Contributed to outcome (probable cause); cases with it: [Piper PA-18A, 1 case](https://openairdocs.org/ntsb-findings/03034040/cases.md?model=7101804), [All aircraft, 1,008 cases](https://openairdocs.org/ntsb-findings/03034040/cases.md)
- [Wind: crosswind](https://openairdocs.org/ntsb-findings/03034040): Environmental issues › Conditions/weather/phenomena · Response/compensation (probable cause); cases with it: [Piper PA-18A, 1 case](https://openairdocs.org/ntsb-findings/03034040/cases.md?model=7101804), [All aircraft, 1,008 cases](https://openairdocs.org/ntsb-findings/03034040/cases.md)
- [Use of equip/info: aircraft control](https://openairdocs.org/ntsb-findings/02063040): Personnel issues › Task performance · Pilot (probable cause); cases with it: [Piper PA-18A, 13 cases](https://openairdocs.org/ntsb-findings/02063040/cases.md?model=7101804), [All aircraft, 9,295 cases](https://openairdocs.org/ntsb-findings/02063040/cases.md)
- [Performance/control parameters: lateral/bank control](https://openairdocs.org/ntsb-findings/01062023): Aircraft › Aircraft oper/perf/capability · Not attained/maintained (probable cause); cases with it: [Piper PA-18A, 1 case](https://openairdocs.org/ntsb-findings/01062023/cases.md?model=7101804), [All aircraft, 390 cases](https://openairdocs.org/ntsb-findings/01062023/cases.md)

## Sequence of events

The events NTSB coded, in order, by phase of flight. The defining event best describes what happened.

- [Landing: Loss of control in flight](https://openairdocs.org/ntsb-events/240) (defining event); cases with it: [Piper PA-18A, 6 cases](https://openairdocs.org/ntsb-events/240/sequence.md?model=7101804), [All aircraft, 5,002 cases](https://openairdocs.org/ntsb-events/240/sequence.md)
- [Uncontrolled descent: Collision with terr/obj (non-CFIT) ](https://openairdocs.org/ntsb-events/470); cases with it: [Piper PA-18A, 10 cases](https://openairdocs.org/ntsb-events/470/sequence.md?model=7101804), [All aircraft, 10,189 cases](https://openairdocs.org/ntsb-events/470/sequence.md)

## Analysis

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, wouldproduce significantly less downwash relative to what it would produce when static hovering or hover taxiing.

## Factual narrative

On August 10, 2010, about 0818 mountain daylight time, a Piper PA18A, N2660A, was substantially damaged during impact with terrain subsequent to a loss of aircraft control during landing at Billings Logan International Airport (BIL), Billings, Montana. The private pilot and his passenger received minor injuries. The airplane was being operated by 172 LLC of Park City, Montana, under the provisions of 14 Code of Federal Regulations Part 91. Visual meteorological conditions prevailed for the personal cross-country flight, which had departed from Laurel, Montana, approximately 15 minutes before the accident. A flight plan had not been filed. According to the pilot, BIL tower cleared him to land on runway 28L. The pilot reported hearing BIL tower tell an inbound helicopter to "follow the cub," and he heard the helicopter pilot respond "traffic in sight." The pilot said he was planning to fly low down the runway in order to exit at the runway 25 intersection. The pilot said that "just as I was touching down, I saw the helicopter flying towards me. He was on the left edge of the runway, definitely not over the [parallel] taxiway." The pilot stated that, just as he was passing the helicopter, his left wing tip was "violently slammed down." He further stated that he had the flaps fully extended, which "magnified the effect of the rotor wash." He further stated that he must have added power to try and correct the problem because the airplane "broke right and hit more turbulence and at that time went out of control to the right." Next, he remembers seeing the ground rushing towards him as the airplane "slammed" into the ground at an extremely steep angle. The passenger in the airplane, who was a student pilot, said he was wearing a headset and was on intercom with the pilot. He said that as the airplane approached runway 28L for landing, the pilot lined up left of the runway centerline for landing. As the airplane passed over the end of the runway, he saw the helicopter for the first time. He thought it was over the accident airplane's left wing. The passenger said that next the airplane's left wing dipped hard, but did not touch the runway; he said it just missed the ground. He said the accident airplane "jumped" up to about 15 feet above ground level (agl) "as if rotor wash lifted it up." Next, the left wing rose up and the airplane veered to the right. Moments later, the airplane dropped steeply down with its left wing low impacting the ground with its wing tip and nose simultaneously. A witness, located at the approach end of runway 28L, observed the accident airplane flare over the approach end of the runway and proceed to fly down the runway at 10 to 15 feet above ground level (agl). He said the airplane did not touch down. The witness observed a helicopter flying in the opposite direction over taxiway Hotel, which was parallel to and south of runway 28L. At about the midpoint of runway 28L, the helicopter, which had been descending, leveled outabout 10 to 15 feet agl and continued to fly east along the taxiway. The witness stated that shortly after the two aircraft passed each other the airplane made an abrupt hard left roll, with its left wing tip striking the runway. He said the airplane appeared to recover and remain in the air without his tires touching the ground. Immediately the airplane veered right and appeared to be trying to gain altitude. During this time, the airplane was rocking back and forth. A few seconds later, it appeared to stall, roll left, and strike the ground from about 20 feet agl. From what the witness could see, it appeared that the left wing and propeller spinner hit the ground simultaneously. The airplane then cartwheeled to the right wing before the tail settled to the ground. The airplane came to rest upright heading about 180 degrees from the direction that it was headed in after the initial wing strike on the runway. The helicopter pilot said the tower controller cleared him to land on taxiway Hotel and hover taxi to parking. He was established heading eastbound over taxiway Hotel at about 100 feet agl when he observed an airplane westbound on runway 28L. He continued his descent to taxiway Hotel and then hover taxied to parking. The helicopter pilot stated that "at no time did the helicopter ever hover over or around the [airplane]" and that the helicopter's "landing to a hover was accomplished approximately 300 feet from the [airplane]." The mechanic who was a passenger in the helicopter stated that they executed a right turn over the west corner of runway 10R and descended over taxiway Hotel. He stated that the helicopter "never overflew any aircraft." Review of a recording of BIL radio communications indicated that, as the helicopter approached the airport, the tower controller told the pilot of the helicopter to "pass behind [the airplane], you are cleared to land Hotel taxiway, taxi to parking." The review of the recording also indicated that when the airplane was about to turn onto final approach for runway 28L, the BIL tower controller told the pilot of the airplane that "off your left you'll see a helicopter, he'll be landing [on] Hotel taxiway." There was no acknowledgment of this transmission from the pilot of the airplane. BIL has an Airport Surveillance Radar (ASR) site located on airport property at the north end of closed runway 18/36. The ASR recorded the positions of the two aircraft about once every 4.8 seconds. The recorded data depicted the airplane landing to the west on runway 28L and the helicopter landing to the east on taxiway Hotel. The radar tracks of the two aircraft were parallel with a lateral separation of about 300 feet. The radar data indicated the two aircraft passed one another about 885 feet from the approach end of runway 28R. At the time they passed one another, the helicopter's ground speed was about 58 mph, and the airplane's ground speed was about 50 mph. Additionally, the radar data shows that at the time of thelast radar hit from the airplane, the helicopter was more than 1,350 feet from the airplane. BIL operations personnel photographed the scene after the accident. These photographs show a yellow paint transfer on the runway surface, which appears to match the color of the accident airplane, located at 45:48:25.33 north and 108:33:17.42 west, or about 1,616 feet from the threshold of runway 28L and about 18 feet from the runway's right side edge. As determined from the radar data, the transfer mark was located 731 feet beyond the passing point of the two aircraft and about 170 feet beyond the airplane's last radar hit. The airplane's wingspan was 35 feet 2 inches. To produce the paint transfer with its left wing, the airplane's fuselage would have been over the right edge of the runway. The main wreckage was located at 45:48:27.21 north and 108:33:19.17 west, or about 1,808 feet from the threshold of runway 28L and about 111 feet north of the runway's edge. The main landing gear collapsed, the fuselage was twisted, and the engine was displaced aft, damaging the firewall and the instrument panel. Additionally, the bottom of the rudder and the right elevator were bent and wrinkled. The helicopter that was landing on taxiway Hotel was a Eurocopter Deutschland GMBH EC135P1. Its main rotor disc measured 33.46 feet in diameter. The Federal Aviation Administration's 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." In this case, that would be 101 feet for the EC135P1. 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. At 0826, the reported weather conditions at BIL were: wind 190 degrees at 6 knots; visibility 10 statute miles; cloud condition, clear; temperature 61 degrees Fahrenheit; dew point 55 degrees Fahrenheit; altimeter setting 29.95 inches of mercury. This weather report indicated a direct left crosswind for landing on runway 28L at BIL. Runway 10R/28L is 3,801 feet long and 75 feet wide; it is paralleled on its south side by taxiway H, which is 44 feet wide. Measurements from aerial photographs indicate that the distance from the centerline of the runway and the centerline of the taxiway is 200 feet.

## Aircraft

- Registration: [N2660A](https://openairdocs.org/aircraft/N2660A), registered now, S/N 18-2184, built 1952 (OpenAirDocs)
- Reported make and model: PIPER PA18A
- Registry model: [Piper PA-18A](https://openairdocs.org/model/piper-pa-18a) (registry code 7101804) (OpenAirDocs)
- Registry engine: [Lycoming 0-320 series](https://openairdocs.org/engine/lycoming-0-320-series) (registry code 41508, reciprocating) (OpenAirDocs)
- Category: Airplane
- Serial number: 18-2184
- Airframe hours: 2850
- Engines: Lycoming O-320-A2B 160 horsepower reciprocating
- Damage: Substantial damage
- Flight: Personal, Part 91
- Airworthiness certificate: Standard, Normal
- Last inspection: Annual, June 16, 2010
- Departed: 6S8, Laurel, MT
- Destination: BIL, Billings, MT
- Airport: BIL, Billings Logan International, runway 28L, 3,801 × 75 ft, asphalt

## Flight crew

As NTSB recorded them. NTSB leaves out names.

- Pilot; age 52; injuries: minor; private; airplane ratings: single-engine land; medical: class 3, with waivers/limitations; last flight review May 8, 2009; seat: front; flight hours: 754 total, 206 in this make and model, 34 in the last 90 days, 34 in the last 30 days, 1 in the last 24 hours

## Weather

- Conditions: Visual (VMC), Day
- Wind: 190° at 6 knots
- Visibility: 10 statute miles
- Lowest ceiling: none
- Temperature: 61 °F, dew point 55 °F
- Altimeter: 29.95 inHg
- Observed at: BIL

## FAA reports on this event (1)

The FAA's own accident and incident reports, matched to the aircraft by N-number and date (OpenAirDocs).

- [Accident 20100810041589A](https://openairdocs.org/incident/20100810041589A), Aug 10, 2010: Piper PA-18A, Billings, MT, Substantial damage. On August 10, 2010, at 0818 MDT, a Piper PA-18A, N2660A, registered to 172 LLC, during landing at the Billings Logan international airport (bil), went off…

## Docket (27 files)

The files NTSB released with the investigation on June 8, 2011, on NTSB's docket system: https://data.ntsb.gov/Docket?ProjectID=76921. 5.1 MB in all.

- Pilot/Operator Aircraft Accident Report, NTSB Form 6120.1 (item 1, .PDF, 415 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40348410&FileExtension=.PDF&FileName=Pilot%2FOperator%20Aircraft%20Accident%20Report,%20NTSB%20Form%206120.1-Redacted.PDF
- Record of Conversation - Passenger (item 2, .PDF, 59 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40348412&FileExtension=.PDF&FileName=Record%20of%20Conversation%20-%20Passenger-Master.PDF
- Record of Conversation - American Eurocopter (item 3, .PDF, 52 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40348418&FileExtension=.PDF&FileName=Record%20of%20Conversation%20-%20American%20Eurocopter-Master.PDF
- Witness Statement (item 4, .PDF, 178 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40348415&FileExtension=.PDF&FileName=Witness%20Statement-Redacted.PDF
- Transcript of Radio Communications (item 5, .PDF, 62 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40348416&FileExtension=.PDF&FileName=Transcript%20of%20Radio%20Communications-Master.PDF
- Statement of Thomas Kelly (item 6, .PDF, 130 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40348413&FileExtension=.PDF&FileName=Statement%20of%20Thomas%20Kelly-Redacted.PDF
- Statement of Michael Buckley (item 7, .PDF, 109 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40348414&FileExtension=.PDF&FileName=Statement%20of%20Michael%20Buckley-Redacted.PDF
- Incident/Accident Report (item 8, .PDF, 240 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40348423&FileExtension=.PDF&FileName=Incident%2FAccident%20Report%20-Master.PDF
- EC135 Dimensions (item 9, .PDF, 35 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40348419&FileExtension=.PDF&FileName=EC135%20Dimensions-Master.PDF
- EC135 Aircraft Registry Information (item 10, .PDF, 35 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40348421&FileExtension=.PDF&FileName=EC135%20Aircraft%20Registry%20Information-Master.PDF
- Piper PA-18 Information (item 11, .PDF, 109 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40348420&FileExtension=.PDF&FileName=Piper%20PA-18%20Information-Master.PDF
- Billings Airport Diagram (item 12, .PDF, 113 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40348411&FileExtension=.PDF&FileName=Billings%20Airport%20Diagram-Master.PDF
- BIL Operations (item 13, .PDF, 938 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40348425&FileExtension=.PDF&FileName=BIL%20Operations-Master.PDF
- Aerial Final (item 14, .PDF, 252 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40348426&FileExtension=.PDF&FileName=Aerial%20Final-Master.PDF
- Radar Overview (item 15, .PDF, 484 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40348427&FileExtension=.PDF&FileName=Radar%20Overview-Master.PDF
- Closer Radar Overview (item 16, .PDF, 339 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40348429&FileExtension=.PDF&FileName=Closer%20Radar%20Overview-Master.PDF
- Excerpt from FAA Aeronautical Information Manual (item 17, .PDF, 32 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40348417&FileExtension=.PDF&FileName=Excerpt%20from%20FAA%20Aeronautical%20Information%20Manual-Master.PDF
- FAA Advisory Circular AC No. 90-66A (item 18, .PDF, 309 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40348422&FileExtension=.PDF&FileName=FAA%20Advisory%20Circular%20AC%20No.%2090-66A-Redacted.PDF
- Image 1. Accident airplance facing east. (item 19, .PDF, 103 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40348398&FileExtension=.PDF&FileName=Image%201.%20Accident%20airplance%20facing%20east.-Master.PDF
- Image 2. Notice damage to left wing tip. (item 20, .PDF, 139 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40348399&FileExtension=.PDF&FileName=Image%202.%20Notice%20damage%20to%20left%20wing%20tip.-Master.PDF
- Image 3. Close up of engine and airframe damage. (item 21, .PDF, 135 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40348400&FileExtension=.PDF&FileName=Image%203.%20Close%20up%20of%20engine%20and%20airframe%20damage.-Master.PDF
- Image 4. Note, flaps full down. (item 22, .PDF, 157 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40348402&FileExtension=.PDF&FileName=Image%204.%20Note,%20flaps%20full%20down.-Master.PDF
- Image 5. Note large tundra tire. (item 23, .PDF, 130 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40348404&FileExtension=.PDF&FileName=Image%205.%20Note%20large%20tundra%20tire.-Master.PDF
- Image 6. Right side-top view of wreckage. (item 24, .PDF, 149 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40348405&FileExtension=.PDF&FileName=Image%206.%20Right%20side-top%20view%20of%20wreckage.-Master.PDF
- Image 7. Airplane's paint transfer, 1616 ft from runway threshold. (item 25, .PDF, 201 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40348406&FileExtension=.PDF&FileName=Image%207.%20Airplane%27s%20paint%20transfer,%201616%20ft%20from%20runway%20threshold.-Master.PDF
- Image 8. Paint transfer, note distance from centerline. (item 26, .PDF, 104 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40348407&FileExtension=.PDF&FileName=Image%208.%20Paint%20transfer,%20note%20distance%20from%20centerline.-Master.PDF
- Image 9. Billings runway looking east. (item 27, .PDF, 123 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40348408&FileExtension=.PDF&FileName=Image%209.%20Billings%20runway%20looking%20east.-Master.PDF

From the NTSB's public API. Aircraft are matched to registry aircraft by N-number and event date, checked against the reported serial number, make and model; the registry's history has gaps, so older matches can be wrong. Compare the reported make and model.

---
OpenAirDocs.org is an independent research project of [Contrail Labs](https://contraillabs.com/). It is not affiliated with the FAA or the NTSB. Source documents are U.S. government works in the public domain.