Connect with us

Regulations & Safety

NTSB Report Details Altitude Deviation in Epic E1000 Crash

NTSB preliminary report finds Epic E1000 turboprop descended below minimum altitude before fatal crash near Steamboat Springs, Colorado.

Published

on

This article is based on the preliminary investigation report released by the National Transportation Safety Board (NTSB) regarding the incident involving N98FK.

NTSB Preliminary Report Reveals Altitude Deviation in Fatal Epic E1000 Crash

The National Transportation Safety Board (NTSB) has released its preliminary report regarding the fatal crash of an Epic E1000 turboprop near Steamboat Springs, Colorado. The accident, which occurred on February 13, 2026, claimed the lives of the pilot and three passengers. The investigation’s initial findings suggest the aircraft was flying a stable descent profile but was operating below the required minimum altitude for that segment of the approach prior to impacting terrain.

This incident marks a significant event in general aviation as it appears to be the first fatal hull loss involving the certified production model of the Epic E1000. Previous accidents involving this airframe type were limited to the experimental “LT” kit-built versions. While the preliminary report offers factual data gathered shortly after the accident, it does not yet determine a probable cause, a conclusion that typically requires 12 to 24 months of analysis.

Flight Trajectory and Impact Details

According to the NTSB, the flight originated in Nashville, Tennessee, and made a scheduled fuel stop at Kansas City Charles B. Wheeler Downtown Airport (KMKC) before departing for Bob Adams Airport (KSBS) in Steamboat Springs. The aircraft, registered as N98FK, was conducting an Instrument Flight Rules (IFR) approach to Runway 32 shortly after midnight local time.

Altitude Discrepancies

Flight track data recovered by investigators indicates that the aircraft was established on the RNAV (GPS)-Z approach. However, the data reveals a critical deviation from the published approach procedures. The report notes that the aircraft crossed the waypoint WDCHK at approximately 9,025 feet Mean Sea Level (MSL).

For this specific segment of the approach, the published Minimum Descent Altitude (MDA) is 9,100 feet MSL. The aircraft was roughly 75 feet below the required floor for that sector. The descent rate was recorded as steady, approximately 1,000 feet per minute, with no sudden maneuvers or distress calls transmitted by the pilot, suggesting a controlled flight profile up until the moment of impact.

Collision with Terrain

The aircraft impacted the south-facing slope of Emerald Mountain (also known locally as Quarry Mountain) at an elevation of approximately 8,250 feet MSL. The mountain, located about three nautical miles south of the destination airport, has a summit elevation between 8,200 and 8,300 feet. The impact point suggests the aircraft did not level off at the required altitude to clear the terrain obstacles in the final approach path.

Operational Environment and Infrastructure

The investigation has highlighted several environmental and infrastructural factors that may have complicated the night approach into the mountainous region.

Compromised Visual Aids

At the time of the accident, Notices to Air Missions (NOTAMs) indicated that critical visual landing aids for Runway 32 were out of service. Specifically, the Runway End Identifier Lights (REILs) and the Precision Approach Path Indicator (PAPI) were inoperative. The PAPI system is particularly vital for night operations in mountainous terrain, as it provides pilots with visual vertical guidance to ensure they remain on a safe glide path clear of obstacles.

Weather Conditions

Meteorological reports from the time of the crash indicate that conditions were technically Visual Flight Rules (VFR), though visibility was variable due to cloud layers. Visibility was reported between 5 and 10 statute miles. The NTSB noted scattered clouds at 500 feet Above Ground Level (AGL), broken layers between 2,400 and 2,600 feet AGL, and an overcast layer at 4,100 feet AGL. Winds were reported as light and variable.

Aircraft and Victim Identification

The aircraft involved was a 2024 model Epic E1000, a high-performance single-engine turboprop powered by a Pratt & Whitney PT6A-67A engine. It was equipped with the Garmin G1000 NXi avionics suite, a modern system that typically includes synthetic vision and terrain awareness capabilities.

Local authorities in Routt County identified the four victims as residents of the Franklin, Tennessee area. They included the pilot and owner, Aaron Stokes (47), his son Jakson Stokes (21), his nephew Colin Stokes (21), and family friend Austin Huskey (37). There were no survivors.

AirPro News Analysis

The Risks of Night Approaches in Mountainous Terrain

While the NTSB has not yet assigned cause, the factual evidence presented in the preliminary report aligns with the profile of a Controlled Flight Into Terrain (CFIT) event. In CFIT accidents, a mechanically sound aircraft is flown inadvertently into the ground, often due to a loss of situational awareness.

The absence of the PAPI system is a critical detail. Without visual vertical guidance, pilots flying at night into “black hole” conditions, where few ground lights exist to provide depth perception, must rely strictly on their altimeters and approach charts. The “step-down” nature of the approach into Steamboat Springs requires precise adherence to altitude floors at specific waypoints. The data showing the aircraft below the MDA at the WDCHK waypoint suggests a possible premature descent or a failure to level off, a common precursor to CFIT in complex terrain.

Frequently Asked Questions

What is a Preliminary Report?
A preliminary report is an initial release of factual information gathered by the NTSB shortly after an accident. It details the “what” and “where” but does not analyze the “why.” It does not determine probable cause.

When will the final report be released?
The NTSB typically takes between 12 and 24 months to complete a full investigation and issue a final report with a probable cause determination.

Was the aircraft equipped with terrain warning systems?
Yes, the Epic E1000 is equipped with the Garmin G1000 NXi suite, which includes terrain awareness features. Investigators will likely analyze why these systems did not prevent the collision, or if the warnings were not perceived.

Sources

Photo Credit: Aviation Safety Network

Continue Reading
Click to comment

Leave a Reply

Regulations & Safety

NTSB: Thermal Plugs Caused AA Flight 3023 Tire Failure

NTSB determines melted thermal relief plugs caused tire failure on American Airlines 737-8 at Denver, triggering emergency evacuation.

Published

on

The National Transportation Safety Board (NTSB) has determined that melted thermal relief plugs caused the left main landing gear tires to fail on an American Airlines Boeing 737-8 during a July 2025 takeoff roll at Denver International Airport (DEN), prompting a high-speed rejected takeoff and emergency evacuation.

The final aviation investigation report, published on August 26, 2026, officially closes the inquiry into American Airlines Flight 3023. The document details the mechanical sequence that led to the tire failure while highlighting significant passenger noncompliance during the subsequent evacuation, as travelers ignored crew commands and retrieved carry-on baggage.

Mechanical sequence and rejected takeoff

The incident occurred on July 26, 2025, involving a Boeing 737-8, registration N306SW, equipped with CFM International LEAP-1B28 engines. According to the NTSB, the flight experienced an approximate 25-minute delay while awaiting departure at runway 34L.

During the subsequent takeoff roll, as the aircraft reached an indicated airspeed between 90 and 100 knots, the captain reported hearing a loud pop accompanied by a noticeable bump. The flight crew initiated a rejected takeoff at speeds above 80 knots.

The NTSB determined the probable cause of the incident was the melting of thermal relief plugs in the left main landing gear. This melting released tire pressure and caused the tires and wheels to fail during the takeoff roll. The agency noted that this failure resulted in abnormal airplane handling characteristics, which prompted the flight crew to reject the takeoff. Debris from the fractured wheels caused minor damage to the aircraft, including a three-inch dent on the lower skin of the left wing.

Emergency evacuation and passenger behavior

Following the rejected takeoff, the flight crew initially instructed the cabin to remain seated. Between 30 and 45 seconds later, after identifying smoke and fire originating from the left main landing gear, the crew ordered an emergency evacuation.

The aircraft carried 175 occupants, comprising 169 passengers and six crew members. The NTSB final report confirms that zero injuries occurred during the event. This official casualty figure supersedes preliminary media reports from July 2025 that had indicated minor injuries and hospital evaluations.

The investigation report draws specific attention to passenger behavior during the emergency egress. The NTSB stated that the cabin crew described the evacuation as rapid but hindered by significant passenger confusion and noncompliance. Despite flight attendants repeatedly commanding passengers to leave their belongings behind, multiple individuals retrieved their carry-on baggage. The NTSB concluded that this noncompliance directly slowed the flow of egress from the aircraft.

AirPro News analysis

The NTSB findings regarding American Airlines Flight 3023 add to a well-documented and growing safety concern within the commercial aviation sector. Passenger retrieval of carry-on baggage during emergency evacuations is a recurring issue that compromises the 90-second evacuation standard mandated by the Federal Aviation Administration (FAA).

When passengers stop to open overhead bins and carry luggage down escape slides, they not only slow the egress rate for those behind them but also introduce the risk of puncturing the evacuation slides or injuring fellow passengers. We continue to see official accident reports cite passenger noncompliance as a negative factor in evacuation efficiency. This recurring behavioral pattern has prompted safety advocates and lawmakers to question whether current FAA evacuation certification tests, which rely on compliant participants, accurately reflect real-world human behavior during an emergency.

Sources: National Transportation Safety Board

Photo Credit: National Transportation Safety Board

Continue Reading

Regulations & Safety

Marine One Loss of Separation at DCA: NTSB Preliminary Report

NTSB cites radio line-of-sight failure after Marine One and Envoy Air E-170 came within 0.82 NM at Reagan National.

Published

on

This is a developing story. Information may change as official details are released.

This is original reporting and analysis by AirPro News.

A loss of separation occurred on August 4, 2026, between a Sikorsky VH-3D operating as Marine One and an Envoy Air Embraer E-170 departing Ronald Reagan Washington National Airport (DCA). The incident took place approximately two miles north of the airport at 14:34 EDT and prompted an immediate Federal Aviation Administration (FAA) relocation of radio equipment after investigators identified a communication failure.

According to a preliminary report released on August 27, 2026, by the National Transportation Safety Board (NTSB), air traffic controllers at DCA did not receive a required three-minute pre-departure warning from the helicopter. The event triggered a review of strict Safety protocols implemented following a fatal midair collision in the same airspace in January 2025.

Incident timeline and separation data

The loss of separation occurred when Marine One departed The Ellipse simultaneously with Envoy Air flight 3742 departing runway 1 at DCA. Preliminary FAA estimates indicate the aircraft came within 0.82 nautical miles (NM) laterally and 700 feet vertically. The NTSB is currently analyzing surveillance data to establish the exact closest point of approach.

President Donald Trump was on board the Sikorsky VH-3D at the time of the incident. In a statement provided to CBS News, White House spokesman Kush Desai confirmed the President was never in danger.

Marine One flights are piloted by the finest aviators in the world, and the White House maintains the utmost confidence in these patriots and other security officials who are responsible for ensuring the President’s safety.

No injuries were reported among the occupants of either aircraft, and both flights continued to their respective destinations without further incident.

Communication failure and FAA response

The NTSB preliminary report points to inadequate radio line-of-sight coverage between The Ellipse and the DCA tower as the primary factor in the missed pre-departure warning. A DCA tower controller reported that the transmission attempt from the helicopter was “broken and unreadable,” according to CBS News.

Following the August 4 incident, FAA technicians evaluated the infrastructure and confirmed the line-of-sight deficiency. To resolve the issue, the agency relocated the helicopter-control radio equipment to the top of the DCA control tower. Subsequent communication checks were successful.

CBS News also reported that recent construction at the White House may have contributed to the radio line-of-sight degradation, though the NTSB has not yet issued a final determination on the cause.

Regulatory context and prior airspace changes

The airspace surrounding DCA operates under highly specific procedural rules designed to deconflict fixed-wing airline traffic from frequent VIP helicopter movements. These procedures were significantly tightened following a fatal midair collision on January 29, 2025, involving an airliner and an Army Black Hawk helicopter near the airport.

Following the 2025 accident, regulators instituted a requirement for a ground stop at DCA anytime a Helicopters passes on a conflicting route. The failure of the three-minute warning on August 4 prevented controllers from initiating this required ground stop for the Envoy Air departure.

Air traffic controllers and Marine One pilots had previously met on July 28, 2026, exactly one week prior to the incident, to discuss ongoing communication challenges in the sector.

AirPro News analysis

The August 4 loss of separation highlights the fragility of procedural deconfliction in the Washington, D.C. airspace. While the FAA characterized the event as a momentary loss of separation, the failure of a critical communication link reveals a single point of failure in the safety protocols established after the 2025 collision. We note that the rapid relocation of the radio equipment by the FAA demonstrates an acknowledgment of the infrastructure gap. As the NTSB continues its Investigation, we will monitor the docket for potential systemic recommendations regarding how VIP helicopter movements integrate with high-volume Commercial-Aircraft traffic at DCA, particularly concerning redundant communication systems.

Sources: National Transportation Safety Board

Photo Credit: National Transportation Safety Board

Continue Reading

Regulations & Safety

FAA Moves to Fire Two LaGuardia Controllers After Fatal Collision

FAA initiates termination proceedings against two LaGuardia controllers for early shift departures on the night of the March 22, 2026 runway collision.

Published

on

This is a developing story. Information may change as official details are released.

This article summarizes reporting by Reuters by David Shepardson and Doyinsola Oladipo.

The FAA has initiated termination proceedings against two air traffic controllers accused of leaving their shifts early on the night of a fatal runway collision at LaGuardia Airport (LGA) in March 2026. The agency is classifying the unauthorized early departures as timecard fraud amid a broader national crackdown on the practice.

The disciplinary action follows the March 22, 2026, accident in which Air Canada Express Flight 8646, operated by Jazz Aviation LP, collided with an aircraft rescue firefighting (ARFF) vehicle while landing on Runway 4. According to Reuters, the two controllers allegedly departed the facility approximately one hour before their scheduled shifts ended, a practice colloquially known as an “early shove.”

Disciplinary actions and union response

The FAA stated its commitment to holding employees accountable, emphasizing that it will not compromise the safety or efficiency of the national airspace system. U.S. Secretary of Transportation Sean Duffy condemned the practice, stating that while most controllers complete their full shifts, the department will not tolerate fraud from individuals who unfairly burden their colleagues and impact the airspace.

The National Air Traffic Controllers Association (NATCA) confirmed it is actively discussing the allegations with FAA leadership. The union indicated that these internal discussions are the appropriate forum for addressing the matter. Reuters reports that the FAA is currently conducting a nationwide enforcement effort targeting employees who leave on break at the end of their shifts and fail to return.

The March 22 collision and investigation

The NTSB continues to investigate the March 22 collision under investigation ID DCA26MA161. The official cause of the accident remains undetermined. The aircraft involved was an MHI RJ Aviation CRJ-900, and the ground equipment was an Oshkosh Striker 1500 ARFF vehicle.

Official NTSB figures confirm that 76 people were on board the aircraft, including 72 passengers, two flight attendants, and two pilots. The captain and first officer sustained fatal injuries. Thirty-nine individuals were transported to local hospitals, with six reported to have serious injuries.

It remains unverified whether the controllers’ early departure directly influenced the events leading to the collision. Speaking in March 2026, NTSB Chair Jennifer Homendy noted that operating with two controllers in the tower cab during a midnight shift is common practice across the national airspace system, suggesting the facility may have been operating at standard staffing levels at the time of the accident.

Regulatory response to surface safety

Following the LaGuardia accident, the FAA accelerated initiatives to improve surface visibility at airports. On May 13, 2026, the agency announced a $16.5 million investment to equip all airport vehicles with transponders.

These vehicle movement area transponders (VMATs) are designed to provide ATC with better situational awareness of ground equipment operating on runways and taxiways.

AirPro News analysis

We note that the FAA’s decision to pursue termination for timecard fraud rather than operational errors highlights a strict administrative approach to facility management. By focusing on the unauthorized absence, the agency addresses the “early shove” culture directly without preempting the NTSB’s ongoing safety investigation into the collision’s root causes. The distinction between administrative violations and operational fault will likely remain a focal point as NATCA engages with FAA leadership.

Sources: Reuters, NTSB

Photo Credit: Mike Segar – Reuters

Continue Reading
Every coffee directly supports the work behind the headlines.

Support AirPro News!

Advertisement

Follow Us

newsletter

Latest

Categories

Tags

Every coffee directly supports the work behind the headlines.

Support AirPro News!

Popular News