14 Feb 20166:31 reconstruction11K views

“I’m sorry for all those emergency people sitting down there waiting on me”

Advertisement

Broken Throttle Forces Cessna 172 Into Atlanta Emergency

Cathy Lewan was taking aerial photographs around Atlanta on February 14, 2016, when the throttle cable in her Cessna 172S broke and left the engine operating at near-maximum power. The malfunction created a difficult problem: she could not simply reduce power and slow the aircraft for a normal landing.

Lewan was flying about ten miles from Hartsfield-Jackson Atlanta International Airport. She contacted Atlanta TRACON and declared an emergency. Controller Patrick Burrows established the aircraft's location and learned that the throttle was stuck at maximum power. The aircraft also had substantial fuel remaining, giving the controllers time to develop a plan.

Because the communications on the original frequency were difficult, Burrows transferred Lewan to another sector where reception was better. Controller Mason Braddock then stayed with her through much of the emergency. Behind the scenes, other controllers and a traffic-management specialist helped build a plan for the unusual landing.

The first priority was not to rush toward the runway. The aircraft needed to manage its energy. Controllers arranged for Lewan to circle in the Atlanta area while traffic around the airport continued moving.

The problem was complicated by the environment. Hartsfield-Jackson is one of the busiest airports in the United States, and the emergency aircraft could not simply enter the runway environment without affecting other traffic. Controllers therefore had to separate the Cessna from the commercial flow while keeping the aircraft in a position from which it could eventually land.

Lewan also had to manage the airplane without normal throttle authority. She later described concerns about excessive speed, her own state of mind, surrounding aircraft and the possibility of a stall. The throttle problem therefore affected both the aircraft's speed control and the pilot's workload.

As the emergency continued, the controllers coordinated emergency services and prepared the runway. A flight instructor working within Atlanta TRACON helped the controllers understand the pilot's situation and contributed to the landing plan.

After roughly 50 minutes, Lewan was brought toward Runway 10. The plan called for a controlled approach with the engine ultimately being shut down once the aircraft was positioned over the runway.

The landing was successful. Emergency vehicles were waiting, and the aircraft was later towed from the runway environment. Lewan was unharmed.

The most revealing part of the incident is how much work occurred before the final approach. The emergency was not solved by a single instruction. It required locating the aircraft, moving the communication to a more reliable frequency, managing surrounding traffic, building a landing plan and keeping the pilot reassured while she continued flying.

I should be able to knock this out. — the incident record.

“I should be able to knock this out.”

Accident Facts

Date
February 14, 2016
Aircraft
Cessna 172S
Event
Broken Throttle Forces Cessna 172 Into Atlanta Emergency
Category
Incident / Emergency
Timeline
February 14, 2016 —
Cathy Lewan departed Madison Municipal Airport for aerial photography.
1.
Emergency —
The Cessna 172S developed a throttle malfunction and became stuck at near-maximum power.
2.
Initial ATC contact —
Lewan declared an emergency and Atlanta TRACON established her position.
3.
Handoff —
Communications were moved to a sector with better reception.
4.
Holding phase —
Controllers kept the aircraft clear of commercial traffic while Lewan managed speed and altitude.
5.
Planning —
Controllers and a flight instructor developed a landing procedure.
6.
About 50 minutes later —
Lewan approached Runway 10.
7.
Landing —
The Cessna landed safely and was later towed away.
8.
The emergency became a successful example of coordinated human performance because the pilot retained control of the aircraft while controllers created enough space and time for her to use it.
9.
The emergency was also a traffic-management challenge. Hartsfield-Jackson could not simply stop all arrivals and departures for a small aircraft, yet the Cessna needed protected airspace and a predictable runway environment. The controllers therefore had to keep commercial traffic moving while maintaining a safe envelope around Lewan.
10.
That work continued until the final approach. The emergency services were positioned before the landing, and the landing plan had been discussed in advance rather than improvised during the final seconds.
11.
The public recognition later given to the controllers is relevant because it confirms that the event was treated as an example of coordinated emergency handling. It does not change the underlying facts: the throttle remained stuck, the aircraft stayed airborne, and the pilot landed safely.
12.

Sources

Advertisement

The weekly incident