NYC97LA135

NTSB accident investigation · Cessna 182B · Medford, NJ · July 6, 1997

Accident · No injuriesLimited investigationFinal report
Date
July 5, 1997, 20:25 local (Jul 6, 1997, 00:25 UTC)
Place
Medford, NJ
Injuries
3 uninjured
Damage
Destroyed
Phase of flight
Approach
Aircraft
N166KMCessna 182B
Weather
Visual (VMC) · Day
Status
Completed · report April 24, 1998
Report
Approved by Office Director
FAA report
19970705016909A
Case key
39394

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

An inflight engine fire of undetermined origin.

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.

Fire/explosionApproach - vfr pattern - final approach
Powerplant - fire
Reason for occurrence undeterminedCause
Hard landingLanding
Nose overLanding - flare/touchdown

Analysis

The pilot had flown three circuits in the traffic pattern before he landed and shut the engine down to await hot air balloon traffic to depart the area. According to the pilot, '(The engine) was running great. Everything sounded normal and looked normal. About half way down on final I heard something between a bang and a thump. I don't know where it came from. The aircraft tried to nose up - started to pitch up, so I pushed the nose down. I didn't touch the throttle because I didn't want it to pitch up. I lost some altitude in a critical spot [and] struck the nose gear on the end of the runway. We went skidding down the runway on the nose. There were sparks and then out and out flames.' According to a witness, 'After they waited for the balloons, they did a fourth pattern. They were coming in on final when I heard a 'pow' noise - a loud 'pop'. After the 'pop', the plane came down like someone dropping a ball. I saw flames coming out of the cowlings while it was still in the air. The airplane touched down and the [nose] wheel popped back. The airplane slid for a short ways on the nose with the tail up in the air. Then the flames came from underneath and around the cabin.' Extensive fire damage precluded determination of the origin or what initiated the fire.

Factual narrative

On July 5, 1997, at 2025 eastern daylight time, a Cessna 182B, N166KM, was destroyed during a forced landing and subsequent fire at the South Jersey Regional Airport (VAY), Medford, New Jersey. The certificated commercial pilot and two passengers were not injured. Visual meteorological conditions prevailed for the local flight that originated at VAY, at 2015. No flight plan was filed for the personal flight conducted under 14 CFR Part 91.

In a telephone interview, the pilot reported that he took off from VAY, about 2000, and flew three traffic patterns. After the third traffic pattern, he landed the airplane, shut down the engine, and waited for three hot air balloons to cross over the airport. The balloons departed the area and the pilot restarted the engine and flew a fourth pattern. When describing the performance of the airplane, the pilot said:

"It was running great. Everything sounded normal and looked normal. About half way down on final I heard something between a bang and a thump. I don't know where it came from. The aircraft tried to nose up - started to pitch up, so I pushed the nose down. I didn't touch the throttle because I didn't want it to pitch up. I lost some altitude in a critical spot [and] struck the nose gear on the end of the runway. We went skidding down the runway on the nose. There were sparks and then out and out flames. I yelled for everyone to get out and within 2 minutes [the plane] was completely gone."

A witness on the airport was watching N166KM through binoculars. Her son was a passenger on the airplane. In a telephone interview the witness reported:

"After they waited for the balloons, they did a fourth pattern. They were coming in on final when I heard a 'pow' noise - a loud 'pop'. After the 'pop', the plane came down like someone dropping a ball. I saw flames coming out of the cowlings while it was still in the air. The airplane touched down and the [nose] wheel popped back. The airplane slid for a short ways on the nose with the tail up in the air. Then the flames came from underneath and around the cabin."

The witness reported that the three occupants climbed from the airplane uninjured and that the airplane was consumed by fire in less than 2 minutes.

Examination of the wreckage by an Federal Aviation Administration Inspector revealed:

"Flames consumed the aircraft within approximately 2-3 minutes completely destroying the aircraft and engine leaving this inspector with an aircraft and engine of ashes."

Aircraft

Registration
N166KM
Reported as
Cessna 182B
Category
Airplane
Serial number
51646
Airframe hours
3,362
Engine
Continental O-470-L, 230 horsepower, reciprocating
Damage
Destroyed
Fire
In-Flight
Flight
Personal · Part 91
Registered owner
John F. Stollsteimer
Airworthiness certificate
Standard, Normal
Last inspection
Annual · May 30, 1997 · 20 hours before
Departed
VAY
Airport
VAY · South Jersey Regional, runway 26, 3,911 × 50 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
53
Certificate
Commercial
Airplane ratings
Single-engine land, Multi-engine land
Instrument ratings
Airplane
Medical
Class 2, Valid Medical--w/ waivers/lim
Seat
Left
Flight hours
1,160 total · 800 in this make and model · 960 as pilot in command · 60 in the last 90 days · 20 in the last 30 days · 1 in the last 24 hours

Weather

Conditions
Visual (VMC) · Day
Wind
280° at 5 knots
Visibility
7 statute miles
Lowest ceiling
None
Temperature
73 °F, dew point 54 °F
Altimeter
29.00 inHg
Observed at
WRI, 28 nm away

Docket · 4

The files NTSB released with the investigation on March 5, 1998, on NTSB’s docket system: statements, records, photos and specialists’ reports. 626 KB in all.

FAA reports on this event · 1

The FAA’s own accident and incident reports, matched to the aircraft by N-number and date.