Flight and Engine Failure
After departure, the flight was unable to establish two-way communication with Daytona Beach Approach Control, and the decision was made to return to the airport. While turning onto the base leg of the traffic pattern, the engine failed to respond to throttle inputs. The pilot attempted to restore engine power but was unsuccessful. Subsequently turning onto final approach, the pilot executed a forced landing in trees approximately 0.6 nautical mile from the runway.
Postaccident Examination
Examination of the carburetor disclosed that the inlet fitting had been pulled from the throttle body assembly. When tested postaccident, fuel leakage was observed from the throat of the carburetor. The engine was started and operated at low power settings only, as it had sustained damage during the forced landing. Following the engine run, bench testing and teardown of the carburetor revealed no malfunctions or discrepancies.
Previous Maintenance History
The carburetor had been repaired and installed on March 17, 2000. Since that repair, the airplane had accumulated 13.6 hours of flight time. During a flight from Oklahoma to Florida, while stopped for refueling, fuel leakage from the throat of the carburetor was noted. A mechanic informed the pilot that a stuck float might have caused the leakage and that the airplane was safe to fly; no maintenance was performed on the carburetor at that time. No further carburetor-related discrepancies were reported during the remainder of the flights to Florida.