LAX99LA247 · Rose VELOCITY 173/FG-E VELOCITY
Rose VELOCITY 173/FG-E VELOCITY · Accident: loss of control on ground/water during landing
From Camarillo International Airport (CMA) to an unrecorded destination
Narrative check · The NTSB narrative appears to contradict this record's aircraft involved. Values are shown as recorded, not corrected; compare with the narrative.
Event
- NTSB case
- LAX99LA247
- 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
- 0
- 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
Rose VELOCITY 173/FG-E VELOCITY Possible conflict
- Aircraft type
- Rose 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
- N137V
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Camarillo International Airport (CMA), Camarillo, CATo not recorded
- 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
- Loss of control on ground/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 › Compensation for wind conditions, inadequate
- Pilot in command › Proper alignment, not maintained
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
The pilot was on a return flight back to the airport, and after obtaining the ATIS, he made a right traffic pattern for runway 21. ATIS reported winds at 240 degrees and 12 knots. The pilot said that during the landing sequence just as the landing gear were about to touchdown, there was a strong gust of wind from the right, which lifted the wing significantly. The airplane was lifted 6 feet in the air and suddenly dropped to the ground. The airplane bounced and began to porpoise down the runway. The pilot applied full throttle and initiated a go-around. The plane accelerated and started to climb, but slowly due to the partially deployed speed brake. The airplane passed over the taxiway guardrail and clipped two airplanes parked next to a hangar. The airplane came to rest after it crossed another taxiway and hit a steel hangar door.
Probable cause
The pilot's inadequate compensation for the existing crosswind condition and his failure to maintain runway alignment.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record LAX99LA247
- Event ID
- 20001212X19298
- Case number
- LAX99LA247
- 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. 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: c7b8661ec6d4d77f7c130da72ceef92c5d1e7ccd77027bc98737e756981f61a4; retrieved 2026-09-21T20:28:42.833Z.