CEN26LA283 · Velocity Aircraft Velocity 173 FG Eli
Velocity Aircraft Velocity 173 FG Eli · Accident: loss of engine power (total) en route
From St Louis Regional Airport (ALN) to Whiteside County Airport - Joseph H Bittorf Field (SQI)
Event
- NTSB case
- CEN26LA283
- 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
- Ongoing
- 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
Velocity Aircraft Velocity 173 FG Eli
- Aircraft type
- Velocity VELOCITY
- 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
- N6954K
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From St Louis Regional Airport (ALN), East Alton, ILTo Whiteside County Airport - Joseph H Bittorf Field (SQI), Rock Falls, IL
- Aircraft age
- About 28 years (built 1998)
- 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
- 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 engine power (total)
- 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
On August 10, 2026, about 1248 central daylight time, an experimental Velocity 173 FG Elite II airplane, N6954K, sustained substantial damage when it was involved in an accident near Palmyra, Illinois. The pilot and two passengers sustained no injuries. The airplane was operated as a Title 14 Code of Federal Regulations Part 91 personal cross-country flight. According to the pilot, 14 gallons of 100 low lead fuel was purchased prior to the flight at the St. Louis Regional Airport (ALN), East Alton, Illinois. The airplane departed from ALN about 1210, and the destination was the Whiteside County Airport (SQI), Rock Falls, Illinois, where the pilot based the airplane. The airplane climbed to about 7,500 ft msl and established a cruise flight configuration. About 15 minutes later, the engine sustained a total loss of power. The pilot declared an emergency with air traffic control. The pilot coordinated with the controller, and he decided to divert to the nearest airport, the Zelmer Memorial Airpark (5K1), Palmyra, Illinois. During the emergency descent, he attempted to restore the engine power. He noticed that partial engine power was restored by pulling the mixture control nearly to the idle cutoff position. He further noticed that further attempts at a richer setting caused a loss of engine power. The pilot maneuvered the airplane for a straight-in approach to runway 18 at 5K1. He noted that the approach was too high and too fast. During the landing, the airplane departed the runway to the left. The airplane came to rest upright in a flat soybean field. The experimental canard airplane sustained substantial damage to the fuselage, the right wing, and the right canard. Postaccident examination found the fuel system to be intact, and the two wing fuel tanks were found to be more than half full. A fuel sample did not reveal any contamination. According to the pilot, there is no fuel selector valve assembly installed, only a fuel cutoff control. The two wing fuel tanks feed into a single header fuel tank. The airplane was recovered from the accident site, and it was transported to a secure location for future examination. The composite airplane was built from a kit in 1998. A review of FAA records showed that the pilot purchased the airplane in May 2008. The airplane was equipped with a Lycoming Engines IO-360-C1D6 reciprocating engine and a MT-Propeller MTV-18-B/LD168-101 controllable pitch three blade wood-composite propeller. A review of the airplane’s maintenance records showed that a condition inspection was performed by a mechanic on February 15, 2026, for the airframe, the engine, and the propeller. The airplane accumulated 23.7 hours since the condition inspection.
Verbatim NTSB factual narrative from the NTSB dataset
Sources
NTSB record CEN26LA283
- Event ID
- 20260810203562
- Case number
- CEN26LA283
- 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: 6cabd91ee4ece7da9b23584845828210dbb184fbee6b00122c2c4679bd36fefe; retrieved 2026-09-17T05:23:29.009Z.