FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

ATL07FA031 · Cessna 182P

4 Jan 2007 · Columbia, SC, United States

M.B. Kahn Construction Cessna 182P · Accident: in flight collision with object on approach

From Newport News Williamsburg International Airport (KPHF) to Jim Hamilton L.B. Owens Airport (KCUB)

Report a problem

Event

NTSB case
ATL07FA031
Event typeAccident: someone killed or seriously injured, or the aircraft substantially damaged (NTSB definition). Incident: an occurrence that affected or could have affected safety, short of that. Glossary
Accident
InvestigationHow far the investigation had got when the record was published: preliminary, ongoing, final or completed. Unknown where the source does not say. Glossary
Completed
API-reported fatalities
3 · all aircraft and ground
Ground fatalities
Unknown
OperationWhat kind of flying it was, grouped by the rules it flew under: airline (US Part 121), air taxi and commuter (Part 135), general aviation (Part 91 and similar), military or government. Glossary
General aviation
WeatherVisual meteorological conditions (VMC): good enough to fly by looking outside. Instrument conditions (IMC): cloud or low visibility, flying by instruments. Glossary
Instrument Meteorological Cond

Cessna 182P

Aircraft type
Cessna 182
Category
Airplane
RegistrationThe aircraft's tail number, such as N12345 or G-ABCD. Registrations are reissued, so the same one years apart can be a different aircraft. Glossary
N55YS
Onboard fatalities
Unknown
Route
From Newport News Williamsburg International Airport (KPHF), Newport News, VATo Jim Hamilton L.B. Owens Airport (KCUB), Columbia, SC
Aircraft age
Not recorded
Flight rulesThe regulations the flight operated under: in the US, Part 91 (general aviation), Part 121 (airlines), Part 135 (air taxi and commuter) and others; for flights abroad, the NTSB's coarser commercial or non-commercial code. Glossary
Part 91: General Aviation
Phase of flightThe stage of the flight when things started to go wrong: standing, taxi, takeoff, initial climb, en route, maneuvering, approach or landing. Glossary
Approach · IFR final approach
First occurrenceThe single coded event the NTSB judges best describes what happened (records from 2008 on). Older records name the first occurrence in the sequence instead. Glossary
In flight collision with object
Also codedOther events the NTSB coded in the sequence, such as a wire strike after a loss of power. Flight Findings uses them for its kinds of event. Glossary
Tree(s)
DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
Destroyed

Cause areas

  • Pilot in command › Decision height, not maintained
  • Pilot in command › Procedures/directives, not followed

Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.

NTSB narrative

The pilot was cleared for a Localizer Runway 31 approach at Columbia Owens Downtown Airport, Columbia, South Carolina. Review of radar data for N55YS, revealed the airplane crossed HIDEE intersection at 1,300 feet (all altitudes msl), 500 feet below the published minimum crossing altitude. The Minimum Safe Altitude Warning alert activated and was presented on the north radar controller's display as a recurring "LA" to indicate low altitude. The north radar controller did not issue a safety alert to the pilot. The pilot informed the north radar controller that he was executing a missed approach and initiated a right turn instead of executing the published missed approach procedure. The minimum descent altitude for the approach is 660 feet and the airplane-recorded altitude was 400 feet. The radar north controller informed the pilot the airplane was radar contact, to climb and maintain two thousand one hundred and stated, "All right sir, hope you're on a heading of three one zero still on the localizer there, don't get too far to the north, I don't know what's out there at that altitude." The pilot acknowledged the transmission, and was provided the weather at Columbia Metropolitan Airport and vectors for the ILS runway 11at that airport. The pilot was cleared for the ILS runway 11, four miles from the outer marker and instructed to maintain 2,100 feet until established. The decision height for the approach is 436 feet. Review of radar data revealed the airplane crossed the outer marker at 1,700 feet. A low altitude alert was observed on the radar playback from this point for the remainder of the approach. The north radar controller did not issue any safety alerts. The final low altitude alert was at 300 feet, 1 mile from the end of the runway. The pilot was instructed to contact the tower and acknowledged the transmission. After communications were transferred to the local controller in the control tower, the local controller was unable to establish radio contact with N55YS. The local controller made numerous transmissions including a low altitude alert, a clearance to land, weather information, runway visual range, and position correlation information; however, the local controller did not receive a response from the pilot of N55YS. Non-ATC recordings revealed the pilot of N55YS responded to the local controller transmissions; however, the radio calls from N55YS while on the local control frequency were not heard by the controller or recorded by the ATC facility. There was no further contact with the pilot and the radar track went into the coast mode. The airplane was located the following morning about 1 mile west of the runway in a wooded area. Examination of the airframe, flight controls, engine assembly, and accessories revealed no evidence of a pre-crash mechanical failure or malfunction. Examination of the flight instruments revealed no anomalies. There was no entry in the logbook indicating a current altimeter test.

This report was modified on January 25, 2008.

Probable cause

The pilot's failure to follow approach procedures by descending below the prescribed descision height altitude resulting in an in-flight collision with trees and the ground.

This report was modified on January 25, 2008.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record ATL07FA031
Event ID
20070111X00040
Case number
ATL07FA031
Dataset
historical-pre2008
Source SHA-256
89e2df6d848e7ab3b42e7d7c7a03ff403303057a26ca04c95b3ea67201c3ce74
Source notes (4)
  • Unreviewed is an editorial label, not an investigation status. API-sourced is not report-checked or human-reviewed. Explicit event totals are used without summing aircraft injury tables; onboard allocation is withheld. Unknown values remain unknown. The operation category is mapped from the NTSB-reported FAR part and has not been reviewed.
  • Filled from the NTSB case API where the bulk record had no value: local date, investigation status, coordinates. Values present in the bulk record are kept.
  • The date is the local date; the NTSB stores the UTC date 2007-01-05.
  • API snapshot SHA-256: c494ab41a3ced37ed91e741844be7b422d253a9e103256f145116b8a1b48e686; retrieved 2026-09-20T16:55:01.452Z.