- Date
- October 2, 2001, 18:28 local (22:28 UTC)
- Place
- Elberon, VA
- Injuries
- 1 serious, 1 minor
- Damage
- Substantial damage
- Phase of flight
- Initial climb
- Aircraft
- N673KDClark T Bird II
- Weather
- Visual (VMC) · Day
- Status
- Completed · report May 1, 2003
- Report
- Approved by Office Director
- Parties
- FAA FSDO-21
- FAA report
- 20011002028589A
- Case key
- 53554
From the NTSB’s public API. By law, NTSB reports can’t be used as evidence in lawsuits over the accident.
On this page
Probable cause
A partial power loss for undetermined reasons.
Sequence of events
NTSB’s coding before 2008: each occurrence and phase of flight, and the causes and factors under it. The codes are defined in NTSB’s coding manual.
Analysis
The engine start, taxi, and run-up seemed normal. The pilot then tookoff on runway 09, a 1,800-foot long, 50-foot wide turf runway. About 50 feet above the ground, the engine lost partial power, and the pilot lowered the nose of the airplane. He then turned right to avoid tree stumps, and the airplane impacted in a soybean field, located off the right side of the runway. The pilot added that within the 60-day period prior to the accident, on two occasions, he had difficulty priming the engine. However, after each occurrence, the fittings and primer hose appeared normal. The airport manager examined the airplane after the accident. He observed that the primer hose, which connected the fuel primer to both carburetors, was loose. The manager could not be certain if it was loose before the impact, or if the impact loosened the hose. A Federal Aviation Administration inspector examined the engine. He was able to rotate the propeller by hand, and attain thumb compression on both cylinders. The inspector observed fuel in the fuel bowl, it appeared similar to automotive gasoline, and was absent of contamination. Due to safety concerns, the inspector did not attempt to check the spark plugs.
Factual narrative
On October 2, 2001, about 1828 eastern daylight time, a T Bird II amateur built airplane, N673KD, was substantially damaged during a forced landing after takeoff from a private airstrip near Elberon, Virginia. The certificated private pilot sustained minor injuries, and the passenger sustained serious injuries. Visual meteorological conditions prevailed, and no flight plan was filed for the local personal flight conducted under 14 CFR Part 91.
The pilot stated that the engine start, taxi, and run-up seemed normal. He tookoff on runway 09, a 1,800-foot long, 50-foot wide turf runway. About 50 feet above the ground, the engine lost partial power, and the pilot lowered the nose of the airplane. As the airplane descended, he then turned right to avoid tree stumps, and the airplane impacted in a soybean field, located off the right side of the runway. The pilot added that within the 60-day period prior to the accident, on two occasions, he "had trouble getting the primer bulb to prime." However, after each occurrence, the fittings and hose appeared normal.
The airport manager examined the airplane after the accident. He observed fuel leaking from the fuel tank onto the ground, and a strong fuel odor was present. Further examination by the manager revealed that the primer hose, which connected the fuel primer to both carburetors, was loose. The manager could not be certain if it was loose before the impact, or if the impact loosened the hose.
The airplane was equipped with a Rotax 582 engine. A Federal Aviation Administration inspector examined the engine. He was able to rotate the propeller by hand, and attain thumb compression on both cylinders. Although the fuel tank was empty when the inspector arrived at the scene, he did observe fuel in the fuel bowl. It appeared similar to automotive gasoline, and was absent of contamination. The inspector added that the fuselage was substantially damaged. Due to safety concerns, he did not attempt to check the spark plugs.
An excerpt from the manufacturer's make and model engine manual revealed:
"Danger! This engine, by its design, is subject to sudden stoppage! Engine stoppage can result in crash landings. Such crash landings can lead to serious bodily injury or death.
Never fly the aircraft equipped with this engine at locations, airspeeds, altitudes, or other circumstances from which a successful no-power landing cannot be made, after sudden engine stoppage.
Warning! Although these engine types have undergone considerable durability testing, this engine is not a certified aircraft engine. It has not received any individual safety or durability testing and conforms to no aircraft standards. It is for use in experimental and ultralight uncertified aircraft and vehicles only, in which an engine failure will not compromise safety.
User assumes all risk of use and acknowledges by his use the he knows this engine is subject to sudden stoppage."
Aircraft
- Registration
- N673KD
- Reported as
- Clark T Bird II
- Category
- Airplane, amateur-built
- Serial number
- 900110
- Airframe hours
- 49
- Engine
- Rotax 582, 66 horsepower, reciprocating
- Damage
- Substantial damage
- Flight
- Personal · Part 91
- Registered owner
- Richard B. Clark
- Airworthiness certificate
- Special, Experimental (Special)
- Last inspection
- Annual · May 16, 2001 · 49 hours before
- Departed
- NONE · Elberon, VA
- Airport
- NONE · Private, runway 090, 1,800 × 50 ft, grass/turf
Matched to the registry by N-number and the event date; the registry’s history has gaps, so older matches can be wrong. Compare the reported make and model.
Flight crew
As NTSB recorded them. NTSB leaves out names.
- Role
- Pilot
- Age
- 51
- Injuries
- Minor
- Certificate
- Private
- Airplane ratings
- Single-engine land
- Instrument ratings
- Airplane
- Medical
- Class 3, Valid Medical--w/ waivers/lim
- Last flight review
- April 26, 2000
- Seat
- Left
- Flight hours
- 509 total · 49 in this make and model · 509 as pilot in command
Weather
- Conditions
- Visual (VMC) · Day
- Wind
- Calm
- Visibility
- 10 statute miles
- Lowest ceiling
- None
- Temperature
- 66 °F, dew point 57 °F
- Altimeter
- 30.03 inHg
- Observed at
- PHF, 12 nm away
FAA reports on this event · 1
The FAA’s own accident and incident reports, matched to the aircraft by N-number and date.