CHI97LA238 · Velocity VELOCITY ELITE RG VELOCITY E
Velocity VELOCITY ELITE RG VELOCITY E · Accident: loss of control on ground/water during landing
From JS4 · SASKATCHEWAN to Grand Forks International Airport (GFK)
Event
- NTSB case
- CHI97LA238
- 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
Velocity VELOCITY ELITE RG VELOCITY E
- Aircraft type
- Velocity ELITE 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
- CGPNX
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From JS4 · SASKATCHEWANTo Grand Forks International Airport (GFK), GRANKD FORKS, ND
- 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 · landing roll
- 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 › Directional control, not maintained
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
According to the pilot, the winds along the route were from 240 degrees at 20-30 knots, and '...all airports in the vicinity that had fuel, had a runway (paved) heading of 32/14.' Devils Lake, 42 nautical miles southwest of Langdon, was reporting winds from 230 at 11 knots at about the time of the accident. The pilot elected to land at Robertson Field on runway 32 to refuel. During the landing roll, the airplane skidded off the right side of the runway, striking a taxiway sign located 100 feet prior to the departure end of runway 32. According to a witness, the airplane landed long and fast, then skidded in a tight circle before coming to rest. The pilot added in his report that he 'could not hold plane on runway or stop quickly enough.'
Probable cause
failure of the pilot to maintain directional control during the landing roll. The crosswind and proximity of the taxiway sign were related factors.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record CHI97LA238
- Event ID
- 20001208X08347
- Case number
- CHI97LA238
- 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: cc6c0810315c9eaea2d63076caa047b496a900606c1ef8e2acd2a745f367c89c; retrieved 2026-09-22T18:57:19.693Z.