NYC07FA037 · Cirrus SR22
Cirrus SR22 · Accident: loss of control in flight on approach
From DeKalb Peachtree Airport (PDK) to Charlotte Douglas International Airport (CLT)
Event
- NTSB case
- NYC07FA037
- 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
- 1 · 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
Cirrus SR22
- Aircraft type
- Cirrus SR22
- 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
- N665CD
- Onboard fatalities
- Unknown
- Route
- From DeKalb Peachtree Airport (PDK), Dekalb-Peachtre, GATo Charlotte Douglas International Airport (CLT), Charlotte, NC
- 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
- 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
- Loss of control in flight
- 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
- Stall/spin; 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 › Aircraft control, not maintained
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 provided an intercept vector and cleared for an Instrument Landing System (ILS) approach during night instrument meteorological conditions; however, the airplane crossed through the final approach course. The air traffic controller alerted the pilot, and issued a vector to rejoin the final approach course, but as the airplane maneuvered, it descended below a safe altitude. The controller issued a "low altitude warning," and instructed the pilot to climb "immediately" to 3,000 feet. During the following 20 seconds, the airplane climbed from 1,800 feet to 3,800 feet, heading changed from 180 degrees to about 330 degrees, and airspeed decreased from 183 knots to 90 knots. The airplane then entered a rapid descent with the final recorded radar target being approximately 1/4 mile from the accident site. A witness statement and physical evidence at the scene were consistent with the airplane's engine producing power until impact. The debris path was approximately 100 feet long and contained fragmented portions of all the airplane's components. Examination of the airplane revealed no mechanical anomalies. The pilot's logbook was not located and his total or recent actual instrument experience could not be determined.
Probable cause
The pilot's failure to maintain aircraft control. Contributing to the accident was the night instrument meteorological conditions.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record NYC07FA037
- Event ID
- 20061208X01760
- Case number
- NYC07FA037
- 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 2006-12-01.
- API snapshot SHA-256: e9462fd6ca986e83891582a46039241d0b6152ab2c1432506b2c1500a0b9da51; retrieved 2026-09-20T16:58:39.463Z.