Civilian data compiles crash record before official findings

Summary

FlightAware tracking data and LiveATC.net audio supplied the public record of Heartbeat 104’s final minutes before any official account existed, making civilian observation infrastructure the accident’s de facto first compiler of evidence.
The dispatcher’s “electrical issue” relay, the loss of radio and radar, and the end of tracking data at roughly 11,000 feet narrow the cause to systems-failure mechanisms — progressive electrical loss, decompression followed by emergency descent, or electrical fire — while excluding fuel exhaustion and pilot incapacitation.
Latitude Air Ambulance’s pledge that it “will not speculate about what occurred” protects the families and the investigation while also guarding the operator’s position with insurers, regulators, and future patients.
The published account centers the operator and emergency responders, leaving the patient, the Bermudian community, and the region’s medical-evacuation chain outside the frame.

Civilian observation infrastructure assembled the public record of Heartbeat 104’s final minutes before any official account existed: FlightAware tracking data reviewed by BBC News showed the Gulfstream G-100 descending from roughly 7,300 meters to 3,300 meters, and LiveATC.net transmissions reviewed by The Boston Globe captured the air-traffic controller’s emergency-declaration exchange with the aircraft. Six people aboard the medical transport — two Canadian pilots, two Canadian medical staff, and a Bermudian patient and family escort — are presumed dead after the aircraft, operated by Canadian firm Latitude Air Ambulance, disappeared off Nantucket, Massachusetts, en route from Bermuda to Boston Logan International Airport; the United States Coast Guard ended its search Sunday evening, and the operator said the six “are presumed to have died.” The cause of the loss is not established: the cited evidence supports a family of systems-failure mechanisms — progressive electrical loss, decompression followed by emergency descent, or an electrical fire — and excludes fuel exhaustion and pilot incapacitation, without identifying an initiating event. That determination now rests with the investigation, not the public record.

What the record shows

The flight departed L.F. Wade International Airport in Bermuda at 23:40 local time Friday, bound for Boston Logan International Airport, where it was due at 01:30 EDT Saturday. The Federal Aviation Administration lost contact with the aircraft just after 01:00 EDT, roughly half an hour before the scheduled landing. The aircraft, a Gulfstream G-100 designated Heartbeat 104, was operated by Latitude Air Ambulance, a Canadian company “that provides international medical flights for patients returning home.” According to Latitude director of flight operations Clarence Togeretz, speaking to CBC News, six people were aboard: two pilots and two medical staff, Canadian nationals who had flown to Bermuda to collect a patient, and the patient and a family escort, Bermudian nationals. The operator has identified the dead by role, not by name.

FlightAware tracking data reviewed by BBC News showed the aircraft dropped from approximately 7,300 meters (24,000 feet) to 3,300 meters (11,000 feet) before communications went dark. Radio transmissions reviewed by The Boston Globe from LiveATC.net captured the air traffic controller asking: “You’re coming in blind? Is that what you said?” and then “Are you declaring an emergency, or no?” The pilot’s response was inaudible. The controller later confirmed the pilot had declared an emergency — an input that reached air traffic control through a channel that survived the degradation of the voice communications themselves. An area fire dispatcher, according to the same transmissions, asked emergency crews to prepare to meet a plane with an “electrical issue,” and shortly afterwards relayed that “the aircraft has lost radio and radar.”

On Saturday evening, authorities located a debris field confirmed to be from the aircraft. The Coast Guard ended its search the following evening — a search-and-rescue judgment about the prospects of survival, distinct from any determination of cause. Latitude said it must “now face the heartbreaking reality that the four members of our Latitude team, our patient and the patient’s family escort, who were aboard Heartbeat 104, are presumed to have died.” The company’s president, Peter Byl, said its “focus now is on supporting their families, supporting our people and assisting the authorities. We will honour our colleagues by remembering the care, professionalism, and commitment they brought to their work every day.”

What the evidence supports and excludes

On the public record, the candidate explanations sort into a family of mechanisms rather than a single cause. The three most direct evidentiary signals are the “electrical issue” relayed by the area fire dispatcher — a secondhand account, a ground dispatcher’s relay rather than the aircraft’s own words, which caps its diagnostic weight — the loss of radio and radar, and the cessation of tracking data at roughly 11,000 feet (3,300 meters).

Those three signals are consistent with a progressive loss of electrical power: voice communications degraded first, hence the controller’s “You’re coming in blind?”, and then the aircraft’s radio and radar transmitters ceased. The altitude trace is consistent with an emergency descent — a drop of approximately 4,000 meters, broadly consistent with published guidance on emergency descents after cabin-pressure loss, where supplemental oxygen becomes necessary for continued occupant consciousness. The two candidate mechanisms are not mutually exclusive: an initiating electrical event can accompany or produce a pressurization emergency, and a progressive loss of electrical power can end in smoke, fire, or total system failure. An electrical fire producing smoke and progressive system loss is a rare but serious candidate that would combine these mechanisms and is consistent with the pattern of the record.

The tracking record ends at approximately 11,000 feet; the aircraft continued past that point in silence until the debris field confirmed water impact. An electrical-or-avionics cascade is supported by the observed degradation of communications, by the “electrical issue” framing from operational dispatch, and by the preservation of pilot function sufficient to declare an emergency. The cascade hypothesis distinguishes the loss pattern from a pure pilot-incapacitation event: the simultaneous incapacitation of both flight crew members is inconsistent with the controller-confirmed emergency declaration, which requires at least one functioning pilot on the flight deck and an emergency-indicating input on a working channel. The cascade hypothesis is also inconsistent with a pure fuel-exhaustion scenario, in which the loss of communications and radar would not be predicted to precede fuel exhaustion — a sequence the dispatcher’s account does not reflect. Fuel exhaustion finds no support in the cited transmissions or tracking data: it does not predict an “electrical issue” framing from dispatch, nor communications loss preceding engine flameout. Pilot incapacitation, while not impossible in principle, is inconsistent with the controller-confirmed emergency declaration given the reported two-pilot complement. A navigation error or a controlled descent into the water sits uneasily with the preserved contact with air traffic control in the final minutes.

Structural failure or in-flight break-up remains a possibility that the electrical-failure framing might eclipse; it would predict a more rapid, uncontrolled altitude loss and a debris field distributed accordingly. No adverse-weather report appears in the cited record, though the absence of a report is not evidence that weather played no part. The null hypothesis — that the event was benign and self-resolving — is excluded by the confirmed debris field.

The public record does not currently permit a distinction between a controlled descent rate and an uncontrolled break-up. That test requires investigation material on the altitude-rate profile, debris distribution, electrical-system forensic data, and crew inputs. One counterfactual clarifies how the ranking depends on the record: if the controller’s later confirmation of the emergency declaration were absent — that is, if communications were lost before any declaration could be recorded — the evidentiary weight would shift. The electrical cascade would remain possible but weaker on pilot-function evidence; pilot incapacitation and structural failure would gain relative weight; and the controlled-versus-uncontrolled descent distinction would become the dominant analytical question. As published, the record places the declaration inside the window of partial communications, and that placement affects the ranking.

Tracking telemetry and air-traffic audio cannot resolve a cause. The evidence supports a family of systems-failure candidates and excludes a handful of alternatives; it does not identify an initiating event. On the present record, the cause of the loss is properly the investigation’s question to answer, not the public record’s.

Who investigates, and how the record took shape

Latitude Air Ambulance, as a Canadian operator, falls under Transport Canada as the state of the operator — a connection conditional on Latitude holding a Canadian air operator certificate, and falsifiable if it did not. The departure from L.F. Wade International Airport places the operation under the Bermuda Civil Aviation Authority at the origin. Operations in US airspace fall under the Federal Aviation Administration. The accident’s location in US waters places the investigative lead with the National Transportation Safety Board, with the Transportation Safety Board of Canada as the participating state of the operator — a connection falsifiable if the crash had occurred outside US waters. Each jurisdictional connection is falsifiable by a specific observation; had communications not been lost, the operational dependency between air traffic control and the aircraft would have continued.

The network around the flight forms a hub-and-spoke structure with the aircraft at the center. The logistics spokes run from L.F. Wade International Airport to Boston Logan, with the search area off Nantucket as the terminus. The response spokes are the Federal Aviation Administration, the United States Coast Guard, and the area fire and emergency crews. The corporate spoke is Latitude Air Ambulance, represented by its president, Peter Byl, and its director of flight operations, Clarence Togeretz. The observation spoke — the flight-tracking service FlightAware, the radio archive LiveATC.net, and the news organizations that relayed both — supplied the public with the evidentiary spine of the story.

The accident’s public record was compiled by passive, civilian infrastructure before any official account existed. The altitude drop and the emergency-declaration exchange that define public understanding of the event came from a flight-tracking service and an archive of air-traffic audio. That infrastructure functions as a de facto first compiler of the investigatory record: the same data will be scrutinized by the authorities and, later, by insurers and representatives of the parties. It performs a public-interest function of transparency and simultaneously raises a privacy consideration for the families, whose dead are now the subjects of a publicly reconstructed timeline. According to the FAA type-certificate record, the Gulfstream G-100 is the US-marketed variant of the IAI Astra platform; as the investigation network forms, the airframe’s manufacturer and type-certificate holder are among the parties drawn into it.

Where the consequences fall

With the cause undetermined, the distribution of consequence is necessarily provisional. Operational liability could attach to Latitude. Type-certificate implications could attach to the Gulfstream G-100’s manufacturer if a design or maintenance issue emerges. Oversight implications could attach to the Bermuda Civil Aviation Authority if departure-side procedures are implicated. Financial distribution through insurance arrangements remains a live consideration.

The cross-link that matters runs between two domains the news frame keeps apart: aviation safety and health-care access. The aircraft functioned as medical infrastructure — a piece of the logistics chain connecting a small island jurisdiction’s health system to the mainland medical network. The patient had needed to be moved offshore; the loss is simultaneously an aviation accident and an interruption in that chain. The article does not take up what the loss of this capacity means for Bermuda; measured against the story the flight tells, that absence is a fact about the frame.

The operator’s restraint — “we will not speculate about what occurred” — is a genuine public good. In aviation accidents, early speculation harms families and contaminates investigations, and the company’s pledge that its “focus now is on supporting their families, supporting our people and assisting the authorities” is the standard to which survivors expect operators to be held. The same restraint also serves institutional interests the article does not need to name. Careful formulations such as “presumed to have died” carry meaning in the registers of insurance, liability, and investigation protocol as well as in the register of grief. The discipline that protects the families also protects the operator’s position with its insurers, its regulators, and its future patients, during a period in which its reputation is an operating asset. Nothing in this observation alleges wrongdoing; the legitimate value a position serves and the distributional consequences of that position are separable, and both are visible here.

How this is being framed

The story as published is operator-and-response centered. The company’s leadership supplies the human voice — Togeretz to CBC News, Byl in a statement Sunday evening — and the Coast Guard and the FAA supply the timeline. That ordering is not arbitrary.

The parties absent from the frame are identifiable from the article’s own facts. The families of the six appear only as the objects of the company’s pledge. The patient is present only as a nationality and a role. The Bermudian community, two of whose members are dead, is present only by implication, and its medical-evacuation capacity is thinned. The patients who will need such flights after this one failed — and who fund the system indirectly through insurance — are not present. The accident-investigation authority goes unnamed in the article. The local emergency crews appear as relays of the “electrical issue” message.

Costs treated as natural in the published frame include the private losses of those families, the preparation of a reception for a plane that never came, and the resources of a search conducted to its announced end.

An alternative frame built from the patient-and-family constituency’s interests is available and equally well-formed on the same facts. It would foreground the interrupted care pathway: the patient’s condition, the destination hospital, the choices available when a sick person must cross the ocean for treatment. It would ask what assurances exist that the evacuated and the repatriated will continue to be moved reliably when the chain is a thin one. It would examine the economics and oversight of a corner of medical transport where the patient rarely chooses the carrier. It would hold the operator, the states, and the insurers to the support pledge the company has made, on a timeline the families can use. That frame is not the article’s frame; it rests, nevertheless, entirely on facts the article itself supplies.

What happens next

On the question of cause, the honest position is the one the record requires: unsolved. The investigation, to which the operator has pledged to “continue to cooperate with relevant authorities during ongoing recovery efforts and investigations,” is the authoritative venue for that answer. What the record does establish is the sequence of communications and altitude.

What can be said now is narrower but real. The public understanding of the accident was assembled by open data before any official findings existed. The flight was part of a medical-transport chain that small jurisdictions depend on. Six people — four a professional crew, two a patient and the person who accompanied them — are presumed dead. The company has pledged to “honour our colleagues by remembering the care, professionalism, and commitment they brought to their work every day.” Whether the institutions around this accident match that standard in the months ahead is a question the families, and the record, will be watching.

Analytical techniques used in this piece

This analysis applies the methods below. Each links to a short, plain-English explainer you can read and reuse.

Cui Bono — Who Benefits: Asks who gains and who pays from a state of affairs, decision, or claim.
Differential Diagnosis: Lists the candidate explanations for a symptom and rules them out one by one.
Relationship Mapping: Extracts the network of ties among people, institutions, and entities.