FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

ERA14FA068 · Cessna 310R

8 Dec 2013 · Jacksonville, FL, United States

Cessna 310R · Accident: loss of control in flight on approach

From Treasure Coast International Airport (FPR) to Jacksonville Executive at Craig Airport (CRG)

Report a problem

Event

NTSB case
ERA14FA068
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 310R

Aircraft type
Cessna 310
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
N98BT
Onboard fatalities
Unknown
Route
From Treasure Coast International Airport (FPR), Fort Pierce, FLTo Jacksonville Executive at Craig Airport (CRG), Jacksonville, FL
Aircraft age
About 34 years (built 1979)
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 missed approach
Defining eventThe 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
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

  • Aircraft › Aircraft oper/perf/capability
  • Personnel issues › Experience/knowledge
  • Personnel issues › Psychological
  • Personnel issues › Task performance

Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.

NTSB narrative

The pilot filed an instrument flight rules (IFR) flight plan with flight services, and the briefer asked the pilot if he would like weather information. The pilot replied "no," and stated that the weather "looked good"; however, at that time, the weather at the destination airport included visibility of 2 miles and a 400-foot overcast ceiling. The pilot proceeded on the approximate 1-hour night flight to the destination airport in low IFR conditions. During the instrument landing system approach, the pilot flew about 1 mile right of and 900 feet below the final approach fix. The tower controller issued a low altitude alert and instructed the pilot to check his altitude. The pilot acknowledged the instruction and confirmed that the airplane's altitude was 600 feet, which was the altitude indicated on radar. He then flew the airplane left of the final approach course twice before intercepting it a third time, descending to 300 feet, and then reporting that he was going to conduct a missed approach.

The published missed approach procedure was to climb to 700 feet and then to make a climbing right turn to 1,900 feet on a 180-degree heading. However, the tower controller instructed the pilot to fly a heading of 280 degrees, and the pilot acknowledged the instruction. The controller did not provide an altitude and was not required to do so. After the pilot acknowledged the instruction, the airplane made a climbing left turn to 900 feet before radar and radio communications were lost. The airplane subsequently descended and collided with a retaining pond near the last recorded radar target. Although the tower controller's issuance of nonstandard missed approach instructions without specifying an altitude might have added to the pilot's workload, radar data show an initial turn consistent with the instructions and an associated climb indicating that the nonstandard instructions were not a factor in the accident. Examinations of the airplane and engine revealed no preimpact mechanical malfunctions that would have precluded normal operation, and there was no evidence of medical impairment that would have affected the pilot's performance.

Given the night instrument meteorological conditions (IMC) with restricted visibility and the sustained left turn and climb, it is likely the pilot experienced spatial disorientation. The investigation could not determinate the pilot's overall and recent experience in actual IMC; however, his inability to align the airplane with both the final approach fix's lateral and vertical constraints is consistent with a lack of instrument proficiency.

Probable cause

The pilot’s failure to maintain airplane control during a missed approach in night instrument meteorological conditions due to spatial disorientation and a lack of instrument proficiency.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record ERA14FA068
Event ID
20131208X92103
Case number
ERA14FA068
Dataset
full-current
Source SHA-256
5cf380f0061817c0331a6b2d8cc7e0ee3a79bea469a1001dc5c10e56f35f5ab3
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: investigation status. Values present in the bulk record are kept.
  • The date is the local date, which is the same as the UTC date the NTSB stores.
  • API snapshot SHA-256: 8d643866076338d31bbeaffdae04f8c5b0ddf6d4ee4faa704c2d3b6b2e753840; retrieved 2026-09-14T16:08:34.383Z.