- Date
- November 1, 1996, 17:45 local (22:45 UTC)
- Place
- Brooksville, FL
- Injuries
- 1 uninjured
- Damage
- Substantial damage
- Phase of flight
- Approach
- Aircraft
- N81435Piper PA-28-161
- Weather
- Visual (VMC) · Day
- Status
- Completed · report March 31, 1998
- Report
- Approved by Office Director
- FAA report
- 19961101034749A
- Case key
- 3804
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 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 aircraft owner reported that the student pilot was conducting traffic pattern training when he experienced a total loss of engine power while on final approach. The student pilot reported that he completed the before landing check that included the application of carburetor heat. After he turned on to the final approach leg the student pilot noticed that the engine had quit. During the forced landing roll the airplane collided with two parked vehicles. The examination of the aircraft at the accident site failed to disclose a mechanical problem. A subsequent functional check of the engine disclosed that it operated normally throughout all power ranges. Weather conditions were favorable for the formation of carburetor ice.
Factual narrative
On November 1, 1996, at 1745 eastern standard time, a Piper PA-28-161, N81435, collided with two travel trailers in a secure lot east of the Hernando County Airport in Brooksville, Florida. The instructional flight operated under the provisions of Title 14 CFR Part 91 with no flight plan filed. Visual weather conditions prevailed at the time of the accident. The airplane sustained substantial damage, and the student pilot was not injured. The flight departed Brooksville, at 1730.
The aircraft owner reported that the student pilot was conducting traffic pattern training when he experienced a total loss of engine power while on final approach to runway 27. The student pilot reported that he completed the before landing check, that included the application of carburetor heat. After the student pilot turned on to the final approach leg, he noticed that the engine had quit. The student pilot selected an area near the airport and attempted a forced landing. During the forced landing roll out, the airplane collided with two parked vehicles.
The examination of the aircraft at the accident site failed to disclose a mechanical problem. A subsequent functional check of the engine disclosed that it operated normally throughout all power ranges. This check was repeated with the same results. A review of the weather data disclosed that conditions were favorable for the formation of carburetor icing.
Aircraft
- Registration
- N81435
- Reported as
- Piper PA-28-161
- Category
- Airplane
- Serial number
- 28-8016363
- Airframe hours
- 7,063
- Engine
- Lycoming O-360-D3G, 160 horsepower, reciprocating
- Damage
- Substantial damage
- Flight
- Instructional · Part 91
- Operator
- Donald G. Pearson
- Registered owner
- Aerotec Inc.,
- Airworthiness certificate
- Standard, Normal
- Last inspection
- Annual · July 1, 1996 · 100 hours before
- Departed
- BKV
- Airport
- BKV · Hernando County Airport, runway 27, 7,000 × 50 ft, concrete
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
- 33
- Certificate
- Student
- Medical
- Class 2, Valid Medical--no waivers/lim.
- Seat
- Left
- Flight hours
- 157 total · 3 in this make and model · 24 as pilot in command · 24 in the last 90 days · 10 in the last 30 days
Weather
- Conditions
- Visual (VMC) · Day
- Wind
- 280° at 5 knots
- Visibility
- 10 statute miles
- Lowest ceiling
- None
- Temperature
- 75 °F, dew point 70 °F
- Altimeter
- 29.00 inHg
- Observed at
- BKV, 1 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.