SEA06FA116 · Lciv LLC Lancair IV-P Propjet
Lciv LLC Lancair IV-P Propjet · Accident: in flight collision with terrain/water on approach
From St George Regional Airport (SGU) to Provo Municipal Airport (PVU)
Event
- NTSB case
- SEA06FA116
- 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
- 3 · 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
Lciv LLC Lancair IV-P Propjet
- Aircraft type
- Lciv LANCAIR IV-P PROPJET
- 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
- N95CE
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From St George Regional Airport (SGU), St. George, UTTo Provo Municipal Airport (PVU), Provo, UT
- 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
- Approach · VFR pattern final
- 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 collision with terrain/water
- 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 › Altitude/clearance, not maintained
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
After reporting the airport in sight and canceling an IFR flight plan, the pilot was executing a visual approach to an airport located on the shore of a lake during dark night visual meteorological conditions. The final approach path was over the lake. About 50 seconds before the accident occurred, the airplane was aligned for landing on runway 13 and was approximately 1.5 miles from the threshold, about 750 feet agl, at an indicated airspeed of 210 knots, and a descent rate of 1,900 feet per minute (fpm). Twelve seconds later, the airplane began a right turn. The airplane continued to turn right until it impacted the water on a heading of about 332 degrees, at an indicated airspeed of 123 knots, and a descent rate of 1,300 fpm. Examination of the wreckage confirmed that the airplane impacted the water in a right wing low attitude. No evidence of any mechanical discrepancies was found. Scattered very heavy and intense thunderstorms were located north through east of the accident location. No convective showers or thunderstorms were in the vicinity of the airplane when it crashed. Several cloud layers were present over the destination airport around the accident time. The amount and layers of low cloudiness make it unlikely that the pilot was able to maintain visual contact with the airport during his approach to the field. At the time the airplane turned right off the final approach course, it was at approximately the altitude of the lowest cloud layer. The pilot had completed a familiarization course in the airplane the day before the accident. The course consisted of about 30 hours of ground instruction and 18 hours of flight instruction. The course flight time was the pilot's total flight experience in this make and model of airplane. The instructor who provided the training reported that during the course he twice discussed with the pilot a list of pilot limitations to be adhered to following course completion. These limitations included no flights in IMC until the pilot had a minimum of 100 hours in make and model and no night flights until the pilot had a minimum of 50 hours in make and model.
Probable cause
The pilot's failure to maintain altitude/clearance during a VFR approach, which resulted in an in-flight collision with water. Contributing factors were the dark night light conditions and the low clouds.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record SEA06FA116
- Event ID
- 20060616X00749
- Case number
- SEA06FA116
- 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: local date, investigation status, coordinates. Values present in the bulk record are kept.
- The date is the local date; the NTSB stores the UTC date 2006-06-09.
- API snapshot SHA-256: 451a470238e1469d34727ba5b20aa9dbee7aedc7ed2c6a1b4e68d0bef80e7a2c; retrieved 2026-09-20T17:18:17.523Z.