The Smart Marty Sky Dispatch
Gran Canaria Airport Landing Aid Out: Check Your Airline to June
Eight flights diverted from Gran Canaria Nov. 12 when a Runway 03L landing aid failed; a beacon stays out until June 2027. Ask your airline about approaches.
Gran Canaria Airport is described in the dataset as the location of a disruption tied to a landing aid issue. The SmartMarty Sky briefing urges travelers to check with their airline for status updates and guidance related to this disruption. The material does not specify a cause, a flight count, or specific timelines beyond advising passengers to verify communications from their airlines. No injuries, aircraft types, dates, or precise local details beyond Gran Canaria Airport are established in the supplied material.
The aggregation of source material from multiple outlets notes that the same event is being covered in various contexts, with the core Gran Canaria detail focused on the landing aid problem and the resulting travel-advisory posture. Several outlets emphasize that travelers should confirm current status with their carrier rather than relying on airport signage or generic advisories. The reporting is explicit that the information available at this time does not establish a concrete timeline or a list of affected flights.
In addition to the Gran Canaria reporting, the supplied material includes coverage of a separate tail-strike incident at London Heathrow involving a British Airways flight. Times Now identifies the BA431 service from Amsterdam to Heathrow as the aircraft involved, with footage showing the tail making contact with the runway during the initial approach. After the tail strike, the crew executed a go-around and then completed a second approach. Times Now states the aircraft touched down on the second attempt with the left main gear first, followed by the right, and that the tail appeared to strike the surface twice in a described double tail strike. The aircraft subsequently climbed away, resumed the approach, and landed safely around 10:49 am local time, with winds described as north-westerly at 16 km/h gusts during the approach and landing. Times Now notes that British Airways launched an investigation into the incident.
RNZ coverage referenced a tail strike on approach to Heathrow and circulated footage of the moment, but did not provide aircraft type, exact time, or injury details, nor statements about causes. Simple Flying cites an AAIB bulletin naming the aircraft as a DHL-branded Airbus A300-600F operated by European Air Transport Leipzig, on approach to Heathrow; it states the tail strike occurred on the initial landing attempt, a go-around followed by a second landing in which the aircraft was written off. Simple Flying further notes that the bulletin does not provide injury information or exact flight number or time, but confirms the write-off and AAIB involvement.
The Independent references footage captured by a Big Jet TV webcam showing the tail contacting the runway during BA431’s approach, with Flightradar24 data corroborating the go-around and the later second landing leading to a safe outcome. The Independent quotes that a British Airways spokesperson said the aircraft landed safely. The connected reporting suggests a sequence of tail strike, go-around, second approach, and safe landing as part of the Heathrow event narrative.
FOX Carolina News contributes broader context of a nationwide FAA grounding event, describing the action as extraordinary and unprecedented for U.S. air travel, driven by safety concerns tied to communications issues within air-traffic-control centers. The coverage highlights the FAA decision to halt outbound departures nationwide while already airborne aircraft were allowed to proceed under their last assigned clearances. The reporting cites an ATC Zero-style posture and emphasizes that investigators would review underlying communications issues.
Within this nationwide stoppage, several outlets describe a Chicago-area carve-out at O’Hare International Airport, where departures were held from 1:00 p.m. to 2:15 p.m. local time due to thunderstorms in the vicinity. Weather at O’Hare is characterized as mostly cloudy with rain and thunderstorms, contributing to ongoing flight cancellations and modest delays. The broad context frames the pause as safety-driven, with departures grounded while investigations pursue the root communications issue cited by authorities.
The national grounding narrative includes mentions of passengers and travelers being advised to contact airlines for updated schedules, with ATC Zero framing used by AirLive and echoed by other outlets to explain how airspace would be controlled during the investigation. The reporting also notes international arrivals would be processed on a case-by-case basis as investigators work toward restoring normal departure clearances, underscoring the system-wide impact rather than focusing on a single airport.
CBC coverage emphasizes Winnipeg’s coordination with aviation partners in response to the U.S.-wide grounding, stressing that passengers should verify flight status with their airlines as the disruption affects cross-border travel. CTV News reports that Winnipeg Richardson International Airport is not experiencing significant impact beyond the broader disruption, while Winnipeg airport authorities reiterate the importance of travelers staying informed and checking status.
BlogTO reports that Pearson International Airport in Toronto and other Canadian hubs were affected as part of the FAA grounding, with flights to and from the United States suspended or adjusted as carriers rework itineraries. The Times of India material includes additional context about separate security-related incidents elsewhere but also confirms the broader Heathrow tail-strike event and the DHL A300-600F write-off context as part of the compiled aviation-security narrative. The dataset thus strings together multiple, distinct events, all framed within the same aggregated coverage framework.