PC-12 Crashes: What the Available Records Confirm and What They Cannot Establish

What the available PC-12 records can—and cannot—answer

The phrase “pc12 crashes” covers separate events involving different aircraft, registrations, locations, operations, and record sources. The PC-12 is a Pilatus aircraft model, and the supplied records identify variants such as the PC-12/45, PC-12/45E, PC-12/47, and PC-12/47E. A useful answer begins by separating those events instead of treating every database entry as part of one accident pattern.

The records identify a PC-12/45 registered as N128CM in a 2009 Montana accident. A separate Aviation Safety Network entry reported a PC-12/45 registered as N774DK at Hanscom Field in Massachusetts on October 3, 2026. Other database entries identify a PC-12/47 registered as ZS-GAA near Robberg, South Africa, and a PC-12/45 registered as VT-ACF at Faridabad, India. The model name connects these aircraft to the PC-12 family; it does not connect their causes, operators, investigations, or legal consequences.

Those records can establish that particular events were recorded, along with selected details such as location, registration, occupants, fatalities, or aircraft status. They cannot, by themselves, establish that every event had the same cause, that a particular person or organization was legally responsible, or that the same legal theory applies across jurisdictions. Read each record as an event-specific account, and keep confirmed facts separate from conclusions that require an investigation or legal analysis.

The central question is not whether a database contains the words “PC-12” and “crash.” The useful question is what a particular source actually establishes about a particular registration on a particular date. That approach helps you distinguish an investigative record from a database entry, a recorded outcome from a causal finding, and a general technical issue from proof about one aircraft.

Separate the documented events before comparing them

The first comparison should be between records, not between assumed causes. The following table keeps these events separate by aircraft, registration, place, source, and recorded outcome.

The rows do not describe one continuing investigation. They come from different records and concern different aircraft. The NTSB entry provides a specific U.S. accident account. The Hanscom entry is an Aviation Safety Network event record with a reported verification basis. The South Africa and India entries are database listings with selected outcome fields. That difference matters: a listed fatality count or damage status is not the same thing as a final explanation of what happened.

Registration is the first practical identifier. A model designation alone is too broad to keep separate events apart. Add the event date and location, then identify the source that supplied each detail. If a record gives only a location and outcome field, preserve that limited scope rather than filling the gaps with details from another aircraft.

Before you compare two PC-12 events, write down the registration and date first. If those identifiers differ, keep the events in separate files or notes until an authoritative investigation connects them. Do not transfer a cause, operational detail, or legal conclusion from one row to another.

What the NTSB confirms about the 2009 Butte PC-12 accident

According to the NTSB, on March 22, 2009, a Pilatus PC-12/45 registered as N128CM crashed near the approach end of runway 33 at Bert Mooney Airport in Butte, Montana. The airplane was owned and operated by Eagle Cap Leasing of Enterprise, Oregon, as a personal flight under 14 Code of Federal Regulations Part 91.

The NTSB states that the flight departed Oroville, California, was destined for Gallatin Field in Montana, and was diverting to Butte when the accident occurred. The record also states that visual meteorological conditions prevailed at the time of the accident. Those route and weather details describe this flight; they do not establish why the aircraft crashed.

The NTSB records that all 14 people aboard the PC-12 were killed and that there were no ground injuries. Those are the reported human consequences of this particular event; they should not be used to characterize every PC-12 occurrence.

A separate FAA Safety Briefing stated that, according to the NTSB, 474 people perished in fatal general aviation accidents in 2009. That figure describes fatal general aviation accidents broadly. It is not a PC-12 count, a rate for this aircraft type, or a measure of the Butte accident’s cause.

The NTSB record establishes the aircraft, flight context, route, weather description, location, and reported fatalities. It does not support assigning a cause here. A careful account therefore stops at those confirmed details rather than adding assumptions about pilot conduct, weather, maintenance, equipment, or another factor.

The same boundary applies to responsibility. The fact that an accident occurred, even when an official record identifies the aircraft and casualties, does not by itself identify a negligent act, a defective component, a responsible operator, or a recoverable claim. Those questions require event-specific records and a legal analysis tied to the people, organizations, and jurisdiction involved.

What the 2026 Hanscom Field entry records—and leaves open

The Hanscom Field entry concerns a different aircraft: a Pilatus PC-12/45 registered as N774DK. The Aviation Safety Network record reported an event on October 3, 2026, at Laurence G. Hanscom Field in Bedford, Massachusetts, during landing. It listed three occupants and fatalities of 0.

The Aviation Safety Network record says its information was verified through data from accident investigation authorities. That statement describes the record’s verification rating. It does not supply a causal finding in the available record.

Use this entry to identify the aircraft, date, location, phase of flight, occupant count, and recorded fatality field. Do not turn it into a conclusion about injuries, aircraft damage, pilot decisions, maintenance, or responsibility unless an authoritative event-specific record establishes those points. A zero-fatality entry is not a finding that the event had no other consequences.

The contrast with the Butte accident is direct but limited. N128CM was recorded in a fatal Montana crash involving 14 people aboard; N774DK was recorded in a Massachusetts event with three occupants and fatalities listed as 0. The contrast shows why registration, date, location, and record type must come before any attempt to identify a pattern.

If you are examining the Hanscom event for a personal or family reason, treat the database entry as a locator for the underlying record rather than as a complete account. Preserve the registration and date, note exactly what the entry says, and keep unanswered questions—such as injuries, damage, or cause—separate from the recorded fatality field.

What limited database listings establish about other PC-12 events

The Aviation Safety Network database lists a Pilatus PC-12/47 registered as ZS-GAA near Robberg, Plettenberg Bay, in South Africa. The entry lists nine fatalities and identifies the aircraft as written off.

The same database passage lists a Pilatus PC-12/45 registered as VT-ACF at Faridabad, India. It records the fatality field as “7+3” and identifies the aircraft as written off. Preserve that notation rather than silently converting it into a different number or assuming what the two figures represent.

These entries are useful identifiers for further event-specific review. They show that the database associates particular registrations with particular places and outcome fields. They do not establish a common cause, a common operator, a defect, a violation, or a final allocation of legal responsibility.

Treat a database listing as a starting point for locating the underlying investigation or official record. Quote the field you can support, label the record as a listing when that is what it is, and avoid filling gaps with a theory that belongs to another accident.

A written-off designation describes the aircraft’s recorded status. It does not tell you whether a particular component failed, whether a rule was violated, whether weather contributed, or which party might bear legal responsibility. Likewise, a fatality field describes an outcome recorded in the database; it does not explain the sequence that produced that outcome.

Why technical context cannot substitute for an event-specific finding

The FAA Part 23 icing report states that aircraft not certificated for icing accounted for 54% of the events in its event database. It states that two events involving aircraft not certificated for icing yielded no survivors; both involved a stall followed by loss of control, and icing was inferred from air traffic control transmissions.

That material provides context about the particular FAA icing event database and the findings described in that report. It does not establish that icing caused the 2009 Butte accident, the 2026 Hanscom event, or either of the South Africa and India entries. The 54% figure is not a PC-12 crash rate.

A separate FAA summary stated that an airworthiness directive applies to all Pilatus Model PC-12 airplanes and prohibits positioning the power levers below the flight idle stop while the airplane is in flight. The summary said the directive resulted from numerous incidents and five documented accidents involving turboprop-engine airplanes where propeller beta was improperly used during flight.

The directive is important regulatory and operational context, but its existence does not prove that improper power-lever positioning or propeller beta caused a particular PC-12 event. To make that connection, an event-specific investigation would need to establish the aircraft’s condition, applicable requirements, recorded operations, and the relationship between any identified issue and the outcome.

The icing report and the power-lever directive answer different questions. The first describes a broader FAA event database and the findings reported for particular icing-related events. The second describes a requirement applicable to PC-12 airplanes and the circumstances behind that regulatory action. Neither source identifies a cause for N128CM, N774DK, ZS-GAA, or VT-ACF.

Technical context helps you identify questions; it does not answer them in advance. For a particular event, keep separate questions about icing, controls, maintenance, training, weather, and operation. Treat each as unresolved until the responsible investigative record connects it to the aircraft and occurrence in question.

An evidence checklist for interpreting a specific PC-12 event

A short event record can become confusing when details from separate aircraft are combined. Use the following checklist to build one event file at a time. The N128CM NTSB record and the N774DK Aviation Safety Network entry illustrate why the registration, date, source, and reported outcome should stay together.

1. Identify the aircraft. Record the model variant, registration, and any serial or fleet identifier supplied by the authoritative record. Registration is the anchor that keeps N128CM separate from N774DK, ZS-GAA, and VT-ACF.
2. Fix the date and place. Write the date, airport or geographic location, and phase of flight when those details are established. Do not replace a precise location with a broad state or country label.
3. Record the people-related fields exactly. Separate occupants, fatalities, injuries, and ground injuries. If a database uses shorthand such as “7+3,” preserve the notation and identify it as a database field rather than interpreting it.
4. Describe the operation. Note the operator, flight purpose, regulatory context, departure, destination, and diversion only when the applicable record establishes them. The NTSB supplies those details for the Butte flight; they should not be assumed for another event.
5. Name the source and its status. Identify whether the statement comes from an investigative authority, a database, a preliminary account, or a final finding. Keep a reported description separate from an attributed explanation.
6. Mark what remains open. Create a separate space for proposed causes, disputed accounts, missing records, and questions awaiting an investigative conclusion. An unresolved question should remain unresolved in your notes.

The NTSB account of N128CM supplies a specific flight route and Part 91 personal-flight context. The N774DK entry supplies a date, location, landing phase, occupant count, and fatality field, and says its information was verified through data from accident investigation authorities. Those are different levels and kinds of information. Label each field instead of treating them as interchangeable evidence.

A simple status label can keep your notes precise:

• Confirmed: the source directly records the fact, such as a registration or location.
• Reported: a database or account describes the event, but the available material does not establish the full investigative meaning.
• Attributed: the source assigns an explanation to a person, organization, or finding; preserve that attribution rather than presenting it as your own conclusion.
• Unresolved: the available record leaves the question open.

Use the narrowest label that fits the material you have. The label should travel with the fact when you share notes with a family member, lawyer, insurer, or investigator. If two records appear to conflict, compare the specific field, date, source role, and wording before treating them as contradictory. A difference in a fatality field or aircraft-status field may not answer the same question as a causal finding. If the difference remains unexplained, preserve both accounts and mark the conflict unresolved.

We consider gathering evidence, including medical records, incident reports, and witness statements, vital for substantiating a claim after an airplane crash. Keep the checklist with the documents you already have, and note which fact each document is intended to support. Preserve original documents where possible, and distinguish what you personally observed from what another source reported.

What a documented PC-12 accident may mean for an affected family

A documented PC-12 accident can give you a factual starting point, but an accident entry alone does not establish negligence, a product defect, a liable party, or the outcome of an individual claim. Those questions require the facts of the specific occurrence, the available records, the people and organizations involved, and the governing legal framework.

We consider medical records, incident reports, and witness statements important evidence to gather after an airplane crash. Start with the documents that connect the event to the harm: treatment and billing records, reports you received, and contact information or statements from people who observed the event. Keep the original wording and the date you obtained each item.

A documented account can preserve what happened, the treatment that followed, communications you received, and the practical effects on daily life. You can keep a factual account of what happened, the treatment that followed, communications you received, and the practical effects on daily life.

Organize the material around the event rather than around a suspected theory. A useful file may include:

• the aircraft registration, event date, and location;
• the official or database records you located;
• medical and billing records connected to the injury;
• incident reports, photographs, messages, and witness information; and
• a dated account of communications, treatment, and ongoing effects.

Keep facts, documents, and questions in separate sections. That structure makes it easier to see which points are supported and which require further review.

Preservation is not the same as a liability conclusion. A medical record may document treatment, an incident report may document an occurrence, and a witness statement may preserve an observation; none should be rewritten to say more than it says. Keep those materials distinct from later theories about cause or responsibility.

If a death or injury affected your family, the organized record can help identify the questions that need review: what happened, who controlled or maintained the aircraft, which investigation is active or complete, and which documents remain available. It can also show where the facts are still uncertain. That is a sound basis for deciding whether to seek general information about potential aviation-accident claims.

Use the confirmed record to decide what to preserve next

The available PC-12 records support a disciplined conclusion: separate the aircraft and event first, quote the confirmed fields accurately, and keep technical context from becoming an assumed cause. The Butte accident, the Hanscom Field entry, and the South Africa and India listings describe different records with different levels of detail.

Preserve the registration, date, location, reports, medical records, incident materials, witness information, and your own factual documentation. A qualified aviation-accident lawyer must assess your individual facts, potential responsibility, and applicable law before advising you about a claim.

Use the confirmed record to identify what you know, what remains open, and what should be preserved next. Do not let a database label answer a causal or legal question that belongs to the event-specific investigation.