approach phase Archives - Aviation Today

Colorado Plane Crash Kills 4 Onboard Near Steamboat, All Victims Identified By Police

Aviation Today News Desk / February 16, 2026

Steamboat Springs, United States: A private single-engine aircraft crashed into mountainous terrain near Steamboat Springs in the early hours of […]

Galveston, United States: New federal investigative findings reveal critical communication misunderstandings and extremely limited visibility as major factors immediately preceding the December 22, 2025, crash of a Mexican Navy medical flight in Galveston Bay that killed six people and left two seriously injured, according to the preliminary report released by the U.S. National Transportation Safety Board (NTSB). The Beechcraft B300 aircraft, registered ANX1209 and operated by the Mexican Navy, was on a humanitarian medical mission coordinated with the Michou y Mau Foundation. The flight was transporting a severely burned pediatric patient from Mérida, Mexico, to Shriners Children’s Hospital in Galveston, Texas, when it crashed into West Bay during its approach to Scholes International Airport shortly before 3:15 p.m. local time. According to the NTSB preliminary report, Houston Approach Control cleared the flight crew for an RNAV (GPS-based) approach to Runway 14 but did not clear the aircraft to land. The flight crew’s initial readback mistakenly stated they were “cleared to land,” prompting controllers to twice clarify that the aircraft was cleared only for the approach and not for landing. Controllers then directed the crew to contact the tower. Despite repeated clarifications, the crew’s responses indicated persistent misunderstanding. During the final stages of the approach, air traffic controllers issued multiple low-altitude alerts, but received no further communication from the flight crew before radar contact was lost. The preliminary report and weather observations confirmed dense fog and severely restricted visibility during the aircraft’s final descent. Controllers advised the crew that cloud ceilings near the airport were approximately 300 feet, a condition that significantly limits visual reference and places heavy reliance on instrument procedures. Local weather data and witness accounts indicate visibility at times was as low as approximately a quarter mile with heavy sea fog common along the Texas Gulf Coast under certain conditions further complicating the approach. The aircraft impacted the waters of West Galveston Bay approximately half a mile from the shoreline. Six occupants including the pilot, co-pilot, two flight crew members and two passengers were fatally injured. Two passengers, reported to be a flight nurse and the mother of the pediatric patient, survived with serious injuries. Search and rescue operations immediately following the crash involved the U.S. Coast Guard, Texas Department of Public Safety, Galveston County Sheriff’s Office and local first responders. The wreckage was located in shallow water, facilitating recovery efforts. The NTSB’s preliminary report is part of an ongoing investigation to determine all contributing factors. These factual reports do not assign probable cause but document the circumstances surrounding the accident based on available data, including air traffic control communications and radar information. Federal investigators will continue to analyze cockpit voice recordings, flight data, maintenance records and meteorological data. A final report typically released 12–24 months after an accident will include a probable cause determination and safety recommendations aimed at preventing similar tragedies.

Investigation

NTSB Preliminary Report Cites Miscommunication, Low Visibility In Galveston Bay Crash

Aviation Today News Desk / February 5, 2026

Galveston, United States: New federal investigative findings reveal critical communication misunderstandings and extremely limited visibility as major factors immediately preceding

Muscat, Oman: A Turkish Airlines flight from Istanbul to Muscat International Airport (MCT) became the centre of an unusual aviation exchange on Sunday when the aircraft’s flight crew and Muscat air traffic control (ATC) disagreed over a descent clearance during the approach phase. The Airbus A321neo was being vectored for an Instrument Landing System (ILS) approach when Muscat ATC instructed the crew to descend to 2,200 feet, identified by controllers as a minimum safe altitude suitable for sequencing and terrain clearance in that segment of airspace. The pilot responded that the airline’s company-approved navigation charts did not list 2,200 feet as an acceptable minimum altitude in that sector and that his flight crew could only descend to 3,600 feet in accordance with their procedures and published minimum vectoring altitudes (MVAs). In recorded ATC transmissions that have circulated within aviation safety analysis communities, the exchange became tense as the pilot repeatedly stated he was “unable to accept vectors” below the charted limit. The controller, while asserting that “our minimum safe altitude is 2,200,” urged the flight crew to comply with ATC instructions. Despite the firm tone in radio exchanges, both sides maintained professional conduct, and the disagreement did not escalate into an unsafe operational situation. The pilot proposed alternative vectors that would allow the aircraft to remain at or above 3,600 feet while aligning for the approach sequence. Minimum vectoring altitude and minimum safe altitude figures are critical safety parameters that provide required terrain and obstacle clearance during radar vectoring. Air traffic controllers and pilots derive these altitudes from different sources controllers from their local surveillance and obstacle databases, and pilots from company-approved charts often supplied by third-party aeronautical data providers. International aviation regulations and standard operating procedures emphasise that the pilot in command retains ultimate responsibility for the safety of the aircraft. When an ATC-issued clearance conflicts with a pilot’s verified safety limits, the flight crew may lawfully decline and request clarification or alternative instructions. The Turkish Airlines aircraft remained at or above the altitude the crew could accept until it was safely established on the final approach. There were no reported safety incidents, and the flight landed without further operational disruption.

Incidents

Turkish Airlines Pilot Disputes Descent Clearance With Muscat ATC, Flight Lands Safely

Aviation Today News Desk / December 29, 2025

Muscat, Oman: A Turkish Airlines flight from Istanbul to Muscat International Airport (MCT) became the centre of an unusual aviation

approach phase

Colorado Plane Crash Kills 4 Onboard Near Steamboat, All Victims Identified By Police

NTSB Preliminary Report Cites Miscommunication, Low Visibility In Galveston Bay Crash

Turkish Airlines Pilot Disputes Descent Clearance With Muscat ATC, Flight Lands Safely

Follow Us

Quick Links

Navigate

General Support

News Desk Support

Follow Us