Sat, Jul 26, 2003
Pipeline Pilot Didn't Know About Restrictions
When you're flying
along, doing your job and suddenly notice an F-16 and a couple of
Blackhawks off your wing, with the pilots looking at you real hard,
that's a bad thing, right? That's just what happened to an aviator
from Underwood Aerial Patrol in Bloomingburg (OH).
Secret Service: "Wrong Place, Wrong Time"
President Bush was in Philadelphia Thursday to announce the
first distribution of government checks under his Child Credit Act.
Some 25-million families will each receive up to $400 per child
from Uncle Sam. The president was traveling in motorcade along I-95
from the airport to the check processing center when the unnamed
pilot flew right overhead. What the pilot apparently didn't know
was that a Temporary Flight Restriction had been issued, extending
30 miles in all directions from the center of Philadelphia. He flew
along the Delaware River and crossed over the motorcade at
approximately 800 ft. AGL, according to the FAA.
When the pilot didn't respond to ATC, a city police helicopter
was sent to intercept him. A USAF F-16 joined the party and the
pilot was forced to land his Cessna 172 at the Camden County
Airport in Winslow Township (NJ). His aircraft was met by
some 30 local and federal law officers with guns drawn. The pilot
was handcuffed and sat down for a little chat with federal
agents.
That Was Just The Beginning
For the next two and a half hours, the Secret Service says the
pilot was grilled about his intentions and whether he knew there
was a TFR in place. The upshot? Federal agents decided the pipeline
pilot was clean.
"He had no idea the President was in Philadelphia or that he was
near a motorcade route," Secret Service spokesman James Borasi
said. "He meant no ill will, malice or threat at all. It was a
matter of wrong place, wrong time."
AOPA Chimes In
"It cannot have helped
matters that the NOTAM establishing the temporary flight
restriction (TFR) was not issued until late the night before, or
that the effective time was extended that very morning," said AOPA
President Phil Boyer. "Here was a businessman conducting a
legitimate flight and he didn’t get the word."
Boyer sounded a little like Cool Hand Luke when he added, "What
we have here is a failure to communicate. The FAA waited so long to
get the word out about the TFR that it was bound to cause
problems."
More News
“The market demand for TBM and Kodiak continues to be resilient, benefitting from the versatility and operational efficiency of these aircraft – which is backed by Dahe>[...]
Aero Linx: N3N Owners and Restorers Association The N3N holds a special place in aviation history. The aircraft was both designed and built by the Naval Aircraft Factory, located o>[...]
Also: USAF Contractor Suit, Secret Service UAVs, Delta/Joby/Uber, Ferrovial Acquired Vertical Aerospace announced the testing program of its prototype VX4 took another significant >[...]
Also: Starship Threatened, SAOC Replacement, Navy Helos To CA Fires, 12 Planes Of Christmas A firefighting aircraft operating over the Palisades Fire in Los Angeles is grounded and>[...]
Airplane Began An Un-Commanded Roll Forward And It Subsequently Struck An Unoccupied, Parked Company Raytheon Aircraft Company C90A On December 20, 2024, about 2315 Hawaii-Aleutian>[...]