Kitfox Aircraft Stick and Rudder Stein Air Grove Aircraft TCW Technologies Dynon Avionics AeroLED MGL Avionics Leading Edge Airfoils Desser EarthX Batteries Garmin G3X Touch
Page 1 of 2 12 LastLast
Results 1 to 10 of 24

Thread: Oops! Don't bust a POTUS TFR!

Hybrid View

Previous Post Previous Post   Next Post Next Post
  1. #1
    Senior Member
    Join Date
    Oct 2009
    Location
    NJ
    Posts
    218

    Default Re: Oops! Don't bust a POTUS TFR!

    From AlertNewEngland.com
    -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
    Fighters intercept planes over Connecticut

    ... a "no fly zone" was established around the areas ...
    ... C) THE UNITED STATES GOVERNMENT MAY USE DEADLY FORCE AGAINST THE AIRBORNE AIRCRAFT...

    Sometime just before 8:00 PM local time, a small aircraft (a Kitfox Sport) with tail number N725CE entered the area designated as National Defense Airspace. Prior to entering this area, the aircraft will be hailed on an emergency frequency, and warned to turn away. Several warnings are typically given, and they typically include distance from the restricted area, and the fastest way away from it. N725CE likely did not hear the warnings, and probably wasn't aware of the restricted airspace, and must have proceeded past the boundary. At some point, a decision would have been made to scramble F-15's to intercept the small plane. You can listen to them take off from Barnes here:

    The intercept aircraft, call signs SLAM31 and SLAM32, are directed by NORAD to their target, which is referred to as the 'TOI' - Target of Interest. When the fighters launched, N725CE was approximately 80 miles away from them. The F-15's covered this distance in six minutes, going supersonic in order to reach the target before it came within striking distance of the President. Once they identified the plane, the fighters used a series of visual signals to order the pilot to establish communications and/or follow them to a designated landing site. N725CE was escorted by the jets to Long Island MacArthur Airport, where he was ordered to park on a remote taxiway. The pilot was taken into custody by airport law enforcement and held until United States Secret Service officers arrived on scene to take him into custody and interview him. You can listen to the radio communications between the pilot, tower, and airport law enforcement here: Part 1 Part 2
    A second plane was then also intercepted by the same flight of F-15's.
    -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
    And, according to NYCaviation.com, the second plane must have been the Red Baron's. (The Focker triplane probably undergoing maintenance.)
    -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
    F-15's intercept TFR Violator
    2 F-15's intercepted a Biplane that violated the Presidential TFR this afternoon. The Biplane was escorted to ISP where it was forced (sic) to land & was escorted to Suffolk PD Aviation base.
    As of this time, the pilot is being questioned by personal from the Secret Service, FBI, & Suffolk County PD."
    -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
    At least they had the courtesy of capitalizing the word "Biplane".
    Double
    the wings, double the danger.

    Roberto.


  2. #2

    Join Date
    Dec 2009
    Location
    Lawrenceville, GA
    Posts
    180

    Default Re: Oops! Don't bust a POTUS TFR!

    Oh, crap!!

  3. #3
    Senior Member
    Join Date
    Sep 2008
    Location
    Winchester, KY
    Posts
    299

    Default Re: Oops! Don't bust a POTUS TFR!

    Big Brother at Work!!! Idiots don't even know you can't communicate with both hands in the air. And their suppossed to be protecting our country and rights. Leaves a lot to be desired and a total waste of manpower and resources(2 F-15's and pilots, Norad, tower controllers, police??, secret service and who knows what else). Makes you wonder where we are all headed.

    Dick B

  4. #4
    Senior Member
    Join Date
    Oct 2009
    Location
    NJ
    Posts
    218

    Default Re: Oops! Don't bust a POTUS TFR!

    Now that our supreme commander has been captured, it is not necessary to keep his heroic efforts hidden anymore
    Yes, we were part of a conspiracy to overthrow the government, restore the Monarchy and reinstate the descendants of King George the 3rd as the rightful rulers of the 13 colonies. (This would happen just hours after the fall of Washington, DC and Cleveland, Ohio)
    The North-East Kitfox fly-in was just a cover up for the leaders to meet and finalize our plans before the final push. The historic document below shows General CDE2FLy and myself before taking off for a pretended sight-seeing local trip, whose real purpose was to choose the best route for our supply lines.
    At the same time, the Kitfox cockpit provided the indispensable protection from ear dropping by government infiltrators and paparazzis, while we ironed out the fine details of the planned offensive.
    I guess we brought this defeat upon ourselves. In retrospect, painting our aerial fleet to match the color of the British Colonial Forces red coats was a giveaway.
    Still, I know our day will came …

    Lieutenant General Roberto.

    PS: Please, somebody tell the McBeans to stop fitting the long range drop tanks on the 3000 Kitfoxes in their secret underground factory.

    PS2: Chris, hope you are OK.

    .
    Attached Images Attached Images
    Last edited by rwaltman; 08-07-2012 at 07:45 PM.

  5. #5

    Join Date
    Feb 2009
    Location
    NY
    Posts
    40

    Default Re: Oops! Don't bust a POTUS TFR!

    So I guess this is my 15 minutes of fame....just not what I had in mind! As you can imagine, the past 24 hours have been a bit hectic/stressful. Been trying to stay away from most of the coverage to help with the decompression though my kids have been consuming every news snippet with great enthusiasm and relaying the highlights. Still sorting out the details of the specific violation so I’ll provide more info on that later other than to say (as far as I can tell) the TFR is not listed on the FAAs webpage posting such restrictions www.tfr.gov and there was some confusion with the FAA on the field last night as to the specific nature of the violation, timing of the TFR, etc. I’m sure the FAA will make it exceeding clear to me sometime soon in a letter but for now just waiting to hear back from them.

    Was heading down to meet the family for some R&R at a beach house in Long Island. I almost always contact Approach Control when I’m down in that area for VFR flight following just to increase the situational awareness for both them and me (it can be very busy airspace with commercial and private jet traffic). Yesterday’s vacation frame of mind included careful attention to avoid the established controlled airspace in the NYC region and just enjoy the flight monitoring VFR frequencies. Imagine my surprise at the sudden appearance of the F15s! It took a few seconds to realize I was the target of their intercept and switched over to monitor 121.5. They escorted me to ISP where local law enforcement was awaiting my arrival. I’m guessing over 50 personnel and 20 vehicles were on the scene within 5 minutes and I was immediately detained to await the arrival of the Secret Service about an hour and a half later (note to group….handcuffs are very uncomfortable…I strongly advise making all attempts to avoid situations requiring their use!). I must say that everyone involved was extremely professional though absolutely focused on their mission. I was treated with courtesy and respect at all times and particularly so by the Secret Service. Lots of information was exchanged and of course the airplane and baggage thoroughly searched. I believe the search included a scan with a geiger counter though the view from the back seat of the police crusier some distance from the airplane was not the best.

    Some initial thoughts/advice:

    · Determine a reliable way of verifying TFRs before your flight. Not sure the FAA web page accomplishes this but I may be wrong on this and continuing to investigate my particular circumstances. In the future, I will be calling Flight Service for a briefing anytime I venture away from home base as a double check and to have a record of my inquiry. If any of you have a favorate web page that you trust for this purpose, please let me know.

    · As with many situations, treat others the way you would like to be treated and it’s usually reciprocated. Like most of us, the agents involved have a job to do and are trying to do it as well as possible often with limited information in a very dynamic environment. One of the Secret Service agents called me this morning to check to see how I was doing, confirm all was well, and thank me again for my courtesy and cooperation.

    · The next time you’re at the hanger DOUBLE CHECK to be sure you have all required documents in the airplane. I had removed the airworthiness certificate during the annual in the spring and inadvertently left it out of the airplane. The certificate must be the original….a copy does not suffice. I drove 8 hours home to get the original so I can remove the airplane from ISP. The FAA was not interested in the copy on record with their agency….must have the original in the airplane.

    · When in doubt, monitor 121.5….thankfully I was able to communicate with the F15 pilots soon after we made visual contact. Not sure what would have happened otherwise….they fly way to fast to follow so they were simply flying very close to get my attention but it was not clear for a few seconds what direction to fly or what they wanted me to do.

    · Be very careful in checking Presidential TFRs. They may be posted on very short notice so as not to disclose the President’s location to far in advance for security reasons.
    Thanks for the support….truly grateful for this fine group. I’m sure I’ll get through the red tape with the FAA and be a better pilot for it with a deeper respect for checking multiple sources of TFR information and getting a pre-flight briefing on record before I leave the local area.
    Chris

  6. #6

    Join Date
    Feb 2009
    Location
    NY
    Posts
    40

    Default Re: Oops! Don't bust a POTUS TFR!

    Roberto - thanks for the comic relief!! Just went back and read your post...I think it was the first time I smiled since my untimely meeting with the F15s....I needed that!

  7. #7
    Senior Member GWright6970's Avatar
    Join Date
    Jan 2011
    Location
    Vacaville, CA
    Posts
    359

    Default Re: Oops! Don't bust a POTUS TFR!

    Hang in there Chris.... your attitude is an inspiration!

  8. #8
    Senior Member
    Join Date
    Oct 2009
    Location
    NJ
    Posts
    218

    Default Re: Oops! Don't bust a POTUS TFR!

    Quote Originally Posted by CDE2FLY View Post
    ... thanks for the comic relief!!
    Any time. And thank you, for the lesson ...

  9. #9
    Senior Member dholly's Avatar
    Join Date
    Mar 2009
    Location
    Clemmons, NC
    Posts
    285

    Default Re: Oops! Don't bust a POTUS TFR!

    Quote Originally Posted by CDE2FLY View Post
    Thanks for the support….truly grateful for this fine group. I’m sure I’ll get through the red tape with the FAA and be a better pilot for it with a deeper respect for checking multiple sources of TFR information and getting a pre-flight briefing on record before I leave the local area.
    Chris
    With any luck a little less red tape now that the new Pilot's Bill of Rights was signed into law last week (Aug. 3rd). Improving and centralizing NOTAMs is a main priority in the bill. Hopefully, you will still get to enjoy a few days on the beach with your family!
    -Aeropro CZ Aerotrek A240 Tri-Gear SLSA 912uls
    -Airdale Avid+ on CZAW Amphibs 'FatAvid Floater' (building)
    -Kitfox 4-1200 TD 912ul (sold)
    -Kitfox Model III TD 582 (R.I.P.)
    -Avid Flyer Mk-IV TD (sold)

  10. #10
    Senior Member
    Join Date
    Oct 2009
    Location
    NJ
    Posts
    218

    Default Re: Oops! Don't bust a POTUS TFR!

    Quote Originally Posted by CDE2FLY View Post
    ...the FAAs webpage posting such restrictions www.tfr.gov

    That link doesn't work for me.
    This one does: http://tfr.faa.gov/

    The page includes this footnote: "Depicted TFR data may not be a complete listing. Pilots should not use the information on this website for flight planning purposes. For the latest information, call your local Flight Service Station at 1-800-WX-BRIEF.
    "

    Roberto.

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •