FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

LAX06LA141 · Velocity XL-RG

12 Apr 2006 · Pearce, AZ, United States

Velocity XL-RG · Accident: loss of control in flight en route

From Tucson International Airport (TUS) to Tucson International Airport (TUS)

Report a problem

Event

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

Velocity XL-RG

Aircraft type
Velocity XL-RG
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
N732RA
Operator
Unknown
Onboard fatalities
Unknown
Route
From Tucson International Airport (TUS), Tucson, AZTo Tucson International Airport (TUS)
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 · 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
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

  • Reason for occurrence undetermined

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

NTSB narrative

The airplane departed controlled cruise flight, completed two descending 360-degree turns, and collided with desert terrain. The purpose of the accident flight was for the pilot to execute a 3-hour flight test mission following a predetermined test plan that he had created. The plan prescribed that he would perform a series of maneuvers (including stalls) all of which were to be conducted above 2,000 feet above ground level (agl). Witnesses heard the engine sputter and observed smoke emitting from the airplane. The airplane began to spiral and completed two 360-degree turns while descending. Prior to ground impact, the airplane assumed a wings level configuration and descended nearly vertically toward flat desert terrain. The airplane impacted with little horizontal velocity. A United States Air Force squadron commander who was operating a jet in the accident area the day of the accident stated that he had previously coordinated simultaneous operations with the accident pilot. The commander did not hear or receive a radio call from the accident pilot nor did he make visual contact with the airplane, as he had anticipated. The accident pilot was in communication with Air Route Traffic Control Center (ARTCC) personnel and receiving traffic advisories. The pilot's last known communication occurred about 8 minutes prior to the accident. The radar data revealed that the airplane was in cruise flight heading southwest between 4,300 and 4,600 feet agl. The last radar return was recorded approximately 0.58 nautical miles (nm) northeast of the accident location. The accident airplane, an experimental amateur-built that was purchased by the operator for a classified research program, was typical of other Velocity models in its assembly and design configuration. The airplane was loaded with an aft center of gravity (CG) that was 0.4 inches aft of the kit manufacturer's recommended CG envelope; however, the kit manufacturer said the airplane would have been controllable without adverse handling characteristics. The pilot's actions and the airplane's flight characteristics were recorded during the flight by data acquisition units and any deviation from the test card would have been seen by the operator upon the return of the flight. Witnesses in the area observed clear skies at the time of the accident. The airplane and all the equipment onboard were thermally destroyed. During the post accident examinations of the wreckage, no anomalies were found with the airframe or engine.

Probable cause

a departure from controlled flight for undetermined reasons, resulting in a collision with terrain.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record LAX06LA141
Event ID
20060420X00464
Case number
LAX06LA141
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: b05739faa8cf5646340188d0f37f5eebfed8636fdcbfecc96c4db1ff3f8136b4; retrieved 2026-09-20T17:25:52.566Z.