FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

ATL06LA111 · Canadair F86

24 Jul 2006 · Hickory, NC, United States

Canadair F86 · Accident: on ground/water collision with object during takeoff

From Hickory Regional Airport (HKY) to Wittman Regional Airport (OSH)

Report a problem

Event

NTSB case
ATL06LA111
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
1 · 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
Visual Meteorological Cond

Canadair F86

Aircraft type
Canadair F86
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
N86FS
Operator
Silas W. Fuller · private individual
Onboard fatalities
Unknown
Route
From Hickory Regional Airport (HKY), Hickory, NCTo Wittman Regional Airport (OSH), Oshkosh, WI
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
Takeoff · rejected takeoff
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
On ground/water collision with object
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 › Aborted takeoff, delayed
  • Pilot in command › Aircraft weight and balance, exceeded
  • Pilot in command › Maintenance, installation, improper

Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.

NTSB narrative

Witnesses observed the F86 airplane on takeoff. A decrease in engine power was heard after the airplane crossed an intersecting runway and a few puffs of smoke were observed in the vicinity of the main landing gear. The airplane continued off the runway onto the overrun, collided with fixed objects, and came to a complete stop on an airport perimeter highway engulfed in flames. Initial performance documentation provided to the FAA by the project manager for the F86 revealed the maximum takeoff gross weight of the airplane was 17,300 pounds. The initial takeoff weight computed by the project manager for the F86 was 17,705 pounds. The FAA computed the initial takeoff weight at 17,693 pounds. A subsequent weight and balance was submitted to the FAA by the project manager with undocumented figures indicating the takeoff weight was 16,983 pounds. The departure runway is 6,400 feet long, and the takeoff distance required was 2,600 feet. Examination of the runway revealed evidence of braking action beginning 2,175 feet before the end of the runway. The project manager stated the pilot had observed the assembly and installation of the F86 brake assemblies on four different occasions The pilot assembled and installed the brakes on the F86 by himself four or five days before the accident. Examination and disassembly of the brakes revealed the clearance nuts on the adjuster pins were not rotated the proper amount on the left and right brake assemblies as required by the F86 Restricted Executive Order.

Probable cause

The pilot's improper assembly of the airplanes brakes, exceeding the authorized gross weight of the airplane at takeoff, and the pilot's failure to abort the takeoff in sufficient time to avoid an on-ground collision with fixed objects. A factor in the accident was the pilot's lack of experience in assembling the airplanes brakes.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record ATL06LA111
Event ID
20060725X01009
Case number
ATL06LA111
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, coordinates. 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: 1a3306ee5d5e458ae82a614497988dc8b8b6bc71311d93143b236979cd34da31; retrieved 2026-09-20T17:08:01.224Z.