1 / 34

Flying from Atlanta to Boston with TeleType GPS

Flying from Atlanta to Boston with TeleType GPS. KLZU to KBED May 27, 2005. Pre-Flight Planning. AOPA DUATS Flight Planner showed good tailwinds, 5.5 hours enroute Piper Turbo Arrow N47912 has 7 hours fuel St. Mary's County Airport (2W6) is half way

meagan
Télécharger la présentation

Flying from Atlanta to Boston with TeleType GPS

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Flying from Atlanta to Bostonwith TeleType GPS KLZU to KBED May 27, 2005

  2. Pre-Flight Planning • AOPA DUATS Flight Planner showed good tailwinds, 5.5 hours enroute • Piper Turbo Arrow N47912 has 7 hours fuel • St. Mary's County Airport (2W6) is half way • Good refueling stop along route, VFR expected • Will pass 2W6 before sunset • Stay there often • ATE + TTG > 6.0 hours is "BINGO" • ATE + TTG are Actual Time Enroute + Time To Go • BINGO: mission rule refuel stop time limit • Flew non-stop, refueling stop not needed

  3. DUATS Flight Plan • Requested LZU to BED • DUATS approximates great circle route • Does not generate FAA preferred routes CORCE V222 BZM V20 COLIN V213 RBVV123 LGA V433BDR V229 DVANY V1 WHYB • Manually change to previous clearance route CORCE V222 BZM V20 COLIN V16 JFK V229HFD DREEM • 11,000 ft to take advantage of tailwinds • Cleared as filed!

  4. Entering Flight Plan Route • Start by Clearing route • Enter origin airport • In Airport text box, K-prefix is optional

  5. Enter First Waypoint • Flight plan has CORCEintersection • Clearance will say"Radar Vectors to Sugarloaf", skipping CORCE and ODF

  6. Enter Victor Airway, Next Fix • CORCE V222 BZMexpands to insert ODFand SUG • If you make an error typing the Vnnn or fix,TTGPS reports an error

  7. Enter Pairs of Vnnn and Fixes • Check current fix, enternext Vnnn and fix • Updated MagneticBearings (MBG) andDistances providesanity checks • Out-of-order entries willhave obviously wrongheadings and distances

  8. Victor Airways Reduce Work • BZM V20 COLIN expands to insertSBV RIC TAPPA

  9. Preferred Route Past NYC • COLIN V16 JFK is theFAA preferred route • Altitude assignment willbe 7000 feet over JFK

  10. Preferred Route After NYC • Dog leg to PUGGS avoids LGA traffic • Controllers often "Clear direct to HFD" whenBDR and HFD arealigned, straight lineto DREEM

  11. Final Fix Before Destination • V229 ends at DVANY • DREEM is on extendedHFD R053 • After HFD, enter directto DREEM waypoint

  12. Enter Destination Airport • Hanscom Field, BedfordMassachusetts

  13. Route is Complete • Completed flight routeshows no wind timeenroute estimate • Favorable wind forecaston DUATS showed anestimate of 5.5 hrs.

  14. Save Route • Default file name isORIG-DEST.trp • klzu-kbed.trp

  15. TTGPS Shows Destination • This reconstruction ofthe flight route showsthe route in green andthe trace of the flight in black • No GPS signal present

  16. Reviewing the Route • Pilot can view route,drag column headers orscroll table left/right tosee Vnnn details • Entered fixes are uppercase, expansions lower • Press on column headDist or Time and selectLeg, So Far or To Goto select calculations

  17. Reviewing Waypoints • Tools > Waypointsleads to dialog

  18. Info About Waypoints • Click on Start waypoint • Shows airport name • Lat/Long

  19. Other Enroute Fixes • Example: Hartford, CN • On Victor 229 • VOR-DME

  20. Destination Airport • Hanscom Field, KBED

  21. Simulate Flight Route • Right-click on route • Select Start Simulator

  22. Start Sim • Select fix • Reset Actual TimeEnroute • OK

  23. Sim Starts • Aircraft icon followsflight plan route • Bottom right corner ofmap shows FR:71g(fuel remaining) • FR is computed fromaircraft profile and flighttime

  24. Review of Flight • Flight plan, actual flighttrace, paused Sim • Sim follows stored route • Altimeter and GPS ALTwill vary with weather

  25. Review Flight at 50nm Scale • Takeoff on RW25 • Departure gave radarvectors • Then cleared direct to Sugarloaf

  26. Up the Coast • Over Virginia • By Atlantic City

  27. Last Segments • Near Philadelphia • Over JFK • Over Worcester Mass • Bedford, Mass

  28. Approach to Bedford • Hanscom ATIS: • Expect Visual ApproachRunway 29

  29. Visual Approach RWY29 • Entered Left Downwind • Taxi to refuel

  30. Reviewing Trace Data • Trace data can bedisplayed during andafter the flight • File auto-saves • Save named file afterflight for review

  31. Trace Data After Takeoff • Showing trace dataright after takeoff • UTC avoids problemswith time zone changes • Trace info is GPS data

  32. Trace Point Information • Press on trace line • Select Info… from menu • Handy for start and endtimes for logbook • This flight took 5h26m

  33. Turn Anticipation • Countdown starts 30s before fix • Turn time is angle / 3° per sec • Half before fix, half after • Starts turn at angle/6+3s beforeflyover time • Pilot can adjust for roll rate • Displays next fix and heading:WPT: JFK65° to PUGGSin 20s • After passing fix:WPT: PUGGS

  34. Conclusion • TTGPS is very handy and intuitive to use • Victor Airways support eases pilot workload • In-flight calculations improve situational awareness and safety • Trace information aids post-flight review • Turn anticipation is a technology demonstration that shows how computing power can augment GPS

More Related