- Date
- December 21, 2005, 09:53 local (14:53 UTC)
- Place
- Chaplin, CT
- Injuries
- 1 serious
- Damage
- Substantial damage
- Phase of flight
- Approach
- Aircraft
- N7631RBeech 23
- Weather
- Visual (VMC) · Day
- Status
- Completed · report February 26, 2007
- Report
- Approved by Office Director
- Parties
- FAA
- FAA report
- 20051221030659A
- Case key
- 62967
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 complete loss of engine power due to carburetor ice. A contributing factor was the lack of suitable terrain for the emergency 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.
Analysis
The pilot stated that while on approach to Windham Airport, the engine began to run roughly, then completely lost power. He switched fuel tanks, and attempted an engine restart, but was unsuccessful. The pilot then maneuvered the airplane toward a snow-covered field, but could not clear trees during the final approach. After the accident, evidence of fuel was found at the scene. Fuel was plumbed to the engine through the left fuel tank, and the engine was started, and ran continuously on the airframe without interruption. The temperature was 19 degrees Fahrenheit and the dew point was 13 degrees Fahrenheit. Interpolation of a carburetor icing probability chart revealed that atmospheric conditions were conducive to "icing at glide or cruise power." The pilot reported that there were no mechanical deficiencies with the airplane, and stated, " I have reason to believe that carburetor ice was the problem, although I was using carburetor heat at the time."
Factual narrative
On December 21, 2005, at 0953 eastern standard time, a Beech 23, N7631R, was substantially damaged during a forced landing following a loss of engine power in Chaplin, Connecticut. The certificated airline transport pilot/owner sustained serious injuries. Visual meteorological conditions prevailed, and no flight plan was filed for the flight that departed Quonset State Airport (OQU), Kingston, Rhode Island, and was destined for Windham Airport (IJD), Willimantic, Connecticut. The personal flight was conducted under 14 CFR Part 91.
The pilot/owner provided a statement to a Federal Aviation Administration (FAA) aviation safety inspector. The pilot stated that while on approach to Windham Airport, the engine began to run roughly, then completely lost power. He switched fuel tanks, and attempted an engine restart, but was unsuccessful. The pilot then maneuvered the airplane toward a snow-covered field, but could not clear trees during the final approach.
The manager of the fixed base operator (FBO) at Windham Airport responded to the scene, and an examination of the airplane revealed that both wings were impact damaged, and that the fuel cells were compromised. There was an odor of fuel, but no evidence of fuel in the tanks, and little evidence of fuel spillage at the scene.
The FBO manager noticed that the fuel pump was running, so he turned off the pump and moved the fuel selector to the "Off" position. He then turned the airplane beacon and battery off.
The airplane was later moved to Windham Airport for further examination.
On December 22, 2005, the propeller was straightened, and a can of fuel was plumbed through the left fuel tank of the airplane. The engine was then started, and ran continuously on the airframe without interruption.
Examination of aircraft and fuel records revealed that the pilot had serviced the airplane with 44 gallons of fuel on November 23, 2005, and that the airplane had flown approximately 1 hour since that service.
The FAA inspector reexamined the scene with a fire inspector, and discovered considerable evidence of fuel in the soil beneath the snow.
The pilot held an airline transport pilot certificate, as well as a commercial pilot certificate with a rating for airplane single engine land. His most recent FAA second-class medical certificate was issued January 13, 2003. He reported 26,950 total hours of flight experience, 580 hours of which were in make and model.
At 0952, the weather reported at Windham Airport included clear skies and no wind. The temperature was 19 degrees Fahrenheit and the dew point was 13 degrees Fahrenheit.
Interpolation of a carburetor icing probability chart revealed that atmospheric conditions were conducive to "icing at glide or cruise power." In a subsequent written statement, the pilot reported that there were no mechanical deficiencies with the airplane, and stated, " I have reason to believe that carburetor ice was the problem, although I was using carburetor heat at the time."
Aircraft
- Registration
- N7631R
- Reported as
- Beech 23
- Category
- Airplane
- Serial number
- 1252
- Airframe hours
- 1,701
- Engine
- Lycoming O-360, 180 horsepower, reciprocating
- Damage
- Substantial damage
- Flight
- Personal · Part 91
- Registered owner
- Albert Schmid
- Airworthiness certificate
- Standard, Normal
- Last inspection
- Annual · November 1, 2005 · 1 hours before
- Departed
- OQU · North Kingstown, RI
- Destination
- IJD · Willimantic, CT
- Airport
- IJD · Windham, runway 27, 4,278 × 100 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
- 76
- Injuries
- Serious
- Certificate
- Airline transport
- Airplane ratings
- Multi-engine land, Single-engine land
- Instrument ratings
- Airplane
- Medical
- Class 3, With waivers/limitations
- Last flight review
- January 1, 2004
- Seat
- Left
- Flight hours
- 26,950 total · 580 in this make and model · 8 in the last 90 days · 4 in the last 30 days · 1 in the last 24 hours
Weather
- Conditions
- Visual (VMC) · Day
- Wind
- Calm
- Visibility
- 10 statute miles
- Lowest ceiling
- None
- Temperature
- 19 °F, dew point 12 °F
- Altimeter
- 30.19 inHg
- Observed at
- IJD, 3 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.