N4889R

Destroyed
Fatal

Vans RV9S/N: 90421

Accident Details

Date
Sunday, September 13, 2020
NTSB Number
ERA20LA315
Location
Steinhatchee, FL
Event ID
20200913X12433
Coordinates
29.700000, -83.516670
Aircraft Damage
Destroyed
Highest Injury
Fatal
Fatalities
2
Serious Injuries
0
Minor Injuries
0
Uninjured
0
Total Aboard
2

Probable Cause and Findings

The failure of the air traffic controller to provide hazardous weather information to the pilot, resulting in the flight’s encounter with strong updraft conditions, an inflight loss of airplane control, and an in-flight breakup. Contributing was the pilot’s decision to initiate a flight into an area under the influence of a tropical storm, with forecast rain showers and thunderstorms, which increased the potential for an encounter with significant convective weather

Aircraft Information

Registration
N4889R
Make
VANS
Serial Number
90421
Engine Type
Reciprocating
Year Built
2003
Model / ICAO
RV9RV9
Aircraft Type
Fixed Wing Single Engine
No. of Engines
1

Registered Owner (Historical)

Name
SCARFO ROMAN E
Address
3139 CLAUDE LN
Status
Deregistered
City
SARASOTA
State / Zip Code
FL 34234-7905
Country
United States

Analysis

HISTORY OF FLIGHTOn September 13, 2020, about 1215 eastern daylight time (EDT), an experimental amateur-built Van’s RV-9A, N4889R, was destroyed when it was involved in an accident near Steinhatchee, Florida. The pilot and a student pilot-certificated passenger were fatally injured. The airplane was operated as a Title 14 Code of Federal Regulations Part 91 personal flight.

The flight departed Jack Edwards Field (JKA), Gulf Shores, Alabama, about 1003 under an instrument flight rules flight plan with the destination of Ocala International Airport (OCF), Ocala, Florida. At 1149, during the cruise portion of the flight, the pilot requested to divert to Cross City Airport (CTY), Cross City, Florida due to weather.

At 1154:23, the pilot first contacted the Jacksonville, FL (ZJX) Air Route Traffic Control Center sector 13 controller while level at 9,000 ft above mean sea level (msl) and requested the RNAV (GPS)-A approach to CTY. At 1155:15, the sector 13 controller asked the pilot, “and ah eight niner romeo just confirm you wanted the RNAV runway three one.” The pilot responded, “un ah negative ah eight niner ah romeo we would like the RNAV Alpha into Cross City.” At 1155:32, the sector 13 controller acknowledged the pilot and cleared the flight direct to the initial approach fix, UGLUF. The pilot read back the clearance.

At 1204:03, the sector 13 controller instructed the pilot of N4889R to “cross UGLUF at or above three thousand, cleared RNAV Alpha into ah Cross City.” The pilot responded, “Alright ah cross ah UGLUF at ah above ah three thousand cleared for the ah RNAV Alpha into Cross City eight niner romeo.” The controller did not provide any weather information to the pilot, including the local altimeter setting, radar-depicted precipitation, weather advisories, or current CTY weather.

According to automatic dependent surveillance broadcast (ADS-B) data, at 1214:13 the airplane was in a left turn to the north, directly into an area of precipitation, with a Mode C reported altitude of 6,500 feet msl. The last ADS-B target was at 1214:27 at a reported altitude of 6,100 feet msl, as the airplane was in a left, descending spiral. At 1218:09, the sector 13 controller transmitted, “november eight niner romeo ah radar contact lost ah say position.” The pilot did not respond.

PERSONNEL INFORMATIONThe pilot’s logbook(s) was not located after the accident, and no flight time was entered on the pilot’s latest Federal Aviation Administration (FAA) medical certificate application.

The student pilot-certificated passenger’s logbook was not located after the accident; his total flight time was derived from his latest FAA medical certificate application, dated July 31, 2018.

AIRCRAFT INFORMATIONThe aircraft and engine logbooks were not located after the accident; inspection information was obtained from the mechanic who performed the latest condition inspection.

METEOROLOGICAL INFORMATIONAt the time of the accident, Tropical Storm Sally was located in the eastern Gulf of Mexico with bands of rain showers and thunderstorms rotating counter-clockwise around it. The accident airplane flew directly into one of the building spiral rain bands, as evidenced by the growing radar reflectivity signatures. The area penetrated by the airplane included moderate to heavy precipitation. In addition, high-resolution rapid refresh (HRRR) sounding indicated an unstable environment with the potential for strong updrafts on the order of ~12,000 ft/minute.

The accident site and surrounding area were covered by center weather advisories (CWAs), issued at 1051 and 1159, respectively. These advisories warned of an area of scattered moderate to heavy rain showers and thunderstorms moving northward. The rain shower and thunderstorm area was expected to gradually increase in size and intensity over the Gulf of Mexico waters during the period. The 1159 CWA (about 16 minutes prior to the accident) was not broadcast by the ZJX sector 13 controller for the accident pilot’s awareness. Also, an AIRMET was valid for moderate turbulence below 12,000 ft.

The pilot received a weather briefing through ForeFlight at 0730 on the morning of the accident. The briefing contained all the standard imagery valid at the accident time and provided a forecast that thunderstorms and rain showers would be scattered to numerous (between 30% and 100% chance) around the destination airport and the accident site at the proposed landing time. The Terminal Aerodrome Forecast information for the proposed route of flight (via ForeFlight) also warned of the potential rain shower and thunderstorm conditions. Even though the CWAs were issued after departure, the accident region was covered by Convective SIGMET outlook areas and an ongoing convective SIGMET for just east of the proposed destination location.

Consolidated Storm Prediction for Aviation (CoSPA) images were retrieved for 1200, 1210, 1215, and 1220. The data showed that rain shower activity was moving from southeast to northwest with time and growing in areal coverage. Also, the accident site was located within an area of projected rain shower or thunderstorm growth from 1210 onward. This data would have been available to the ZJX controllers as a reference.

FAA Order JO 7110.65Y, Air Traffic Control, includes air traffic control procedures and phraseology pertaining to weather for use by personnel providing air traffic control services. The ZJX sector 13 controller did not issue the local altimeter setting per section 2-7-2c, and she did not issue radar depicted precipitation per section 2-6-4. The ZJX sector 13 controller did not provide pertinent CWAs to the pilot per section 2-6-6. The ZJX sector 13 controller did not provide local CTY weather per sections 2-1-2 and 4-7-10, and she did not ask for or provide pilot reports, or PIREPS, per section 2-6-2.

AIRPORT INFORMATIONThe aircraft and engine logbooks were not located after the accident; inspection information was obtained from the mechanic who performed the latest condition inspection.

WRECKAGE AND IMPACT INFORMATIONThe wreckage was located by local authorities in shallow water, about 1 nm offshore, and about 21 nm west-northwest of CTY. The main wreckage, consisting of the forward fuselage, engine, propeller, and landing gear, was located about 0.34 nm northwest of the last ADS-B target. The separated left wing was located about 290 ft west of the main wreckage. The separated right wing was located about 482 ft northwest of the main wreckage. Parts of the empennage were located about 1,300 ft west-northwest of the main wreckage. Many of the recovered parts were found floating; therefore, drift from their original positions was probable.

After recovery from the water, the wreckage was transported to a storage facility for further examination by an NTSB air safety investigator.

Fuselage

The fuselage separated at the cockpit area, forward of the cockpit seats, and was continuous aft to the area where it was separated at the empennage. The aft fuselage structure was crushed in a downward direction. The right seat lap belt and shoulder harness were in place and unbuckled. The left seat lap belt was attached to structure on the left-wing aft spar carry-though. The left seat shoulder harness was missing. Neither cockpit seat was located. The windscreen and canopy were not located.

The forward fuselage consisted of the main spar carry-through structure, main landing gear, engine firewall, engine, propeller, and nose landing gear. The rudder cables remained attached to the rudder assembly; the right seat pedals were separated and missing. The elevator pushrod was connected to the control yoke assembly and extended aft. The flight control tubes from the cockpit to the empennage were separated and missing; therefore, control continuity to the empennage could not be confirmed.

Left Wing

The left wing was separated from the fuselage and was generally intact; the separation occurred at the wing root. The fracture surfaces of the main spar caps exhibited overload signatures. There was minimal bending of the spar caps at the fracture points. There was not any noticeable permanent bending of the main spar along its length. Bending on the spar mating surfaces in the fuselage was consistent with an up and aft failure mode. The left aileron remained attached to the wing by its hardware. The outer edges of the aileron were bent down. Control continuity was confirmed from the control surface through the pushrod to the break at the wing root. The tubular pushrod fracture exhibited overstress signatures. The left flap was found in the retracted position.

Right Wing

The right wing exhibited more impact damage than the left wing. The main spar fractured about 12 in from the wing root. The bending of the spar was consistent with an aft-and-down direction at the time of failure. The leading edge of the right wing exhibited an up-and-aft bending signature; the origin of the damage was not evident. The fracture surfaces of the main spar caps exhibited overload signatures. The aileron was separated from the wing; the outboard 1 ft was missing. The inboard 4 ft of flap were separated from the main wing structure. Flight control continuity to the aileron could not be confirmed due to the impact damage.

Empennage

The vertical stabilizer separated from the tail cone at the base. The rudder remained attached to the vertical stabilizer. The lower 12 inches of the rudder was missing. The upper 16 inches of the rudder, including the counterweight, was folded over 180º to the left. The leading edge of the vertical stabilizer exhibited no significant impact damage. There was a diagonal bend at the forward left side of the vertical stabilizer, about 14 inches long.

The left horizontal stabilizer was separated and intact. There was no evidence of impact damage to the leading edge of the stabilizer. The outboard 40 inches of the upper surface of the left elevator was torn ...

Data Source

Data provided by the National Transportation Safety Board (NTSB). For more information on this event, visit the NTSB Records Search website. NTSB# ERA20LA315