FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

MIA07CA048 · American Champion 7GCBC

8 Feb 2007 · Deland, FL, United States

American Champion 7GCBC · Accident: in flight collision with terrain/water during landing

From Orlando Sanford International Airport (KSFB) to 1J6 · Deland, FL

Report a problem

Event

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

American Champion 7GCBC

Aircraft type
American Champion 7
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
N711AT
Operator
Unknown
Onboard fatalities
Unknown
Route
From Orlando Sanford International Airport (KSFB), Sanford, FLTo 1J6 · Deland, 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
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
In flight 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 › Directional 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

The pilot stated that he was on approach to a grass airstrip, with the intention of a full stop landing. As he started to flare, the airplane went slightly south of centerline for which he applied the necessary correction, however, the airplane responded quicker than anticipated and over flew the centerline. While attempting to correct, the right landing gear hit and got stuck in a soft sandy spot on the runway, collapsing the gear leg and stopping the airplane. The pilot stated there were no mechanical failures or malfunctions to the airplane or any of its systems prior to the accident.

Probable cause

The pilot's failure to maintain directional control during the landing flare, resulting in an in-flight collision with soft terrain, and a collapse of the right main landing gear.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record MIA07CA048
Event ID
20070314X00290
Case number
MIA07CA048
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: e19b2e84a49d4a5a95831faba26ea7b89466aca6fd4c7a73b263b112e92b3b73; retrieved 2026-09-22T04:02:50.300Z.