ATL06CA034 · Labarre Hatz CB1
Labarre Hatz CB1 · Accident: on ground/water collision with terrain/water during landing
From Tokenna, SC to Walhalla, SC
Narrative check · The NTSB narrative appears to contradict this record's departure or destination. Values are shown as recorded, not corrected; compare with the narrative.
Event
- NTSB case
- ATL06CA034
- 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
- 0 · 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
Labarre Hatz CB1
- Aircraft type
- Labarre HATZ CB1
- 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
- N86LL
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route Possible conflict
- From Tokenna, SCTo Walhalla, SC
- 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
- Landing · flare/touchdown
- 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 terrain/water
- DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
- Substantial
Cause areas
- Pilot in command › Unsuitable terrain or takeoff/landing/taxi area, selected
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
The pilot stated that it had been raining for a couple of days prior to the accident flight. He departed Clemson, South Carolina, on a visual flight rules flight and flew around the local area before landing at Seneca, South Carolina. The pilot stated that he took a short break and departed Seneca en route to Walhalla, South Carolina. The pilot stated that he thought about not landing at Walhalla Airport since it has a grass strip and there had been a lot of rain. He entered left traffic and decided to land. Upon touchdown the main landing gear collided with the wet, soft, soggy, grass runway, and the airplane nosed over. The pilot stated, "I made an improper decision by not making a three point landing. I knew the grass was wet and the airplane would not have nosed over on touchdown in a three point attitude." The pilot further stated that he did not experience any mechanical problems with the airplane before the accident.
Probable cause
The pilot's selection of unsuitable terrain to land. Contributing factors were the wet, soft, grassy runway.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record ATL06CA034
- Event ID
- 20060201X00146
- Case number
- ATL06CA034
- 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: d8b9dfac1c1e478041362b0d1113beee1a1206beeaa82518c28bbe74c5557806; retrieved 2026-09-22T05:09:52.798Z.