ATL07LA115 · Cirrus Design Corp. SR20
Cirrus Design Corp. SR20 · Accident: in flight encounter with weather while maneuvering
From Westchester County Airport (KHPN) to Nantucket Memorial Airport (KACK)
Narrative check · The NTSB narrative appears to contradict this record's location. Values are shown as recorded, not corrected; compare with the narrative.
Event
- NTSB case
- ATL07LA115
- 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
- 0 · 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 Design Corp. SR20
- Aircraft type
- Cirrus SR20
- 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
- N869CD
- Operator
- Thomas Jackson
- Onboard fatalities
- Unknown
- Route
- From Westchester County Airport (KHPN), White Plains, NYTo Nantucket Memorial Airport (KACK), Nantucket, MA
- 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
- Maneuvering
- 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 encounter with weather
- 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
- Guy wire
- DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
- Substantial
Cause areas
- Pilot in command › In-flight planning/decision, improper
- Pilot in command › Spatial disorientation
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
The non-instrument rated pilot was conducting a night VFR flight to his destination airport. As the pilot neared the airport, he initiated a descent and established radio contact with the control tower. The controller pointed out traffic and instructed the pilot to continue for runway 24. The pilot continued his descent and was informed by the controller that the airport was changing to IFR and instructed the pilot to contact approach control. A low layer of clouds had moved into the area. The pilot contacted the approach controller and asked if he could perform the ILS runway 24 approach. The controller started vectoring the pilot for a left downwind, and asked the pilot if he was instrument qualified and current. The pilot replied, "We are IFR qualified," even though he was not. The controller informed the pilot to turn left to a heading and the pilot responded by saying he was turning right The controller again instructed the pilot to turn to the left, expect the ILS runway 24 approach, and to advise that he had the current airport information. The pilot responded by saying he was turning right and that he would pick up the airport information. The controller informed the pilot that it was not a right turn, and informed the pilot he had turned in the wrong direction on the last turn and to turn to the left. The pilot replied that he was turning to the left to the assigned heading. The controller asked the pilot what his type of airplane was, and the pilot replied, "Cirrus I had to pull the parachute." The pilot stated in an interview with the NTSB that he was struggling to keep the airplane level; he was in instrument conditions, in a black hole without a visible horizon or ambient light, and that he became spatially disoriented and pulled the parachute. Advisory Circular 60-4A states in part, "The attitude of an aircraft is generally determined by reference to the natural horizon or other visual references with the surface. If neither horizon nor surface references exist, the attitude of an aircraft must be determined by artificial means from the flight instruments. Sight, supported by other senses, allows the pilot to maintain orientation. However; during periods of low visibility, the supporting senses sometimes conflict with what is seen. When this happens, a pilot is particularly vulnerable to disorientation." Because of the clouds that had moved into the area, the pilot likely could not distinguish ground cues that would have helped him determine the airplanes attitude. Without an instrument rating, the pilot was unable to use his flight instruments to help him successfully orient and land the airplane. Had the pilot informed the controller that he was not instrument rated, the controller may have been able to instruct the pilot to climb to visual flight conditions and land at another VFR airport.
Probable cause
The non-instrument rated pilot's loss of control at night in instrument flight conditions due to spatial disorientation. A factor was the pilot's in-flight decision not to inform the controller that he was not instrument rated.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record ATL07LA115
- Event ID
- 20070821X01216
- Case number
- ATL07LA115
- 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. Values present in the bulk record are kept.
- The date is the local date; the NTSB stores the UTC date 2007-08-18.
- API snapshot SHA-256: 485a9121be9f62af2f7073ac0089bae8df5b2cc1c894a32bd81b1d90652f2f41; retrieved 2026-09-21T08:45:24.162Z.