# False Report? **URL:** \ **Category:** General\ **Created:** [May 15, 2006, 6:21pm UTC](https://discussions.flightaware.com/t/false-report/1352 "2006-05-15T18:21:15Z")\ **Posts on this page:** 16\ **Page:** 1
**Author:** ![JHEM](https://sea1.discourse-cdn.com/flex019/user_avatar/discussions.flightaware.com/jhem/32/9683_2.png) [@JHEM](https://discussions.flightaware.com/u/JHEM)\ **Post date:** [May 15, 2006, 6:21pm UTC](https://discussions.flightaware.com/t/false-report/1352/1 "2006-05-15T18:21:15Z")
[Any ideas on what caused this flight to take a reported one minute to cover this distance?](http://flightaware.com/live/flight/N669AF/history/20060515/1406Z/KVUJ/KPDK) My son’s PC12 must have magically turned into an SR71! Regards, James ---
**Author:** ![dbaker](https://sea1.discourse-cdn.com/flex019/user_avatar/discussions.flightaware.com/dbaker/32/97166_2.png) [@dbaker](https://discussions.flightaware.com/u/dbaker)\ **Post date:** [May 15, 2006, 6:31pm UTC](https://discussions.flightaware.com/t/false-report/1352/2 "2006-05-15T18:31:34Z")
Checked the data on that flight – we got an IFR cancellation a few minutes after takeoff and then the flight continued to send IFR radar position updates although never sent another departure, amendment, or arrival. Looks like a glitch on the FAA side. ---
**Author:** ![pika1000](https://sea1.discourse-cdn.com/flex019/user_avatar/discussions.flightaware.com/pika1000/32/124076_2.png) [@pika1000](https://discussions.flightaware.com/u/pika1000)\ **Post date:** [May 15, 2006, 7:04pm UTC](https://discussions.flightaware.com/t/false-report/1352/3 "2006-05-15T19:04:36Z")
SUUURRRREEEE… Blame the FAA…take the easy way out… ---
**Author:** ![JHEM](https://sea1.discourse-cdn.com/flex019/user_avatar/discussions.flightaware.com/jhem/32/9683_2.png) [@JHEM](https://discussions.flightaware.com/u/JHEM)\ **Post date:** [May 15, 2006, 7:05pm UTC](https://discussions.flightaware.com/t/false-report/1352/4 "2006-05-15T19:05:22Z")
Thanks, I rather suspected a hiccup on the FAA side. Regards, James ---
**Author:** ![BTaylor](https://sea1.discourse-cdn.com/flex019/user_avatar/discussions.flightaware.com/btaylor/32/76077_2.png) [@BTaylor](https://discussions.flightaware.com/u/BTaylor)\ **Post date:** [May 16, 2006, 9:38am UTC](https://discussions.flightaware.com/t/false-report/1352/5 "2006-05-16T09:38:09Z")
> [@pika1000](#): > > SUUURRRREEEE… Blame the FAA…take the easy way out… I’m willing to bet it IS on the FAA end, I’ll put my money on FA. Who are you going to trust, the FAA who claims to be broke, or FA who is bringing you this great free site in spite of them? 🙂 ---
**Author:** ![pika1000](https://sea1.discourse-cdn.com/flex019/user_avatar/discussions.flightaware.com/pika1000/32/124076_2.png) [@pika1000](https://discussions.flightaware.com/u/pika1000)\ **Post date:** [May 16, 2006, 12:05pm UTC](https://discussions.flightaware.com/t/false-report/1352/6 "2006-05-16T12:05:39Z")
I’ll go with the popular opinion… Blame George!!! ---
**Author:** ![cfijames](https://avatars.discourse-cdn.com/v4/letter/c/b487fb/32.png) [@cfijames](https://discussions.flightaware.com/u/cfijames)\ **Post date:** [May 17, 2006, 11:05pm UTC](https://discussions.flightaware.com/t/false-report/1352/7 "2006-05-17T23:05:49Z")
We had an IFR on file, but we decided to go VFR to avoid the TRBOW7 arival into PDK which is a pain in the ass and takes more time. Tower gave us a squawk code while we were still on the ground. We werent able to reach approach until we were at 3000 feet or so, and then we were radar contact. So maybe something in the system kept us as IFR until we were able to get in radar contact with Greensboro. Dunno…I know it took longer than 1 minute though! ---
**Author:** ![pika1000](https://sea1.discourse-cdn.com/flex019/user_avatar/discussions.flightaware.com/pika1000/32/124076_2.png) [@pika1000](https://discussions.flightaware.com/u/pika1000)\ **Post date:** [May 18, 2006, 11:59am UTC](https://discussions.flightaware.com/t/false-report/1352/8 "2006-05-18T11:59:20Z")
How could you admit that it took more than one minute??? You dad is going to be devistated!!! ---
**Author:** ![JHEM](https://sea1.discourse-cdn.com/flex019/user_avatar/discussions.flightaware.com/jhem/32/9683_2.png) [@JHEM](https://discussions.flightaware.com/u/JHEM)\ **Post date:** [May 24, 2006, 1:15am UTC](https://discussions.flightaware.com/t/false-report/1352/9 "2006-05-24T01:15:21Z")
> [@pika1000](#): > > How could you admit that it took more than one minute??? You dad is going to be devistated!!! [Looks like the boy did it again!](http://flightaware.com/live/flight/N619AF/history/20060522/1609Z/KAAF/KPNS) Two minutes from Apalachicola to Pensacola this morning. I sure hope we get to blame the FAA again. 😉 Regards, James ---
**Author:** ![dbaker](https://sea1.discourse-cdn.com/flex019/user_avatar/discussions.flightaware.com/dbaker/32/97166_2.png) [@dbaker](https://discussions.flightaware.com/u/dbaker)\ **Post date:** [May 24, 2006, 3:00am UTC](https://discussions.flightaware.com/t/false-report/1352/10 "2006-05-24T03:00:54Z")
Yeah – a flight plan cancellation minutes after the arrival and then only a handful of radar position updates followed by a flight plan for the INT-PWK leg. ---
**Author:** ![JHEM](https://sea1.discourse-cdn.com/flex019/user_avatar/discussions.flightaware.com/jhem/32/9683_2.png) [@JHEM](https://discussions.flightaware.com/u/JHEM)\ **Post date:** [May 24, 2006, 3:33am UTC](https://discussions.flightaware.com/t/false-report/1352/11 "2006-05-24T03:33:39Z")
Thanks for the update. I knew it couldn’t have been YOU guys. Regards, James ---
**Author:** ![cfijames](https://avatars.discourse-cdn.com/v4/letter/c/b487fb/32.png) [@cfijames](https://discussions.flightaware.com/u/cfijames)\ **Post date:** [May 24, 2006, 3:34am UTC](https://discussions.flightaware.com/t/false-report/1352/12 "2006-05-24T03:34:25Z")
We went VFR the whole way. We were supposed to leave out of Pensecola at 3, but the pax wanted to go at EIGHT! We were there early to begin with (anything to get out of Apalachicola), plus I didnt realize that Pensecola is central time, so another hour. Anyway, the INT flight was pushed back to 5, and the PWK flight never happened. INT-MDW the next morning, and tomorrow MDW-PWK (yes i know, its only 20 miles) and then back down to INT. BORING. Oh well, still cant believe they pay me for this. ---
**Author:** ![JHEM](https://sea1.discourse-cdn.com/flex019/user_avatar/discussions.flightaware.com/jhem/32/9683_2.png) [@JHEM](https://discussions.flightaware.com/u/JHEM)\ **Post date:** [May 24, 2006, 3:52am UTC](https://discussions.flightaware.com/t/false-report/1352/13 "2006-05-24T03:52:43Z")
Thanks for the update. You can tell me about the ball game tomorrow. Pop ---
**Author:** ![JHEM](https://sea1.discourse-cdn.com/flex019/user_avatar/discussions.flightaware.com/jhem/32/9683_2.png) [@JHEM](https://discussions.flightaware.com/u/JHEM)\ **Post date:** [May 25, 2006, 11:05pm UTC](https://discussions.flightaware.com/t/false-report/1352/14 "2006-05-25T23:05:15Z")
[Got another one for you Dan!](http://flightaware.com/live/flight/N619AF) Duplication of N number? AFAIK the KMMU-KHTO-KMHT schedule is the correct one. Could just be a scheduling glitch on the part of Planesense as well. Regards, James ---
**Author:** ![dbaker](https://sea1.discourse-cdn.com/flex019/user_avatar/discussions.flightaware.com/dbaker/32/97166_2.png) [@dbaker](https://discussions.flightaware.com/u/dbaker)\ **Post date:** [May 25, 2006, 11:26pm UTC](https://discussions.flightaware.com/t/false-report/1352/15 "2006-05-25T23:26:19Z")
Probably a mistake that the operator made – usually duped N numbers are very short ones. The bogus flights will be automatically removed. ---
**Author:** ![JHEM](https://sea1.discourse-cdn.com/flex019/user_avatar/discussions.flightaware.com/jhem/32/9683_2.png) [@JHEM](https://discussions.flightaware.com/u/JHEM)\ **Post date:** [May 25, 2006, 11:29pm UTC](https://discussions.flightaware.com/t/false-report/1352/16 "2006-05-25T23:29:29Z")
Thank you for the explanation sir. Regards, James