DFW07CA161

NTSB accident investigation · Rodgers Zodiac 601XL · Levelland, TX · July 14, 2007

Accident · No injuriesData collectionFinal report
Date
July 14, 2007, 13:18 local (18:18 UTC)
Place
Levelland, TX
Injuries
1 uninjured
Damage
Substantial damage
Phase of flight
Initial climb
Aircraft
N4589Rodgers Zodiac 601XL
Weather
Visual (VMC) · Day
Status
Completed · report October 31, 2007
Report
Approved by Office Director
Parties
Lubbock, Texas
FAA report
20070714012569A
Case key
66242

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

The loss of engine power for undermined reasons. A contributing factor was the lack of suitable terrain for the forced landing.

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.

Loss of engine powerTakeoff - initial climb
Reason for occurrence undeterminedCause
Forced landingEmergency landing after takeoff
In flight collision with terrain/waterEmergency landing
Airspeed - not maintainedPilot in command
Terrain condition - ground
Terrain condition - none suitableFactor

Analysis

The 287-hour private pilot reported that the homebuilt airplane experienced a loss of engine power during initial takeoff climb. The airplane impacted the ground while the pilot attempted to return to the airport. The airplane impacted the ground in a nose low attitude and came to rest in the upright position in an open field within 50 yards of the runway. The Federal Aviation Administration inspector, who responded to the accident site, was able to interview the pilot at the scene of the accident. The pilot reported that the airport perimeter fence limited the possibility of proceeding straight ahead for a forced landing. The pilot added that a turn was needed to maneuver the airplane to a suitable landing area. The inspector documented structural damage to all portions of the airplane forward of the cockpit, confirmed the availability of full fuel on board, and did not note any obvious discrepancies. In a telephone interview with the NTSB Investigator-in-Charge (IIC), the pilot stated that during the emergency turn back to the airport, he allowed the airplane to slow below minimum flying speed, and due to close proximity to the ground, was not able to successfully recover the aircraft prior to impacting the terrain. The pilot, who was also the builder of the airplane, was not able to determine the reason for the engine's occasional loss of power. The pilot, who was also a mechanic, performed an inspection on the engine and could find a reason for the loss of engine power. The pilot added that he thought the engine malfunction was the result of a carburetor related problem. The airframe and engine had accumulated a total of 175 hours.

Factual narrative

The 287-hour private pilot reported that the homebuilt airplane experienced a loss of engine power during initial takeoff climb. The airplane impacted the ground while the pilot attempted to return to the airport. The airplane impacted the ground in a nose low attitude and came to rest in the upright position in an open field within 50 yards of the runway. The Federal Aviation Administration inspector, who responded to the accident site, was able to interview the pilot at the scene of the accident. The pilot reported that the airport perimeter fence limited the possibility of proceeding straight ahead for a forced landing. The pilot added that a turn was needed to maneuver the airplane to a suitable landing area. The inspector documented structural damage to all portions of the airplane forward of the cockpit, confirmed the availability of full fuel on board, and did not note any obvious discrepancies.

In a telephone interview with the NTSB Investigator-in-Charge (IIC), the pilot stated that during the emergency turn back to the airport, he allowed the airplane to slow below minimum flying speed and, due to close proximity to the ground, was not able to successfully recover the aircraft prior to impacting the terrain. The pilot, who was also the builder of the airplane, was not able to determine the reason for the engine's occasional loss of power. The pilot, who was also a mechanic, performed an inspection on the engine and could find a reason for the loss of engine power. The pilot added that he thought the engine malfunction was the result of a carburetor related problem. The airframe and engine had accumulated a total of 175 hours.

An automated weather reported station at the Lubbock Preston Smith Airport (KLBB), 32 nautical miles south-east of the accident site, reported at 1253 winds from 060 degrees at 3 knots, visibility 10 statute miles, scattered clouds at 5,000 feet, temperature 83 degrees Fahrenheit, dew point 57 degrees Fahrenheit, and barometric pressure of 30.12 inches of Mercury.

Aircraft

Registration
N4589
Reported as
Rodgers Zodiac 601XL
Category
Airplane, amateur-built
Serial number
65607
Airframe hours
175
Engine
Jabiru 3300, 110 horsepower, reciprocating
Damage
Substantial damage
Flight
Personal · Part 91
Registered owner
Bobby Rodgers
Airworthiness certificate
Special, Experimental (Special)
Last inspection
Annual · July 1, 2004
Departed
LLN · Levelland, TX
Destination
Levelland, TX
Airport
LLN · Levelland Muni, runway 35, 6,110 × 75 ft, asphalt

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
56
Injuries
None
Certificate
Private
Airplane ratings
Single-engine land
Medical
Class 3, With waivers/limitations
Last flight review
August 1, 2006
Seat
Left
Flight hours
287 total · 150 in this make and model · 186 as pilot in command · 10 in the last 90 days · 2 in the last 30 days

Weather

Conditions
Visual (VMC) · Day
Wind
60° at 3 knots
Visibility
10 statute miles
Lowest ceiling
None
Temperature
82 °F, dew point 57 °F
Altimeter
30.12 inHg
Observed at
KLBB, 28 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.