Welcome, Guest. Please login or register.
Did you miss your activation email?
July 28, 2014, 12:27:30 PM
Home Help Login Register      
News: NEW Follow LiveATC updates on Twitter and Facebook


+  LiveATC Discussion Forums
|-+  Air Traffic Monitoring
| |-+  Aviation Audio Clips (Moderators: dave, RonR)
| | |-+  C172 busting TFR at Morristown
« previous next »
Pages: [1] 2 Go Down Print
Author Topic: C172 busting TFR at Morristown  (Read 13193 times)
keith
Sr. Member
****
Offline Offline

Posts: 272


WWW
« on: September 18, 2006, 05:33:44 PM »

I hadn't listened to my feed for a while, so I fired it up today, and not 5 minutes later, heard the following exchange between a Cessna and Morristown tower, a Class D field just outside of NYC.

There is a Temporary Flight Restriction (TFR) today covering the lateral limits of the Class B airspace (a big chunk of sky around NJ/NY), from surface to FL180.  This pilot misunderstood the dimensions of the TFR. Hilarity ensues.

Poor guy, he actually handles it pretty well, given the cirumstances. As luck would have it, the exchange happens from 2026z to around 2035z, and some convo is lost during the archive rollover.

The lost content consists of the pilot asking whether he can make repeated departures from the airport, and if memory serves, the controller asks if the Cessna has his escort in sight.

Edited archive is attached, removed some silence (although I kept the brief silence that follows after the first mention of the F16 escort). It's a brown trousers moment that I couldn't trim.
Logged

KS Flight Log - pics, videos, ATC/intercom audio and in depth flight reviews
PilotEdge - add ATC to your simulation experience
RayZor
Jr. Member
**
Offline Offline

Posts: 66


« Reply #1 on: September 18, 2006, 06:47:23 PM »

You were right about the pilot handling the situation well...I probably would have been crying if that happened to me.  Does anybody know what number that was he had to call?  And what kind of consequences will he face since he violated the TFR?
Logged
Jason
Hero Member
*****
Offline Offline

Posts: 1260


CFI/CFII


« Reply #2 on: September 18, 2006, 07:50:12 PM »

You were right about the pilot handling the situation well...I probably would have been crying if that happened to me.  Does anybody know what number that was he had to call?  And what kind of consequences will he face since he violated the TFR?

The number Morristown tower gave to the pilot rings N90 (NY TRACON) in Westbury, LI.  Most likely not a direct line to the Operation (Radar) Room; however it probably goes to the supervisor on duty at the time or an FAA representative.  Usually they give you the number for the nearest FSDO, but in this case it's a number to the TRACON.

To me, it appears he violated 14 CFR §91.141 (Flight restrictions in the proximity of the Presidential and other parties.) in addition to §91.103 (Preflight action.)

Not sure what kind of consequences he'll face for violating the TFR...that's up the FAA.

Although I do agree the pilot did handle the situation well, I have a hard time trying to figure out how some pilots either don't know the specific details of such a TFR, if any.  §91.103 (which I freakishly have memorized) states  "Each pilot in command shall, before beginning a flight, become familiar with all available information concerning that flight."  I received at least 1 (possibly 2) e-mails from AOPA regarding the NY Airspace TFR, and the TFR is graphically depicted on many sources.  Sigh.

Jason

P.S. Good catch, Keith!  Thanks for posting.  Hopefully many pilots can learn from this incident.
« Last Edit: September 18, 2006, 08:00:30 PM by Jason » Logged
KSYR-pjr
Hero Member
*****
Offline Offline

Posts: 1722



« Reply #3 on: September 19, 2006, 01:38:51 PM »

For a moment I thought that was the same pilot who really botched the OSH arrival over the summer.  The voices were similar.  However, after re-listening to the OSH clip, I discovered the tail ids were different.
Logged

Regards, Peter
ATC Feed:  Syracuse (KSYR), NY
KTUS
Newbie
*
Offline Offline

Posts: 17


« Reply #4 on: September 19, 2006, 05:49:26 PM »

This may not be his only problem. I just looked up the tail number N8192L and the FAA web site had this to say...


ATTENTION!
This aircraft's registration status may not be suitable for operation.
Please contact the Aircraft Registration Branch at 1-866-762-9434 for additional information.
Logged
Ryfly
Newbie
*
Offline Offline

Posts: 2


WWW
« Reply #5 on: September 24, 2006, 04:03:58 AM »

So what phone number are They talking about?
Logged
flying2275
Newbie
*
Offline Offline

Posts: 1


« Reply #6 on: June 25, 2007, 12:45:07 AM »

So what phone number are They talking about?
I just tried calling it and its been disconected
Logged
Trevor
Newbie
*
Offline Offline

Posts: 5


« Reply #7 on: June 25, 2007, 09:53:26 AM »

So what phone number are They talking about?
I just tried calling it and its been disconected

Why would you do that? This is why phone numbers should be beeped out of recordings. Sigh.
Logged
crash
Newbie
*
Offline Offline

Posts: 12


« Reply #8 on: June 27, 2007, 08:03:04 PM »

So what phone number are They talking about?

Controllers give a pilot a phone number to call when they violate a regulation, in this case he busted into a TFR.  Its the one thing pilots dread the most. Once you land you call it and its usually goes to the ATC supervisor and they talk things out to see what happened and if it is severe enough the case goes to the FAA for an enforcement action.
Logged
LockedinIMC
Newbie
*
Offline Offline

Posts: 7



« Reply #9 on: July 08, 2007, 04:20:27 AM »

So what phone number are They talking about?
I just tried calling it and its been disconected

Thats stupid of you.
Logged
The Hoffspatcher
Jr. Member
**
Offline Offline

Posts: 84


« Reply #10 on: July 08, 2007, 08:51:39 AM »

I feel sorry for that guy ... lets remember to read those NOTAMs people, or, call 1-800-WX-BRIEF and have them read to you  cheesy
Logged

Ben Hoffman; BAv, ADX
Trust your Dispatcher!
Studentpilo
Newbie
*
Offline Offline

Posts: 43


« Reply #11 on: July 08, 2007, 12:09:07 PM »

Good luck getting an FSS on the phone  rolleyes
Logged
crash
Newbie
*
Offline Offline

Posts: 12


« Reply #12 on: July 09, 2007, 01:23:41 AM »

Good luck getting an FSS on the phone  rolleyes

Ha ha, they have gotten slower lateley!
Logged
digger
Sr. Member
****
Offline Offline

Posts: 281


« Reply #13 on: July 09, 2007, 08:07:22 AM »

From what I hear, a "Temporary" Flight Restriction could be expired before they pick up the line...     rolleyes
Logged
dave
Site Founder
Administrator
Hero Member
*****
Offline Offline

Posts: 3628



WWW
« Reply #14 on: July 09, 2007, 01:27:36 PM »

From what I hear, a "Temporary" Flight Restriction could be expired before they pick up the line...     rolleyes

I can vouch for this.  It's a good thing that plenty of weather outlets exist online (like ADDS, etc.).  I waited 20 minutes for an FSS person to pick up twice in the last 3 days.  The first time I just gave up.  Yesterday the FSS guy that answered heard me complaining to my passengers - he picked up right in the middle of my rant and profusely apologized for the delay.  Apparently they have fewer people on staff now.  Is pilot and passenger safety something we as a community really want to skimp on?

I hope Lockheed-Martin has a lot of liability insurance - if an accident were to happen due to FSS never providing this much needed service, a service that pilots are *trained* to use, then I fear their useful life providing this service will be short.

Where is the accountability?

-dave




Logged
Pages: [1] 2 Go Up Print 
« previous next »
Jump to:  


Login with username, password and session length

Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2011, Simple Machines Valid XHTML 1.0! Valid CSS!