TARGY One Departure KWYS
Posted: Sat Dec 02, 2017 5:26 am
https://skyvector.com/files/tpp/1712/pdf/00632TARGY.PDF
So KWYS is an uncontrolled field. So my first question about this departure procedure is would a pilot file it as part of their flight plan? Usually when I do my FP on Skyvector it add the departure name in my FP string but when I put LO or Targy into my FP it didnt. Another weird thing to me is that there is a "W" on the LO which is the NDB. Where does the W come from? There is an intersection or waypoint Targy and the NDB identifier is LO but does LOW or the W have any meaning?
My FP from KWYS to KIDA last night was SABAT V365 IDA. I flew the Targy One Departure since I departed rwy 19 so it was basically straight out but should I of listed it or can the controller not accept it as part of the plan? If I did include it would it of looked like this LOW1.LOW SABAT V365 IDA? Because there is no fix named LOW in that area but that is how it is listed on the plate. Just trying to get a better idea of what that is all about.
So KWYS is an uncontrolled field. So my first question about this departure procedure is would a pilot file it as part of their flight plan? Usually when I do my FP on Skyvector it add the departure name in my FP string but when I put LO or Targy into my FP it didnt. Another weird thing to me is that there is a "W" on the LO which is the NDB. Where does the W come from? There is an intersection or waypoint Targy and the NDB identifier is LO but does LOW or the W have any meaning?
My FP from KWYS to KIDA last night was SABAT V365 IDA. I flew the Targy One Departure since I departed rwy 19 so it was basically straight out but should I of listed it or can the controller not accept it as part of the plan? If I did include it would it of looked like this LOW1.LOW SABAT V365 IDA? Because there is no fix named LOW in that area but that is how it is listed on the plate. Just trying to get a better idea of what that is all about.