ATL82FA263 · Cessna 170A
Cessna 170A · Accident: in flight encounter with weather en route
From C · Columbia, SC to C · Daytona Beach, FL
Event
- NTSB case
- ATL82FA263
- 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
- Unknown
Cessna 170A
- Aircraft type
- Cessna 170
- 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
- N9263A
- Operator
- Leonard Heighton
- Onboard fatalities
- Unknown
- Route
- From C · Columbia, SCTo C · Daytona Beach, FL
- 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
- En route · cruise
- 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
- 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 › Flight into known adverse weather, continued
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
THE NON-INSTRUMENT RATED PILOT WAS ON A FLIGHT FROM IRONTON, OH TO DAYTONA BEACH, FL WITH AN EN ROUTE STOP AT COLUMBIA, SC. HE OBTAINED A WEATHER BRIEFING PRIOR TO DEPARTING IRONTON, BUT DID NOT UPDATE IT AFTER LANDING AT COLUMBIA. THE AIRCRAFT CRASHED ON THE 2ND LEG OF THE FLIGHT IN AN AREA WHERE A LINE OF THUNDERSTORMS HAD PASSED THROUGH. BASED ON THE CRUISE SPEED OF THE AIRCRAFT AND ITS DISTANCE FROM THE DEPARTURE POINT, THE PLANE CRASHED AT ABOUT THE SAME TIME THE THUNDERSTORMS HAD OCCURRED. THE INITIAL IMPACT OCCURRED IN A MARSHY AREA NEXT TO HERMITAGE ISLAND. TIRE PRINTS WERE VISIBLE AT LOW TIDE IN THE MARSHY GROUND. AFTER THE INITIAL IMPACT, THE AIRCRAFT CONTINUED 110 FT AND HIT A LARGE PALM TREE ON THE ISLAND AND WAS DESTROYED. THE RIGHT FUEL TANK WAS RUPTURED, BUT THE LEFT TANK REMAINED INTACT AND CONTAINED FUEL. AN EXAMINATION OF THE WRECKAGE WAS MADE, BUT NO PREIMPACT MALFUNCTION OR FAILURES WERE FOUND.
Verbatim NTSB analysis from the NTSB dataset
Sources
NTSB record ATL82FA263
- Event ID
- 20020917X04276
- Case number
- ATL82FA263
- 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: 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: fddc47aaa176336d9613caad8425b18268323def29da32693fcbc0032100dcfe; retrieved 2026-09-21T07:51:45.486Z.