FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

FTW04LA004 · Colliander RV-8

6 Oct 2003 · Van, TX, United States

Colliander RV-8 · Accident: in flight encounter with weather en route

From 4F4 · Gilmer, TX to Georgetown Executive Airport at Johnny Gantt Field (GTU)

Report a problem

Event

NTSB case
FTW04LA004
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
Instrument Meteorological Cond

Colliander RV-8

Aircraft type
Colliander RV-8
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
N27JW
Operator
Unknown
Onboard fatalities
Unknown
Route
From 4F4 · Gilmer, TXTo Georgetown Executive Airport at Johnny Gantt Field (GTU), Georgetown, TX
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
In flight encounter with weather
Also codedOther events the NTSB coded in the sequence, such as a wire strike after a loss of power. Flight Findings uses them for its kinds of event. Glossary
Visual flight rules (VFR) flight into instrument meteorological conditions (IMC)
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

  • Pilot in command › Aircraft control, not maintained
  • Pilot in command › Spatial disorientation

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

NTSB narrative

The accident airplane assumed the number two position of a four airplane formation flight that departed toward Tyler, Texas and "encountered an unreported layer of clouds at approximately 1,000 feet msl." The formation flight climbed through a "hole" on top of the cloud layer, leveling off at 3,300 msl. The lead pilot reported the visibility to be approximately 5 to 7 miles with a "misty, milky white undefined layer above. The broken layer below was "well defined with lots of holes to see the ground." Northwest of Tyler, Texas, and "the undefined layer above started to come down toward the broken layer below." The formation flight turned to the right, heading northeast, then north, while still between the layers. The formation flight initiated a shallow climb "through the misty white undefined layer," turning to the west, with an "in-flight visibility of approximately five miles." The formation flight "popped through an unseen layer of clouds, then back into the same white misty mass with decent visibility." The formation flight entered "another unseen layer of thick clouds and heavy rain at 5,500 feet msl. Subsequently, the pilot of airplane number two called lost sight, followed quickly by the pilot of airplane number four. The lead pilot told both pilots to "go lost wingman as they briefed the previous day, get on the attitude indicator, and start a shallow descent." Several witnesses observed the airplane flying overhead with the "wings fluttering" and then suddenly "nose diving" into the ground. One witness reported the weather at the time of the accident to be "very low clouds, poor visibility, and a heavy rain shower that started approximately 10 minutes after the time of the accident." Weather reports obtained from Tyler, Texas reported visibility of 6 statute miles, cloud ceilings of 2,900 feet agl deteriorating to visibility of 1 1/2 statute miles and 1,000 feet broken. Doppler weather radar images indicated very strong weather echoes were present in the vicinity of Van, Texas, near the time of the accident. The non-instrument rated private pilot of airplane number two had accumulated a total of 746-hours total time, of which 18 hours were in the accident make/model aircraft.

Probable cause

The pilot's failure to maintain control of the airplane due to spatial disorientation. Contributing factors were the low ceilings, rain, and fog.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record FTW04LA004
Event ID
20031009X01690
Case number
FTW04LA004
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: 25e302b08e422567cb2cfb17013dd3eba9153e7658623239a5ad5d462aab03b7; retrieved 2026-09-20T18:54:45.430Z.