An Hour of Circling: The Seneca's Nose-Gear Emergency at Gaithersburg

A Piper Seneca with two people aboard spent roughly an hour circling its home airport in Gaithersburg, Maryland, trying to solve a nose-gear problem that never fully resolved — and came down hard on the nose when the crew finally committed to landing.

A Problem That Didn't Have a Quick Fix

The aircraft, operated by High Flyers Aviation Service, developed a nose-gear malfunction while operating out of Montgomery County Airpark. Rather than land immediately, the crew spent close to an hour circling the field, working through the gear checklist, trying alternate extension methods, and — implicitly, given how long they stayed up — hoping for an indication that never came.

A Hard Landing, Not a Belly Landing

When the crew finally committed to landing, the nose gear was apparently still retracted, and the aircraft came down hard, with the nose contacting the runway directly. That's a meaningfully different outcome than the "hold the nose off and let it settle gently" technique that worked for the NetJets Citation at Akron-Canton three weeks earlier in this same batch — a Seneca's twin nose-mounted gear geometry and lower approach speed give a crew less room to finesse the touchdown than a jet does, and here the nose made contact more abruptly.

No Injuries, No Fire

Despite the hard nose contact, emergency crews who responded found no injuries and no fire. The airpark was temporarily closed to flight operations afterward while the aircraft was cleared from the runway and the incident assessed.

Investigation Status

What caused the nose gear to fail to extend, and why an hour of troubleshooting in the air didn't resolve it, has not been determined publicly as of this writing; the circumstances remain under investigation.

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.
• Registration N1519T independently confirmed by WJLA, Baltimore Sun, and Bethesda Magazine coverage of the same incident.