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
Aero Linx: Transport Canada We are a federal institution, leading the Transport Canada portfolio and working with our partners. Transport Canada is responsible for transportation p>[...]
Gross Navigation Error (GNE) A lateral deviation from a cleared track, normally in excess of 25 Nautical Miles (NM). More stringent standards (for example, 10NM in some parts of th>[...]
From AirVenture 2017 (YouTube Edition): Flight-Proven Booster On Display At AirVenture… EAA AirVenture Oshkosh is known primarily as a celebration of experimental and amateu>[...]
Aircraft Parachute System (CAPS) Was Deployed About 293 Ft Above Ground Level, Which Was Too Low To Allow For Full Deployment Of The Parachute System Analysis: The day before the a>[...]
Also: 48th Annual Air Race Classic, Hot Air Balloon Fire, FAA v Banning 100LL, Complete Remote Pilot The news Piper PA-18 Super Cub owners have been waiting for has finally arrived>[...]