FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

ATL07LA129 · Kolb Company MK II

22 Sept 2007 · Sweetwater, TN, United States

Kolb Company MK II · Accident: loss of control in flight en route

From West Wind Airpark (TN64) to West Wind Airpark (TN64)

Report a problem

Event

NTSB case
ATL07LA129
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

Kolb Company MK II

Aircraft type
Kolb MK
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
N43046
Operator
Unknown
Onboard fatalities
Unknown
Route
From West Wind Airpark (TN64), Sweetwater, TNTo West Wind Airpark (TN64), Sweetwater, TN
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 · climb to 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
Loss of control in flight
Also codedOther events the NTSB coded in the sequence, such as a wire strike after a loss of power. Flight Findings uses them for its kinds of event. Glossary
Tree(s)
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 › Aircraft control, not maintained

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

NTSB narrative

A witness recalled that the non-certificated pilot seemed "rusty" or unfamiliar with the assembly of the amateur-built airplane. The witness watched as the airplane "wobbled" into the air during climbout, and approximately 1 mile from the departure airport, the nose pitched down and continued straight down until it disappeared behind trees. No pilot or aircraft logbooks were recovered. Examination of the wreckage revealed no obvious mechanical deficiencies, and that the airplane was equipped with a ballistic recovery parachute. The parachute was deployed, but did not inflate.

Probable cause

The pilot's failure to maintain control of the airplane during climb.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record ATL07LA129
Event ID
20071005X01518
Case number
ATL07LA129
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: 890b06e7f591e8712d4218652a06da56f17c756bf7a0122602032cd8b736f80b; retrieved 2026-09-20T16:15:19.719Z.