Regulations & Safety
NTSB Urges FAA to Update Runway Condition Assessment Matrix for Heavy Rain
NTSB recommends FAA revise runway condition assessments and expand rainfall reporting after 11 runway overruns linked to heavy rain from 2008 to 2022.

This article is based on an official press release from the National Transportation Safety Board (NTSB).
On May 26, 2026, the National Transportation Safety Board (NTSB) issued a press release urging the Federal Aviation Administration (FAA) to overhaul how runway conditions are assessed during heavy rainfall. The safety board warns that the current framework leaves flight crews vulnerable to runway overruns by failing to capture the true impact of severe weather on aircraft braking performance.
Stemming from investigations into 11 runway overrun accidents and incidents that occurred on wet runways between 2008 and 2022, the NTSB has issued three new safety recommendations. These directives focus on updating the Runway Condition Assessment Matrix (RCAM) and expanding aviation weather reporting standards to better equip pilots with accurate data.
According to the NTSB, the current system fails to adequately account for the progressive loss of wheel braking friction as rainfall intensity increases. This creates a critical blind spot for pilots and dispatchers when calculating safe landing distances during intense storms.
The Limitations of Current Weather Reporting and RCAM
The RCAM is a standardized framework utilized by airport operators and flight crews to evaluate and report runway surface conditions. As noted in the NTSB release, it plays a vital role in calculating required landing distances, particularly on wet or contaminated runways.
However, the NTSB’s Aviation Investigation Report 26-04 (AIR-26-04), titled “Accounting for the Progressive Decrease in Runway Friction Associated with Increasing Rainfall Intensity,” highlights a significant flaw. The current matrix does not factor in the progressive decrease in runway friction that correlates with heavier rainfall.
Expanding Rainfall Descriptors
Currently, aviation weather reports cap the “heavy rain” threshold at 0.3 inches per hour. The NTSB points out that this limitation prevents flight crews from accurately assessing runway slipperiness when rainfall exceeds this rate.
To address this, the NTSB recommends that the FAA add new rainfall intensity descriptors to aviation weather reports. This would allow pilots to identify rainfall rates that surpass the 0.3 inches per hour mark, enabling more accurate landing distance calculations and better aeronautical decision-making.
Case Study: Miami Air International Flight 293
The NTSB’s recommendations are heavily informed by historical data, notably the crash of Miami Air International Flight 293. On May 3, 2019, a Boeing 737-81Q carrying 142 passengers and crew overran ungrooved runway 10 at Jacksonville Naval Air Station in Florida, coming to rest in the shallow waters of the St. Johns River.
While there were no serious injuries, the aircraft sustained substantial damage. The NTSB investigation determined that the probable cause was directly linked to the runway conditions and the intensity of the precipitation.
Extreme Conditions and Pilot Decision-Making
Crucially, the NTSB found that rainfall intensities during the Miami Air incident were two to eight times higher than the FAA’s heavy rain threshold of 0.3 inches per hour.
“an extreme loss of braking friction due to heavy rain and the water depth on the ungrooved runway, which resulted in viscous hydroplaning”
In its official report, the NTSB attributed the above cause to the Jacksonville overrun. The safety board noted that under such extreme conditions, braking effectiveness is reduced so severely that pilots should not even attempt to land.
NTSB’s Three Core Recommendations
Based on these findings, the NTSB has formally issued three safety recommendations to the FAA to mitigate future risks and improve operational safety.
First, the FAA must revise the RCAM to account for the progressive decrease in the wheel braking friction coefficient associated with increasing rainfall intensity. The NTSB advises that progressively higher rainfall intensities should correspond to progressively lower runway condition codes.
Second, as previously noted, the FAA should expand rainfall intensity descriptors in aviation weather reports to capture data beyond the current 0.3 inches per hour maximum.
Third, the NTSB emphasizes the need to improve flight crew awareness. By providing a broader range of descriptors, pilots will be better equipped to associate heavy rainfall with lower runway condition codes, preventing the dangerous underestimation of required landing distances.
AirPro News analysis
We view these recommendations as a necessary and overdue evolution in aviation safety protocols. If the FAA adopts these changes, it will fundamentally alter how pilots and dispatchers calculate landing performance during severe weather events, likely leading to an increase in weather-related diversions but a significant decrease in runway excursions.
The NTSB’s findings underscore that pilots are currently forced to make critical landing decisions based on incomplete weather data. Providing accurate descriptors for extreme rain will empower flight crews to confidently divert flights rather than risk a catastrophic runway overrun. Furthermore, the specific mention of an “ungrooved runway” in the Miami Air case highlights the ongoing need for airports to evaluate their infrastructure. The interaction between pavement types (grooved versus ungrooved) and heavy rainfall remains a critical variable in RCAM calculations that airport operators must prioritize.
Frequently Asked Questions (FAQ)
What is the RCAM?
The Runway Condition Assessment Matrix (RCAM) is a standardized framework used by airport operators and flight crews to assess and report runway surface conditions. It is essential for calculating safe landing distances.
Why is the NTSB recommending changes to the RCAM?
The NTSB found that the current RCAM and weather reporting standards do not adequately account for the progressive loss of braking friction during rainfall that exceeds 0.3 inches per hour, leading pilots to underestimate required landing distances.
How many accidents prompted this NTSB report?
The NTSB based its recommendations on data gathered from investigations into 11 runway overrun accidents and incidents that occurred on wet runways between 2008 and 2022.
Sources
Photo Credit: NTSB
Regulations & Safety
FAA Investigates Marine One Separation Incident Near DCA
The FAA is investigating a loss of standard separation on Aug 4, 2026, involving Marine One and Envoy Air Flight 3742 near Reagan National Airport.

This is a developing story. Information may change as official details are released.
This article summarizes reporting by Reuters, The Wall Street Journal, Forbes, The Guardian, and CNN.
The Federal Aviation Administration (FAA) is investigating a loss of standard separation incident that occurred on August 4, 2026, involving Marine One and an Envoy Air commercial flight in the airspace near Ronald Reagan Washington National Airport (DCA). The safety occurrence took place when air traffic controllers did not halt commercial departures at the airport during the presidential helicopter’s takeoff from the White House Ellipse.
The incident highlights ongoing airspace management challenges around the capital. The specific ground-stop protocol that was apparently bypassed had been implemented following a fatal mid-air collision in the same airspace in January 2025.
Timeline of the separation loss
According to air traffic control audio reported by CNN, the pilot of Marine One radioed the DCA tower at 18:31 UTC (14:31 EDT) with a departure warning. The pilot stated, “Tower, do you copy. Marine One, three minutes to lift.” The transmission was reportedly not acknowledged by the controller.
Marine One departed the Ellipse at 18:33 UTC (14:33 EDT) en route to Joint Base Andrews. One minute later, at 18:34 UTC (14:34 EDT), Envoy Air Flight 3742 departed DCA bound for Pensacola, Florida. Envoy Air is a wholly owned subsidiary of American Airlines Group Inc., and the flight was operated using an Embraer E170.
The simultaneous movements resulted in a loss of standard separation. The FAA requires a minimum separation of 1.5 nautical miles horizontally and 500 feet vertically for aircraft operating in the airspace immediately surrounding the airport.
An FAA spokesperson confirmed the investigation to Reuters, noting that while standard separation was lost, the event did not appear to be a “dangerous close call” and the two aircraft were not converging.
Airspace protocols and the 2025 collision
The airspace surrounding Washington, D.C., operates under strict security and safety regulations. Following a January 2025 mid-air collision between a U.S. Army Black Hawk helicopter and an American Airlines passenger jet that resulted in 67 fatalities, the FAA enacted heavy restrictions on mixed air traffic in the area.
A key component of these revised safety protocols requires air traffic controllers to temporarily halt all commercial flights at DCA when Marine One takes off from the White House area. The August 4 incident occurred because this specific ground-stop procedure was not executed.
AirPro News analysis
We view this incident as a critical test of the FAA’s procedural safeguards in one of the most complex airspace environments in the United States. The failure to execute a mandatory ground stop, despite a direct radio warning from the Marine One crew, raises questions regarding controller workload management and inter-facility communication.
While the FAA has stated the aircraft were not on converging flight paths, the breakdown of a protocol designed specifically to prevent a repeat of the 2025 disaster will likely draw intense scrutiny from lawmakers and independent safety investigators. The focus will now shift to understanding why the DCA tower did not acknowledge the presidential helicopter’s departure notification and why the commercial clearance was not canceled.
Sources: Reuters
Photo Credit: U.S. Naval Institute
Regulations & Safety
Air India A320neo Drops 300 Feet, 12 Hospitalized
An Air India A320neo lost 300 feet during cruise on Aug 4, 2026, hospitalizing 12. DGCA launches formal investigation.

This is a developing story. Information may change as official details are released.
Twelve people were hospitalized after an Air India (AI) Airbus A320neo experienced a sudden 300-foot altitude drop during cruise flight from Phuket to New Delhi on August 4, 2026.
The Directorate General of Civil Aviation (DGCA) has launched a formal investigation into the occurrence. According to a press release from the Ministry of Civil Aviation (MoCA), Flight AI2379 encountered severe turbulence, prompting an immediate medical response upon its safe landing at Indira Gandhi International Airport (DEL).
In-flight occurrence and medical response
The aircraft, an Airbus A320neo registered as VT-EXO, was carrying 137 passengers, including three infants, alongside eight crew members. During the cruise phase of the flight, the aircraft experienced what the airline described as a momentary change in altitude. Preliminary reports from the DGCA indicate the aircraft lost approximately 300 feet of altitude during the turbulence event.
Following the aircraft’s safe arrival in New Delhi, medical teams evaluated the occupants. The MoCA confirmed that eight passengers and four cabin crew members required admission to local hospitals for further treatment.
Union Civil Aviation Minister Ram Mohan Naidu stated that he directed authorities to provide medical updates on each patient every two hours, adding that he instructed the DGCA to “initiate a detailed investigation into the occurrence.” The MoCA further noted that passenger safety remains the highest priority and that all necessary measures are being taken to support the injured.
Regulatory investigation
The DGCA immediately initiated a detailed investigation into the turbulence encounter. As part of the standard investigative protocol, authorities have secured the aircraft’s Flight Data Recorder (FDR) and Cockpit Voice Recorder (CVR) to analyze the flight parameters and crew response during the altitude variation.
An Air India spokesperson confirmed the event, stating that Flight AI2379 encountered a “brief in-flight turbulence-related event during cruise” on August 4, which caused the altitude drop. The airline noted that the aircraft landed without further incident and all occupants safely disembarked before medical personnel intervened.
AirPro News analysis
While the official cause of the altitude variation remains under investigation by the DGCA, severe turbulence encounters during cruise highlight ongoing operational challenges for flight crews navigating complex weather systems. We note that securing the FDR and CVR is a routine but critical step that will allow investigators to determine the exact meteorological conditions and the aerodynamic performance of the Airbus A320neo during the 300-foot descent. The high ratio of cabin crew injuries relative to the total crew complement underscores the occupational risks flight attendants face during sudden in-flight disturbances.
Sources: Ministry of Civil Aviation
Photo Credit: Air India
Regulations & Safety
FAA Mandates Radio Altimeter Upgrades for 5G Interference
FAA final rule requires 5G-resistant radio altimeters by 2030-2034. FCC rebate offsets costs for domestic operators facing up to $120K per aircraft.

The Federal Aviation Administration (FAA) has published a final rule requiring operators to upgrade or replace aircraft radio altimeters to withstand interference from 5G wireless telecommunications. The mandate, published in the Federal Register on July 31, 2026, is paired with a Federal Communications Commission (FCC) rebate program designed to help domestic operators offset the substantial costs of the required equipment changes.
According to a press release issued by the National Business Aviation Association (NBAA), the rule addresses long-standing safety concerns regarding the expansion of wireless networks into the 3.98-4.2 GHz Upper C-band. The radio altimeter provides critical height-above-terrain data for low-visibility landings and automated safety systems. The coordinated interagency approach provides the aviation industry with a phased compliance timeline extending through 2034.
Fleet impact and compliance deadlines
The FAA mandate applies to flight operations within the 48 contiguous United States and the District of Columbia. The agency established a tiered compliance schedule based on operation type. Commercial-Aircraft airlines operating under Part 121 must equip their aircraft with compliant radio altimeters by December 30, 2030. Operators flying under Part 135 and specific Part 91 business aviation regulations have until October 31, 2034, to meet the new standards.
The scale of the required retrofits is extensive. The NBAA estimates that 58,500 radio altimeters across the United States fleet will require replacement or modification. Reporting by Aviation Week indicates that the upgrades will cost between $80,000 and $120,000 per aircraft. Across the entire affected civil aviation fleet, total equipage costs are projected to reach between $4.8 billion and $7.2 billion.
Financial relief through FCC rebates
To mitigate the financial impact on aircraft operators, the FCC adopted a rebate framework on July 22, 2026, funded by proceeds from wireless spectrum auctions. The program will reimburse eligible domestic operators for the costs associated with hardening their radio altimeters against 5G interference.
NBAA Vice President of Air Traffic Services and Infrastructure Heidi Williams praised the interagency coordination that led to the funding mechanism.
“Radio altimeter modifications or replacements can represent a substantial, unplanned expense, and ensuring that all affected operators have access to this funding will help accelerate equipage, support compliance and preserve access to the nation’s aviation system,” Williams stated.
Williams also noted that the rebate program is a vital component of the mandate and a clear win for business aviation operators. The NBAA plans to host a dedicated educational session regarding the radio altimeter mandate at the NBAA Business Aviation Convention & Exhibition (NBAA-BACE) on October 20, 2026.
While domestic operators will benefit from the FCC funding, foreign operators are excluded from the rebate program. According to Aviation Week, international carriers must bear the full cost of upgrading their aircraft to maintain access to United States airspace.
AirPro News analysis
The publication of this final rule brings regulatory certainty to an issue that has generated significant friction between the aviation and telecommunications sectors. By aligning the Part 121 compliance deadline of December 30, 2030, with the FCC schedule for permitting new wireless services in the 75 largest United States markets, regulators have avoided the immediate operational disruptions that characterized early 5G rollouts.
We view the FCC rebate program as a critical pressure release valve for domestic operators facing billions in collective upgrade costs. However, the exclusion of foreign operators creates a bifurcated financial landscape. International airlines flying into the United States will absorb the full $80,000 to $120,000 per-aircraft cost, which could influence fleet deployment decisions for routes serving the contiguous United States over the next decade.
Photo Credit: NBAA
-
Regulations & Safety5 days agoICON Aircraft Launches ICON Sense Amphibious Safety System
-
Route Development7 days agoWashington Dulles Airport $20 Billion Overhaul Announced
-
Aircraft Orders & Deliveries3 days agoYakovlev MC-21-310 Completes Maiden Flight at Irkutsk Plant
-
Technology & Innovation4 days agoCosmic Aerospace Unveils Cosmic One Under FAA MOSAIC Rules
-
Technology & Innovation6 days agoAir India, SkyDrive and Suzuki Sign eVTOL Medical Logistics MoU
