Friday, February 27, 2026

Epic E1000, N98FK, fatal accident occurred on February 13, 2026, near Steamboat Springs Airport (SBS/KSBS), Steamboat Springs, Colorado

  • Location: Steamboat Springs, CO 
  • Accident Number: CEN26FA115 
  • Date & Time: February 13, 2026, 00:19 Local 
  • Registration: N98FK 
  • Aircraft: Epic E1000 
  • Injuries: 4 Fatal 
  • Flight Conducted Under: Part 91: General aviation - Personal

https://data.ntsb.gov/carol-repgen/api/Aviation/ReportMain/GenerateNewestReport/202430/pdf

https://registry.faa.gov/AircraftInquiry/Search/NNumberResult?nNumberTxt=N98FK

On February 13, 2026, about 0019 mountain standard time, an Epic E1000 airplane, N98FK, was substantially damaged when it was involved in an accident near Steamboat Springs, Colorado. The pilot and three passengers were fatally injured. The airplane was operated as a Title 14 Code of Federal Regulations Part 91 personal flight.

According to on-board data collected at the accident site, the airplane departed from John C. Tune Airport (JWN), Nashville, Tennessee, about 1910 central standard time to Steamboat Springs Airport/Bob Adams Field (SBS), Steamboat Springs, Colorado, with a fuel stop in Kansas City Downtown Airport-Wheeler Field (MKC), Kansas City, Missouri. The airplane landed at MKC about 2053, was refueled, and departed to SBS about 2303.

According to preliminary air traffic control data, the pilot was given vectors to TILLI, which is the initial approach fix for both the RNAV Z RWY 32 approach and the RNAV – E approach to SBS. The controller cleared the pilot for the RNAV approach to SBS. The pilot acknowledged the clearance but replied, “RNAV 32 to Steamboat Springs.” The controller approved a frequency change to the SBS common traffic advisory frequency to which the pilot acknowledged. No further communications were received from the pilot. An Alert Notice was issued, and a subsequent search for the wreckage was initiated.

The wreckage was located in mountainous terrain about 3 miles south of SBS at an elevation of about 8,200 ft mean sea level (msl). A ground scar was found about 80 ft south of the main wreckage at an elevation of about 8,175 ft msl. The mountain peak is about 8,250 ft msl. The initial impact ground scars were aligned on an estimated 340° true heading. An odor consistent with jet fuel was present at the scene. Postaccident examination of the engine and airframe found no preimpact anomalies that would have precluded normal operation. 

According to the Garmin G1000 data, the engine was producing about 1,700 propeller rpm (Np) and 92% gas generator speed (Ng). All recorded engine parameters were consistent with normal engine operation at the time of the accident. About 100 gallons of fuel remained at the time of the accident. The waypoints in the data were consistent with the RNAV Z RWY 32 approach. The minimum descent altitude for the approach is 9,100 ft msl. The last recorded altitude for the airplane was 8,221 ft msl, and the airplane’s autopilot was engaged.

The RNAV Z 32 approach plate lists that the approach, both the circling and straight-in to runway 32, is not authorized at night. Additionally, the approach plate lists “Visual Segment – Obstacles.”

A review of SBS meteorological aerodrome reports revealed a report issued four minutes before the accident. At 0015, the wind was calm, visibility was 10 statute miles, and scattered clouds were reported 500 ft above ground level (agl), broken clouds 1,600 ft agl, and overcast clouds 2,400 ft agl. Data from FAA weather cameras installed at SBS was collected for further review.

According to FAA airman and operator records, the pilot held a commercial pilot certificate for airplane single-engine land with an instrument rating. He was issued a first-class medical certificate on October 22, 2025, and on the medical application, the airman reported 1,150 total flight hours.

At the time of the accident, there were two Notice to Airmen (NOTAMs) issued for SBS. One listed the runway end identifier lights (REIL) for runway 32 unusable. The other listed the Precision Approach Path Indicator (PAPI) lights for runway 32 unusable. 

The wreckage was retained for further examination.

Cessna 182G Skylane, N515CL, accident occurred on February 16, 2026, at Richards Field Airport (04FA), Homestead, Florida

  • Location: Quail Heights, FL 
  • Accident Number: ERA26LA116 
  • Date & Time: February 16, 2026, 10:20 Local 
  • Registration: N515CL 
  • Aircraft: Cessna 182G 
  • Injuries: 3 None 
  • Flight Conducted Under: Part 91: General aviation - Personal

https://data.ntsb.gov/carol-repgen/api/Aviation/ReportMain/GenerateNewestReport/202440/pdf

https://registry.faa.gov/AircraftInquiry/Search/NNumberResult?nNumberTxt=N515CL

On February 16, 2026, at 1020 eastern standard time a Cessna 182G, N515CL, was substantially damaged when it was involved in an accident near Quail Heights, Florida. The pilot and two passengers were not injured. The airplane was operated as a Title 14 Code of Federal Regulations Part 91 personal flight.

The pilot reported that during the preflight inspection he added a small quantity of fuel to both wing tanks to ensure both were full, then sumped the wing tank drains and the fuel strainer, finding no contamination. Taxi out and runup were normal with no anomalies noted. Shortly after takeoff, the engine lost all power. The pilot decided to return to the airport and conducted a downwind landing opposite the direction of departure. After touchdown, he was unable to stop the airplane, and it overran the runway and subsequently impacted trees. The left wing and fuselage sustained substantial damage.

Post accident examination by the NTSB and FAA found no visible damage to the engine. Engine control continuity was established. Fuel was observed in both wing tanks, the carburetor bowl, and the fuel strainer, which also contained a small amount of particulate contamination. The upper spark plugs were removed and several exhibited sooting on the electrodes.

The wreckage was retained for further examination.

Cessna 182S Skylane, N7276V, accident occurred on February 21, 2026, at Table Rock Airport (MO32), Golden, Missouri

This is preliminary information, subject to change, and may contain errors. Any errors in this report will be corrected when the final report has been completed.

https://registry.faa.gov/AircraftInquiry/Search/NNumberResult?nNumberTxt=N7276V

https://data.ntsb.gov/carol-repgen/api/Aviation/ReportMain/GenerateNewestReport/202483/pdf

- History of Flight:
On February 21, 2026, at about 1131 local time, a Cessna 182S Skylane, N7276V, registered to Legends Air Center LLC, sustained substantial damage when it was accident at Table Rock Airport (MO32), Golden, Missouri. The pilot and three passengers were not injured. The cross-country personal flight originated from Bentonville Municipal Airport/Louise M Thaden Field (VBT/KVBT), Bentonville, Arkansas, and was destined to MO32.

The FAA reported: "Aircraft went off the end of the runway during landing and through a fence." The winds at the time were from 20° at 12 knots. The NTSB is investigating.

Windshear or thunderstorm: Boeing 737-7H4, N247WN, accident occurred on May 2, 2025, near Centerville, Tennessee

  • Location: Centerville, Tennessee 
  • Accident Number: DCA25LA197 
  • Date & Time: May 2, 2025, 12:00 Local 
  • Registration: N247WN Aircraft: Boeing 737 
  • Aircraft Damage: Substantial 
  • Defining Event: Windshear or thunderstorm 
  • Injuries: 149 None 
  • Flight Conducted Under: Part 121: Air carrier - Scheduled

https://data.ntsb.gov/carol-repgen/api/Aviation/ReportMain/GenerateNewestReport/200101/pdf

https://data.ntsb.gov/Docket?ProjectID=200101 

On May 2, 2025, at 1200 pm central daylight time, Southwest Airlines flight 2231 (SWA2231) encountered turbulence and hail during initial descent into Nashville International airport (BNA), Nashville, Tennessee. The flight was a regularly scheduled passenger flight from AustinBergstrom International airport (AUS) to BNA. As a result of the hail, the airplane sustained substantial damage to the leading edges of the wings and horizontal stabilizer. The flight continued to its destination without further incident.

The flight crew reported that thunderstorm activity was forecast for their arrival at BNA, and they observed weather approaching the airport using a weather application (WSI app) on their electronic flight bag (EFB). They planned and conducted a deviation to the north to avoid the weather. As the airplane passed the Memphis area, the captain asked the flight attendants to be seated early in the event of unforeseen turbulence.

Prior to the encounter, while descending from flight level (FL) 360 toward FL240, the flight had been in clear air and the flight crew could see a cloud build-up at their 1:00 o’clock position. Air Traffic Control (ATC) also advised of “a cell” at their 12:30 to 1:00 o’clock position. However, after reviewing the on-board weather radar and the WSI app on the EFB, those sources did not depict any indications of weather directly ahead of the airplane. As the descent continued, the flight crew noticed below and ahead of the airplane was a flat stratus cloud layer, with no buildups. ATC advised of moderate to extreme precipitation at their 12:30 to 1:00 position, which the crew associated with the buildup they had visually seen at their 1:00 o’clock position.

SWA2231 entered the clouds at about FL320 and initially the ride was smooth, with occasional light chop. While at a speed of 290 knots, at FL280, SWA2231 suddenly encountered precipitation and turbulence. The captain recalled that the rain was very heavy and the excessive noise caused him to suspect hail, but he was unable to verify visually. He retarded the throttles and deployed the speed brake to slow to turbulent air penetration speed. After about 1 minute the heavy precipitation ceased, and the airplane levelled off at FL240, still in instrument meteorological conditions. The flight crew reported the moderate turbulence to ATC and continued to BNA.

A review of weather records revealed that the National Weather Service’s (NWS) Aviation Weather Center had issued Convective SIGMET 99C at 1155 which was extended over the area for an area of severe embedded thunderstorms, moving from 250° at 40 knots, with maximum tops above FL450. Hail to one inch in diameter and wind gusts to 50 knots were possible with the storms. The NWS Storm Prediction Center had issued a severe thunderstorm weather watch at 0956 for a line of severe thunderstorms moving across Tennessee.

Figure 3 shows the nearest WSR-88D weather radar base reflectivity image for the for 3.12° elevation scan at 1202, with SWA2231’s flight track position overlaid at 30 second intervals. The flight passed through an area of extreme intensity echoes up to 65 dBZ at lower elevation scans and 58.5 dBZ at the airplane’s flight level. The severe hail algorithm indicated hail to 1.58 inches in the vicinity of the flight track during the period with the maximum height of the 18.5 dBZ echoes or echo tops to FL446.

Figure 4 is a software analysis cross section of the WSR-88D imagery at 1202, with the approximate flight track of SWA2231 overlaid in white and depicting the flight overflying a maximum reflectivity core of 60 dBZ and in echoes of 56.0 dBZ along the track.

The reason that the severe weather depicted in figures 3 and 4 was not depicted by the onboard weather radar system or the WSI app was not determined. The first officer did not recall the onboard radar system tilt setting(s) used at the time, and the onboard radar imagery was not recorded. The operator had no means to replicate which imagery was available to or used by the crew from the WSI app. The Federal Aviation Administration’s Aviation Weather Handbook notes the following about airborne weather radar:

The radar display also does not provide assurance of avoiding instrument weather conditions from clouds and fog. A phenomenon called attenuation (see Section 15.2.5) may exist when a cell absorbs or reflects all of the radio signals sent by the radar system (see Figure 15-5). Attenuation may prevent the radar from detecting additional cells that might lie behind the first cell. This is sometimes referred to as a radar “shadow.” For aircraft equipped with airborne weather radar, pilots are expected to be familiar with the operating techniques and limitations of the specific system.

It is important to note that while hail always gives a radar echo, it may fall several miles from the nearest visible cloud, and hazardous turbulence may extend to as much as 20 mi from the echo edge.

The severe weather may not have been depicted to the crew on their resources due to radar limitations or the specific settings of the onboard radar (such as tilt and range), rapid development and/or movement of the severe weather, latency in the data provided by the weather application, or other factor(s). There was insufficient evidence available to determine if any of these characteristics were a factor or not.

- Probable Cause: An encounter with hail during descent.

Grumman American AA-5A Cheetah, N9939U, accident occurred on February 23, 2026, near Admire, Kansas

  • Location: Admire, KS 
  • Accident Number: CEN26LA123 
  • Date & Time: February 23, 2026, 09:58 Local 
  • Registration: N9939U 
  • Aircraft: Grumman AA5 
  • Injuries: 2 None 
  • Flight Conducted Under: Part 91: General aviation - Personal

https://data.ntsb.gov/carol-repgen/api/Aviation/ReportMain/GenerateNewestReport/202486/pdf

https://registry.faa.gov/AircraftInquiry/Search/NNumberResult?nNumberTxt=N9939U

On February 23, 2026, about 0958 central standard time, a Grumman AA-5A airplane, N9939U, was substantially damaged when it was involved in an accident near Admire, Kansas. The pilot and passenger were not injured. The airplane operated under the provisions of Title 14 Code of Federal Regulations Part 91 as a personal flight.

The airplane was equipped with long-range fuel tanks and the pilot stated that on the day of the accident, he fully fueled the airplane and departed from the Ellington Airport (LUG), Lewisburg, Tennessee. Based on ADS-B data and pilot recollection, the airplane departed LUG about 0440 and flew to Kansas City Downtown Airport – Wheeler Field (MKC), Kansas City, Missouri, landing about 0825. After a brief stop, the airplane departed MKC about 0910 and headed towards Council Grove Airport (K63), Council Grove, Kansas. While the airplane was in cruise flight at 2,500 ft mean sea level, the pilot reported the engine RPM began to increase and then decrease. When the engine power began to decrease, and he switched fuel tanks, but was unable to restore engine power. He performed a forced landing to a field. During the forced landing, the landing gear collapsed, and both wings were substantially damaged.

The airplane was retained for further examination.