ERA17FA074 · Independent Technologies Inc EPIC LT
Independent Technologies Inc EPIC LT · Accident: loss of control in flight on approach
From Millington-Memphis Airport (NQA) to Spruce Creek Airport (7FL6)
Event
- NTSB case
- ERA17FA074
- 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
Independent Technologies Inc EPIC LT
- Aircraft type
- Independent Technologies EPIC LT
- 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
- N669WR
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Millington-Memphis Airport (NQA), Millington, TNTo Spruce Creek Airport (7FL6), Port Orange, FL
- Aircraft age
- About 7 years (built 2009)
- 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 · IFR missed approach
- 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 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
- Substantial
Cause areas
- Aircraft › Aircraft oper/perf/capability
- Environmental issues › Conditions/weather/phenomena
- Personnel issues › Psychological
- Personnel issues › Task performance
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
The private pilot obtained a full weather briefing before departing on a long cross-country flight. The destination airport was forecast to be under visual meteorological conditions, but there was an AIRMET and Center Weather Advisory (CWA) issued for low instrument flight rules (IFR) conditions later that day. The briefer told the pilot to check the weather again en route to see if the AIRMET and CWA had been updated. At the time the pilot stopped for fuel, another CWA was issued for low IFR conditions at his destination airport; however, there were no records to indicate that the pilot obtained this information during the fuel stop or after departing on the last leg of the flight.
A review of air traffic control communications revealed that, about 10 minutes before arriving at the airport, the pilot reported that he had obtained the current weather conditions at his destination airport. The most recent observation, about 1 hour before the accident indicated good visibility; however, the weather reporting equipment did not provide ceiling heights. It is unknown if the pilot obtained weather information from nearby airports, which were reporting low instrument meteorological conditions (visibility between 1/4 and 1/2 mile and ceilings 200-300 ft above ground level [agl]). Additionally, three pilot reports (PIREPs) describing the poor weather conditions were filed within the hour before the accident. The controller did not relay the PIREPs or the CWA information to the pilot, so the pilot was likely unaware of the deteriorating conditions.
Based on radar information and statements from witnesses, the pilot's approach to the airport was unstabilized. He descended below the minimum descent altitude of 440 ft, and, after breaking through the fog about 100 ft agl, the airplane reentered the fog and completed a 360° right turn near the approach end of the runway, during which its altitude varied from 100 ft to 300 ft. The airplane then climbed to an altitude about 800 ft before radar contact was lost near the accident site. The airplane came to rest inverted, consistent with one witness's statement that it descended through the clouds in a spin before impact; postaccident examination revealed no preimpact anomalies with the airplane or engine that would have precluded normal operation. Although the pilot was instrument rated, his recent instrument experience could not be established.
The circumstances of the accident, including the restricted visibility conditions and the pilot's maneuvering of the airplane before the impact, are consistent with a spatial disorientation event. It is likely that the pilot experienced a loss of control due to spatial disorientation, which resulted in an aerodynamic stall and spin.
Probable cause
The pilot's loss of airplane control due to spatial disorientation, which resulted in the exceedance of the airplane's critical angle of attack and an aerodynamic stall/spin. Contributing to the accident was the pilot's failure to fly a stabilized approach consistent with the published instrument approach procedure.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record ERA17FA074
- Event ID
- 20161227X85755
- Case number
- ERA17FA074
- 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: 4117dc3fbc213453ddb1e356ad063b7ee5a10951568ccb8c3e9038d92d7cdbb0; retrieved 2026-09-14T22:04:50.983Z.