If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below. |
|
|
Thread Tools | Display Modes |
|
#1
|
|||
|
|||
|
#2
|
|||
|
|||
|
#3
|
|||
|
|||
"David Megginson" wrote in message
et.cable.rogers.com Since there's no point filing a flight plan that you cannot legally use, that seems to settle the point. Not necessarily. I certainly filed quite a number of IFR flight plans during my instrument training and I certainly did use them legally even though I was not PIC for the training flights. -- John T http://tknowlogy.com/TknoFlyer http://www.pocketgear.com/products_s...veloperid=4415 ____________________ |
#4
|
|||
|
|||
I have tried to do such a thing down here in the Houston terminal
airspace to try and circumvent a common practice by the TRACON. It didnt work for me. What I did, which I garnered from usenet, was file an IFR plan under DUATS with VFR in the altitude block, and VFR flight following in the remarks section. The rationale was based on the fact that when you are placed in the system from a flight following standpoint, you have to submit nearly the same info that you would to get an IFR plan (pop up or pre-filed). You are assigned a data block just like any other IFR plan, the only diff is that unless in Class B, separation isnt the controllers "fault". Well.. it may work elsewhere, but it does NOT work in Houston. The standard practice in Houston is NO HANDOFFS for VFR's at all. Cant even get a "center" code, rather than a "local" code if you call up early on clearance delivery. If its night, and slow, sometimes I can get Houston to take the handoff coming back IN from the Center's territory but never on the outbound leg. Dave PPSEL Paul Safran wrote: I seem to have read or been told once that, one can file an IFR flightplan with remark for VFR flight conditions when not instrument rated, or current, to get routing and practice within the system. Comments? |
#5
|
|||
|
|||
"Dave S" wrote in message link.net... I have tried to do such a thing down here in the Houston terminal airspace to try and circumvent a common practice by the TRACON. It didnt work for me. What I did, which I garnered from usenet, was file an IFR plan under DUATS with VFR in the altitude block, and VFR flight following in the remarks section. The rationale was based on the fact that when you are placed in the system from a flight following standpoint, you have to submit nearly the same info that you would to get an IFR plan (pop up or pre-filed). You are assigned a data block just like any other IFR plan, the only diff is that unless in Class B, separation isnt the controllers "fault". Well.. it may work elsewhere, but it does NOT work in Houston. The standard practice in Houston is NO HANDOFFS for VFR's at all. Cant even get a "center" code, rather than a "local" code if you call up early on clearance delivery. If its night, and slow, sometimes I can get Houston to take the handoff coming back IN from the Center's territory but never on the outbound leg. Hello Dave, Regarding VFR flights departing the Houston area... Are you saying that Houston Center will generally not take a VFR handoff from Houston Approach? Or are you saying Approach will not accept a VFR handoff from a tower? Which airport exactly are you talking about, as an example? DWH? SGR? ?? Cheers, John Clonts Temple, Texas N7NZ |
#6
|
|||
|
|||
I am saying that Houston APPROACH will not hand off outbound VFR's to
Center, and Approach will RARELY accept inboung VFR's as handoff's with regards to flight following. It is particularly frustrating because folks at Regional Approach (Dallas) work the handoff's both ways pretty much 100% of the times I've been there. I personally would much rather be talking to someone, or be in the system. I dont mind taking a vector even though its "voluntary" if it helps me stay separated. And while I dont rely on it, it's nice to have another set of eyes calling pertinent traffic when able The occasions that I have departed from towered fields in the HOU terminal airspace, I have only recieved a local (tower or Tracon) code with regards to VFR flight following. Never a center code, even when they know you are heading out of bounds. The drill is "get terminated, call up the center in a few miles" I apologize for not being more clear in my initial post. Dave John Clonts wrote: "Dave S" wrote in message link.net... I have tried to do such a thing down here in the Houston terminal airspace to try and circumvent a common practice by the TRACON. It didnt work for me. What I did, which I garnered from usenet, was file an IFR plan under DUATS with VFR in the altitude block, and VFR flight following in the remarks section. The rationale was based on the fact that when you are placed in the system from a flight following standpoint, you have to submit nearly the same info that you would to get an IFR plan (pop up or pre-filed). You are assigned a data block just like any other IFR plan, the only diff is that unless in Class B, separation isnt the controllers "fault". Well.. it may work elsewhere, but it does NOT work in Houston. The standard practice in Houston is NO HANDOFFS for VFR's at all. Cant even get a "center" code, rather than a "local" code if you call up early on clearance delivery. If its night, and slow, sometimes I can get Houston to take the handoff coming back IN from the Center's territory but never on the outbound leg. Hello Dave, Regarding VFR flights departing the Houston area... Are you saying that Houston Center will generally not take a VFR handoff from Houston Approach? Or are you saying Approach will not accept a VFR handoff from a tower? Which airport exactly are you talking about, as an example? DWH? SGR? ?? Cheers, John Clonts Temple, Texas N7NZ |
#7
|
|||
|
|||
"Dave S" wrote in message link.net... The occasions that I have departed from towered fields in the HOU terminal airspace, I have only recieved a local (tower or Tracon) code with regards to VFR flight following. Never a center code, even when they know you are heading out of bounds. The drill is "get terminated, call up the center in a few miles" We do this as standard procedure because that's what people want. We have found that virtually nobody wants center flight following, less than 5% ask for it, whether on the ground before departure or in the air. |
#8
|
|||
|
|||
We have found that virtually nobody wants center flight following, less than 5% ask for it, whether on the ground before departure or in the air. If somebody calls asking for center flight following, do you still assume they dont' want it? Jose -- (for Email, make the obvious changes in my address) |
#9
|
|||
|
|||
"Dave S" wrote in message link.net... I have tried to do such a thing down here in the Houston terminal airspace to try and circumvent a common practice by the TRACON. It didnt work for me. What I did, which I garnered from usenet, was file an IFR plan under DUATS with VFR in the altitude block, and VFR flight following in the remarks section. The rationale was based on the fact that when you are placed in the system from a flight following standpoint, you have to submit nearly the same info that you would to get an IFR plan (pop up or pre-filed). You are assigned a data block just like any other IFR plan, the only diff is that unless in Class B, separation isnt the controllers "fault". Well.. it may work elsewhere, but it does NOT work in Houston. The standard practice in Houston is NO HANDOFFS for VFR's at all. Cant even get a "center" code, rather than a "local" code if you call up early on clearance delivery. If its night, and slow, sometimes I can get Houston to take the handoff coming back IN from the Center's territory but never on the outbound leg. VFR handoffs are procedurally suppressed in many parts of the country because the local controllers have convinced themselves that they are too busy and too important to bother themselves with trivial matters like VFR flight following. Houston suffers from that corporate attitude, as do other facilities. In most locations, like in Houston, this controller attitude is pathetically laughable. Chip, ZTL |
#10
|
|||
|
|||
"Chip Jones" wrote: In most locations, like in Houston, this controller attitude is pathetically laughable. Yes, it's bad in Houston; I never ask them for advisories anymore. Even if they do take you, they may fail to call traffic. But if you listen to their frequencies on a nice Friday afternoon, you can almost understand their attitude. The miserable radio technique of a lot of VFR pilots can really clog up the air. It's embarassing to listen to, sometimes. -- Dan C172RG at BFM |
Thread Tools | |
Display Modes | |
|
|
Similar Threads | ||||
Thread | Thread Starter | Forum | Replies | Last Post |
AOPA Stall/Spin Study -- Stowell's Review (8,000 words) | Rich Stowell | Aerobatics | 28 | January 2nd 09 02:26 PM |
Logging approaches | Ron Garrison | Instrument Flight Rules | 109 | March 2nd 04 05:54 PM |
FAA letter on flight into known icing | C J Campbell | Instrument Flight Rules | 78 | December 22nd 03 07:44 PM |
Sim time loggable? | [email protected] | Instrument Flight Rules | 12 | December 6th 03 07:47 AM |
IFR flight plan filing question | Tune2828 | Instrument Flight Rules | 2 | July 23rd 03 03:33 AM |