Hawker Jet PANIC Moments at Teterboro Smoke in Cockpit

Advertisement

"Climb, Ted! Climb!"

Nine minutes was the entire length of the flight. On the morning of 24 December 2024, a Hawker 800XP, N892TX, operated by Byte Me Transportation Inc., lifted off from Teterboro Airport bound for La Romana in the Dominican Republic — a routine Christmas Eve departure, until the initial climb, when the cockpit began filling with smoke.

A Struggle to Keep Climbing

The crew's transmissions to Teterboro tower captured a cockpit under real pressure — one pilot, apparently coaching or urging the other through the emergency, with radio calls including the kind of terse, urgent phrasing that makes clear this wasn't a minor caution light. The pilots reported severe smoke filling the cockpit while still trying to maintain a safe climb gradient, immediately requesting to return to the airport they'd just left.

Nine Minutes, Runway 19

Teterboro's controllers worked the returning aircraft in ahead of anything else in the pattern, and the Hawker came back around for a safe landing on Runway 19 roughly nine minutes after it had first departed — barely enough time to climb out, declare the emergency, turn back, and get established on final approach. Everyone aboard walked away unhurt. The aircraft itself sustained no reported damage beyond whatever produced the smoke in the first place.

Smoke Without a Confirmed Source

Cockpit smoke is treated as one of the most serious in-flight emergencies precisely because its source isn't always immediately obvious — it can originate from an electrical fault, an environmental or pressurization system component overheating, a bleed-air contamination issue, or, in rarer and more dangerous cases, something burning within the airframe itself. Crews are trained to treat any smoke event as though it could be the more serious kind until proven otherwise, which is exactly why this crew prioritized getting the aircraft on the ground over troubleshooting the source mid-flight. Publicly available reporting on this incident doesn't specify what was ultimately found to have caused the smoke.

A Save, Not a Crash

Despite how the raw ATC audio sounds — tense, urgent, genuinely alarming to listen to — this incident ended the way cockpit-smoke emergencies are supposed to: with a fast, correctly prioritized return and a landing with no injuries and no significant damage.

Reading a Cockpit Under Stress From the Radio Alone

Air traffic control audio offers a genuinely unfiltered window into how a crew handles an emergency, precisely because pilots under real pressure don't have time to compose measured, formal radio calls — what comes across the frequency is closer to how people actually communicate when something has gone wrong and needs to be fixed immediately.

Why Climb Performance Matters Most in the First Minute

The urgency around maintaining climb rate during this specific emergency reflects a fundamental tension in how pilots are trained to handle in-flight fires or smoke: the instinct to descend and land as quickly as possible has to be balanced against the very real danger of terrain, obstacles, and traffic immediately after takeoff, when an aircraft hasn't yet reached a safe maneuvering altitude.

Business jets like the Hawker 800XP draw bleed air from their engines to pressurize and condition the cabin — a system that, when something goes wrong upstream, can introduce contaminated or overheated air directly into the environment pilots and passengers breathe.

Why This Incident Never Became a Bigger Story

Successful emergency returns like this one rarely generate the sustained public attention that accidents with injuries or fatalities receive, even when the raw audio sounds every bit as dramatic.

What Investigation Typically Follows a Non-Fatal Return

Incidents like this one, resolved without injury or significant aircraft damage, generally receive a lighter investigative footprint than accidents involving fatalities or serious injuries — often handled through the operator's own internal safety review and, depending on the specifics, an FAA inquiry into the cause rather than a full NTSB accident investigation.

Accident Facts

Incident date
24 Dec 2024
Registration
N892TX
Aircraft
Hawker 800XP (Byte Me Transportation Inc.)
Airports
Teterboro (TEB), returned to TEB ~9 minutes after departure;
Injuries
None; safe emergency landing, no reported aircraft damage
Investigation status
No public NTSB/FAA final report identified;
Category
Emergency, Fire / Smoke
Reconstruction
8:03
Timeline
Sequence —
The pilots reported severe smoke filling the cockpit while still trying to maintain a safe climb gradient, immediately requesting to return to the airport they'd just left.
1.
Approach / landing —
Teterboro's controllers worked the returning aircraft in ahead of anything else in the pattern, and the Hawker came back around for a safe landing on Runway 19 roughly nine minutes after it had first departed.
2.
Approach / landing —
Despite how the raw ATC audio sounds — tense, urgent, genuinely alarming to listen to — this incident ended the way cockpit-smoke emergencies are supposed to: with a fast, correctly prioritized return and a landing with no injuries and no significant damage.
3.
During flight —
The urgency around maintaining climb rate during this specific emergency reflects a fundamental tension in how pilots are trained to handle in-flight fires or smoke: the instinct to descend and land as quickly as possible has to be balanced against the very r…
4.
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

Sources

The weekly incident