A Kalitta Air cargo jet scraped its tail against the runway while attempting to land at Cincinnati/Northern Kentucky International Airport on the evening of July 19, 2026, forcing the crew to abort the approach and circle back for a second landing. The Boeing 777-300ER, operating as Flight 264 with registration N778CK, had departed Brussels Airport and was completing a transatlantic cargo run when the tail strike occurred. The aircraft landed safely at about 8:15 p.m. local time, and no injuries were reported, but the incident has raised pointed questions about what went wrong during the final moments of approach and why federal investigators have yet to assign a formal case number.
Why the Kalitta Air tail strike demands closer scrutiny
A tail strike during a go-around is not a routine event. When a pilot aborts a landing and applies full power to climb away, the aircraft pitches nose-up sharply. On a long-fuselage jet like the 777-300ER, the geometry leaves very little room between the tail and the pavement. If the aircraft is already in a high sink rate or the pitch rotation is too aggressive, the tail can contact the runway surface before the jet gains enough altitude to clear it. That sequence appears to match what happened to N778CK over Covington, Kentucky, based on the federal record describing the event.
The FAA classified the event as an incident involving a Boeing freighter conducting cargo operations. That designation sits below “accident” in severity but still triggers mandatory reporting and review. A tail strike can compromise the rear pressure bulkhead, and any structural damage to that section of a widebody freighter can ground the aircraft for weeks of inspection and repair. For Kalitta Air, a Michigan-based cargo carrier that operates 777 freighters on long-haul routes, even a single aircraft out of service can disrupt contract schedules.
Tail strikes on large jets also carry long-term safety implications beyond the immediate flight. If damage to the rear fuselage goes undetected or is improperly repaired, it can weaken the structure around the pressurized cabin and cargo holds. In past cases involving other operators and aircraft types, latent damage in this area has been linked to serious structural failures years after the original incident. This is why regulators generally treat such events as more than minor scrapes, even when the crew lands safely and no one is hurt.
FAA records and the missing NTSB case file
Two separate FAA databases confirm the core facts. The agency’s public statement on aviation incidents identifies the flight as Kalitta Air Flight 264, a Boeing 777-300ER that departed Brussels and whose tail scraped the runway during a go-around before landing safely at about 8:15 p.m. local time on Sunday, July 19, 2026. A parallel entry in the FAA’s Aviation Safety Information Analysis and Sharing system, created July 20, 2026, lists the same aircraft by registration N778CK, records the location as Covington, Kentucky, and describes the event in plain terms: the aircraft experienced a tail strike while attempting to land and executed a go-around. The flight activity field reads “CARGO.”
A second FAA-hosted view of the same incident record corroborates the narrative description word for word, providing an additional archival confirmation of the event details. Both entries classify the event type as “INCIDENT” rather than “ACCIDENT,” a distinction that affects the scope and speed of any federal investigation. An incident label generally suggests that regulators do not yet see evidence of serious injuries or substantial damage that would automatically trigger a higher-level response.
What stands out is the absence of a corresponding entry in the National Transportation Safety Board’s investigation database. A search of the NTSB’s Docket Management System and its aviation query portal returns no assigned investigation number for the July 19 tail strike as of the current date. The NTSB is not required to investigate every FAA-classified incident, but tail strikes on widebody jets often warrant at least a preliminary factual report. The gap between the FAA’s prompt documentation and the NTSB’s silence creates an information vacuum around the cause and severity of the event.
That vacuum has practical consequences. Without an NTSB case, there is no public timeline for when more detailed information might emerge, such as a synopsis of the flight’s final approach or a summary of any structural inspections. For airport communities and cargo customers, it becomes harder to assess whether the event points to a one-off crew error, a procedural issue, or a broader operational risk that could recur.
Critical gaps in the Kalitta Air Flight 264 record
Several pieces of evidence that would normally clarify a tail strike’s cause are not yet public. No air traffic control transcripts from the approach have surfaced. No flight data recorder readout showing the aircraft’s sink rate, pitch angle, or airspeed on short final has been released. No pilot statement or crew report has appeared in any federal database. And no statement from Kalitta Air or the Cincinnati/Northern Kentucky airport authority has addressed the incident publicly.
Without those records, the specific chain of events that led the 777’s tail to contact the runway remains a matter of informed inference rather than confirmed fact. One plausible sequence, consistent with known tail-strike patterns on the 777-300ER, involves a high sink rate on short final that exceeded the aircraft’s tail clearance margin during the go-around pitch-up. The 777-300ER has one of the longest fuselages in commercial aviation, and its tail clearance during rotation is measured in single-digit degrees. A delayed go-around decision, combined with a steep descent profile or gusty conditions, could close that margin to zero. But confirming or ruling out this scenario requires data that only the flight recorders and crew debriefs can provide.
Other scenarios cannot be excluded. Automation mode confusion, for example, can leave a heavy jet temporarily misconfigured for the actual approach path, especially if last-minute changes to runway assignment or glidepath intercept occur. Sudden wind shear close to the ground can also force pilots into aggressive pitch changes that narrow the tail clearance margin. In each case, investigators would normally reconstruct the flight using recorded parameters to determine whether crew actions, environmental factors, or aircraft systems played the dominant role.
There are also open questions about the extent of any damage to N778CK. The FAA incident summaries do not specify whether the aircraft sustained structural harm or only superficial scraping to the tail skid or lower fuselage. In the absence of an NTSB docket, there is no public record of post-flight inspections, repair work, or the length of time the aircraft remained out of service. For a cargo operator whose business depends on tight schedules and high aircraft utilization, these details matter both operationally and financially.
Why transparency on this incident matters
Kalitta Air Flight 264 ended without injuries or an emergency evacuation, and the crew successfully brought the jet back for a second landing. That outcome should not obscure the fact that a tail strike on a fully loaded long-haul freighter represents a serious close call. The combination of heavy weight, long fuselage, and low altitude leaves little margin for error. When such an event occurs at a major cargo hub, the lessons learned can inform training, procedures, and infrastructure planning across the industry.
Greater transparency from both regulators and the operator would help close the current gaps. A brief factual summary from the NTSB, even if it stops short of a full narrative report, could outline the basic circumstances of the approach and go-around. Kalitta Air could indicate whether the aircraft suffered structural damage and what corrective actions, if any, it has taken in response. The airport authority could clarify whether runway conditions, lighting, or navigation aids played any role. None of these disclosures requires assigning blame; they simply provide context.
In the meantime, the FAA’s incident records are the only official window into what happened above Covington that Sunday evening. They confirm that a heavily loaded Boeing 777-300ER, operating as a cargo flight from Brussels, struck its tail on the runway during a go-around and landed safely minutes later. Until investigators release more detailed findings-or explain why such findings will not be pursued-the July 19 tail strike will remain a case study in how much, and how little, the public can learn about a serious but non-fatal aviation event.
More from Morning Overview
*This article was researched with the help of AI, with human editors creating the final content.
