ERA16FA074 · Hinton Paul M RV 4
Hinton Paul M RV 4 · Accident: VFR encounter with IMC en route
From Orlando Apopka Airport (X04) to Tallahassee International Airport (TLH)
Event
- NTSB case
- ERA16FA074
- 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
Hinton Paul M RV 4
- Aircraft type
- Hinton Paul RV-4
- 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
- N77BP
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Orlando Apopka Airport (X04), Apopka, FLTo Tallahassee International Airport (TLH), Tallahassee, FL
- Aircraft age
- About 20 years (built 1995)
- 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
- VFR encounter with 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
- Aircraft › Aircraft oper/perf/capability
- Personnel issues › Action/decision
- Personnel issues › Psychological
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
The airline transport pilot, who was a US Navy flight instructor and newly certificated civilian flight instructor, was flying his cousin to his home base where he planned to provide her with initial flight training. He received a weather briefing earlier in the day, and the briefer indicated that visual flight rules (VFR) flight was not recommended due to instrument meteorological conditions (IMC) at the surface. Despite the briefer's statement, the pilot indicated he planned on remaining VFR throughout the flight.
Before taking off for the accident flight, during ground operations, the pilot discussed the weather with a former flight service station pilot weather briefer, who told the pilot that the weather was "really bad" in the direction of the pilot's destination, and the pilot agreed, yet he chose to depart anyway. He reported that the pilot appeared to be "in a hurry." No evidence was found indicating that the pilot received any additional weather briefing information before taking off for the accident flight.
The flight departed to the northwest toward an approaching cold front. The conditions associated with the front included low clouds and mist. As the pilot proceeded toward his destination, the flight encountered the front, and the pilot declared an emergency with air traffic control (ATC), stating that he was in instrument flight rules (IFR) conditions and that his airplane was "not capable of IFR." Radar data of the final segment of the flight showed the airplane in a left, 180-degree turn for 43 seconds, immediately followed by a right, 90-degree turn for 37 seconds before radar and radio contact was lost. The last radar return was observed at an altitude of about 1,200 ft mean sea level.
The wreckage was located about 0.2 nautical mile southeast of the last radar return. Forward-to-aft crushing signatures to the wreckage, damage to adjacent trees, and the lack of a linear wreckage debris path were consistent with a near-vertical, nose-low attitude at impact. An examination of the airframe and engine did not reveal any evidence of a preimpact anomaly or malfunction, and the pilot did not report any mechanical issues to ATC. According to the airplane builder and Federal Aviation Administration records, the airplane was not approved for flight in IMC.
The low visibility conditions that existed during the flight, which was conducted at night in instrument conditions, were conducive to the development of spatial disorientation. Further, the pilot's actions and responses and the airplane's turning ground track and near-vertical descent were consistent with the pilot losing airplane control due to spatial disorientation. The pilot should not have initiated the flight into a known approaching cold front in an airplane not equipped for IMC flight, and this decision directly led to the accident.
Probable cause
The pilot's decision to initiate the flight into known adverse weather conditions, in an airplane that was not approved for instrument flight, which resulted in an encounter with instrument meteorological conditions and his subsequent spatial disorientation and loss of airplane control.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record ERA16FA074
- Event ID
- 20151218X21206
- Case number
- ERA16FA074
- 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: local date, investigation status. Values present in the bulk record are kept.
- The date is the local date; the NTSB stores the UTC date 2015-12-18.
- API snapshot SHA-256: eefcd2e4e4c186cfecb4d90268666a125d03d27a3f119faa95e5179b9af49089; retrieved 2026-09-14T21:35:49.279Z.