MIA08LA152 · Morris George Velocity 173RG
Morris George Velocity 173RG · Accident: loss of control in flight during takeoff
From Northeast Florida Regional Airport (SGJ) to Northeast Florida Regional Airport (SGJ)
Event
- NTSB case
- MIA08LA152
- 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
- 2 · 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
Morris George Velocity 173RG
- Aircraft type
- Morris George VELOCITY 173
- 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
- N269VE
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Northeast Florida Regional Airport (SGJ), ST AUGUSTINE, FLTo Northeast Florida Regional Airport (SGJ), ST AUGUSTINE, 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
- Takeoff
- Defining eventThe 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
- 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
No findings designated as a cause are recorded in the NTSB data yet.
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
The purpose of the flight was a demonstration for a prospective buyer. According to witnesses, after becoming airborne and reaching approximately 50 feet above ground level the airplane's engine began to surge. The airplane then entered a bank to the left and impacted a marshy area, producing a debris path approximately 100 feet long. The main wreckage came to rest with the engine partially submerged. All major structural components and flight control surfaces were accounted for at the scene; however, flight control continuity could not be confirmed because of impact damage. Postaccident examination of the airframe and engine identified no anomalies that would produce engine surges or a loss of control.
Probable cause
A loss of control in flight due to undetermined reasons.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record MIA08LA152
- Event ID
- 20080825X01308
- Case number
- MIA08LA152
- Dataset
- full-current
- Source SHA-256
- 5cf380f0061817c0331a6b2d8cc7e0ee3a79bea469a1001dc5c10e56f35f5ab3
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: 64b293494ed01421a8ec8c93c59b80cdfce2633b4d82e776db5009e0f03d7edd; retrieved 2026-09-13T19:23:46.053Z.