Piper PA-34-200T accident near Bullfrog Basin, Utah, April 13, 2006
On April 13, 2006 at about 3:30 pm local time, a Piper PA-34-200T, registered N2227W, was substantially damaged in an accident near Bullfrog Basin, Utah (Bullfrog Basin Airport). It was a personal flight under general aviation rules (Part 91). No one was hurt; 4 people were on board or involved. The weather was visual conditions (good weather).
Preview. This page is not yet listed for search engines.
The NTSB's probable cause their words, unchanged
A high airspeed at touchdown resulting in a high ground speed during the landing roll. Downhill sloping runway, a tailwind, the pilot's delayed remedial action and rough terrain off the end of the runway were factors.
Source: NTSB aviation accident database, copy made October 4, 2026. Docket and reports at the NTSB.
What the record shows
- Date
- April 13, 2006 · about 3:30 pm local time
- Place
- Bullfrog Basin, Utah · Bullfrog Basin Airport · map
- Type
- Accident
- Injuries
- No one was hurt; 4 people were on board or involved.
- Weather
- visual conditions (good weather)
- Aircraft
- Piper PA-34-200T · all PA-34-200Ts on the register
- Registration
- N2227W · registry record · serial 34-7970171
- Damage
- Substantial damage
- Flight
- Personal flight · general aviation rules (Part 91)
The NTSB's narrative final · quoted from the NTSB record
The pilot reported that due to traffic on the runway, he circled around until the traffic was clear of the runway. The pilot then set-up for a landing on runway 01, but had to go-around for the first attempt as "...the runway was disappearing too fast..." During the second attempt, the pilot set-up for a short field landing and the aircraft touched down at the beginning of the 3,500 foot long down sloping runway. During the landing roll, the pilot realized that the ground speed was too fast and the aircraft was not going to stop in time. The pilot stated that there was not enough runway left for another go-around, so the aircraft ran off the end of the runway. After the accident, the pilot noted that the wind had shifted and that he landed with a tailwind. An FAA Inspector reported that the aircraft traveled over the rough terrain directly off the end of the runway for about 200 feet before coming to rest. The main landing gear tires were blown, the right main landing gear collapsed and the upper wing surfaces were buckled.
The complete narrative as the NTSB published it. The NTSB's docket holds the report as a PDF and any photographs, statements and other documents from the investigation.
The factual record from the NTSB's investigation tables, in plain English
Pilot
- Certificate: private
- Ratings: multi-engine land
- Flight time: 3,300 hours in all; 3,200 in this make and model
- Last flight review: April 1, 2006
- Medical certificate: Class 3
- Seat: left
- Injury: no injuries
The aircraft
- Airframe total time: 3,843 hours
- Last inspection: annual inspection, April 1, 2005; 64 hours since
- Maximum gross weight: 4,600 lb
- Seats: 6
- Landing gear: retractable
- Engine: Continental TSIO-360 (piston); 0 hours total
The flight
- Departed from: U42 Salt Lake City UT at 3:10 pm
- Destination: U07 Bullfrog Basin UT
- Flight plan: none
- Runway 1, 3,500 ft by 40 ft
Weather at the time
- Light: daylight
- Visibility: 10 statute miles
- Sky: clear
- Temperature: 61°F (16°C), dew point 14°F (-10°C)
- Altimeter: 30.22 inHg
- Observation at 2:56 pm from PGA, 52 miles away
Injuries
| Fatal | Serious | Minor | None | |
|---|---|---|---|---|
| Crew | 1 | |||
| Passengers | 3 |
About this page
Everything above comes from the NTSB's public accident database: the narrative, probable cause and findings are the NTSB's own words, and the coded tables behind its report (pilot, aircraft, flight, weather, injuries, sequence of events) are written out in plain English. Pilots' ages, home towns and medical details are left out on purpose. The docket at the NTSB holds the report as a PDF and the investigation's photographs and documents. This site never names pilots, passengers or anyone else involved. A preliminary report describes what is known soon after the event and can change; the final report, with the probable cause, usually follows one to two years later and this page is refreshed when it does. Case number SEA06LA075.