King Air 200 Pilot Incapacitation MID-Air | Auto-land Saves life

Advertisement

The correction from the operator is important to the record: this should not be described as a confirmed pilot-incapacitation accident. The documented event was a pressurization emergency in which automated systems were used to help bring the aircraft safely to the airport.

The King Air reached the airport and landed safely on Runway 30. The event became notable because the aircraft's automated systems handled a substantial portion of the flight and ATC coordination after the emergency developed.

Emergency Descent Mode reduced the aircraft's altitude, while Garmin Autoland was used as part of the emergency sequence. The automated system communicated with air traffic control and guided the aircraft toward Rocky Mountain Metropolitan Airport.

The later account from the operator changed that interpretation. Both pilots were aboard, and the emergency involved the aircraft's pressurization system rather than a confirmed pilot incapacitation. The aircraft's automated emergency systems responded while the crew dealt with the pressurization problem.

On December 20, 2025, King Air 200 N479BR was flying from Aspen toward Rocky Mountain Metropolitan Airport when the aircraft experienced a rapid loss of pressurization during climb. Early accounts interpreted the automated emergency transmissions as evidence that the pilot had become incapacitated.

A King Air Used Automated Systems During a Pressurization Emergency

The case is also useful because the automation did not operate in isolation. Air traffic controllers had to understand the automated transmissions, protect the aircraft's route and prepare the airport for an abnormal arrival. The successful landing resulted from the interaction between the aircraft's emergency systems, the crew, the automated communications and ATC handling.

The later correction is more than a wording change. The early automated radio calls created a plausible impression that the pilot was unable to operate the aircraft, but that interpretation was not supported by the operator's subsequent account. The aircraft's pressurization emergency and the automated systems were the central features of the documented event.

Accident Facts

Date
20 December 2025
Aircraft
Beech B200 Super King Air
Registration
N479BR
Location
Colorado; Aspen to Rocky Mountain Metropolitan
Outcome
Safe Emergency Autoland after pressurization loss
Investigation / classification
Incident

Timeline

Timeline
20 December 2025
20 December 2025: King Air 200 N479BR departed Aspen, Colorado, for Rocky Mountain Metropolitan Airport.
1
During climb
During climb: The aircraft experienced a rapid, uncommanded loss of pressurization while climbing through about 23,000 feet.
2
After the emergency developed
After the emergency developed: The aircraft’s Emergency Descent Mode and Garmin Autoland systems engaged.
3
During the automated flight
During the automated flight: The aircraft navigated toward Rocky Mountain Metropolitan Airport and communicated with ATC through its automated system.
4
Safe landing
Landing: The King Air landed safely on Runway 30 at Rocky Mountain Metropolitan Airport.
5
Crew report
Afterward: The operator clarified that the pilot had not been incapacitated; the initial reports had interpreted the automated emergency communications as an incapacitation event.
6
Later reporting materially changed
Later reporting materially changed the early description of the event. The aircraft was not simply a pilot-incapacitation case: the operator said both pilots were present and the automated systems engaged following a rapid loss of pressurization.
7
That correction is important
That correction is important because the original ATC automation was interpreted as evidence that a pilot was unconscious, while the operator later explained the actual sequence.
8
The operator later said
The operator later said the pilot was
9

Sources

Audio from the original air traffic control recording, sourced from public recordings and released investigation records. The reconstruction, animation and written account are our own.
Advertisement

The weekly incident