Cessna 210D N3963Y
23 April 2011 · Altavista, Virginia, United States · Fatal
Summary
On 23 April 2011 at about 01:46 local time, a Cessna 210D registered N3963Y, operated by DI Giulio Robert H, was involved in an accident near Altavista, Virginia, United States. One person was on board and one died. The aircraft was substantially damaged. The NTSB has published a probable cause for this accident; it is quoted in full below.
The record
- Date
- at 01:46
- Classification
- Accident
- Location
- Altavista, Virginia, United States
- Nearest airport
- Lynchburg Regional (LYH)
- Coordinates
- 37.1142, -79.3078
- Aircraft
- Cessna 210D
- Registration
- N3963Y
- Category
- Airplane
- Engines
- 1
- Operator
- DI Giulio Robert H
- Operating rule
- Part 91: General Aviation
- Purpose of flight
- Personal
- Phase of flight
- Not recorded
- Route
- Winchester → Lynchburg
- Aircraft damage
- Substantial
- Weather
- IMC
- Light
- Night/Dark
- NTSB number
- ERA11FA258
People
1 person died.
| On board | Died | Serious | Minor | Uninjured |
|---|---|---|---|---|
| 1 | 1 | 0 | 0 | 0 |
Probable cause
The pilot’s loss of airplane control due to spatial disorientation. Contributing to the accident was the pilot’s lack of experience in actual night instrument conditions.
Quoted verbatim from the NTSB record. This site does not paraphrase or interpret it.
Read the full NTSB narrative
The pilot was conducting an instrument flight rules flight during night, instrument meteorological conditions. About 15 minutes into the flight, the air traffic controller observed that the pilot was not flying assigned headings. When queried, the pilot responded that he was "…a little disoriented…" The pilot continued to deviate from assigned headings as he was vectored to the airport for the approach. During his first attempt at the instrument landing system (ILS) approach, the pilot executed a missed approach, citing problems with his engine monitor. Following the missed approach, the air traffic controller issued a low altitude alert to the pilot. On his second attempt at an ILS approach, the pilot unknowingly deviated well right of the localizer course and was instructed to climb immediately due to another low altitude alert. The pilot was then vectored to an intersection south of the airport and was offered a global positioning system (GPS) approach. The pilot continued to have difficulty with heading and altitude control, receiving an additional low altitude alert from the air traffic controller. The pilot subsequently informed the controller that he had "complete gyro failure" and needed assistance with heading and altitude monitoring. When asked if he was tracking a navigational aid, the pilot responded that he was "…a little dizzy…" The pilot asked for an altitude check at 5,200 feet mean sea level (msl) and the controller confirmed that altitude on his radar. The controller subsequently issued another altitude alert to the pilot at 1,400 feet msl, and the pilot did not acknowledge the call. At that point, radar and radio contact was lost. Radar, GPS, and witness information confirmed that the airplane collided with the ground during a right, descending spiral. The wreckage was highly fragmented, including the engine. Propeller signatures indicated high engine power at impact. The landing gear and flaps were retracted. Not all of the cockpit instruments could be identified or located due to the impact damage. Data recovered from the engine monitor showed that the engine, vacuum system, and electrical system were operating normally during the flight. The pilot received his instrument rating about six weeks prior to the accident and had not logged any actual instrument time at night. The pilot was an insulin-dependent diabetic and was required to monitor his blood glucose level before and during the flight; however, the investigation was unable to determine if the pilot’s glucose level affected his performance. Although the pilot reported problems with his cockpit instrumentation, physical evidence of an in-flight instrument failure was inconclusive. The environmental conditions that existed during the flight and the pilot's actions and responses indicate that he likely experienced significant spatial disorientation.
Quoted verbatim from the NTSB record.
Other Cessna 210 accidents
| Date | Aircraft | Location | Operator | Outcome | Died |
|---|---|---|---|---|---|
| 10 Jul 2011 | Cessna 210-5(205) | McKenzie Bridge, Oregon, United States | Stephen Perrault Construction LLC | No injuries | - |
| 12 Nov 2011 | Cessna 210 | Cuiaba, Brazil | - | Fatal | 4 |
| 6 Oct 2011 | Cessna 210A | Wolfe City, Texas, United States | Spradling T Glenn JR | No injuries | - |
| 22 Nov 2011 | Cessna 210 | Alto Alegre, Brazil | Paramazonia Taxi Aereo Ltda | Fatal | 1 |
| 6 Mar 2011 | Cessna 210 | Pahrump, Nevada, United States | - | No injuries | - |
| 7 Dec 2011 | Cessna 210 | Roma, Australia, Australia | Chipford Pty Ltd | Fatal | 1 |
All 2,022 records for this type
Other accidents in this area
| Date | Aircraft | Location | Operator | Outcome | Died |
|---|---|---|---|---|---|
| 17 Aug 2011 | Let L 33 SOLO | Wakefield, Virginia, United States | Tidewater Soaring Society | No injuries | - |
| 19 Aug 2011 | Piper PA46 | Manasses, Virginia, United States | - | No injuries | - |
| 6 Nov 2011 | Sigmon Harvey E VANS RV 6 | Abingdon, Virginia, United States | Seats Frank R | No injuries | - |
| 6 Oct 2011 | Rivers William J KR-2 | Wytheville, Virginia, United States | - | Fatal | 1 |
| 5 Oct 2011 | Cessna 180J | Norfolk, Virginia, United States | Crider Michael A | No injuries | - |
| 24 Apr 2011 | Cessna 182A | Galax, Virginia, United States | N4920D LLC | Minor injuries | - |