Amateur-built Starduster II accident near Junction City, Kansas, April 14, 2006
On April 14, 2006, a amateur-built Starduster II, registered N7JC, was substantially damaged in an accident near Junction City, Kansas (Junction City Airport). It was a personal flight under general aviation rules (Part 91). No one was hurt; 1 person was on board or involved. The weather was visual conditions (good weather).
The NTSB's probable cause their words, unchanged
Vapor lock which resulted in total engine failure and the pilot's abrupt brake application on touchdown. Factors contributing to the accident were the improper design of the fuel system resulting in the misrouting of the fuel lines close to the exhaust pipes, and the short landing area.
Source: NTSB aviation accident database, copy made October 5, 2026. Docket and reports at the NTSB.
What the record shows
- Date
- April 14, 2006
- Place
- Junction City, Kansas · Junction City Airport · map
- Type
- Accident
- Injuries
- No one was hurt; 1 person was on board or involved.
- Weather
- visual conditions (good weather)
- Aircraft
- Amateur-built Starduster II
- Registration
- N7JC · registry record · serial 743
- Damage
- Substantial damage
- Flight
- Personal flight · general aviation rules (Part 91)
The NTSB's narrative final · quoted from the NTSB record
The pilot reported making a normal takeoff and climb out. At about 200 feet above the ground, the pilot said the engine lost power without any prior warning. The pilot immediately executed a forced landing. On touchdown, the pilot applied "hard brakes" to avoid a ravine at the end of the grass strip. The airplane subsequently nosed over on its back causing substantial damage to the top wing, vertical stabilizer, and rudder. An examination of the engine showed that the fuel lines had been routed within 1-1/4 inches of the dual exhaust pipes. FAA requirements for certified airplanes requires a minimum of 6 inches separation due to the potential for fuel in the lines to boil and subsequently cause a vapor lock in the lines. No other anomalies were found.
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; single-engine land; instrument: airplane
- Flight time: 3,770 hours in all; 31 in this make and model; 30 in the last 90 days; 15 in the last 30 days; 3,700 as pilot in command
- Last flight review: January 1, 2005
- Medical certificate: Class 3 (with waivers/limitations)
- Seat: sngl
- Injury: no injuries
The aircraft
- Airframe total time: 345 hours
- Last inspection: condition inspection, April 1, 2005
- Maximum gross weight: 1,610 lb
- Seats: 2
- Landing gear: fixed
- Engine: Franklin 6A-350-C1-C1A (piston); 0 hours total
The flight
- Departed from: 3JC Junction City KS
- Destination: 8KS8 Chapman KS
- Flight plan: none
- Runway 5, 1,927 ft by 200 ft
Weather at the time
- Light: dusk
- Visibility: 10 statute miles
- Sky: clear
- Temperature: 84°F (29°C), dew point 50°F (10°C)
- Altimeter: 29.79 inHg
Injuries
| Fatal | Serious | Minor | None | |
|---|---|---|---|---|
| Crew | 1 |
Documents from the investigation the NTSB's docket: the evidence folder behind the report
The docket, the folder of records gathered during an investigation (maintenance records, photographs, witness statements, examinations), has not been read from the NTSB for this case yet; the list appears here once it has. Open the docket at the NTSB.
Everything on this page comes from the NTSB's public records. The narrative, probable cause and findings are the NTSB's own words; the coded tables behind the report are written out in plain English, with pilots' ages, home towns and medical details left out. The documents and photographs are the NTSB's docket, shown as the NTSB released them. This site's own text never names anyone involved. A preliminary report can change; the final report usually follows one to two years later, and the page is refreshed when it does.