FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

FTW83FA128 · Cessna P-206C

23 Feb 1983 · Brookland, AR, United States

Cessna P-206C · Accident: loss of control in flight on approach

From Nashville International Airport (BNA) to Jonesboro Municipal Airport (JBR)

Report a problem

Event

NTSB case
FTW83FA128
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
0
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 P-206C

Aircraft type
Cessna P-206
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
N8637Z
Operator
Unknown
Onboard fatalities
Unknown
Route
From Nashville International Airport (BNA), Nashville, TNTo Jonesboro Municipal Airport (JBR), Jonesboro, AR
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 missed 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
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 › IFR procedure, poor

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

NTSB narrative

THE ACFT CRASHED IN IMC WEATHER AFTER THE PILOT FAILED TO COMPLETE A VOR APPROACH TO JONESBORO. ACCORDING TO THE OWNER OF THE ACCIDENT ACFT, THE PLT WAS INSTRUMENT RATED AND HAD FILED AN IFR FLT PLAN BUT WAS NOT VERY PROFICIENT IN INSTRUMENT FLYING. DURING THIS FLT THE PLT WANDERED OFF COURSE AND ALT AND HAD TO BE CORRECTED BY ATC. HE IMPROPERLY CALLED NASHVILLE TOWER AS KNOXVILLE TOWER AND MEMPHIS ARTCC AS ATLANTA. THE PLT ALSO DECLARED A MISSED APPROACH AT JONESBORO TWO MINUTES AFTER RECEIVING FINAL CLEARANCE AT 240O FT. THE CONTROLLER ON DUTY STATED THAT HE DID NOT BELIEVE AN APPROACH COULD BE MADE FROM 2400 FT IN 2 MINUTES NOR DID HE HEAR THE ACFT PASS OVER THE ARPT. THE PLT REQUESTED A 2NDAPPROACH AND THERE WERE NO MORE TRANSMISSIONS RECEIVED FROM HIM. THE ACFT CRASHED IN A 90 DEGREE LEFT BANK INTO A WHEAT FIELD ABOUT 6 MILES FROM THE ARPT.

Verbatim NTSB analysis from the NTSB dataset

Sources

NTSB record FTW83FA128
Event ID
20001214X42196
Case number
FTW83FA128
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 1983-02-24.
  • API snapshot SHA-256: 5334b1f4eddb885799a777786deb256aca27e056666c2123fca0daa7a741f378; retrieved 2026-09-21T07:08:17.586Z.