Staying on Frequency: Slate Aviation 719's Flap Emergency Over Teterboro

A Slate Aviation crew working a stuck-flap problem after departing Teterboro made a small but telling choice early on: when the controller offered to move them to a quieter frequency to run their checklist, they said no, they'd rather stay right where they were.

A Flap That Wouldn't Retract

Shortly after departure, New York Departure asked the crew to explain their request, and got a clear answer: a flight-control problem, specifically flaps that had failed to retract from the takeoff setting. Flaps stuck extended change an aircraft's speed and fuel-burn characteristics for as long as the condition lasts, and — as this crew already suspected before they'd even declared anything formally — change what a safe approach speed looks like once it's time to land.

Choosing to Stay on a Busy Frequency

The controller offered to hand the flight off to approach control, where the crew could work their checklist without competing for airtime on a busy departure frequency. The crew asked to stay put instead. The controller agreed, and kept managing other traffic around them — including issuing a traffic advisory for a Citation crossing three miles ahead at 3,000 feet — while the Slate Aviation crew worked the problem in the background. That's a real trust call in both directions: the crew judging that staying with a controller already tracking their situation mattered more than a quieter frequency, and the controller agreeing to keep juggling both jobs at once.

The Mayday, Once They Had a Plan

About three minutes later, once the crew had worked through enough of the checklist to know what they were dealing with, they declared a mayday — not at the first sign of trouble, but once they had specifics to report: the flaps hadn't retracted completely, the approach would need to be flown faster than normal as a result, and they wanted emergency equipment standing by along with a longer-than-normal landing rollout on Runway 1 to account for the added speed.

A Coordinated Return

Departure cleared the flight for an immediate return, and Newark Approach vectored it onto final for the RNAV Runway 1 approach at Teterboro — a handoff between two different facilities working the same emergency without the crew losing continuity along the way.

This reconstruction was researched from official investigation records where they exist, the original air traffic control recording, and contemporary reporting. The aircraft movement, timeline and written account were assembled independently by Flight Follower. Where an investigation is open or no probable cause has been published, the account says so rather than offering one.

Timeline

Accident Facts

Sources

• Account built from the ATC recording. No independent news coverage of this specific flight was located.