Jump to content

Search the Community

Showing results for tags 'around the world'.

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

  • New Forum Software - Suggestions
    • New Forum Software
  • Microsoft Flight Simulator 2024 - Early Discussion
    • Microsoft Flight Simulator 2024 - Early Discussion
  • Microsoft Flight Simulator 2020
    • Microsoft Flight Simulator 2020 General Discussion
    • MSFS 2020 Aircraft and Helicopters Discussion
    • MSFS Navigation - FMC Systems and Avionics
    • MSFS Screenshots and Videos Forum
    • MSFS 2020 News
    • News from Commercial Developers
  • Microsoft FSX
    • FSX General Discussion
    • FSX Aircraft
    • FSX Scenery
    • FSX Screenshots
  • Microsoft Flight Simulators FS2004 - 2002 - Flight
    • FS2004
    • FS2002
    • Microsoft Flight
  • General Interest
    • Newcomer Services
    • The Outer Marker
    • Comments
    • Group Flights & Events
    • Swap Meet
    • Virtual Airlines
    • RSS Feeds
  • X-Plane
    • X-Plane
    • X-Plane Screen Shots And Videos
    • News, Pre-Releases & Releases
    • Developers Corner
    • X-Plane Shoutbox Forum
  • Prepar3D
    • Prepar3D
    • Prepar3D Screen Shots And Videos
    • Prepar3D Shoutbox Forum
  • Mobile Apps
    • RORTOS
    • SkyFox Games
    • Mobile Apps - General
  • Auto Sports Simulations
    • General Support
  • Other Sims
    • Military Flight Sims
    • CFS3
    • PRE-Flight
    • FlightGear Flight Simulator
    • Dovetail Games
  • Technical Forums
    • PC Hardware, Video And Audio Help
    • PC Software Tech
    • Cockpit Builders
  • Designer Forums
    • Aircraft Design
    • Painter's Workshop
    • Panel & Gauge Design
    • Scenery Design
  • Real World Aviation
    • Real Aviation General Discussion
    • Real Aviation Profiles
    • Real Aviation Photos & Videos
    • Real Aviation Favorite Headline News
    • Real Aviation Tutorials & FAQs
  • Support Forums
    • pizzagalli.ch Support
    • Airport for Windows Support
    • DreamFleet
    • Quality Wings
    • Air Manager Support
    • FS-AOM Support
    • SGA Support
  • Archive
    • FS2000
    • FS98
    • FS5
    • FS4
    • CFS
    • Scenery Design Archive
    • Aircraft Design Archive
  • Nels Corner
    • Nels Corner - News
    • Nels Corner - Articles
    • Featured Articles and Tutorials
  • Aviation Enthusiasts's Aviation Enthusiasts Topics
  • CFS3 Freaks's CFS3 Freaks Topics
  • Friends Of The fsOC 727-200's Friends Of The fsOC 727-200 Topics
  • FS9 Users's FS9 Users Topics
  • 737-200 Lovers's 737-200 Lovers Topics
  • FS9 Mulitplayer Group's FS9 Mulitplayer Group Topics
  • The Dirty Old Mens Flying Circus's The Dirty Old Mens Flying Circus Topics
  • Old lovers of old Flight Simulator versions.'s Old lovers of old Flight Simulator versions. Topics
  • All about Boeing!!!'s All about Boeing!!! Topics
  • Singapore Airlines's Singapore Airlines Topics
  • The Fokker Club's The Fokker Club Topics
  • 777's!'s 777's! Topics
  • Military aviation enthusiasts's Military aviation enthusiasts Topics
  • Aerobatics club's Aerobatics club Topics
  • In Loving Memory Of All Defunct Airlines's In Loving Memory Of All Defunct Airlines Topics
  • Chuck Norris Appreciation Group's Chuck Norris Appreciation Group Topics
  • The PMDG MD-11 Club's The PMDG MD-11 Club Topics
  • The Turboprop fan club's The Turboprop fan club Topics
  • RTW Race Team's RTW Race Team Topics
  • Dornier Group's Dornier Group Topics
  • NZCDI (New Zealand Cargo Domestic International)'s NZCDI (New Zealand Cargo Domestic International) Topics
  • Dash-8 Fans's Dash-8 Fans Topics
  • FSX lover and fans Razek's SCENERY's FSX lover and fans Razek's SCENERY Topics
  • Vatsim Users's Vatsim Users Topics
  • Icelandair Group's Icelandair Group Topics
  • Airbus Group's Airbus Group Topics
  • Southwest Airlines Fans's Southwest Airlines Fans Topics
  • DC-3 Lovers's DC-3 Lovers Topics
  • general aviation club's general aviation club Topics
  • FSX/FS9 Boeing NewAirplane Group's FSX/FS9 Boeing NewAirplane Group Topics
  • Planespotters Group's Planespotters Group Topics
  • world war 2 aircraft's world war 2 aircraft Topics
  • Project Guppy's Project Guppy Topics
  • Historic aircraft's Historic aircraft Topics
  • PNW flight group's PNW flight group Topics
  • westjet fans's westjet fans Topics
  • AI AIRCRAFT GROUP's AI AIRCRAFT GROUP Topics
  • iFly 737 NG Lovers's iFly 737 NG Lovers Topics
  • Indonesia Flight Simmer's Indonesia Flight Simmer Topics
  • Air Crash SA 252's Air Crash SA 252 Topics
  • WeFly FSX Community & Works Team's WeFly FSX Community & Works Team Topics
  • REPAINTERS CLUB's REPAINTERS CLUB Topics
  • Satellite Airways Fans and Staff's Satellite Airways Fans and Staff Topics
  • FSX Sussex Flyers's FSX Sussex Flyers Topics
  • DC-10 lovers's DC-10 lovers Topics
  • PAINTING LIVERIES FOR AIRCRAFT's I need help on painting!
  • PAINTING LIVERIES FOR AIRCRAFT's REQUEST LIVERY

Blogs

  • pedro21nn's Blog
  • Lenedog's Blog
  • pawneepilots's Blog
  • HawkOne1946's Blog
  • troygauthier71's Blog
  • michael641's Blog
  • rzdukez's Blog
  • wismor's Blog
  • UdoOertel's Blog
  • Sugus1942's Blog
  • scheffer73's Blog
  • Skinnyb8's Blog
  • KdubTheTomatoGamer's Blog
  • Garciamk3g's Blog
  • bobby25's Blog
  • Gerardo Santiago's Blog
  • kiyasuriin's Blog
  • lryrob's Blog
  • soaringeagle's Blog
  • Tytusiks's Blog
  • 22 Yankee's Blog
  • eVInteractive's Blog
  • morty1959's Blog
  • retbxdet's Blog
  • Catalin's Blog
  • chobers's Blog
  • pedroviveiros's Blog
  • RobertsDale's Blog
  • Jumpseater's Blog
  • feribambu's Blog
  • ELHOIM's Blog
  • Flatpack39's Blog
  • ThorstenRenk's Blog
  • George Smith's Blog
  • Terry12's Blog
  • Woodsie.010's Blog
  • alanmimmack's Blog
  • TraeStorm's Blog
  • bismark787's Blog
  • Edward Chudy's Blog
  • H3AZ's Blog
  • Mochafd's Blog
  • coltondou's Blog
  • congtyteambuilding's Blog
  • ron2910's Blog
  • Blondi's Blog
  • steelman78's Blog
  • dp509's Blog
  • tristan2212's Blog
  • izhar's Blog
  • trueshopee's Blog
  • aircavguy's Blog
  • DamienTan's Blog
  • simonernd's Blog
  • denzo737's Blog
  • gisbertmaurer's Blog
  • Baywoof's Blog
  • mirahu92's Blog
  • titanmoon's Blog
  • Gallo's Blog
  • Zon's Blog
  • Kreisel4's Blog
  • Dakrskythe's Blog
  • mmurphy77's Blog
  • soulmax's Blog
  • richavery's Blog
  • RichardDavis's Blog
  • Coyote Old Man's Blog
  • OscarJ1337's Blog
  • Tina_MWD's Blog
  • ginni's Blog
  • AviatorD777's Blog
  • Ferike's Blog
  • jimcarroll's Blog
  • RichAdair's Blog
  • punder's Blog
  • jmshald's Blog
  • tj4hjono's Blog
  • christian2018's Blog
  • knowlesp's Blog
  • Flug2308's Blog
  • jlbflyboy182's Blog
  • peewee's Blog
  • bhf1950's Blog
  • RonSpain's Blog
  • Harold909's Blog
  • Cmte Watts's Blog
  • hassan aldahshan's Blog
  • Jett's Blog
  • PBassMan's Blog
  • Harry Davis's Blog
  • Quackarov's Blog
  • mike_forr@hotmail.com's Blog
  • Slickrock's Blog
  • Flightsimhero's Blog
  • BrownBee89's Blog
  • GunnerOIF2003's Blog
  • Mal's Blog
  • walterpha's Blog
  • MikeUlm's Blog
  • Challengerman2016's Blog
  • takahashi kunio's Blog
  • Cesar A Sampaio's Blog
  • vicdel's Blog
  • Prospero246's Blog
  • BD018's Blog
  • eprkeeper's Blog
  • Skyflyer4's Blog
  • zxspectrum's Blog
  • Rainer Juenger's Blog
  • aussi's Blog
  • dutchvan831's Blog
  • jachor's Blog
  • PauloDuarte1981's Blog
  • Sania's Blog
  • TOCALLO's Blog
  • hippiezahn's Blog
  • Ian61's Blog
  • raz_65's Blog
  • nerotuga's Blog
  • cdavis360's Blog
  • clankilp's Blog
  • Udoudo's Blog
  • barosqueen's Blog
  • Lasamlandings's Blog
  • Jarmo's Blog
  • iloveass's Blog
  • danny_mullins's Blog
  • meinit4's Blog
  • Hobbsie71's Blog
  • Cotangens's Blog
  • Flyguy1998's Blog
  • Henry21's Blog
  • MooseGB's Blog
  • X-Octavia-X's Blog
  • LesAD10's Blog
  • chadgeezee's Blog
  • whiterock-flyboy's Blog
  • cencio's Blog
  • Edson Dias's Blog
  • LIPAO's Blog
  • robertsjohn878@gmail.com's Blog
  • Skymccloud 1's Blog
  • medic597's Blog
  • trakadasantonios's Blog
  • Albercik's Blog
  • mdamstel's Blog
  • DrMAJ's Blog
  • Marconev's Blog
  • Joemed725's Blog
  • EspanaPete's Blog
  • AviatorEevees's Blog
  • ARMY 342's Blog
  • Kahu_Helo's Blog
  • WonkaVSN02's Blog
  • NICK121's Blog
  • iaintw1's Blog
  • A319_Lica's Blog
  • TheAviationEnthusiast's Blog
  • attackace's Blog
  • Fuelin's Blog
  • topgun2369's Blog
  • hud5455's Blog
  • w1ngnut's Blog
  • cessna 150's Blog
  • Alex Dickinson's Blog
  • RayH's Blog
  • Carl Porter's Blog
  • rickkanjurmarg's Blog
  • wfrayer's Blog
  • helmis's Blog
  • caroldixen's Blog
  • digitalpilot's Blog
  • saptarshim2000's Blog
  • ATCLONDRINA's Blog
  • EmoJim's Blog
  • ZeNNeC's Blog
  • vrpilot's Blog
  • Adesoji's Blog
  • chserrano's Blog
  • koord's Blog
  • hardyje1915's Blog
  • jrcooper7's Blog
  • whiteknightz28's Blog
  • Alanalborn's Blog
  • ray56707's Blog
  • Lutz_Fl's Blog
  • dirts32's Blog
  • johnmartin1101's Blog
  • golson33's Blog
  • mrfilbert's Blog
  • pilot omar's Blog
  • koch44's Blog
  • Saaarge's Blog
  • Norman Smith's Blog
  • sheilamorse's Blog
  • animore's Blog
  • debarshiduttagupta's Blog
  • gordonrd45's Blog
  • D.Michael's Blog
  • JackRidle's Blog
  • Ted P's Blog
  • mwauge's Blog
  • DarrellWayne's Blog
  • Scimiter's Blog
  • dasher's Blog
  • breeboone's Blog
  • RobbyDark's Blog
  • George Carter's Blog
  • TAC's Blog
  • uahostee's Blog
  • NoFlyZone's Blog
  • Greyman's Blog
  • RTaylor's Blog
  • StarFlyer's Blog
  • Edmilson Honorio's Blog
  • Ictus's Blog
  • antonin.peniska's Blog
  • fabionba's Blog
  • Sierpe's Blog
  • Shami's Blog
  • luistashburner's Blog
  • Meir's Blog
  • Keith South's Blog
  • Steelersfan71bs's Blog
  • PHILIP WALKER's Blog
  • 139738's Blog
  • Gordon147's Blog
  • Mikeswa66's Blog
  • mitolima's Blog
  • Batfink's Blog
  • HolmesK's Blog
  • dlfrese's Blog
  • Jklindy16's Blog
  • gb_40_au's Blog
  • sweetness's Blog
  • von Trippenhoff's Blog
  • vmrooze's Blog
  • rdkyle43's Blog
  • bareaud's Blog
  • Bammis's Blog
  • Ramflt's Blog
  • Gabos73's Blog
  • Boyblunder's Blog
  • Tandym's Blog
  • Romeo Delta Victor's Blog
  • GhostTown's Blog
  • Christopher Shaw's Blog
  • kevgardner83's Blog
  • tonyemm's Blog
  • P Thompson's Blog
  • caj's Blog
  • David Carrancio's Blog
  • Lona's Blog
  • Jack06's Blog
  • macsmotoblog's Blog
  • klwilliams's Blog
  • SHARMAAYUSH's Blog
  • pmrose's Blog
  • knfulcrum's Blog
  • gipsymoth236k's Blog
  • Kurtn's Blog
  • Malcolm's Blog
  • Ingardy's Blog
  • david_UK's Blog
  • simonwhite1984's Blog
  • lhops's Blog
  • energy74's Blog
  • ant12's Blog
  • Skeeter_Jawn's Blog
  • cessna182@gmail.com's Blog
  • Michel Alpha's Blog
  • CAG0001's Blog
  • Viloria's Blog
  • cabofrio's Blog
  • O r t i s MCC Los key's Blog
  • Petter1's Blog
  • Jumag43's Blog
  • x 737 Pilot's Blog
  • misgav's Blog
  • Zinc22's Blog
  • assaad's's Blog
  • wdworker51's Blog
  • GIANNI.NASAZZI's Blog
  • Flighthawk's Blog
  • goggi's Blog
  • mchristens's Blog
  • VFRguy's Blog
  • vatin's Blog
  • seinogonzou's Blog
  • MLS53's Blog
  • MyiFlyUsername's Blog
  • Sgt_Tailor01's Blog
  • Roger Studer's Blog
  • rms46's Blog
  • peteralberti's Blog
  • jim@civilwar1861.com's Blog
  • Monarch1958's Blog
  • Tbolt65's Blog
  • mattbrown's Blog
  • cleme's Blog
  • phint's Blog
  • Grange Hermit's Blog
  • Cienfuego's Blog
  • pzl 104's Blog
  • yassinyoussef's Blog
  • jim8beaton's Blog
  • NDGraham's Blog
  • Roger Buckley's Blog
  • FamilyWeb's Blog
  • Hugh_Jasole's Blog
  • Thpmas397's Blog
  • Waldojr's Blog
  • Allan Rodrigues 10's Blog
  • bimbi's Blog
  • rosch's Blog
  • 1c2a3r4v5s's Blog
  • tucker935's Blog
  • HAP2's Blog
  • pierluigi's Blog
  • Vigileitor's Blog
  • jamesdcosta's Blog
  • osbo1's Blog
  • chuckiii3's Blog
  • MartinKv's Blog
  • johnbizjak's Blog
  • AndreChambers's Blog
  • Sterk03's Blog
  • Floats's Blog
  • skip1940's Blog
  • mdsbarc1's Blog
  • Digital2k20's Blog
  • Marie Nieves's Blog
  • tiger5's Blog
  • Jubiaba's Blog
  • edsmit's Blog
  • Ancient One's Blog
  • pilotbeni2's Blog
  • pikeriverman's Blog
  • qroquess's Blog
  • airlinesmain's Blog
  • brgauges's Blog
  • Willy3's Blog
  • B777200DAL's Blog
  • OpenSky's Blog
  • BillCalvert's Blog
  • soprisbp's Blog
  • JBorba's Blog
  • testacleez's Blog
  • Gugisa's Blog
  • K5083's Blog
  • mccfran's Blog
  • amiale's Blog
  • Terry628's Blog
  • jomimarpe's Blog
  • RobbAir's Blog
  • SolomonShawn's Blog
  • Araxxos's Blog
  • Moussa3105X's Blog
  • delunderpar's Blog
  • Dog#108's Blog
  • Chrisflyer's Blog
  • 2CharlieMike's Blog
  • A359-1000's Blog
  • silvano's Blog
  • james37611's Blog
  • truemetrofs's Blog
  • mabrodb's Blog
  • w. Rabello's Blog
  • aussielad's Blog
  • flyski's Blog
  • Pilotmatteo's Blog
  • Giloudu974's Blog
  • Space Cowboy's Blog
  • Theo Evers's Blog
  • carlosarruda29's Blog
  • mgscott's Blog
  • aikenscribe's Blog
  • jimmydayle's Blog
  • Larry Jay's Blog
  • LewisRobinson's Blog
  • gillesbo1@hotmail.com's Blog
  • chargr's Blog
  • BarryDon's Blog
  • Squadron350's Blog
  • salamoon2's Blog
  • filidog59's Blog
  • rgarber's Blog
  • richardhudson's Blog
  • delmac2's Blog
  • hade251's Blog
  • lindaween's Blog
  • hawky007's Blog
  • alphacrux's Blog
  • joegracia's Blog
  • Fjalar's Blog
  • Mondo70m's Blog
  • wasteram's Blog
  • eagle97233's Blog
  • DavuReuret's Blog
  • williegjohnson's Blog
  • anmolgarg123's Blog
  • IcelandicWarrior`'s Blog
  • aviator49's Blog
  • BobbyG550's Blog
  • rkv.spotter's Blog
  • VRdude's Blog
  • Brett22's Blog
  • vaca braba's Blog
  • virginlucas's Blog
  • nicolhill's Blog
  • Humbler05's Blog
  • GiveMeRoom's Blog
  • Samuel W. F. Farias's Blog
  • EDDIE53's Blog
  • pmplayer's Blog
  • C/M_Mid's Blog
  • Bossen's Blog
  • r7b's Blog
  • arosenberg's Blog
  • L Johnson's Blog
  • jwbednarz's Blog
  • Angelofly26's Blog
  • Balotta's Blog
  • Hawker77's Blog
  • Kapteinole's Blog
  • mknight1944's Blog
  • Seabreeze's Blog
  • RichSheffield's Blog
  • Kimberly_Love90's Blog
  • Patricia_Sexy22's Blog
  • Stitch-Up's Blog
  • Bgreene1's Blog
  • LeonZitron's Blog
  • Stevemill's Blog
  • Frits Egelie's Blog
  • kspider1950@outlook.com's Blog
  • supercessna's Blog
  • SeattleGA's Blog
  • Caribbean@01's Blog
  • cessnaguy's Blog
  • Kameraden's Blog
  • windme's Blog
  • milleron's Blog
  • ElwoodB_DK's Blog
  • XPICU's Blog
  • StubbornSwiss's Blog
  • FlightDreamer's Blog
  • purpletechnado's Blog
  • Hans Backstrom's Blog
  • GranddadAviator's Blog
  • OTHflier's Blog
  • jetsetter1k's Blog
  • mdelayncera's Blog
  • Upsidedown1234's Blog
  • Patrickb1973's Blog
  • JohnHump's Blog
  • StringFellow's Blog
  • Peter Rice's Blog
  • Tradingcubes's Blog
  • Xohlon's Blog
  • JohnnyJohnJohn's Blog
  • midcon07's Blog
  • Riddle92's Blog
  • BurkhardRenk's Blog
  • InspectorK's Blog
  • vLegion's Blog
  • fosheem's Blog
  • ztxz's Blog
  • ramstein's Blog
  • Av8rG33k's Blog
  • prof_87's Blog
  • GaryBUK's Blog
  • Basile1p's Blog
  • pthomas74's Blog
  • Bowman Creek's Blog
  • Netherlander's Blog
  • k3ndall's Blog
  • SD_Simpilot's Blog
  • CameraManCarl45's Blog
  • old brave math's Blog
  • Nuttyal's Blog
  • ke8yn's Blog
  • Jambo's Blog
  • Bosfor's Blog
  • Seanmo's Blog
  • rbrust's Blog
  • origincookie122's Blog
  • W1RC's Blog
  • METEOR's Blog
  • blackbearladdie's Blog
  • danaLynn's Blog
  • Jon PB's Blog
  • jeffchrisope's Blog
  • bottinga's Blog
  • corcky37's Blog
  • TBob11's Blog
  • dadsome's Blog
  • J_london's Blog
  • Andrew Herd's Blog
  • Flight Sims World
  • j_willis_jr@msn.com's Blog
  • MAD1's Blog
  • Babar Azam's Blog
  • Edzard2's Blog
  • brubsmc's Blog
  • uggenstu2's Blog
  • sublimeorc3's Blog
  • GeorgiaJedi's Blog
  • A.Bekhuis's Blog
  • learaviator's Blog
  • Bighandal's Blog
  • Steve Marine's Blog
  • ndbroome@hotmail.com's Blog
  • AYS73's Blog
  • lolanickson's Blog
  • BLEK's Blog
  • donald mackinnon's Blog
  • kik707's Blog
  • sereaton737's Blog
  • Simuser Doc's Blog
  • Upgently's Blog
  • acg's Blog
  • Mervi75's Blog
  • steelframer's Blog
  • Gary Moran's Blog
  • Hafiy's Blog
  • flightsimJim's Blog
  • 777-X's Blog
  • avarko's Blog
  • WillyCanuck's Blog
  • SimPilot 81's Blog
  • ummagumma's Blog
  • FlyingGreaseMonkey's Blog
  • Tony Volante's Blog
  • EdWill's Blog
  • TJFLYER's Blog
  • kapenagary's Blog
  • Fsdreaworldmesh's Blog
  • luiz carlos machado leite's Blog
  • cliquelack's Blog
  • Mbaril's Blog
  • Gpurg's Blog
  • squidger's Blog
  • ElderSquid's Blog
  • acflight's Blog
  • DrRimn's Blog
  • John - SAC084's Blog
  • thecorporatepilotdad's Blog
  • simoncb's Blog
  • Pilot_33624's Blog
  • Bosso's Blog
  • H724's Blog
  • isaacessex's Blog
  • jf1450's Blog
  • sethjgreenberg's Blog
  • Eurostar27's Blog
  • Bigfish's Blog
  • FlyingPenguinEDDM's Blog
  • Huddison's Blog
  • PitCom's Blog
  • neilends's Blog
  • Mad3irae's Blog
  • gilmaralmeidailheus's Blog
  • zubairkhan's Blog
  • M1 Garand's Blog
  • Billf's Blog
  • cmat's Blog
  • Philjd's Blog
  • ToMiJo's Blog
  • cartera's Blog
  • Alyssalauren's Blog
  • CLE_GrummanTiger's Blog
  • movierunner's Blog
  • Greg C.'s Blog
  • jefevv69's Blog
  • rittash's Blog
  • ianfisher's Blog
  • EVP001's Blog
  • Brian_90Web's Blog
  • johnfbolton47's Blog
  • Rui Jam's Blog
  • gmvaughan's Blog
  • MichelDR400's Blog
  • Robopil's Blog
  • dfreund@sbcglobal.net's Blog
  • DBoydNL's Blog
  • Zinertek's Blog
  • en7613's Blog
  • Michmich38's Blog
  • virtualgaa's Blog
  • snacey's Blog
  • BigStubby's Blog
  • Ecurb's Blog
  • djtnm's Blog
  • josue9920's Blog
  • Simon Castro's Blog
  • stingraybite's Blog
  • dieferson's Blog
  • Sensei's Blog
  • Bump's Blog
  • simairjfk's Blog
  • kain270's Blog
  • Bayvista170's Blog
  • randythepilot's Blog
  • jennie13's Blog
  • nightrider2861's Blog
  • creeker1's Blog
  • garcidi67's Blog
  • JR-Honeycomb's Blog
  • rhab's Blog
  • Alpeggio's Blog
  • dhammond's Blog
  • TawasAir's Blog
  • MaxwellMiky's Blog
  • 767mani's Blog
  • Sim Picklins's Blog
  • mikey442100's Blog
  • Felp1zZ's Blog
  • Mike M 61's Blog
  • nascarbob52's Blog
  • Professor Solderflux's Blog
  • bravoairspace123's Blog
  • eagleiceqc's Blog
  • EDER's Blog
  • glackey495@aol.com's Blog
  • Philstar's Blog
  • donnabrown2813's Blog
  • James Franklin Davis's Blog
  • hot queens's Blog
  • PhrogPhlyer's Blog
  • petersons's Blog
  • FBM953's Blog
  • mamock's Blog
  • Hbphmi's Blog
  • adeelzaidi's Blog
  • syldair's Blog
  • iloveKLM's Blog
  • bigfg's Blog
  • senna94f1's Blog
  • poulsenar's Blog
  • Bob McFarlane's Blog
  • Breus's Blog
  • Rocky Mountain Aero's Blog
  • mike1642's Blog
  • stussy's Blog
  • tunstell's Blog
  • vlasb's Blog
  • N4BWD's Blog
  • da42's Blog
  • Murf7413's Blog
  • SWV14407's Blog
  • John alex's Blog
  • James_TBS's Blog
  • The One and Only's Blog
  • BRIANWHARRISMD@GMAIL.COM's Blog
  • maxmilianoribeiro's Blog
  • shs918's Blog
  • KRDalton88's Blog
  • JAXflight's Blog
  • Terry_F's Blog
  • Head In The Clouds's Blog
  • SAMEO423's Blog
  • newbert's Blog
  • magenois's Blog
  • watsonwalk's Blog
  • lopça's Blog
  • AdventumSims's Blog
  • amarfly's Blog
  • Conyjohn's Blog
  • Mr. Bill's Blog
  • Andrejkatin's Blog
  • henrynikk07's Blog
  • Zig01's Blog
  • sandyd's Blog
  • gangesboy's Blog
  • ethanmiles's Blog
  • NoFace's Blog
  • David Sellens's Blog
  • ECCP's Blog
  • EJR's Blog
  • willcraft's Blog
  • ccc2's Blog
  • Nativeassignment's Blog
  • ringbaloo's Blog
  • sooner_jack's Blog
  • Zachary J's Blog
  • Luciokessler's Blog
  • muldersj@muldersj.plus.com's Blog
  • JJW 75's Blog
  • flight28042's Blog
  • EnvironmentTalks's Blog
  • hawaalbaher's Blog
  • charlibilson's Blog
  • ZaraBolen's Blog
  • reviewexpressnet's Blog
  • issacmartinus's Blog
  • badacare's Blog
  • 31Foxhound's Blog
  • xxKyle2020xx's Blog
  • jurobo2000's Blog
  • NIregoRedd's Blog
  • zabuza88's Blog
  • john.millbrech@outlook.co's Blog
  • Aviator Dave's Blog
  • PilotWave's Blog
  • asrra's Blog
  • PILOTO GOL's Blog
  • Flyer.Ron's Blog
  • Golgotha's Blog
  • propercharles's Blog
  • Chief Wally's Blog
  • danielflopes's Blog
  • zakariyoung's Blog
  • Smikkelbeer72's Blog
  • Jimfish's Blog
  • molydoly's Blog
  • RolfSt's Blog
  • Skitti400's Blog
  • vpilot666's Blog
  • MichalMyg's Blog
  • HSJB120's Blog
  • phoenix33500's Blog
  • LowOnCash's Blog
  • ohiotitleloans's Blog
  • IndianaTitleLoans626's Blog
  • Crunt's Blog
  • Spammy McSpamface's Blog
  • Lane House 73's Blog
  • arihantenergy's Blog
  • 23savage's Blog
  • grovak's Blog
  • lopeezca's Blog
  • michio42's Blog
  • MD60's Blog
  • hookerjaen's Blog
  • alinanew's Blog
  • carolandken653's Blog
  • ShivakKumar's Blog
  • RAMID's Blog
  • maxt78's Blog
  • chapwa0199's Blog
  • Hyperdark's Blog
  • ceaser333's Blog
  • TheDoctor's Blog
  • steveshead's Blog
  • caroljames972022's Blog
  • shukla's Blog
  • kmmiller12's Blog
  • vandanamanturgekar's Blog
  • grucha87snk's Blog
  • Adrian K's Blog
  • werbemaxe's Blog
  • CWC1960's Blog
  • Spring Fashion Man And Women
  • DCS Helicopter Collective Project
  • emailnphonelist
  • Lassen Sie der Spannung freien Lauf: Eine große Auswahl an Spielautomaten im Vulkan Vegas Online Casino
  • Welding Coolants: Boosting Productivity and Quality
  • Elevate Your Website: Freelance Web Developer and SEO Specialist
  • Let's fly the Latecoere 631 around the world.
  • MSFS SDK: How-To
  • rick's Blog
  • dbcole's Blog
  • kevchris's Blog
  • loup's Blog
  • MaxLegroom990's Blog
  • hastings's Blog
  • tdbscotland's Blog
  • JimM's Blog
  • nightwing36's Blog
  • MaverickScot's Blog
  • gary2's Blog
  • mcarvela's Blog
  • av8tor39's Blog
  • ricka47's Blog
  • cat's Blog
  • DreamFleet1's Blog
  • Nels_Anderson's Blog
  • soyuz's Blog
  • mathurpc's Blog
  • nigelgrant's Blog
  • bertvankampen's Blog
  • eacevedo's Blog
  • Glaudrung's Blog
  • tedpan's Blog
  • FearlessTower's Blog
  • skypod's Blog
  • Steve_FSD's Blog
  • mith's Blog
  • Batman2608's Blog
  • Rockcliffe's Blog
  • btwallis's Blog
  • wyattx2's Blog
  • rankin3's Blog
  • BOHICA's Blog
  • mleuck's Blog
  • paulfar's Blog
  • SteveW2's Blog
  • WingsOverCA's Blog
  • stewstewart's Blog
  • BobChurch's Blog
  • Fltsimguy's Blog
  • jimkanold's Blog
  • cfelix's Blog
  • budreiser's Blog
  • sibs6's Blog
  • doering1's Blog
  • NewtonAir's Blog
  • Malbork's Blog
  • pilotlbs's Blog
  • lplus11's Blog
  • slarente's Blog
  • jedster1's Blog
  • vaseycr's Blog
  • Argenfarkle's Blog
  • Steve Halpern's Blog
  • MikeS's Blog
  • dahawg123's Blog
  • Novatar's Blog
  • Propwash's Blog
  • UPHILL3's Blog
  • AOA_TANGO's Blog
  • flightstrike's Blog
  • cdekeyse's Blog
  • gets's Blog
  • drobson's Blog
  • aspong's Blog
  • rservice's Blog
  • titolopez's Blog
  • skyking258's Blog
  • TornadoWilkes's Blog
  • fsc_BK's Blog
  • tomavis's Blog
  • jbdc9's Blog
  • lnuss's Blog
  • RollerBall's Blog
  • skytrek's Blog
  • vergilm's Blog
  • portree's Blog
  • Matheus's Blog
  • MacKuen's Blog
  • Kurtvw's Blog
  • CaptainTower's Blog
  • happyoldone's Blog
  • Gaz's Blog
  • jwenting's Blog
  • hkpgr's Blog
  • JSkorna's Blog
  • MikePotten's Blog
  • Clarindo's Blog
  • EngEd's Blog
  • 707jet's Blog
  • gwillmot's Blog
  • windqaz's Blog
  • Dewey's Blog
  • rneale's Blog
  • scnrfrq's Blog
  • schachow's Blog
  • raybirch's Blog
  • whoosh's Blog
  • flytv1's Blog
  • bilbo's Blog
  • chapmad1's Blog
  • anscad's Blog
  • TCC's Blog
  • kilmer's Blog
  • lifejogger's Blog
  • mleegard's Blog
  • awheeler's Blog
  • baslar's Blog
  • billvons's Blog
  • Gjet's Blog
  • n4gix's Blog
  • populousste's Blog
  • flyfreedave's Blog
  • andyjohnston's Blog
  • jboweruk's Blog
  • vgbaron's Blog
  • greggerm's Blog
  • salmendra's Blog
  • johnnyb's Blog
  • strikeeagle345's Blog
  • vicknight's Blog
  • elcamino's Blog
  • ejoiner's Blog
  • faamecanic's Blog
  • fbobum's Blog
  • Fred's Blog
  • ChristopherT's Blog
  • Hawkeye's Blog
  • rpike's Blog
  • spoiler5oo's Blog
  • plaincorgi's Blog
  • priorityexpress's Blog
  • gazeb's Blog
  • graaant's Blog
  • dsweiner's Blog
  • rocket308's Blog
  • avjones's Blog
  • police's Blog
  • metro752's Blog
  • CurlSnout's Blog
  • SteveC's Blog
  • jimmydunn's Blog
  • roytc's Blog
  • napamule2's Blog
  • fisheye's Blog
  • Kosta's Blog
  • mark786's Blog
  • tacan_dme's Blog
  • ke4wns's Blog
  • michaeljulian's Blog
  • aarmin's Blog
  • DJP's Blog
  • william1953's Blog
  • knocks's Blog
  • Richie800's Blog
  • elitehow's Blog
  • chief95's Blog
  • cagrims's Blog
  • bully's Blog
  • raynuss's Blog
  • familton's Blog
  • uslacmm's Blog
  • Jungleace's Blog
  • JLambCWU's Blog
  • beanmcgreen's Blog
  • lazyeight's Blog
  • seawing's Blog
  • mdannebaum's Blog
  • Rimshot's Blog
  • robert's Blog
  • menardrs's Blog
  • VFR_Steve's Blog
  • degeus's Blog
  • xaviervdv's Blog
  • md11nlm's Blog
  • ljasmann's Blog
  • velociriptor's Blog
  • maxtedr's Blog
  • stretch's Blog
  • The_Association's Blog
  • Rnglgdj's Blog
  • springbok's Blog
  • sharpeassoc's Blog
  • I3D_Support's Blog
  • SteveLewis's Blog
  • soldano's Blog
  • 35325's Blog
  • gatorgrd's Blog
  • nimrod's Blog
  • FuzzyLogic's Blog
  • apeltier's Blog
  • Spiggy's Blog
  • glenrennie's Blog
  • jimjones's Blog
  • jjbastien's Blog
  • Spac3Rat's Blog
  • simman's Blog
  • Zachiii's Blog
  • Augie's Blog
  • Badger's Blog
  • beana5's Blog
  • gforeman's Blog
  • ninlves's Blog
  • pmgebroff's Blog
  • rookiesimpilot's Blog
  • mtflyer's Blog
  • jimpenn's Blog
  • EagleClaw's Blog
  • falcon6's Blog
  • bbfip's Blog
  • mobbe123's Blog
  • InsyleM's Blog
  • jrmartin's Blog
  • noell's Blog
  • pyates's Blog
  • scruffyduck's Blog
  • kitspackman's Blog
  • marooned's Blog
  • fsman's Blog
  • davidlloydhoare's Blog
  • stusue's Blog
  • Fracair's Blog
  • duckbilled's Blog
  • wcandres's Blog
  • Tonyman's Blog
  • enewbold's Blog
  • BrianCPenrod's Blog
  • m8ack's Blog
  • persself's Blog
  • DanWalloch's Blog
  • mickj's Blog
  • david roch's Blog
  • skylab's Blog
  • flightsimmer747's Blog
  • jpinard's Blog
  • getstill's Blog
  • hendo's Blog
  • Cecil's Blog
  • johng's Blog
  • RDeal's Blog
  • ahlan's Blog
  • johanfrc's Blog
  • jmagyar's Blog
  • ChrisD's Blog
  • jochensachs's Blog
  • burge's Blog
  • BrianLund's Blog
  • newe's Blog
  • sascholz's Blog
  • Heather's Blog
  • Eskimo's Blog
  • IanH's Blog
  • simgammer's Blog
  • judge's Blog
  • thedude's Blog
  • adrianclerical's Blog
  • John65's Blog
  • meach's Blog
  • av8ber's Blog
  • boxjockey99's Blog
  • Wolf's Blog
  • johnclift's Blog
  • bgm1961's Blog
  • Schafdx's Blog
  • madPILOT's Blog
  • Erich65's Blog
  • mabe5454's Blog
  • selorme's Blog
  • alexdan's Blog
  • jlaurie's Blog
  • jafred's Blog
  • flyboy208's Blog
  • TKessel's Blog
  • rwolfe03's Blog
  • Concorde_fan's Blog
  • Kimber's Blog
  • Brushstrokes's Blog
  • jdoehlert's Blog
  • girardet's Blog
  • av8tor98's Blog
  • Merv's Blog
  • quantel_1's Blog
  • bstikkel's Blog
  • John_c's Blog
  • lasherid's Blog
  • wwhiteside's Blog
  • IanF's Blog
  • bft's Blog
  • netman's Blog
  • houting's Blog
  • GGFCA's Blog
  • stuart's Blog
  • VegasGeorge's Blog
  • Joker's Blog
  • Danbo020759's Blog
  • Ragtopjohnny's Blog
  • J_Stewart's Blog
  • algay's Blog
  • alain's Blog
  • davestan_ksan's Blog
  • gusifer's Blog
  • lionheart's Blog
  • dworjan's Blog
  • KCD's Blog
  • vortiz56's Blog
  • gsedge's Blog
  • kmgould's Blog
  • sandman's Blog
  • cattz's Blog
  • eagle1's Blog
  • algoguen's Blog
  • jimcraig's Blog
  • kickerpicker's Blog
  • starraker's Blog
  • flotocki's Blog
  • Earthrounder in a Bonanza V35B
  • largo222's Blog
  • GL_FS2002's Blog
  • pilgrim2's Blog
  • bmw1984's Blog
  • oldun's Blog
  • rwooton's Blog
  • Garrett67's Blog
  • AlienA51's Blog
  • MikeH's Blog
  • Dr Bob's Blog
  • wormdirt's Blog
  • mokkum01's Blog
  • Amtran618's Blog
  • bojote's Blog
  • skypilot's Blog
  • silverfox's Blog
  • Strecker64's Blog
  • Navman Francois's Blog
  • drive's Blog
  • briansommers's Blog
  • cloudflyer's Blog
  • 1466721's Blog
  • Full's Blog
  • KChapman's Blog
  • chris18p's Blog
  • jarod99's Blog
  • tomcatguy74's Blog
  • mongoose44's Blog
  • werner's Blog
  • N2056's Blog
  • artiguf's Blog
  • arno's Blog
  • schofi's Blog
  • oldfunflyer's Blog
  • jonjoe's Blog
  • eray9s's Blog
  • johnfromoz's Blog
  • Dan Ellis's Blog
  • bbaird's Blog
  • RobertK's Blog
  • johndaph's Blog
  • Roger Wensley's Blog
  • tompablo's Blog
  • hjwalter's Blog
  • MikeM's Blog
  • Leanne's Blog
  • neinnunb's Blog
  • repaid22's Blog
  • watles's Blog
  • GKKnupper's Blog
  • fireboss's Blog
  • Merv0728's Blog
  • darrenvox's Blog
  • dprosser's Blog
  • LJ922's Blog
  • capn_sonic's Blog
  • AVermeire's Blog
  • vanmulken's Blog
  • lintie's Blog
  • gusmer's Blog
  • Sentry's Blog
  • galeatbroadmead's Blog
  • Aarinu's Blog
  • burtyboy's Blog
  • andyb's Blog
  • rjdahlen's Blog
  • shivendra's Blog
  • copperpen's Blog
  • TX_3306's Blog
  • salt_air's Blog
  • dsarthur's Blog
  • Jive1's Blog
  • harold's Blog
  • loki's Blog
  • danny55's Blog
  • rdaniel's Blog
  • clipperone's Blog
  • ednixon's Blog
  • avallillo's Blog
  • bushp04's Blog
  • flyinggoldfish's Blog
  • adamb's Blog
  • snuggs28's Blog
  • edryan's Blog
  • samsulli's Blog
  • Pabra's Blog
  • neilfb's Blog
  • FATHERTIME's Blog
  • jaguars's Blog
  • mbalvetti's Blog
  • BOF's Blog
  • Gonzo's Blog
  • Icelander's Blog
  • fbfb's Blog
  • inca's Blog
  • neillydun1's Blog
  • Dunross's Blog
  • fsafranek's Blog
  • mike281's Blog
  • Sierra9093's Blog
  • Views From The Canyon
  • clarkg's Blog
  • mcgoldri's Blog
  • colmoore's Blog
  • siXpak's Cockpit
  • wes452's Blog
  • VERT002's Blog
  • cchaserr's Blog
  • hhasty's Blog
  • Big AL's Blog
  • metzgergva's Blog
  • VRobidas's Blog
  • Davejey's Blog
  • ilovetofly's Blog
  • seehunt's Blog
  • JSMR's Blog
  • swjg's Blog
  • dfle44's Blog
  • pipelighter's Blog
  • Jim Robinson's Blog
  • vegasjon's Blog
  • cfijack's Blog
  • RobertO1035's Blog
  • Nick's Blog
  • timest's Blog
  • dunix's Blog
  • mole_man99's Blog
  • kjbs's Blog
  • jcomm's Blog
  • Choljah's Blog
  • Whip's Blog
  • mgh's Blog
  • rhagen11's Blog
  • LuckyBlundy's Blog
  • Bushi's Blog
  • Monument Bob 2's Blog
  • mnpilot's Blog
  • carl092's Blog
  • zoomzoooie's Blog
  • wray's Blog
  • fnerg's Blog
  • wigerup's Blog
  • SideSlip's Blog
  • Gridley's Blog
  • ravenzyrst1's Blog
  • Al737's Blog
  • band_flight's Blog
  • gsnde's Blog
  • shuband's Blog
  • B42L8's Blog
  • helldiver's Blog
  • Kaloha's Blog
  • ozute's Blog
  • jadutton's Blog
  • JPL19's Blog
  • leen de jager's Blog
  • Sidney Schwartz's Blog
  • dlusty's Blog
  • firepanzer's Blog
  • danl's Blog
  • Harlan's Blog
  • noel56z's Blog
  • beryl7's Blog
  • nanar's Blog
  • owend's Blog
  • nevd's Blog
  • odaat's Blog
  • Caveman's Blog
  • Alyot's Blog
  • kittyhawk63's Blog
  • bct's Blog
  • lforgard's Blog
  • x24's Blog
  • DCA996's Blog
  • explorer's Blog
  • xxmikexx's Blog
  • MrLT52's Blog
  • Honus's Blog
  • ACMatrix's Blog
  • stasher's Blog
  • mercohaulic's Blog
  • mjrhealth's Blog
  • ek1's Blog
  • A3330's Blog
  • Finnflyer's Blog
  • ecamara's Blog
  • kingnorris's Blog
  • rwremote's Blog
  • gpry's Blog
  • BEWARRE's Blog
  • FSAOM's Blog
  • yamazaki's Blog
  • yubi's Blog
  • bugdozer's Blog
  • G7USL's Blog
  • tomkk's Blog
  • Carob's Blog
  • Lee's Blog
  • bigmack's Blog
  • N509BY's Blog
  • JoeD's Blog
  • blkmajesty's Blog
  • tnyland's Blog
  • ac103010's Blog
  • Bozo's Blog
  • oglitsch's Blog
  • Denny's Blog
  • minimender's Blog
  • goldhawk's Blog
  • NeverBoring's Blog
  • bobdawkins's Blog
  • SKAir's Blog
  • pdjong's Blog
  • kennyhall's Blog
  • ltyndall's Blog
  • sapphire's Blog
  • PabloJM's Blog
  • normandh's Blog
  • FLYBYKNIGHT's Blog
  • g3laser's Blog
  • pbt63's Blog
  • casarticus's Blog
  • Eric's Blog
  • krisburn's Blog
  • cesarnc's Blog
  • MCSim's Blog
  • DPS's Blog
  • dijkgraaf's Blog
  • mav39's Blog
  • Rantings of a Radio Operator
  • dbrd's Blog
  • JayLink's Blog
  • NEBOJSA's Blog
  • littletiger's Blog
  • josutton's Blog
  • malmac's Blog
  • FrankR's Blog
  • firecracker's Blog
  • Kapitan Aviation Stories
  • jrog's Blog
  • cbyrd1950's Blog
  • Brian_Neuman's Blog
  • mcleod3302's Blog
  • airfrance's Blog
  • Combat144's Blog
  • jdwgraf's Blog
  • fsfilmworks's Blog
  • rthrosby's Blog
  • Danparis's Blog
  • smaill's Blog
  • Charley_Lima's Blog
  • asimmd's Blog
  • aws1953's Blog
  • KPenn5's Blog
  • ukboy's Blog
  • dorianr's Blog
  • schwartzi's Blog
  • pvarn's Blog
  • worldsfair's Blog
  • pgcliffe's Blog
  • Bizub4's Blog
  • plainsman's Blog
  • johnost's Blog
  • BLewis2795's Blog
  • barrington's Blog
  • victorrpeters's Blog
  • hesynergy's Blog
  • zswobbie1's Blog
  • perrycooke's Blog
  • bulpup's Blog
  • unique's Blog
  • arclight's Blog
  • hamiltonman's Blog
  • tinman's Blog
  • cavaricooper's Blog
  • Jackflyer's Blog
  • biggestal's Blog
  • ytrepanier's Blog
  • thepatriot76's Blog
  • whiskey's Blog
  • heyford's Blog
  • jhmidwood's Blog
  • ScatterbrainKid's Blog
  • Smutley's Blog
  • eric_marciano's Blog
  • sky44's Blog
  • deltaleader's Blog
  • Jacbert's Blog
  • billsimm's Blog
  • kd4dra's Blog
  • mondeomangolf's Blog
  • katie88's Blog
  • agrees's Blog
  • HaveBlue's Blog
  • surfrider's Blog
  • milusos's Blog
  • CZW's Blog
  • ecorry's Blog
  • PhilTaylor's Blog
  • frog3764's Blog
  • KrazyKyle's Blog
  • tsteen's Blog
  • rwcatherall's Blog
  • tham's Blog
  • CARex's Blog
  • BigBravo21's Blog
  • GarethW's Blog
  • Firefalcon's Blog
  • WildBlue's Blog
  • jrhunter's Blog
  • raptorairlines's Blog
  • LKLACY55304's Blog
  • w2pzp's Blog
  • caddie's Blog
  • gliderpilot's Blog
  • tacomasailor's Blog
  • American's Blog
  • donatogeraldi's Blog
  • sacb52man's Blog
  • Doods's Blog
  • abz's Blog
  • thomaspattison's Blog
  • Syracuse_Jim's Blog
  • Lowbeam's Blog
  • sirbruchie's Blog
  • rotorguy's Blog
  • capndon's Blog
  • Habu1967's Blog
  • 11269706's Blog
  • commercialcobb's Blog
  • fredmond4's Blog
  • phl's Blog
  • airboatr's Blog
  • peer01's Blog
  • estei2123's Blog
  • hjeck's Blog
  • airbrakes's Blog
  • mvg3d's Blog
  • n452mk's Blog
  • collltip's Blog
  • hyperope's Blog
  • mvjoshi's Blog
  • vanhorst's Blog
  • kenu's Blog
  • murted's Blog
  • adamjosiah's Blog
  • joemckay's Blog
  • ofcbill's Blog
  • wichner2's Blog
  • safari456's Blog
  • humusic2's Blog
  • Deeboe's Blog
  • tigisfat's Blog
  • alfredodedarc's Blog
  • Woodmouse's Blog
  • mcelmes's Blog
  • turbofire's Blog
  • ldlcholester's Blog
  • Jako's Blog
  • jmuzzy's Blog
  • xmitr's Blog
  • mqytn's Blog
  • dcquest's Blog
  • Giarc's Blog
  • SeanG's Blog
  • FO Jevans and his "blog"
  • rbrown's Blog
  • Plane2's Blog
  • tmo1's Blog
  • josh's Blog
  • craigewan's Blog
  • Marblehead's Blog
  • Happnin's Blog
  • HardCub's Blog
  • pablo30's Blog
  • Smiffy's Blog
  • RTod's Blog
  • wannapilot's Blog
  • Craig's Blog
  • csefton's Blog
  • ccwilber's Blog
  • kenmc's Blog
  • jmargot's Blog
  • lgross's Blog
  • flsms's Blog
  • stevepilot's Blog
  • spirit316's Blog
  • fairlane63's Blog
  • f15sim's Blog
  • BillTheSlink's Blog
  • jimginn's Blog
  • Jessew's Blog
  • ldk2002's Blog
  • GreasyBob's Blog
  • warden1974's Blog
  • DrFlightTalk's Blog
  • denvervirtualceo's Blog
  • jamesdeanoo7's Blog
  • patrickvdbemt's Blog
  • Asad Khawer's Blog
  • Star56's Blog
  • kin3's Blog
  • ozinoz's Blog
  • Christoph4445's Blog
  • Problems with flight controls (Flight Sim X)
  • airwolfe's Blog
  • 4449daylight's Blog
  • Autopilot_Abuser's Blog
  • bugdriver's Blog
  • saddles's Blog
  • lansman1's Blog
  • johnellis75's Blog
  • Aviator0327's Blog
  • Alexander's Blog
  • bgets's Blog
  • rgriffi163's Blog
  • hooless's Blog
  • gdr1944's Blog
  • meltsner's Blog
  • dimimiras's Blog
  • shannei's Blog
  • Laurie 1's Blog
  • smallcone's Blog
  • BarryNieuwoudt's Blog
  • jhancoc's Blog
  • wpiner88's Blog
  • mibo's Blog
  • peter58's Blog
  • Xptical's Blog
  • icarusgold's Blog
  • fsxflyerofa380's Blog
  • JeremyFromTexas's Blog
  • fxsttcb's Blog
  • hanss's Blog
  • pegsim's Blog
  • HoratioWondersocks's Blog
  • DJC-kMYR's Blog
  • tommyfl's Blog
  • Plus24's Blog
  • dredgy's Blog
  • fragmentum's Blog
  • LEM's Blog
  • dareman's Blog
  • northeastair's Blog
  • saturno_v's Blog
  • chris.edde's Blog
  • TrafficPilot's Blog
  • Jaywindstreams's Blog
  • Flegmatica's Blog
  • peetey's Blog
  • rcmonster99's Blog
  • sbieg's Blog
  • MOONDOG187's Blog
  • tskillman89's Blog
  • Dangerousdave26's Blog
  • gdr54's Blog
  • CotterNWA's Blog
  • big-mike's Blog
  • martyb2's Blog
  • arcueil's Blog
  • PilotBrad's Blog
  • XML code for Model Match in FsPilot?
  • cardinal21's Blog
  • JonBuck's Blog
  • Mogget's Blog
  • meyerm's Blog
  • GordonR's Blog
  • Bush's Blog
  • wjwoodward's Blog
  • EugeneBancroft's Blog
  • CBris's Blog
  • flyingcoon's Blog
  • Legin3020's Blog
  • PetrSvoboda's Blog
  • nemo1945's Blog
  • maxfs's Blog
  • Dave Hayes's Blog
  • marcori's Blog
  • =Hollywood='s Blog
  • royal's Blog
  • Bobr21's Blog
  • kel0858's Blog
  • FDC001's Blog
  • CessnaFlyer's Blog
  • ricardo_NY1's Blog
  • bbqsteve's Blog
  • M31's Blog
  • r3dt4g's Blog
  • declarke's Blog
  • ronzo155's Blog
  • ssowry's Blog
  • donsor's Blog
  • LOBSTABOAT's Blog
  • bumpkin's Blog
  • aldwick's Blog
  • yanfeng12342000's Blog
  • crl's Blog
  • babyboeing's Blog
  • bumper5895's Blog
  • Algoz66's Blog
  • ytzpilot's Blog
  • readflightsim's Blog
  • Benny's Blog
  • Mav92's Blog
  • rpdonahue's Blog
  • Jimmy_S's Blog
  • Mosha's Blog
  • eytan's Blog
  • HALIMAN's Blog
  • Loke's Blog
  • LandonZ's Blog
  • iluvairplanes's Blog
  • Big777jet's Blog
  • Imtijac's Blog
  • flightluuvr's Blog
  • Boeing 767's Blog
  • jrazz's Blog
  • Orion1969's Blog
  • flightsim2000's Blog
  • vinow's Blog
  • shess57's Blog
  • irishsooner's Blog
  • jazz's Blog
  • Flytsimmer's Blog
  • jeroen79's Blog
  • johnrgby's Blog
  • Canberra Man's Blog
  • brarsj's Blog
  • HAWKEYE784NG's Blog
  • garrytheskate's Blog
  • pjtmcclure's Blog
  • HerkEngineer's Blog
  • hammer_hand's Blog
  • Shimmy's Blog
  • Goupin's Blog
  • cnj's Blog
  • robertwilliams's Blog
  • bd515's Blog
  • Smilin74's Blog
  • Pierre Paquet's Blog
  • Bark0's Blog
  • TCX559K's Blog
  • IOGEAR's Blog
  • airfree's Blog
  • PeterRodwell's Blog
  • mrt12345's Blog
  • kbcadnz's Blog
  • Cessna185's Blog
  • lild20's Blog
  • oskarfourzero's Blog
  • pivirtual's Blog
  • 817's Blog
  • gazzaro's Blog
  • Colk's Blog
  • Laatab's Blog
  • kostas's Blog
  • captainakba's Blog
  • DK-NIK's Blog
  • Constinator25's Blog
  • ryan78's Blog
  • johnfugl's Blog
  • Frisky57's Blog
  • arnaud's Blog
  • DLR_41's Blog
  • FlightArcher's Blog
  • Ed Moore's Blog
  • Flyhigher's Blog
  • adybear's Blog
  • pmkaiser's Blog
  • alitalia2010's Blog
  • lvflyer's Blog
  • declanSw's Blog
  • highlandhippie's Blog
  • The Pilot1's Blog
  • AAVN60's Blog
  • Dean Talbot's Blog
  • dickbutz's Blog
  • tatisop's Blog
  • Krajo's Blog
  • tvieno's Blog
  • francisetti's Blog
  • MarkGilmore's Blog
  • RB211's Blog
  • skywalker73's Blog
  • annber's Blog
  • pollito's Blog
  • bbb's Blog
  • dmartin1957's Blog
  • jrdale210's Blog
  • rambowski's Blog
  • Willyaj's Blog
  • SamIsAHusky's Blog
  • fsfred's Blog
  • davesjamtrax's Blog
  • Jetlantic's Blog
  • franz21943's Blog
  • zapilot's Blog
  • littlewing's Blog
  • thunter's Blog
  • SikStik954's Blog
  • dx5517's Blog
  • RRN1988's Blog
  • ViperPilot2's Blog
  • gandy's Blog
  • marbasan's Blog
  • AJp34's Blog
  • EdmundV's Blog
  • Skyknight_TN's Blog
  • Vandevelde's Blog
  • leeski09's Blog
  • Whales in Russell Ford/Glacier Bay
  • EricASA100's Blog
  • Red15's Blog
  • SkyStryder's Blog
  • sahir bassam's Blog
  • ddd777's Blog
  • fllebrez's Blog
  • Antares's Blog
  • hfkwong's Blog
  • monkeypup's Blog
  • kidkrats's Blog
  • b108's Blog
  • grumpy214's Blog
  • kenwig0556's Blog
  • 1franciscodep's Blog
  • dbourke's Blog
  • ejguil2's Blog
  • FlyerFSX-2004's Blog
  • maximus92's Blog
  • molly89's Blog
  • gaosys's Blog
  • aviat fast's Blog
  • wltaylor's Blog
  • transcontinental's Blog
  • tomvandermeulen's Blog
  • fridtjof's Blog
  • patcox's Blog
  • willpa's Blog
  • davidjones's Blog
  • navigatre's Blog
  • loubensdorp's Blog
  • allanj's Blog
  • jackryan's Blog
  • steveh01's Blog
  • bdouglas's Blog
  • dgrindele's Blog
  • dallison's Blog
  • pwafer's Blog
  • awalkera's Blog
  • alverthein's Blog
  • mahalo's Blog
  • leeholdridge's Blog
  • wingsgary's Blog
  • michaelvader's Blog
  • fssarno's Blog
  • brina's Blog
  • phyl's Blog
  • wyjchen's Blog
  • ronthenupe's Blog
  • larryp35's Blog
  • rockinrobin's Blog
  • ptsmith's Blog
  • karreman's Blog
  • jimatt's Blog
  • shalako's Blog
  • peterquin's Blog
  • optim's Blog
  • mononk's Blog
  • trad's Blog
  • megabriel's Blog
  • zworski's Blog
  • kizer's Blog
  • samra's Blog
  • chrisa1's Blog
  • feichi's Blog
  • maddogken's Blog
  • claudy's Blog
  • rogerdenkler's Blog
  • hencho's Blog
  • dicknebr's Blog
  • phiferwt's Blog
  • maxifer's Blog
  • arthurwilson's Blog
  • parsonsw's Blog
  • Joe's Blog
  • 2107al's Blog
  • tcreagh's Blog
  • vonernsk's Blog
  • test's Blog
  • molniya's Blog
  • cgtjs's Blog
  • pniel's Blog
  • esboz's Blog
  • dotcomet's Blog
  • eyzargrn's Blog
  • polarleif's Blog
  • bearracing's Blog
  • robinmaclaurin's Blog
  • tnutkins's Blog
  • desenne's Blog
  • swanny's Blog
  • iamgen's Blog
  • dingram's Blog
  • tigercub's Blog
  • rwa's Blog
  • tonyevans's Blog
  • knudkurt's Blog
  • swgold's Blog
  • dirkschellaars's Blog
  • jvburden's Blog
  • kittyfish2's Blog
  • gnou's Blog
  • jgardene's Blog
  • nahrgang's Blog
  • johnmur's Blog
  • sanrik's Blog
  • bmartin47's Blog
  • patrickbreack's Blog
  • huberma's Blog
  • elbowsandy's Blog
  • irscds's Blog
  • mb680's Blog
  • jdaigneau's Blog
  • pmcgough's Blog
  • budfay's Blog
  • gerbar's Blog
  • jenpan's Blog
  • brianjoverton's Blog
  • gjwpocock's Blog
  • lloydo's Blog
  • blockhead's Blog
  • bardal2's Blog
  • led4blue's Blog
  • pierreanthony's Blog
  • pjump1's Blog
  • pebbles65's Blog
  • bertnm's Blog
  • smokywash's Blog
  • harryknox's Blog
  • j25wolf's Blog
  • ggeraci's Blog
  • dwain7's Blog
  • billkillen's Blog
  • HELP in Victoria BC
  • clintonfan's Blog
  • oldtimepilot's Blog
  • johngooch's Blog
  • grahamspicer's Blog
  • haroun's Blog
  • dearing's Blog
  • urigor's Blog
  • brucedouglas's Blog
  • obmuz's Blog
  • osval's Blog
  • tomzimmerman's Blog
  • exwcirep's Blog
  • skipjack's Blog
  • coxje's Blog
  • gdebiscop's Blog
  • controller5's Blog
  • bousquet's Blog
  • fpfly's Blog
  • jsaviano's Blog
  • wollie12's Blog
  • alanmerry's Blog
  • wattyville's Blog
  • skyhipete's Blog
  • heikheiksen's Blog
  • beech699's Blog
  • hhvoje's Blog
  • pdxfrederick's Blog
  • bobp38's Blog
  • hondo55's Blog
  • 19kazoo38's Blog
  • andreasprotzen's Blog
  • ggaulin's Blog
  • ggw's Blog
  • donaltman's Blog
  • atlantathrashers's Blog
  • ramair's Blog
  • mdeoliveira's Blog
  • gbarns07's Blog
  • calama's Blog
  • mendell's Blog
  • scoop72's Blog
  • zipper1's Blog
  • mdcude's Blog
  • baardlovaas's Blog
  • jofernandez's Blog
  • electra's Blog
  • grizli's Blog
  • mhhamer's Blog
  • watsonhb's Blog
  • stewartrushton's Blog
  • Cricket29's Blog
  • westway's Blog
  • peterthorp's Blog
  • utf's Blog
  • garrett100's Blog
  • jben120631's Blog
  • kathryn's Blog
  • jbawilliams's Blog
  • jonblu's Blog
  • pboggs's Blog
  • torbenj's Blog
  • douga66's Blog
  • atcogl's Blog
  • simmerdr's Blog
  • allanshaw66's Blog
  • uptownsmoker's Blog
  • wrk218's Blog
  • john62's Blog
  • jimbt's Blog
  • quokka38's Blog
  • eagle22449's Blog
  • wildman06's Blog
  • hoplop's Blog
  • croudson's Blog
  • a320driver's Blog
  • luckydog's Blog
  • bonesfisher's Blog
  • ronaldfalzon's Blog
  • nadina's Blog
  • chewfly's Blog
  • yvesthiebaut's Blog
  • cwo4den's Blog
  • winkebob's Blog
  • spike9's Blog
  • pnel88's Blog
  • green198's Blog
  • KWBAlaska10's Blog
  • moneta's Blog
  • bbuckley's Blog
  • richb's Blog
  • wreck's Blog
  • garry's Blog
  • lacasse's Blog
  • billolga's Blog
  • lexus's Blog
  • cobalt's Blog
  • bmz's Blog
  • wernery's Blog
  • acourt's Blog
  • jlbelard's Blog
  • kasey's Blog
  • rcogg's Blog
  • chicago's Blog
  • jrwentz's Blog
  • KennethKerr's Blog
  • dsansome's Blog
  • roymar's Blog
  • scottm's Blog
  • blondie's Blog
  • torbenja's Blog
  • jwvdhurk's Blog
  • jdlinn's Blog
  • caflyt's Blog
  • heronjr's Blog
  • aler's Blog
  • conair's Blog
  • demerse's Blog
  • luth's Blog
  • searfoss's Blog
  • azzaro's Blog
  • nicked's Blog
  • goldust's Blog
  • leuen's Blog
  • Ambeat07's Blog
  • gmbyrne's Blog
  • hayashi7's Blog
  • jfallcock's Blog
  • tayrona's Blog
  • leester's Blog
  • joancampos's Blog
  • airbus320's Blog
  • leehall's Blog
  • rdrumm26's Blog
  • cheetah621's Blog
  • darim's Blog
  • ramcry's Blog
  • swedeflight's Blog
  • cdome's Blog
  • culturama's Blog
  • oxo's Blog
  • songbyrd's Blog
  • knorring's Blog
  • theyorks's Blog
  • colmedad's Blog
  • mverlin's Blog
  • delhomme's Blog
  • groupwise's Blog
  • juergenmartens's Blog
  • marcas's Blog
  • mshields's Blog
  • acsoft's Blog
  • andrewwebb's Blog
  • wrohrbeck's Blog
  • Cougarnaut's Blog
  • slyf's Blog
  • stinkysock's Blog
  • tietze's Blog
  • stevehg's Blog
  • sroblits's Blog
  • hapadaca's Blog
  • trevg's Blog
  • mrlogic's Blog
  • cmdl1650's Blog
  • kjcollins's Blog
  • tres2's Blog
  • signon's Blog
  • rog3er's Blog
  • mortenthede's Blog
  • ltbulb's Blog
  • rtorres's Blog
  • abbashnaby's Blog
  • hanswerner's Blog
  • jeffhow's Blog
  • haraldh's Blog
  • bucksnort's Blog
  • schu's Blog
  • jtflight's Blog

Categories

  • Featured
  • HN
  • 2018
  • 2019
  • 2020
  • 2021
  • 2022
  • 2023
  • Special Interest
  • Developer Awards
  • Excellence Awards
  • Aircraft Design
  • CFS
  • FS2000
  • FS2002
  • Other
  • X-Plane
  • FSX
  • Aviation
  • FS2004
  • Prepar3D
  • Flight Sim World
  • MSFS_old
  • vBulletin Articles

Categories

  • MSFS
    • MSFS Aircraft
    • MSFS Liveries
    • MSFS Scenery
    • MSFS AI Traffic
    • MSFS Misc.
  • FSX
    • FSX Misc.
    • FSX Scenery
    • FSX Business Jets
    • FSX General Aviation
    • FSX Jetliners
    • FSX Modern Military
    • FSX Propliners
    • FSX Helicopters
    • FSX Missions
    • FSX Turboprops
    • FSX Panels
    • FSX Splash Screens
    • FSX Warbirds
    • FSX Early Aircraft
    • FSX Utilities
    • FSX Sound
    • FSX Other Aircraft
    • FSX Scenery Objects
    • FSX AI Flight Plans
    • FSX AFCAD Files
  • Prepar3D
    • Prepar3D Aircraft
    • Prepar3D Scenery
    • Prepar3D Miscellaneous
    • rick test
  • X-Plane
    • X-Plane Jet Airliners
    • X-Plane Liveries
    • X-Plane Prop Airliners
    • X-Plane General Aviation
    • X-Plane Military Aircraft
    • X-Plane Warbirds
    • X-Plane Early Aircraft
    • X-Plane Other Aircraft
    • X-Plane Scenery
    • X-Plane Scenery Libraries
    • X-Plane Scenery Objects
    • X-Plane Misc.
  • FS2004 (ACOF)
    • FS2004 Scenery
    • FS2004 Liveries
    • FS2004 General Aviation
    • FS2004 Business Jets
    • FS2004 Propliners
    • FS2004 Turboprops
    • FS2004 Modern Military
    • FS2004 Helicopters
    • FS2004 Jetliners
    • FS2004 Sound
    • FS2004 Panels
    • FS2004 Warbirds
    • FS2004 Early Aircraft
    • FS2004 Splash Screens
    • FS2004 Other Aircraft
    • FS2004 AFCAD Files
    • FS2004 AI Flight Plans
    • FS2004 Flights/Adventures
    • FS2004 Scenery Objects
    • Misc.
  • FS2002
    • FS2002 Misc.
    • FS2002 Aircraft
    • FS2002 Panels
    • FS2002 Scenery
    • FS2002 Sound
    • FS2002 AI Flight Plans
    • FS2002 Gates & Taxiways
    • FS2002 Splash Screens
    • FS2002 Scenery Design Macros
  • FS2000
    • FS2000 Aircraft
    • FS2000 Liveries
    • FS2000 Misc.
    • FS2000 Panels
    • FS2000 Scenery
    • FS2000 Sound
    • FS2000 Adventures
    • FS2000 Flight Plans
    • FSTraffic Tracks
  • FS98
    • FS98 Misc.
    • FS98 Aircraft
    • FS98 Scenery
    • FS98 Adventures
    • FS98 Panels
    • FS98 Sound
    • FS98 Gauges
    • FS98 Flight Plans
  • FSFW95
    • FSFW95 Misc.
    • FSFW95 Aircraft
    • FSFW95 Scenery
    • FSFW95 Adventures
    • FSFW95 Panels
  • FS5
    • FS5/FSFS Aircraft
    • FS5 Scenery
    • FS5 Panels
    • FS5 Non-Flight Shop Aircraft
    • FS5 Adventures
  • FS4
    • FS4 Aircraft
    • FS4 Scenery
  • Combat Flight Simulator
    • CFS Aircraft
    • CFS Misc.
    • CFS Scenery
    • CFS Missions
    • CFS Panels
    • CFS2 Aircraft
    • CFS2 Misc.
    • CFS2 Scenery
    • CFS2 Missions
    • CFS2 Panels
    • CFS3 Misc.
    • CFS3 Aircraft
    • CFS3 Missions
  • Aviation
    • Aviation
  • Flight Simulation
    • Utilities and Miscellaneous
    • Uploads
    • Maps And Charts
    • Hangsim
  • Military
    • Military
    • Pacific Fighters
  • PAI
    • PAI Aircraft
    • PAI Aircraft Support Files
  • Looking Glass
    • Flight Unlimited II
    • Flight Unlimited III
  • PAINTING LIVERIES FOR AIRCRAFT's SHARE YOUR LIVERY

Find results in...

Find results that contain...


Date Created

  • Start

    End


Last Updated

  • Start

    End


Filter by number of...

Joined

  • Start

    End


Group


Location


About Me


Occupation


Interests


Homepage


ICQ


AIM


Yahoo


MSN


Skype


User Title

  1. Hi all, thanks for accepting me in this forum. I am the Flight Simulator fan for last 10 years and I am enjoying every time when I am flying. Since I try new FS2020 and when I sow first time this amazing graphics and textures, I simply decided to make one world travel and try to discover as much as possible of FS2020 world. Because I am originally from Serbia, I am flying with Air Serbia A320 neo and most of the time I am online on Ivao platform. My call sign is ASL500 and at the moment I am located in Australia and soon I will be in New Zealand. To make it short, who ever is interested in my world travel project, please visit my website http://www.asl500 .com and give me your feedback, suggestions or ideas for my next flights and whole project.Thanks in advance and have a nice upcoming Christmas holidays.
  2. Ratty's Ramblings - Round The World By Ian Radcliffe Have you flown around the world? I've done it three times now. The first time was after Steve Fossett made the trip non-stop in the GlobalFlyer. There was a nice rendition of the plane for FS2004 and I used it to follow the same route. I don't recall anything eventful from that trip, although I have a hazy recollection that the landing was not all it might have been. The second time was in a Piper Cherokee, of all things. I had just bought the A2A model, and it had turned out to be love at first sight. After only a couple of weeks I decided to go around the world in it. I used Skyvector to draw a line between Gillespie Field in California, the airport near where I live, and Biggin Hill in England, the airport where I learned to fly, and followed that as closely as I could, figuring after that I would make up the rest as I went along. It actually went pretty well. You should understand that, for me, the GPS takes a lot of the fun out of getting around, so I made the trip using maps, radio navaids, and a drift sight. From 9,000 feet I could see the surface most of the time, because the weather was generally favorable, or at least not too awful. I remember persistent carburetor icing on the way up through Japan and the Kurile Islands; and waiting a week in Ile Rodrigues in the southern Indian Ocean for winds that would get me to Diego Garcia. That leg was 912 nautical miles and, using standard tanks because there was no way to "realistically" augment fuel capacity, it was a dangerously long flight that I would never attempt in real life. The Cherokee performed flawlessly the whole way round the planet, and did the almost 23,000 miles in 237 hours. The third trip was an equatorial circumnavigation in the A2A Constellation, starting from and returning to Quito, Ecuador, and once again eschwing the GPS. Across the large stretches of open ocean with no navaids I used the drift sight when possible. Failing that, I made the best calculation of which way to steer and trusted that I would at least pass within range of my destination beacon. It worked every time, though on one long night leg, after a big shift in winds, when I finally picked up the beacon I was almost 100 miles north of track. The total distance for the trip was 21,725 nautical miles, the total flight time 93 hours 57 minutes. Some real-world stats: The very first aerial circumnavigation was in 1924, by two Douglas World Cruiser floatplanes of the United States Army Air Service. They took 175 days and covered 26,345 miles. The first non-stop circumnavigation was in 1949, in a United States Air Force B-50 Superfortress. It flew 23,452 miles in 94 hours and 1 minute, and required four in-flight refuelings. And in 1992 an Air France Concorde achieved the fastest circumnavigation to date, in 32 hours 49 minutes and 3 seconds. What exactly is "around the world"? Well, for a powered aircraft to officially circumnavigate the globe, Federation Aeronautique Internationale stipulations are that it must cross all meridians in one direction, travel a distance of at least 36,770 km (19,854 nautical miles, the length of the Tropic of Cancer), and complete the journey at the point of departure. There is no requirement that it cross the Equator or touch "antipodal points", spots on the globe directly opposite one another. Most round-the-world flights are from west to east, to take advantage of the world's wind patterns, but they have been flown from east to west, and even over the two poles. If you're thinking about doing a round-the-world flight, I have a couple of suggestions. The first is: consider doing a little more planning than I did on my Cherokee trip to make sure you don't wind up at a dead end where you can only go backwards. The second: make the voyage in an airplane you love to fly. You'll come away loving it even more. Multiplayer Flight For the past couple of years I've been flying regularly with a group of A2A enthusiasts. The camaraderie is amazing, and the exchange of knowledge and experiences invaluable. And we have fun! So much, in fact, that I'm amazed that EVERYONE isn't in multiplayer almost all the time. Like so many others, I used to be "mic shy", and I suspect that may be the single biggest thing keeping people away from multiplayer flying. Fear of public speaking is number one for most people, even before the fear of death. So, apparently, most people would rather die than have to stand on a stage and speak. I get it; people might not like you. But what I discovered is that talking about and participating together in a shared passion like ours negates all the silly stuff about "looking good". Try it, I dare you. I'm a big fan of JoinFS; with that program you can find a listing of servers and join in, whether you're using FS2004, FSX, P3D, even X-Plane. Pick a group and connect with their comms channel; TeamSpeak and Discord seem the most popular ways to communicate. Once you hear voices, wait for a gap and speak. All you have to say is something like: "This is Ratty. Mic check." The response you get will tell you everything you need to know about the people on the channel and the way you should conduct yourself. After that you're on your own, but be prepared for some of the richest and most satisfying moments of your sim flying life. Ratty's Ramble This time, let's take a trip around the island of Taiwan. Ever been there? I hadn't either. The geography of the island is nicely varied: a mountainous spine separates the western coastal plain - home to most of the country's metropolitan areas and agriculture - from the rugged eastern side with its enticing valleys and canyons. The tour starts from and returns to Hsinchu Air Base, RCPO. At 400 nautical miles this one is a fairly long flight; also a great sightseeing trip, so unless real weather is particularly benign, I recommend Fair or Clear to really enjoy the view. Skyvector Link
  3. Around the World in Style By Ian Radcliffe It was time for another big adventure. I've been around the world a couple of times, the first time non-stop in the Global Voyager, the second in the A2A Cherokee 180. Although both met the FAI requirements for a "circumnavigation" neither came close to traveling the true circumferential distance. This time I determined to go around at the Equator (or as close as possible) in an airplane that could handle the long overwater flights. Clearly, only one bird was appropriate for the task, so I picked up an A2A Lockheed Constellation as refurbished by Grubich Aerospace, invited thirty close friends along for the ride, and set out from Quito, Ecuador at dawn. First Leg - Quito to Natal Like most of my adventures this one was largely (entirely?) spontaneous and unplanned. I didn't bother to run any numbers - how much can thirty people weigh? - so the load, plus full tanks, plus the 8,000 foot airport altitude made the take off a little anxiety-inducing. She trundled down almost the whole 13,000 feet of runway before taking flight, and even then we were barely doing 110 as we crossed the far end. But after gear up, a couple of shallow turns to avoid buildings/trees, and raising the flaps after gaining a few hundred feet we were into a gentle climb to the north to get high enough to clear the mountains before turning east. Then it was on to Natal. We cruised at 24,000 feet, at 29 inches and 2,200 RPM, a basic cruise setting for this plane. The South American continent at this latitude is pretty flat: hour after hour of almost unbroken green. Some time during cruise the entire flight crew fell asleep for several hours; when we woke up we were within range of the beacon; just 160 nm short of our destination and, miraculously, only 20 miles off track. We landed soon after dusk, at 8:15 pm local. With light headwinds all the way we covered the 2,615 nautical miles in 10 hours 14 minutes, and had 24% fuel remaining at shutdown. I got my first look at the Amazon Basin, but otherwise it was an uneventful trip. Second Leg - Natal to Sao Tome The first long overwater leg. I'm still learning about long-range flying in this plane, but using the last flight as a guide, it looks as though the bird will go around 3,300 miles with ease. Sao Tome, an island off the west coast of Africa in the Gulf of Guinea was only 2,500 miles away. This hop would go for almost 10 hours with no beacons, out of sight of land, but it's hard to miss Africa, right? We cruised with the same settings as before, dodged a few thunderstorms along the way, and picked up Sao Tome VOR from 188 miles out. For several hours, the undercast had precluded use of the drift sight, and we turned out to be 40 nm off course after 2,370 nm of flight - due mainly to a two-degree "gut instinct" course change I made that I didn't need to make. 9 hours 29 minutes. 2,545 miles. 268 knots. Third Leg - Sao Tome to the Seychelles Terrific trip across Africa. I decided to try for the Seychelles, 3,000 miles away, beyond the other side of the continent. We took off from Sao Tome at dawn and headed east and soon Africa emerged from the mist. I took the opportunity to test something I was told a long time ago. Range is range - regardless of the altitude at which you fly (more or less). The trade off is the speed at which you travel: we fly at high altitudes in part because we can cover the same distance faster. Since the first 1200 miles of Africa eastbound from Sao Tome is flat, I flew at 3,000 feet the whole way, to see what sort of range performance I could get - and to give everyone a better view. I kept the airspeed way down, around 155 knots. Six-and-a-half hours into the flight we had travelled 1,110 nm; remaining range - 2,493 nm. Beyond the Congo River the terrain begins to rise, so we climbed gently and leveled at 18,000 for what seemed the best winds. We landed at Seychelles International after 14 hours and 17 minutes of flight; 2,946 miles at an average groundspeed of 206 knots. Fourth Leg - Seychelles to Singapore Uneventful flight from the Seychelles to Singapore. We cruised at 10,000 feet for the best winds (headwinds again) and went 2,925 nm in 12 hours 26 minutes. Average speed 235 knots. At 11,027 nautical miles, we're now just over half-way round. Fifth Leg - Singpore to Nadzab Left Singapore before dawn. I thought about going for distance and trying for the Solomons, but decided to do some sightseeing instead, flying down the Indonesian island chain at a couple of thousand feet. We climbed to 8,000 for the later part of the trip over the mountainous eastern end of the main island, and slipped down between the hills to land at Nadzab after dark. Covered 2,614 miles in 12 hours 19 minutes. Another slow average speed of 212 knots. Sixth Leg - Nadzab to Funafuti On to Funafuti, a thin sweep of land around a large lagoon in the middle of the South Pacific. Fortunately, Funafuti is equipped with both an NDB and DME, so it was easy enough to find - once the stations came into range. Essentially, on these long-distance, no-GPS flights, I'm assuming I can control the drift well enough that I'll pass close enough to my destination to receive whatever homing signal(s) they transmit. (Is there a fixed range for a given beacon type; I've never checked.) So far I've done OK, but mostly with a sizeable landmass to run into in case I miss. Funafuti is all by itself in the middle of the ocean; the closest land, another island, is over 200 miles to the south. It was another easy flight into steady headwinds over broken cloud. We arrived at dusk, which was fortunate as the field is unlighted. 1,937 nm. 9 hours. 215 knots. Seventh Leg - Funafuti to Nuka Hiva A bit of excitement shortly after takeoff. Our next destination, Nuka Hiva, was 2,410 miles away, and 500 miles from the nearest dry spot, so I left well before dawn to ensure arriving in good light. Five minutes into the flight, climbing through three thousand, I was informed we had a sick passenger. There really was only one option: turn around and land. I was a little apprehensive at the thought of landing on that unlit runway at night, but at least I'd seen it in daylight so it wasn't completely new. The cloudbase wasn't really that low, and the visibility was better than marginal, so staying under the cloud and turning to a reciprocal course wasn't too hard. It was DARK out there but I managed to spot the island and the strip sliding by to port. I went downwind a bit and then turned into a curving approach. As the runway came back into view and I was considering gear and flaps and stuff, I was informed the passenger had recovered. We did a sort of missed approach buzz-job and climbed away into the cloud. 2,409 miles in 9 hours 47 minutes. Average speed 246 knots. Eighth Leg - Nuka Hiva to the Galapagos Close to the end of a near-perfect circumnavigation. Some trepidation over this one because from Nuka Hiva to the Galapagos is a shade over 3,000 nm - 3,064 to be exact - and there is nowhere else to land once past the point of no return. We picked up a little icing early on but it was actually a very nice flight at 18,000 feet into light headwinds - until the pressurization failed. The cabin quickly went to 18 thou, so I quickly descended to 12,000 - where we found a 24-knot headwind. We were 2,200 miles into the trip, with 800 to go. I fiddled a lot with the throttles and propeller pitch control. I remembered reading about the WWII Army Air Force operating at low RPM at times to extend their range and finally settled on 23" and 1,800 RPM. The winds were no better at lower altitudes, so we stayed at 12,000 and plodded on, fingers crossed. We picked up the first beacon a long way out and I elected to bypass the closest field and continued on another 80 miles to the main airport with its longer runway. We landed with 141 gallons of fuel remaining, enough for 95 miles, or about 25 minutes flying time. 3,064 miles in 13 hours 20 minutes, for an average speed of 230 knots. Final Leg - The Galapagos to Quito It's less than 700 miles to Quito so I got to take off AND land in daylight. We cruised at 10,000 with gentle winds. Climbed a little over the foothills of the Andes, and then swooped into Quito/Mariscal Sucre (after Antonio Jose de Sucre y Alcala, fourth president of Peru and second president of Bolivia). Landed gracefully, rolled to the ramp, shut her down. 3 hours 5 minutes. 670 miles. 217 knots. Conclusion Trip stats: Total distance: 21,725 nautical miles. Total flight time: 93 hours 57 minutes. Average speed: 231 knots. The A2A Connie is a total delight to fly. I may have gone round the wrong way. The prevailing winds, while generally light, were all out of the east. I don't know if this is typical for the equatorial region; perhaps a seasonal thing. Reminder: A2A aircraft will throw things at you that you won't get with stock FSX planes. If you're flying A2A planes it's a good idea to regularly review and practice your emergency procedures.
  4. "8 Days Around the World" 18 flights in 8 days By Bill Smith Historical flightsim adventure, finally adapted as a movie! See the trailer for the movie here: Background Back in 2001 I submitted to flightsim.com a rather long and breathlessly excited editorial piece which chronicled a "round the world" trip that was flown non-stop for 120 hours in FS98. Re-reading the article recently I was drawn back into the five-day period of relentless hit-and-miss global navigation and very little sleep as I jumped rapidly from one aircraft type to the next. What I lacked in knowledge and preparation back then was more than made up for with a boundless enthusiasm to discover exactly how much flight simulation was too much. My overriding memory of this five day period is how I survived in a kind of semi-hallucinogenic twilight existence right up until my FS time ran out when real world responsibilities came crashing back in on me. I have to admit, as exhausting as it was, it was fun while it lasted. Now of course I like to think that I have matured considerably since 2001, but the truth is that the astronomical advances in flight simulator technology over recent years have drawn me even deeper into the increasingly realistic world of simulated global flying. We all take for granted nowadays the integration of real weather systems and very precise trans-continental navigation over highly detailed terrain in our much improved flight sim programs. There is so much more complexity that we need to come to grips with but the resultant illusion of flight is more complete. So I wondered if it would be possible to somehow capture the essence of that marathon voyage using modern day hardware and software and present the story as a motion picture full of exciting flying sequences. A Few Ground Rules I thought that it was essential to fly the entire route incorporating the correct real world weather over eight sequential days. I would try as far as possible to fly to the same destinations as I had eleven years ago. Using present day air schedules of course it's no surprise to find the airlines' aircraft have changed. (No more shrieking 727s or scary DC-10s.) I definitely wanted to incorporate the mad parachuting sequence over Key West and to re-visit the half naked beach babes in Rio De Janeiro. (Perhaps I haven't matured as much as I thought I had). I figured that as my RTW attempt had ended prematurely in Hong Kong, I should start this voyage re-creation where I had left off, with a plan to arrive back at the start point one week later. The Movie Thanks to the huge assortment of FS add-ons that are available today, the flying sequences look sharp and the trip went far better than I ever anticipated. Also, thanks to a savage regime of editing, the pace of the finished movie is fast; perhaps even relentlessly so. This time around, in recreating this epic voyage I managed to reaffirm my natural place in the world; one step removed from reality. This is something that only other similarly addicted flightsim fanatics can relate to. Enjoy the movie at Youtube: 8 Days Around The World Part 1 8 Days Around The World Part 2 Bill Smith leesmith@ca.com.au
  5. Around The World In ... How Long Does That Take? By Ron Blehm (21 March 2011) In 1873 author Jules Verne published his famous book, "Around the World in 80 days." This novel followed the adventures of Londoner Phineas Fogg and his French valet Mr. Passepartout as they took on a £20,000 challenge to travel around the globe in just 80 days. The novel was written at a time when trans-Asian and trans-American rail lines were just being completed and the possibility of world travel actually because plausible. Many adventures and missteps were had along the way (as in any good novel) but the story got me to thinking, "How long would it take, in today's terms, to do the same trip?" Sure, two or three legs on an A340 or 777 would be pretty quick and flightsim even offers spacecraft that could make the flight in about 80 minutes but I mean really, how long would this take in the real-world (if everything ran on time)? Could I make it all the way around in, say, 80 hours? Several years ago simmer Peter Stark wrote an article about flying the sim around the world in about 600 days and perhaps his piece was a bit of an inspiration to take this on. Well, I fired up FSX and went to www.flightlookup.com and started entering information. (Please note that flight information and equipment change often, sometimes without notice. What I have written here was the information provided on the day I undertook this project.) In the Jules Verne novel the travelers went from London to Suez but there are no direct flights that I could find to Port Said. So instead I searched for London to Cairo and found Egypt Air flight 778 is a non-stop, departing London at 14:00 and scheduled to arrive to Cairo at 20:45. Equipment is listed as a 773. I loaded in a flight plan, downloaded real weather and pushed back from the gate at 14:02 on Monday January 24th. Once clear I started the engines and requested taxi to the active. During my 15-minute taxi and hold I calculated that to win the prize (Maybe I could win a free years' membership to www.flightsim.com?) I needed to be shut down at a Heathrow gate before 22:00 Thursday night January 27th. I departed from runway 27L (above, left) and climbed through 4,500 feet before turning to intercept the route (above, right). As I received clearances I climbed on up to a final cruise of 33,000 feet. Sunset came over Italy somewhere (short days in January in the north) and the last half of the flight was in darkness. The schedule showed that my arrival was to be 20:45 and I landed at 20:42 (below, left). After what felt like a long taxi my actual shut-down at the gate was ... 20:45. Amazing! Next I looked for non-stop flights from Cairo to Mumbai and found Egypt Air flight 968 which leaves at 23:00 and flies a 738. (Seems like a long flight for the 737 family but we'll see) This left me a layover of just over 2 hours. I switched planes, loaded the flight plan, fired up the sim and ... waited for ATC to stop talking to everyone else. It was 23:05 before I started taxi and 23:12 when I started the takeoff roll. (I was number 3 holding for takeoff - above, right). Our cruise level was FL350 and our route took us over Dubai and along the south coast of Iran. Scheduled arrival was to be 07:55 but I showed actual shut-down at 06:11 (below,left). Either that was one heck of a tailwind or Microsoft missed a time zone somewhere! Whatever the case, I only had 1,914 pounds of fuel left in the tank so it was time to land. The next real-world flight is Indigo Air flight 321 from Mumbai to Kolkata which is scheduled to depart at 09:25 and flies an A320 (above, center). Scheduled arrival is to be 12:10 and I was able to shut down at the gate at 12:48 (above, right). I guess that makes up for arriving early into Mumbai! From Kolkata Jules Verne's novel took our intrepid travelers to Hong Kong but I was unable to find any non-stop flights. In the novel there was an interruption as they crossed India, a funeral party was crashed and well ... you'll have to read the book. So, in order to make up for that one-day delay in the story I chose a connection via Delhi. Indigo Air 206 departs at 16:40 so I had about 4 hours to get into town and find some non-airline food! After a "quick" trip into town I was pressed to get back to the airport and ready for departure on time. It was still very hazy as the sun set and I returned to Delhi in darkness (photos above). I did a coupled approach to landing and shut down at the gate at 19:05 Tuesday night - about 4 minutes late. The next leg is flown by Cathay flight 694 which leaves Delhi at 22:15 and flies an A340 to Hong Kong with scheduled arrival at 05:25 Wednesday AM. I loaded the flight plan and pushed back on-time. Cruise was at 37,000 feet (above, left). We landing on runway 25L in Hong Kong and shut down a little bit early at 05:02 (above, right). Our next leg, according to the Jules Verne novel is up to Yokohama. Well, for real schedule and flightsim purposes we'll pick a flight to Narita instead. Delta 638 leaves Hong Kong at 08:00 Wednesday AM and flies a 747-400 (photos above). Scheduled arrival was to be at 12:55, we arrived uneventfully and shut down at 13:44 (below, left). Now hang on; An hour early into Mumbai and an hour late into Tokyo? What's the deal here? Anyway, the next leg is an overnighter to San Francisco, departing Tokyo at 17:00 and scheduled to arrive at 09:03. United uses a 747-400 for flight 838 but so that we could see something different I chose to fly a Pan Am 747-200 (above, right). We left in the light rain Wednesday night and arrived 45 minutes late ... Wednesday AM (below, left). At this point, barring any mechanical failures, I was quite sure that I could complete the task in under 80 hours and win the prize! Our next scheduled flight is United flight 10 leaving SFO at 10:37 AM. This left me just under an hour to get over to the other gate and get the 757 all prepped and ready to go. We pushed back at 10:39 and taxied to the active (above, center). Our route across the US of A took us over Salt Lake and Chicago among other waypoints (above, right). Scheduled arrival to JFK was to be 19:15 but flightsim showed me shut down at 19:53. Now, I was doing Mach 0.81 across the nation with a slight tailwind from the northwest - how on earth was I supposed to be 30 minutes faster? This lead to my next problem. I had planned on taking British Airways flight 176 but that was to leave JFK at 19:55 and obviously I wouldn't be able to make that kind of a turn-around. I had missed my connecting flight!! Since I had already downloaded and installed a British Airways 772 I was debating ... just leave "late" or call it "missed" and look for another flight. American flight 132 uses a 777 and leaves at 21:30 and is set to arrive at 09:35 Thursday AM, about 12 hours early for my 80-hour window. Sorry to the AA fans out there but this was my plan - leave at 21:30 but fly the BA livery. Well, it was a dark and quiet night across the pond, dawn arrived over Ireland and made a straight-in approach to Heathrow's runway 9R shutting down early at 09:02 (photos above). So there you have, Jules Verne fans, using modern equipment and real-world time schedules you CAN fly all the way around the globe in 80 hours. Ron Blehm pretendpilot@yahoo.com
  6. Part 8 Visiting Africa, Indian Ocean And Return To Europe I'm glad to welcome you again for the last time on this Airbus A330-200 that is now about to conclude its virtual journey around the world. A very long journey that could actually have been finished off within a few weeks, but which was spread over more than one year, the first leg dating back to July 2006. Nevertheless, the late conclusion of this series coincides with the release of a highly detailed (and expected) scenery of my home airport, Brussels, where the adventure will definitely come to its end – a fairly nice end then. But before that, we've still a large array of places to visit. Our aircraft will first leave Rio de Janeiro, the previous part's last stop, to cross the Atlantic and reach Cape Town, flying one of the entire journey's longest legs. That will be the last opportunity to tackle the ETOPS flights, the special procedures that allow twin-engined aircraft to cross the oceans as we will see below. From Cape Town, we will head towards the Indian Ocean, visiting the islands of La Réunion and Seychelles. Then, back to Africa with stops at Kilimanjaro in the Rift Valley and Dakar, both modeled with FS2004 default textures. A short flight from Dakar to Tenerife in the Canary islands, belonging to Spain, will introduce our return to Europe as well as to high quality add-on landscapes. Paris–Charles de Gaulle will be our very last destination prior to going back to Belgium, where we will find brand new sceneries for the terrain and, as announced, Brussels airport. In the conclusion words of this series, we will briefly recall the whole trip's features and also touch on some real environmental concerns. Finally, an acknowledgements section will pay tribute to all the people who have made this virtual trip come true. The usual Credits section, giving reference to the software and documentation used for this article, will be displayed last. Flight Horizon 2006 around the world is now again ready for boarding. Passengers please go to the gate and get your boarding pass and passport ready. Horizon Dreams wish you a pleasant flight. Leg 31: Rio de Janeiro, Brazil – Cape Town, South Africa This transatlantic flight will leave Rio de Janeiro at sunset for a morning arrival at destination, the night being shortened by a 5 hours time lag between Rio (UTC–3) and Cape Town (UTC+2). This 8 hours flight would be less long if we were flying an A340 type, i.e. a four-engined aircraft, allowing us to fly a more direct route across the Atlantic. Twin-engined airliners may though be authorized to cross the Atlantic, the other oceans and remote land areas, but following special rules called ETOPS. ETOPS or Extended Twin-engine Operations permit the newer twin-engined commercial aircraft to fly routes that, at some points, are further than a distance of 60 minutes flying time from an adequate diversion airport, at the approved one engine inoperative cruise speed in standard conditions and still air. The main purpose of ETOPS is to provide high levels of safety while facilitating the use of today's twinjets on routes which were previously restricted to three and four-engined aircraft. Taking advantage of the efficiency, performance and safety features of the modern twin-engined aircraft powered by high-bypass engines, ETOPS also permit more effective use of one airline's resources. Before an airline can operate a plane under ETOPS conditions, the aircraft must first have either been designed or modified and approved to meet the ETOPS certification requirements. This is the responsibility of the aircraft manufacturer. The ETOPS Type Design Approval for one given aircraft is split into two parts: the ETOPS type design eligibility the ETOPS type design capability ETOPS type design eligibility concerns the aircraft design features prior to entry into service: the aircraft manufacturer must first demonstrate that its aircraft complies with the ETOPS design criteria. This includes of course the propulsion system reliability (eg. a maximum inflight shutdown rate of 2/100 000 engine hours for 180-minute ETOPS) but also the electrical power sources and systems redundancy, APU and emergency generator design, minimum crew workload, ice protection and safety assessment. The ETOPS type design capability is obtained when the aircraft/engine combination has attained a sufficient reliability level based on in-service experience. Generally, the aviation authorities require from 100 000 to 250 000 engine flying hours of experience in order to obtain a statistically viable reliability analysis. If an airline wants to operate ETOPS flights, the candidate aircraft must have received its ETOPS Type Design Approval but the airline must next get the ETOPS Operational Approval from its national aviation authority prior to starting ETOPS services. In that way, the airline has to prove that it has the appropriate experience with the aircraft/engine combination and that it is familiar with the intended area of ETOPS operation. The first ETOPS flights (90 minutes) took place in 1985 with TWA (B767) and Singapore Airlines (A310). In 1986, PanAm inaugurated the first transatlantic A310 services. The Airbus A330 with Rolls Royce engines obtained the ETOPS Type Design Approval with 90-minute diversion time (ETOPS–90) in 1995 and is eligible for 180-minute ETOPS. Meanwhile, operators who intend to progress to an ETOPS–180 approval must demonstrate one year of trouble-free ETOPS–90 experience with this aircraft/powerplant combination. ETOPS–180 rules make 95% of the Earth's surface available to ETOPS operations and therfore increase the airline efficiency and flexibility. Today's flight, as well as the flights that were made across the Pacific in Parts 4 and 5, will observe an ETOPS–180 rule. This 3 hours diversion time is unrealistic if we consider that our RR-powered A330 is a brand new aircraft that carried on with the trip from the Tel Aviv stop in Part 3. But we are ignoring the real one-year of trouble-free experience rule described above: with a only 90 minute maximum diversion time, most of Around the World 2006-2007 oceanic legs would not have been feasible. Flight Plan From RIO DE JANEIRO/GALEAO ANTONIO CARLOS JOBIM INTL (GIG/SBGL) to CAPE TOWN INTL (CPT/FACT) ETOPS-180 enroute alternate FHAW ASCENSION AUX AB Destination alternate FAJS JOHANNESBURG SBGL15 PCX1 PCX UA611 ALGAL ETOBO UA405 RIV RIV3B FACT01 Distance 3548 nm (6564 km) Flight time 8:00 An ETOPS flight requires specific definitions, fuel planning, cabin equipment, flight crew preparation and dispatching. We will not go further into details here but give a few notions to illustrate and understand today's flight. A suitable airport is an airport than can accomodate the ETOPS rated aircraft for an emergency landing and which satisfies the ETOPS dispatch weather requirements within a validity period. A diversion or enroute alternate airport is a suitable airport to which a diversion can be accomplished, and whose flying time from the point of emergency shall not exceed the ETOPS maximum diversion time (180 minutes in our case). The typical one-engine-out diversion speed is 400 kts (TAS) and the Airbus A330 single-engine ceiling is 22,000 feet. The ETOPS entry point (EEP) is the point on the outbound route where the aircraft goes further than a distance of 60 minutes flying time (at the scheduled one-engine-out diversion speed) from the last suitable airport. From the EEP, the aircraft enters the ETOPS area of operations. The ETOPS segment starts at the EEP and finishes when the route remains within the 60-minute area from a suitable airport. An Equitime Point (ETP) is a point on the route which is located at the same flying time from two diversion airports. We have two ETPs for our present flight. The ETP positions can be easily and geometrically determined in no wind conditions (this is what is done here). In windy conditions, the ETPs positions must be corrected by the wind effect. This is one of the tasks of the dispatcher. The critical point (CP) is the point on the route which is critical with regard to the ETOPS fuel requirements if a diversion has to be initiated from that point. The CP is usually the last ETP within the ETOPS segment. Finally, the ETOPS fuel planning is special and split into two parts: the first one corresponds to a standard fuel scenario from the departure airport to the CP and the second one corresponds to the critical fuel scenario from the CP to the diversion airport (FHAW in our flight). The ETOPS fuel planning is then compared to the standard fuel planning from the departure to the destination airport (and considering the destination alternate, FAJS in our flight). The highest of both fuel requirements shall be considered as the required block fuel for the flight. I confess that I've restricted myself to the usual standard fuel planning here, considering that we've a very long distance from the destination to the destination alternate: 686 nautical miles (1270 km), which is comparable with the distance between the CP and the enroute alternate. Also, the PSS simulated MCDU doesn't handle the ETOPS flights. In the real aircraft, this is well the case and the ETOPS specific points (EEP, ETP, CP) are recognized in the active flight plan and can be displayed on the Nav Display as well. Our ETOPS-180 route, however, is fairly realistic. We need only one enroute alternate for the flight and there is hopefully one island in the middle of the South Atlantic that offers a suitable airport: Ascension island. This is one of the eight islands of St Helena, a British overseas territory, whom principal island is St Helena. St Helena is famous to be the dethroned French emperor Napoléon Bonaparte's last residence. He was sent there as a prisoner by the British government after his defeat at the Waterloo Battle in 1815, and remained there until his death in 1821. Ironically, we will pass near the Waterloo battlefield in the very last seconds of Around the world 2006-2007 when we will be approaching Brussels. Ascension island, located around 800 miles northwest of St Helena, is lived in by a bit more than one thousand people. The airport (FHAW) has a 10,000 feet runway and VOR/DME equipment. But if the flight goes off normally, we shouldn't pay any visit to that remote location. Graphic display of our ETOPS-180 flight from Rio de Janeiro to Cape Town. The map also reveals that there is a direct airway (UA559) connecting the two cities, but it penetrates the ETOPS exclusion zone and will therefore only be available to three or four-engined aircraft. Rio de Janeiro Galeao Intl – holding point runway 15. Another 'classic' encounter with this old 737-200 of the Brazilan carrier VASP. Runway 15 is shorter than runway 10, but taking off from it has a notable advantage that is useless to comment. Already at 3300 ft. Passenger's view 1000 feet higher. Initiating a left turn on the PORTO One standard departure. Back to the 60-minute diversion time area after our ETOPS Atlantic crossing and now with South Africa's coast in sight. CPT (PA): Ladies and gentlemen, this is your captain speaking. We've now successfully completed our Atlantic crossing following the special ETOPS rules that I had briefly told you about yesterday. As you have already been advised by our cabin crew, we've started our descent to Cape Town and we should reach our destination within fifteen minutes. Here from the flightdeck, we have a beautiful sunrise just in front of us and we've the African coast in sight. Weather in Cape Town is pretty nice with scattered clouds, fourteen degrees centigrades and a light wind from the north. During our approach, right-sitting passengers will enjoy a magnificent view of Cape Town and Table Mountain. Local time at destination is a quarter past six a.m., please adjust your watches! As usual, please follow carefully the last cabin crew instructions until we are safely parked at the gate. Thanks for your kind attention. The last time I visited Cape Town during another virtual flight was on a South African A319 from Durban, in August 2005. Arriving from the east, the arrival procedure was totally different from the one described here. I was rather surprised, indeed, to see that the present Robben Island Three Bravo standard arrival path comes really close to Table Mountain, while I was first expecting an offshore trajectory during the flight preparation. The STAR having no altitude constraints (those being probably at ATC discretion in the real world), I let the Flight Management System compute the descent profile and the result was a rather close approach to the 3563 ft (1086 m) flat-topped mountain that dominates Africa's southernmost city. Nice modeling of Table Mountain, provided by add-on terrain mesh with 76m resolution. The textures are the FS2004 default ones. A close approach to the terrain then (now at 4500 ft). This reminds me the rather low New York flyby in Part 5 and I believe that in the real approach here aircraft are much higher as well. Right turn to initiate the downwind leg for runway 01. Leg 32: Cape Town, South Africa – La Réunion Island (France) La Réunion will be third and last French overseas territory that we visit, after Tahiti and Guadeloupe. The fourth, if we also include St Maarten island, which is split between the Netherlands and French Antilles. La Réunion, located in the Indian Ocean 700 km east of Madagascar and 200 km southwest of Mauritius, is a volcanic island that was born around two millions years ago. The eastern part of the island, however, is only 60 000 years old and is made up of one of the most active volcanoes on the planet, known as Piton de la Fournaise. The entire island is only the emerged part of a sub-marine mountain that is more than 30 times bigger! The island's first residents were Europeans who settled here in the beginning of the 16th century. La Réunion is a French territory since 1642. Flight Plan From CAPE TOWN INTL (CPT/FACT) to ST DENIS/ROLAND GARROS (RUN/FMEE) Alternate FIMP MAURITIUS FACT01 WY1D WY BDV DNV ETMOS UA402 GETIR GETIR3E FMEE14 Distance 2159 nm (3994 km) Flight time 4:40 After the Wolseley One Delta departure, we'll first head towards Durban, then hit the southern tip of Madagascar prior to reaching the destination. Some thunderstorm activity is expected on arrival, but nothing really serious. Passing GETIR and starting a 180 miles-long STAR procedure. The sun sets as we've 68 miles more to go. Developing thunderstorm clouds are confirmed. On the base leg for runway 14. This is the typical shape of the cumulo-nimbus (CB) cloud, whose summit can reach the tropopause, up to an altitude of 18 km (60 000 feet) in the tropical latitudes. Now established on the ILS, at 3900 feet and 17 miles more to go. The approach path fortunately goes round the CB cloud, usually triggering heavy turbulence. At 3000 feet, 8 miles away, getting prepared for landing. Night is falling quickly while further dark clouds hide the summits of the island. This is the northern coast of La Réunion, which is exposed to the east trade winds and has a more rainy climate than the southern part of the island. Though encountering some difficulties on short final, because of a rather strong crosswind. Safely down. Leg 33: La Réunion island (France) – Mahé, Seychelles As the last tropical spot to be visited in this journey, the Seychelles are an archipelago of 115 islands spread over a wide area in the Indian Ocean. The main island, where the international airport was built, is Mahé. As well as the other neighbouring islands, including Praslin, it has neither volcanic nor coralline origin but is a micro-continent connected to Africa. Flight Plan From ST DENIS/ROLAND GARROS (RUN/FMEE) to SEYCHELLES INTL (SEZ/FSIA) Alternate HKMO Mombasa FMEE12 NIBIS3C NIBIS UR401 RUBAM SEY FSIA13 Distance 989 nm (1830 km) Flight time 2:30 For this flight (which is nothing but a straight line between the two airports), the alternate airport distance from the destination airport (954 nm) is almost the same as the flight distance itself! Unless I've missed something, from Mahé, the closest suitable airport for the A330 is to be found on the east African coast. Nice morning departure and directly bound towards Seychelles. So long La Réunion Flying the VOR DME Rwy 13 approach at Mahé, which ends up with a full visual landing. Leg 34: Mahé, Seychelles – Kilimanjaro, Tanzania Back to some kind of old memories for me, as this destination was already visited in a first world tour published in early 2003. The fact is, there is not much add-on scenery to fly into in the central Africa region and Kilimanjaro is probably the best that the FS2004 default scenery can offer. The Kilimanjaro is a solitary extinct volcano that dominates the surrounding savanna. It is also Africa's highest point with 5895 m (19 650 ft). The summit is covered with perpetual snow, but this ice cap is nowadays dramatically reducing, making the Kilimanjaro one of the most meaningful symbols of climate change. Flight Plan From SEYCHELLES INTL (SEZ/FSIA) to KILIMANJARO INTL (JRO/HTKJ) Alternate HKMO Mombasa FSIA31 PRA UA610 KV HTKJ09 Distance 1144 nm (2116 km) Flight time 3:00 That's interesting, we have the same alternate as for the previous leg. We will first head towards Praslin island, 25 miles north of Mahé, then head directly towards Kilimanjaro. KV VOR/DME is located on the airport. Arriving a bit too late to enjoy the Kilimanjaro during day time. That will be for the next leg then. Leg 35: Kilimanjaro, Tanzania – Dakar, Senegal This is the last long range leg of the trip. We will cross Africa from one end to the other and the flight distance is almost the same as for the Rio de Janeiro – Cape Town leg. The route will include Mwanza (Lake Victoria), Kigali, Goma, Kisangani, Yaoundé, Douala, Port Harcourt, Lagos, Cotonon, Lomé, Accra and finally Abidjan. In the meantime, we will cross the equator for the sixth and last time in our journey. Flight Plan From KILIMANJARO INTL (JRO/HTKJ) to DAKAR/LEOPOLD SEDAR SENGHOR (DKR/GOOY) Alternate GBYD BANJUL HTKJ09 MODAM UB531 KGI UA610 NLY UR984 TST UA609 ACC UB600 AD UR979 ERIDI ERIDI2A GOOY36 Distance 3552 nm (6571 km) Flight time 8:00 Taking off runway 09. There is far too much snow on the top of the mountain for this FS2004 default scenery. Nowadays the snow covers a surface of only 2 square kilometers, while it was covering an area of 12 km² in 1900. The Kilimanjaro has lost more than 80 percent of its ice cap during the 20th century. Approaching Kigali (Rwanda) /feature/atwcdk8/image025.jpg Flying over Dakar on final to Rwy 36 Leg 36: Dakar, Senegal – Tenerife, Canary Islands (Spain) Tenerife is the biggest of the Canary islands, located west of the coast of Morocco. The Teide, the principal volcano of the island, is also the highest summit of Spain (3718 m). Tenerife is one of the most popular charter destinations in Europe. On April 27, 1977 a ground collision between two Jumbo Jets from KLM and PanAm occurred on the small Los Rodeos airport. The accident was partly due to fog and was recorded as History's worst air disaster. A bigger airport, Reina Sofia, was built afterwards in the south of the island benefiting from a better climate. This is were we will land today. Our flight plan is first a straight line towards Gran Canaria, the second biggest island of the archipelago, following the UB600 high altitude airway. Then we will turn left towards Tenerife and we'll almost be directly bound on the landing runway axis. In this leg, we will enjoy what is, up to my mind, one of the best freeware sceneries ever developed for Flight Simulator (also see credits). An incredible, professional terrain mesh and textures quality will make the end of our flight as real as it gets. Flight Plan From DAKAR/LEOPOLD SEDAR SENGHOR (DKR/GOOY) to TENERIFE SOUTH/REINA SOFIA (TFS/GCTS) Alternate GCXO TENERIFE NORTH GOOY36 LIMAX NULET UB600 GDV TERFE GCTS26 Distance 875 nm (1619 km) Flight time 2:10 Above Gran Canaria at 16000 ft, approaching GDV VOR. After the left turn, now at 10 000 ft and proceeding towards TERFE. Final approach to Tenerife South runway 26. Good weather for landing, and for a little ride on the Teide mountain as well. Another uneventful landing. Welcome back to Europe! Leg 37: Tenerife, Canary Islands (Spain) – Paris, France I wished to make a last stop in another great European city prior to eventually going home. Located on the way back to Brussels, and having still some nice photographic scenery to fly into, Paris was the place to go. Finding the shortest route from Tenerife was not that easy, since we are back to Europe and more busy skies, were the high altitude routes are often one-way corridors. We will first head towards Santiago de Compostella in Spain, hugging the west coast of Portugal. Then, we'll cross the Gulf of Gascogne and finally hit the French coast near the city of Nantes. Back to Europe, but also to more gloomy weather today with an overcast sky and moderate visibility conditions on arrival. Flight Plan From TENERIFE SOUTH/REINA SOFIA (TFS/GCTS) to PARIS/CHARLES DE GAULLE (CDG/LFPG) Alternate LFPO PARIS/ORLY GCTS08 KONBA3E KONBA UN866 STG UN741 TUROP UN864 NOVAN UT460 ERIGA UN741 KEPER KEPER3H LFPG08R Distance 1600 nm (2960 km) Flight time 3:40 Paris–Charles de Gaulle, our destination, is one of the biggest airports in the world and the seventh one considering the number of passengers (ranked as number 2 in Europe after London Heathrow). Its construction started in the early seventies to supply the existing Orly and neighbouring Le Bourget airport. The latter was the first airport of Paris and is still active nowadays, but restricted to general aviation as well as the famous Salon du Bourget event. Paris CDG is a continuously growing airport that has now four runways and actually seems to be made up of two airports, 'Roissy 1' (or CDG 1, in the north) and 'Roissy 2' (south), everything being connected by a complex taxiway system. We will be bound to Terminal 2 on our present flight with a landing scheduled on the recently built runway 08R. Ready to leave – the sun will rise shortly. Cleared for takeoff. CPT: FLEX, SRS, RUNWAY... Power set. F/O: Checked. Already above 20 000 ft, farewell to the Teide. Heading north at Mach 0.82 Passing KEPER at 27 000 ft, starting the standard arrival to Paris CDG. Cloud break abeam the famous Versailles castle and gardens, residence of the kings of France from Louis XIII to Louis XVI. 25 miles left to go. Getting prepared for localizer capture (now at 5000 ft). Paris here we come! Here is the La Défense business district and the futuristic Grande Arche. We can also see the Eiffel tower in the distance. Now fully established. Together with another aircraft approaching runway 09L. Short final. The facilities that we see on the left (Terminal 2) are only the southern part of Charles de Gaulle airport. Seconds from touchdown – the Air Europa aircraft is taking off from runway 08L. Leg 38: The Final Leg - Paris, France – Brussels, Belgium Well, every thing has to end one day. This very short flight (we will reach Brussels within less than one hour) will conclude a 14 months long adventure. In fact, the first leg took place in mid July 2006 and this last leg was flown on September 15, 2007. Weather in Belgium was nice that day, though rather cool, and similar conditions (excepts the wind direction) were set in Flight Simulator. I'm thus going home and in the meantime I will discover a recently released brand new scenery of Brussels Airport. We will leave Paris CDG in the late afternoon, expecting a sunset arrival at destination. Flight Plan From PARIS/CHARLES DE GAULLE (CDG/LFPG) to BRUSSELS (BRU/EBBR) Alternate EBOS OSTEND LFPG08L NURMO9H NURMO UN874 CMB UZ373 ARVOL ARVOL1B EBBR 02 Distance 173 nm (320 km) Flight time 0:50 After taking off from runway 08L, we will observe the NURMO Nine Hotel SID and remain on the runway axis for a few miles, then turn left heading to Cambrai. We will climb up to 24000 feet (7200 m) but will not stay there for long. After Cambrai VOR we will use the UZ373 airway that is reserved for Brussels arrivals. Though radar vectoring is usually expected upon arrival, we will follow the ARVOL One Bravo STAR then fly the published ILS approach to runway 02 (the shortest, transversal runway at EBBR). The result will be some kind of zigzaging path. Holding point runway 08L, number two for takeoff. This runway is among the longest ones in Europe (4215 m) and ATC is currently directing the departing aircraft to taxiway S1 that is not connected to the runway tip. Already at 6000' but still outbound on the takeoff runway heading (left), passing PG084 fix at 9000' and heading north (right). 25 minutes after engine start we are already approaching ARVOL and the Belgian border. We are abeam Lille-Lesquin airport (LFQQ) and descent has started ATC (Paris Center): Horizon two zero zero six heavy, contact Brussels Center on one two five decimal zero. F/O: Brussels on 125.0, Horizon 2006 heavy. Good day. ... Brussels Center, Horizon 2006 heavy, good evening, with you at thirteen thousand. ATC: Horizon 2006 heavy, good evening, descent and maintain nine thousand, expect ILS runway two approach. CPT (PA): Ladies and gentlemen, this is your captain speaking for the last time. We are now back above our home country and we should be landing in around twenty minutes. During our approach we will first fly over Flanders and the west of Brussels, then head south towards Wallonia and we should finally align on the runway somewhere near Waterloo. As you see, weather is nice for our return and temperature at Brussels is now sixteen degrees centigrades. That should be an easy landing. In the name of the whole crew I would like to thank you for your kind cooperation throughout this very long journey, and in particular during the more difficult moments and delays that we have encountered. We should be right on schedule today so you may fully enjoy these last minutes of flight in this Horizon Dreams Airbus A330. Thanks for your attention and bye bye. Between ARVOL and AKOVI (now at 10 000'), above the city of Ronse/Renaix, on the boundary between Flanders (the Dutch speaking part of Belgium) and Wallonia (the French speaking part). The hills that we see below are interesting since they are the first heights to rise from the Flemish plain that stretches up to the North Sea, 65 kilometers away. We can also see the Scheldt river in the distance. ATC (Brussels Center): Horizon two zero zero six heavy, contact Brussels Approach on one one eight decimal two five. F/O: 118.25 Horizon 2006 heavy, good day. ... Brussels Approach, Horizon 2006 heavy, good evening, with you at nine thousand on the ARVOL One Bravo standard arrival for ILS runway two approach. ATC: Brussels Approach, Horizon 2006 heavy, roger, continue approach, descend to two thousand. Maintain two thousand until established on the localizer. Altimeter one zero two three. Contact Brussels Tower on one two zero decimal seven seven when established. Passing KERKY at 5000'. This small town is Ninove, 20 km west of Brussels. The watercourse is the Dender, a Scheldt tributary. The METAR observation for Brussels airport was: EBBR 151730Z 04507KT 9999 SCT030 16/08 Q1023 NOSIG METARs are meteorological airport reports (or aviation routine weather reports) that are updated every 30 minutes. They provide weather observations (not forecasting) for a particular airport. The METAR code contains all the necessary information about wind, visibility, sky condition, temperature, pressure etc. In the real world pilots can access the METAR data through the ACARS system. ACARS (for Aircraft Communication Addressing and Reporting System) is a digital datalink system for transmission of small messages between aircraft and ground stations. Such messages can include weather information, of course, but also all the messages that are used to communicate between the aircraft and its base (not Air Traffic Control), such as enroute delays or aircraft performance reports. Downlink messages are sent by the aircraft, uplink messages, such as weather reports, are received from the airline's computer system. Basically, the ACARS system works a bit like email. The interface between the pilot and the ACARS Management Unit (MU) is usually the MCDU. A print function is also available. If set automatically upon receiving a message, the ACARS can also be compared to a simple fax machine. Unfortunately, and not surprisingly, the ACARS system is not modeled in the simulation, but real time METARs are easily available on the Internet. So here's the nice weather 'hidden' in the METAR code: Brussels Airport, observation made the 15th of the month at 17:30 GMT, wind direction 45°, wind speed 7 knots, visibility: 10 kilometers or more, sky condition: scattered clouds at 3000 ft, temperature 16°C/dew point 8°C, QNH 1023 Hectopascals, no significant change within the next 2 hours. Already at 2000 ft, a few miles before localizer capture. This is not a river but the canal from Brussels to Charleroi, an important thoroughfare in Belgium. CPT: Cabin crew, please be seated for landing. Localizer capture near Waterloo. The countryside under the aircraft's nose is Waterloo battlefield. Final approach to the end of the adventure. ATC (Brussels Tower): Horizon 2006 heavy, cleared to land runway two, wind forty four degrees, six knots. LANDING CHECKLIST CABIN CREW....................ADVISED AUTOTHRUST....................SPEED ECAM LANDING MEMO.............LANDING NO BLUE Seen from here, this new airport scenery already seems outstanding. The new, 65 meters high control tower is visible on the right. This is what the spotter would feel outside the airport fence... ... and the pilot's feeling is not bad as well. Very accurate modeling of Rwy 02. A bit too low for this last landing. This is the last airborne second of Around the world 2006-2007. Finally down and braking action. We can see the old terminal and the old tower here on the left. ATC: Horizon 2006 heavy, exit runway when able. Was I so in a hurry to go home, or wanted to make ATC happy, but the runway was quickly vacated by the high speed taxiway Echo Five, with reverse thrust still applied! A very short taxi to the terminal was to follow then. CABIN CREW: Ladies and gentlemen, welcome back to Brussels, it's forty-five minutes past seven local time. Please remain seated until the seatbelts sign has been turned off and the aircraft has come to a complete stop at the gate. Thank you for flying this long journey with us and we hope to welcome you again in the future on other Horizon Dreams flights. Thanks for your attention. ATC (Brussels Tower): Horizon 2006 heavy, contact Ground on one one eight decimal zero five. ATC (Brussels Ground): Horizon 2006 heavy, taxi to gate one forty-five right by Romeo four. Just reminding us that we had left for a long time, a new airline is born at Brussels! Brussels Airlines started operation in March 2007 after the merging of SN Brussels Airlines (former Sabena) and Virgin Express. The very last meters to gate 145R. No more marshallers here but an automatic docking guidance system. The 'Pier A' is the newest terminal at Brussels Airport, inaugurated in May 2002 to accomodate the Schengen flights. Engine 2 just after shutdown. As well as his team-mate Engine 1, we can say that they made a good job. SHUT DOWN CHECKLIST BEACON.....................OFF FLAPS......................RETRACTED ECAM STATUS................CHKD PARKING BRAKE..............SET THE END. Conclusion words for Around the World 2006-2007 First of all, a few figures. This virtual journey has taken us to 39 destinations in 30 different countries and overseas territories. We have travelled 59,490 nautical miles or 68,790 miles or 110 060 km – that's nearly the third of the distance from the Earth to the Moon. If the whole journey was spread over more than one year, we have added up around 130 flying hours, that's 'only' 5 days and 10 hours of flight. The longest leg was Leg 19 Guam–Anchorage across the Pacific with 4,369 nautical miles or 8082 km. The shortest leg St Maarten–Pointe-à-Pitre (Leg 27) covered at distance of only 148 nm or 274 km. We have visited the FS2004 world, usually enhanced by add-on scenery for many destinations, but only giving an idea of the current available flightsimming software. This project has given me the opportunity to give a general overview of Airbus systems and philosophy, while touching on some further technical topics. Using the same charts as the ones used in the flightdeck (enroute charts, approach charts etc.), as well as many online and offline documentation, the realism level was one of this project's purposes. But we have seen that if many procedures or systems can be exactly simulated, others cannot. Much information was provided throughout the review and I've tried to make a good balance between the travel aspects and the technical stuff. Though many of you have kindly reported a general good technical quality for the articles, inevitable mistakes were made, and the readers feedback was also greatly appreciated. The New York steep descent mistake was the best example for this. If most of the IFR rules were carefully observed, I have also taken the advantage of the liberties that Flight simulation can offer. Flying offline, I have set various weather situations, choosing the weather for each destination, though keeping the climate of the several regions visited in mind. Setting thunderstorm activity at Dubai or clear skies in the middle of the Alaska winter would have been quite laughable. Flying during more than one year in the northern and southern hemispheres, we have even encountered winter conditions two times, in Anchorage and five months later in Ushuaia. There was also an alternation between day and night flights, sunsets and sunrises, though day flights were the most frequent. Other actions were slightly departing from the real world, proposing the very special Amsterdam–Sion–Geneve leg in the beginning of the series or flying ETOPS–180 with a brand new aircraft for example. Finally, we have, as usual, been able to enjoy both flightdeck and passenger views, since in flight simulation you can be both the pilot and the passenger of your aircraft: cabin crew announcements are even available, please check Flightsim.com File library if you don't have 'em yet! The inflight aircraft external views are an exclusivity of flight simulation as well, unless you have a spot plane in the real world. The map displayed above shows what the actual trip looked like, and slightly differs from the scheduled route that was introduced in Part 1. In fact, 18 destinations were cancelled during the project's unfolding, mainly through lack of time, but also with articles size in mind. Further stops were first scheduled in Europe, Australia, New Zealand, the United States, Central America, the Caribbean, South America and North Africa. My first round the world trip had only 11 destinations, we have though travelled to almost four times more places here. This project is the modest outcome of ten years of IFR flightsimming. I'm trying to recall my very first IFR flights with FS5.1, flying the first airliners available at that time (Flight Shop) to some European destinations with neither FMC nor MCDU but a basic 'VOR to VOR' navigation and analog panel gauges. The features described in this series, though only revealing a small part of the FS2004 expedients, were still belonging to 'science-fiction' not a so long time ago. BRUSSELS – LONDON – AMSTERDAM – SION – GENEVE – NICE – MADRID – MALAGA – IBIZA – AJACCIO – LAMEZIA TERME – ATHENS – TEL AVIV – TEHRAN – DUBAI – KATHMANDU – PHUKET – HONG KONG – SYDNEY – GUAM – ANCHORAGE – HONOLULU – TAHITI – LOS ANGELES – NEW YORK – TAMPA – MEXICO – ST MAARTEN – POINTE A PITRE – QUITO – USHUAIA – RIO DE JANEIRO – CAPE TOWN – LA REUNION – SEYCHELLES – KILIMANJARO – DAKAR – TENERIFE – PARIS – BRUSSELS ... what a nice trip. But we all know that travelling has a price that our home planet has to pay. If we disregard the electrical power that was needed to make my computer work, this virtual trip was rather environmentally friendly. But I've wondered what would have been the environmental impact of such a flight if it had actually taken place, considering the greenhouse effect gasses emissions. The result is not really funny. If Around the World 2006-2007 had been an actual event, 3062 tonnes of CO2* would have been sent into the atmosphere. This project's purpose is of course not to discuss the Global warming problem. Meanwhile, if all of this was only a simulation, it was obviously furthering aircraft and air travel. I could not serenely conclude this series without touching on this problem, since air transport does have something to do with it. Worldwide air traffic, including passengers and freight, releases hundreds of millions of tonnes of carbon dioxide into the atmosphere every year. In fact, current estimations report that air traffic is responsible for 3 % of the worldwide CO2 emissions, not considering here the other concerning emissions such as nitrogen oxides (NOx) and contrails. Despite the constant progress made on the engines and fuel efficiency, aircraft are still far more harmful to the environment than other means or transport such as boat or train. During a long haul flight, each passenger produces as much CO2 as if he/she was travelling by car on the same distance. Short haul flights are even more polluting. If we come back to the last leg of our trip, flying from Paris to Brussels with a wide body aircraft like the A330, even with a full load of passengers, is actually the very last thing to do! On such distances, the high speed train competes with the aircraft in terms of time and definitely in terms of CO2 emissions, this is therefore the only sensible choice in this case. If many oil alternatives for road transport such as biofuels already exist, finding a reliable replacement for the kerosene Jet-A1 and producing it in sufficient quantities is not a piece of cake. Many researches in that domain are currently carried out, including biofuels (but facing the huge needed crops surface problem), synthetic fuels or liquid hydrogen. If the two first options would only need minor changes to the existing engines, the latter would generate the design of completely new aircraft, and cause further security problems because of its tricky handling. Making the aircraft environmentally friendly is then another great technological challenge for the 21st century. In the meantime, air traffic will continue to increase an it is currently doubling every ten years. At this rate, the air transport part in the anthropogenic CO2 emissions could reach 25 % fifty years from now. This projection is however made in the worst IPCC emission scenario. In this rather gloomy context, is the future of durable air travel not simply and only... virtual ? Acknowledgments The first thanks go to you, the readers of this series who have faithfully followed this long story from the beginning to the end. Many of you have provided me with comments, remarks or questions and it was a pleasure for me to reply, and also learn more. Since the messages were coming from many different countries, I have also travelled in that way. Secondly, a major tribute has to be paid to the Flight Simulator add-ons developers. Without them, this feature would never have happened. Those high skilled people provide the flight simulation community with additional aircraft, sceneries, sounds or utilities that make Flight Simulator really something else than a game. Among them, the freeware add-ons developers deserve a special thought also. Seeing the high realism level that is nowadays demanded, they spend much time and energy to create high quality add-on software and distribute them on the web for free! The professional level of such works is sometimes incredible. The Canary Islands scenery that was visited in this last part is a very good example for this, but for sure there are many others. Quoting all the developers who have created the add-ons that were used in this round the world flight project would be too long here. With the respect that is due to the authors, they are however all listed in the Credits section for each article. Last but not least, I would like to thank our webmaster Nels Anderson warmly, for his kind cooperation throughout this long project (and its long articles), and more particularly for the precious assistance that was requested to obtain the permission to publish the copyrighted Jeppesen charts (appearing in Parts 1, 2 and 3). Credits The following flight simulation software was used to make this review: Main Microsoft Flight Simulator 2004 A Century of Flight (patched) AI Traffic add-on Ultimate Traffic by Flight1 Software Aircraft add-on A330/A340 Professional developed by Phoenix Simulation Software (PSS), distributed by Just Flight Project Open Sky Airbus A330-200 version 2 for FS2002/2004 Payware scenery add-on VFR Photographic Scenery East & South-East England developed by John Farrie (Visual Flight) and Getmapping PLC, distributed by Just Flight Switzerland Professional by Mailsoft - Flylogic Freeware scenery add-on Belgium 7000 (Belg7000) VFR scenery version 2.3 by Fred. Bridoux Belgium terrain mesh scenery by Jean-Gabriel Laurent Antwerpport scenery version 2 (add-on for Belg7000 enhancing Antwerp port and the Belgian coast) by Johan Thiers Brussels - National airport scenery version 3.2 (beta) by Robert Buysen Brussels - National AFCAD2 file for Robert Buysen's scenery by Thierry Caestecker Ostend airport scenery by Benoit Facon & Hans Vandale The Netherlands 2000 scenery version 2.91 by The Netherlands 2000 Design Team Genève - Cointrin airport scenery by Daniel Gauthier Utilities FSUIPC version 3.48 by Pete Dowson Active Camera 2004 version 2.0 by Guillaume Darier & Serge Baye Replacement runway black texture by V. Nauta Flight simulation, Real aviation, general information documents, websites and other references PSS A330/A340 Professional manual & tutorial JEPPESEN SID, STAR, Approach charts, Airport diagrams, High & Low altitude Enroute charts Approach charts reproduced here (SIMCharts by Jeppesen designed for use with FS2004), courtesy of Jeppesen Jeppesen SIMCharts legend & glossary Formation Pilote: Instruments de Bord (Th. du Puy de Goyne, A. Roumens & P. Lepourry), Cépaduès Editions, Toulouse, France Airbus official website www.airbus.com Airliners (W. Green & G. Swanborough), Bloomsbury Books, London, UK www.airliners.net Project Open Sky A330-200 aircraft repaint in Horizon Dreams livery and real photograph taken at Brussels - National by Cédric De Keyser Digital editing and fictional elements added to the photo by Cédric De Keyser Horizon Dreams fictional advert added on the photograph uses Microsoft Windows 2000/XP (FR) default background bitmaps "Dune" and "Tropiques" Around the World 2006 logo uses a reduction of the Earth model provided by Orbiter 2006 Space Flight Simulator by M. Schweiger Michelin road map of Switzerland (used for some geographical information in the third leg) Any comments about this first part or suggestions concerning the following ones are welcome. Cédric De Keyser Brussels, Belgium cdk@ngi.be
  7. Part 7: Visiting South America Hi everyone, and thank you for joining me again as we are gradually approaching the end of this virtual adventure. There are anyway still many legs more to come and beautiful places to visit, then just make yourself comfortable, relax and take a little hour of your time to share these further flights with me. But don't forget to fasten your seatbelt! We haven't experienced difficult landings or mountain flying since Part 3, but I'm glad to announce that those things are back! We'll first visit Quito in the Andes, as the 'roof' of Around the World 2006-2007; then fly a long range sector towards Ushuaia, the most southern town in the world, close to Cape Horn with the worst weather conditions encountered in this feature. Finally, we'll conclude this 7th part with a well deserved rest on Rio de Janeiro's beaches. This new article will also see the last Airbus systems to be introduced as we'll quickly focus on the Hydraulic, Pneumatic and Air conditioning–Pressurization systems. Leg 28: Pointe-à-Pitre, Guadeloupe (France) – Quito, Ecuador Quito is then the highest point to be visited in this journey. The city elevation is, on average, 2800 m (9200 ft), making it the second highest capital in the world after La Paz in Bolivia. Quito is located only 25 km south of the equator and is surrounded by eight volcanoes, among which one has continuing activity and is under constant monitoring. The Guagua Pichincha's latest big eruption occurred in 1660 when over 10 inches or 25 cm of ash covered the city. The latest eruption, though less devastating, was recorded in 1999 and caused significant disruption of activities including the closing of the international airport. When the latter is open, its approach is not that tricky and is easier than those we had experienced in Sion or Kathmandu earlier in this review. We cannot say about it so much of the takeoff as we shall soon see in the next leg. Horizon Dreams will kindly carry some extra cargo for Air France on this sector. The additional load was taken in mind in the fuel planning and TOW computing. Flight Plan From POINTE-A-PITRE/LE RAIZET (PTP/TFFR) to QUITO/MARISCAL SUCR INTL (UIO/SEQU) Alternate SEGU GUAYAQUIL TFFR11 TULEX3S TULEX UA550 QIT SEQU35 Distance 1442 nm (2668 km) A rather simple flight plan indeed, we'll remain on the same airway for the entire route. Our departure from Le Raizet is to be followed by a 180° turn towards Caracas in Venezuela, Bogota in Colombia as next, then Quito. There is no Standard Arrival published for the destination, the ILS approach to runway 35 will directly begin at Condorcocha VOR/DME (QIT), located north of the airport and city. Ready to push! Powerful take off... please enjoy, the next one will not really see that pitch! Already at 26000 ft, this shot reveals the typical shape of Guadeloupe, looking like a butterfly. Guadeloupe is actually made up of two distinct islands, Grande Terre (above) and Basse Terre (below), the latter housing the Soufrière active volcano. FAA approach chart (public domain) provided by www.fscharts.com DO NOT USE FOR REAL WORLD NAVIGATION To land on Quito Rwy 35, we'll first cross QIT VOR at 17000 ft, then fly downwind on the CAT C track until being 16 miles away, then turn back to final for localizer capture, descending to the final approach altitude of 12000 ft. Aircraft approach category is assigned following the aircraft approach speeds range and is used in calculating airspace and obstacle clearance during the approach procedure. Category C is ours with an initial approach speed range of 160/240 KIAS and a speed at runway threshold (VAT) range of 121/140 KIAS. VAT is based on 1.3 times stall speed (VSO) in the landing configuration at MLW. We have high terrain on both sides of the approach area, and in particular the 15900 ft peak of the Guagua Pichincha volcano, located west of the airport. Crossing QIT VOR, approach begins. Excellent weather and unlimited visibility! D16 QIT is reached, beginning the base leg for localizer capture. Quito is visible on the top of the picture. Quito airport was literally built the middle of the city. Current approach speed is 146 kts. A bit like Tehran, earlier visited in Around the world 2006-2007, the city is rising towards the mountain. But the mountain is a volcano in this case, nothing else than the active Guagua Pichincha itself! Leg 29: Quito, Ecuador – Ushuaia, Argentina If many destinations first scheduled in the birth of this project were unfortunately cancelled later, this new one was to be kept in every case. Ushuaia is an extreme location that is known as the southernmost town in the world. With 45600 residents, Ushuaia is the capital of the Tierra del Fuego province in Argentina and its seaport is the closest one to Antartica, making Ushuaia one of its possible gateways. The town has also given its name to a famous French television nature magazine. Flight Plan From QUITO/MARISCAL SUCRE INTL (UIO/SEQU) to USHUAIA INTL (MALVINAS ARGENTINAS) (USH/SAWH) Alternate SCCI PUNTA ARENAS SEQU35 DEP3 QIT UG426 LIM UL302 TOY UG551 MON UG550 NAS UW115 DARWN USU SAWH25 Distance 3440 nm (6364 km) But prior to going there, we have to make the machine get airborne from one of the highest airports in the world, introducing the most critical takeoff of this journey. With the rather heavy fuel load needed for the flight (46 tonnes exactly) and a Takeoff Weight of 201 tonnes (MTOW 230 T), a full takeoff (TOGA) with Packs OFF will be performed from runway 35. Packs are a device of the Air conditioning system, being itself fed by the Pneumatic system. The latter feeds the Hydraulic system for hydraulic reservoir pressurization. We will briefly focus on the 3 systems here, as the last Airbus systems to be introduced in this review. The Hydraulic system provides hydraulic pressure to operate major components such as flight controls, slats and flaps, landing gear, thrust reversers and cargo doors. The Airbus hydraulic system has three separate and independent systems : Blue, Yellow and Green, each system having its dedicated pumps and reservoir. On the A330, the Blue system is pressurized by a pump driven by Engine 1. The Yellow system is pressurized by a pump driven by Engine 2. The Green system is pressurized by two pumps respectively driven by each engine. A further pump driven by the ram air turbine supplies the Green system in an emergency. Each system has also manually controlled electric pumps that may run automatically in case of engine failure. Lower ECAM (SD) Hydraulics page after Engine 1 start. Engine 2 is not running yet, explaining the amber warning for the Yellow system. The Pneumatic system supplies air pressure for Air conditioning, engine start, wing anti-ice and hydraulic reservoir pressurization. High pressure air can be supplied by Engine bleed systems, APU bleed or external power if available on the ground. APU bleed (or external power) will usually be used for engine start while the engine bleed systems will feed the Air conditioning and other systems inflight while the APU is normally not running. Engine bleed air is bled from the engine's high pressure compressor (the N3 spool on the Rolls Royce engines powering our A330). Please refer to Part 3 for a more complete description of the jet engine. In fact, each spool (N3 in this case) has its own pressure stages for compressor and turbine : high (HP), intermediate (IP) and low (LP). Bleed air is normally taken on the IP stage of the high pressure compressor. If pressure and/or temperature is not adequate, air will be bled from a HP stage of the same compressor. Engine bleed air pressure is regulated by the engine bleed valve for each engine. The engine bleed valve closes during engine start or when APU bleed is ON. SD Bleed page, after engine start with APU bleed ON and engine bleed valves closed (left); inflight with APU OFF and engine bleed valves open and the air bled from the IP stage of the high pressure compressor (right). The Air conditioning system provides ventilation, humidity and temperature control for the cockpit and cabin. The two air conditioning packs are supplied by hot air from the pneumatic system. The conditioned air leaving the packs is then routed to a mixing unit where recirculated cabin air is added. During flight a ram air inlet can be opened to supply the mixing unit with ambient air if both packs fail or if smoke removal is necessary. When maximum efficiency is required from the engines in difficult takeoff configurations such as at MTOW, short runway and/or high airfields, takeoff will usually be planned with packs OFF. In that way, the Air conditioning system will not take air from the engines, ensuring optimum performance. Overhead's Air panel with Packs OFF Finally, the Pressurization system controls the cabin air pressure to maintain safe differential pressure (DP) between inside and outside the aircraft. The cabin pressure is represented by cabin altitude following the standard atmosphere laws. In that way, rate of change of cabin pressure is represented by cabin vertical speed. The cabin vertical speed is controlled by the outflow valve, which vents cabin air overboard. Two additional safety valves prevent excessive differential pressure, either positive or negative. Cabin pressurization is usually automatically controlled for each flight phase, but can also be manually controlled by changing the cabin vertical speed. SD Pressure page, seen after takeoff with Packs still OFF (left) and a bit later with the normal situation and Packs ON (right). Switching off the Packs is not sufficient though to ensure optimum takeoff performance. Also, maximum takeoff thrust is required and is provided by moving the thrust levers to the TOGA gate (that will not be a reduced thrust or FLEX takeoff then). In the meantime, thrust will be applied with parking and toe brakes set until the target TOGA thrust is reached, monitoring the engines EPR value on the upper ECAM. Flaps (and slats) are high-lift devices. When deploying, they increase the camber (by rotation) and surface (moving backwards in a translation) of the wing, creating more lift and reducing the aircraft stall speed, thus making it more effective at low speeds (during takeoff and landing). Lift is one of the two aerodynamic forces created by the wing when moving in the air; the other component is the drag that is against the motion and will also increase when flaps and slats are deployed. The aerodynamic resultant is one of the 3 forces undergone by the aircraft, the two others being the thrust (provided by the engines) and aircraft weight. For our present takeoff, flaps will be set to CONFIG 3, the highest flap setting available for takeoff on the A330. The takeoff rotation speed VR is 164 kts (303 km/h) for this particular departure from Quito. The takeoff speed will vary with aircraft takeoff weight (TOW), aircraft configuration (flaps and slats setting) as well as air density. The latter will be affected by airfield elevation and air temperature. The greater will be these two factors, the lower will be the density and the greater will be the takeoff speed. In the meantime, a headwind will reduce the ground speed needed for takeoff, as there is a greater flow of air over the wings. The rather cool temperature (7°C) of this morning in the Andes and a light headwind will not really help much and our takeoff run will be long... very long. We will rotate at the very end of the runway, making this takeoff the most thrilling one of Around the world 2006-2007! Let's see how the Before takeoff checklist is looking like this time: BEFORE TAKEOFF FLIGHT CONTROLS........................CHKD FLIGHT INSTRUMENTS.....................CHKD FLAP SETTING...........................CONFIG 3 CHKD TCAS...................................ON V1, VR, V2, FLEX TEMP..................157, 164, 164, TOGA CABIN CREW.............................ADVISED ENGINE START SELECTOR..................NORMAL PACKS..................................OFF ECAM TAKEOFF MEMO......................'TAKEOFF NO BLUE' After the takeoff we should immediately turn right to climb and get clear of terrain, then turn back towards QIT VOR once above the clouds and finally turn left to join the UG426 airway, first bound to Lima in Peru. Santiago de Chile will be next and we will finally fly over Punta Arenas prior to reaching Ushuaia, where the landing, I'm afraid, will not be picnic either. Here we go! This is the only time in this journey that we move the thrust levers to the TOGA gate for a full thrust takeoff. TOGA power set, but we're not moving! Parking and toe brakes will be released at EPR = 1.73 (current value is 1.56). We had to wait 30 seconds until the ECAM computed thrust limit was reached, and the engines stabilized at full power! Approaching the end of the 10236' (3120 m) runway, still 10 kts (18.5 km/h) below the takeoff speed, how do you feel? Liftoff! I would really have enjoyed a few more meters of concrete anyway. And the game is not over. We have to accelerate, climb and get clear of terrain. Left turn towards Ascazubi NDB (ZUI) on the Standard Departure 3. Approaching 11000 feet with a current climb rate of 1800 ft/min. Slats are still extended (CONFIG 1) and TOGA thrust still applied! Thrust reduction altitude was though reached a few seconds later. Now safe above the clouds (17000 feet), turning above Condorcocha VOR (QIT) and finally heading south towards destination. The departure is concluded and we fly over Quito for the last time, climbing to the cruise altitude (now @ 24500 feet). AFTER TAKEOFF/CLIMB LANDING GEAR....................UP FLAPS...........................RETRACTED PACKS...........................ON ALTIMETERS......................STD X-CHKD General view of the Overhead panel (seen here during the After take off/Climb checklist), as modeled by PSS. Not every switch is functional though. The VOR ILS DME approach to Ushuaia is rather easy if we do not take into account of the severe weather conditions encountered during our landing: a low cloud base, turbulence and a strong wind with 40 kts gusts and shear. Arriving from the west via DARWN waypoint (no STAR published here as well), we are supposed to fly over Ushuaia VOR, then proceed on the downwind leg until being 16 miles away from the DME, descending to 5100 feet and finally turn left for localizer capture. Please check that your seatbelt is securely fastened. Descending towards Ushuaia VOR – lucky to catch the lightning, but is that the sign of an eventful end of flight? Approaching the VOR. The altitude at which it should be crossed is normally given by ATC in the official procedure, but I let the autopilot managed vertical guidance (DES mode) decide it for me here. Note that despite a rather tight fuel safety margin planned at Quito because of the critical takeoff situation, we have now more than 13 tonnes of remaining fuel. A few minutes from now I'll really appreciate this comfortable extra fuel quantity in the tanks, it will be needed. At 16 nm from the DME and 5100 feet, turning back for localizer capture. Final leg, established at 11.7 nm from the DME. The airport should be behind this 'wall'. Clear skies, runway in sight! But this shot doesn't help a lot to reveal the severe windy conditions occurring now. Autoflight APPR mode still engaged, with both autopilots active. Ushuaia here we come. This is what I believe anyway. Autopilot off, manual landing. Not easy to keep the runway alignment but things don't seem to happen too bad. This time, this is definitely bad. MISSED APPROACH! Engaging the TOGA gate to provide full thrust for a go around. Outside view of my achievement. I was setting my heart on not recording such a fault during the entire journey, I'm afraid to say I didn't make it! Climbing away, gear up, retracting the flaps and initiating the missed approach track for a second attempt. Established once again, gear down and now playing my last card : if I miss a second time, I'll decide to divert to the alternate. Touchdown! The left main gear at least. Not the best landing for sure but a true landing though. Burning more rubber as the nose and right main gear hit the ground on their turn. Follow the arrow... vacating the runway to reach the very small Ushuaia apron. The difficult approach was well worth it. Ushuaia's electric sunset, in the middle of the southern winter. Leg 30: Ushuaia, Argentina – Rio de Janeiro, Brazil As promised, a peaceful leg will conclude the 7th part of this series. Back to sunny beaches with a 5 hours or so flight to Brazil's most famous – and contrasting city. Flight plan From USHUAIA INTL (MALVINAS ARGENTINAS) (USH/SAWH) to RIO DE JANEIRO/GALEAO ANTONIO CARLOS JOBIM INTL (GIG/SBGL) Alternate SBGR SAO PAULO SAWH25 USU5B GRA UT101 MDP UA310 CRR UA309 PAG UA308 BCO UA304 SCR SBGL10 Distance 2353 nm (4353 km) The USU5B standard departure from Ushuaia Rwy 25 will lead to Rio Grande VOR (GRA), we'll then hug the eastern coast of South America, passing Montevideo in Uruguay and Porto Alegre in Brazil. The approach will be a piece of cake this time and we will be directly inbound on the landing runway axis. The approach path, however, passes just between two mountains, respectively 3195 and 3363 feet high. That could be dangerous in low visibility conditions but will not give us much concern today. To make things even more easy, the initial approach speed and approach chart altitude constraints were entered in the MCDU, and we will let the autopilot deal with the descent profile while we'll enjoy the landscape. FAA Approach chart (public domain) provided by www.fscharts.com DO NOT USE FOR REAL WORLD NAVIGATION Inserting speed and altitude constraints for Santa Cruz VOR (SCR) on the MCDU Flight Plan page. The Nav Display in Plan mode (CSTR selected) seen once we've added a further 4000' constraint for NARA, following the information provided on the approach chart. The autopilot used in managed guidance mode will then fly the correct approach profile for us. The sun rises as we cross Rio Grande at 29000 feet. Note the white spot of another aircraft flying below. Approach begins at Santa Cruz VOR. We are at then thousand. Passing NARA @ four thousand. Here's one of the two mountains on the right. 7 miles more to go. Now at 3500'. One mile later, 3000 feet. Ipanema Beach is behind that further mountain. Short final for runway 10, concluding one of the easiest approaches in this journey. Crossing runway 15 with Rio de Janeiro downtown in the distance. Reaching the gate. Does anybody see a marshaller? This is the end of Around the world 2006-2007 seventh article. We have now only one part more to go. In Part 8, we'll first cross the Atlantic and make a few stops in Africa and the Indian Ocean. Then, we'll little by little head back towards Europe and conclude this round the world feature. A few last technical topics, such as ETOPS flights, will be introduced also. Cédric De Keyser Brussels, Belgium cdk@ngi.be
  8. Part 6: Visiting Central America And The Caribbean Welcome again for three further legs, three legs only but with enough new technical aspects and scenery opportunities to give this article the usual 'big size' of this project's standards. The flights that will be described here took place in the 2007 late spring/early summer period (June), almost one year then after the very first flight of this long journey. We're now ready to board the A330 again and say farewell to the United States, with the beautiful Tampa scenery that was last visited. We'll first pay a visit to the Mexico City megalopolis, then head towards the Caribbean. Far more destinations were first scheduled for this 6th part, many of them were unfortunately cancelled later. As you can see on the following map, we will directly 'jump' from Mexico to the Small Antilles, the arc of islands stretching east of the Caribbean Sea. But before that, I wish to come back for a few moments to the previous part of this project, if you agree to do so. First, some of you have reported missing images in the Part 5 article. They were all math formulas actually, those that were provided in Leg 22 where some further explanation was given about the flight instruments and the IRS system. The problem has been fixed since then, so you may open this previous part again and see all the equations displayed properly if you missed them when the article first went online. Secondly, most of you do probably remember the steep descent that took place while approaching New York JFK. We flew the LENDY5 Standard Arrival and 'dived' towards LGA VOR, located on La Guardia airport, prior to our landing on Kennedy's runway 13L. I reported in the article that LGA was to be crossed at 2000 feet, implying a very steep descent from the previous waypoint that was crossed at 19000' (FL190). This was a mistake. In fact, the 2000 feet altitude did appear on the STAR chart leg but was to be interpreted as the minimum altitude to be observed – the altitude that guarantees both ground obstacle clearance and adequate navaids reception, or MEA for Minimum Enroute Altitude – but NOT the altitude that should be flown. In the real world, ATC will never make the traffic bound to JFK level off at 2000' just above La Guardia airport as it will obviously conflict with its own arrivals and departures. Aircraft will usually be radar vectored before reaching LGA and far above 2000 feet. I wish to thank two of our readers, Dean Brown and Tony Vallilo, respectively real life air traffic controller, flight instructor and real life pilot (also familiar to Flightsim.com thanks to his several real flights reviews) for their kind advice and the correction they provided to me. The flight we made was physically possible, but was unrealistic if we consider the real world procedures in force in the New York area. Anyway, as a consolation, we enjoyed great (and low!) views of Manhattan, something that would probably not have happened if we had been higher. Steep ATC descent rates, however, could sometimes be actually encountered in real life operations. I had once the opportunity to fly from Rome FCO to Brussels on the cockpit jumpseat of a Virgin Express B737-300, in October 1998. On our arrival to Brussels, ATC cleared the aircraft to descent very late, so that we really 'dived' towards the destination. I remember the analog variometer needle being at full stroke, meaning a descent rate greater of equal to 6000 ft/min, which is the descent rate we (erroneously) observed while approaching New York in our virtual flight. So, after this necessary finalizing, let's come back to the trip now. Leg 25: Tampa, Florida, United States – Mexico City, Mexico Note: because of the many night screenshots that'll be displayed, this leg flight report will be best viewed in a dark room. We'll begin this sixth part with a night crossing of the Gulf of Mexico. Tampa will be left at dusk and Mexico will be reached some two and a half hours later. Takeoff is planned from runway 18R today, to be followed by a right turn towards the Gulf, flying above the Old Tampa Bay and Clearwater. Flight Plan From TAMPA INTL (TPA/KTPA) to MEXICO CITY/LIC BENITO JUAREZ INTL (MEX/MMMX) Alternate MMAA ACAPULCO KTPA18R TPA3.TPA CIGAR R875 MINOW A509 NUBEL R522 PAZ UJ102 PCA SLM SLM1 MMMX05R Distance 1101 nm (2036 km) Docked to Airside E at Tampa Intl. Prior to joining the flight deck again, let's first perform an external walkaround of the aircraft. In real world operations, the external walkaround is executed by the Captain (CPT) or First Officer (F/O) before each flight. This is a systematic way to walk around the machine and look for possible external damage encountered during the previous sector. Off course, not much surprise is to expected in our virtual world, but the 'Active Camera' add-on (see credits) provides us with the opportunity to simulate this, greatly enhancing the default view options so that every single part of the aircraft can be easily reached, as close as we want. First, we check the static cores (or ports), here on the left side of the fuselage, looking for possible dirt or obstructions. The static cores are sensors for the static pressure, a physical quantity that is used to measure altitude as well as other fundamental flight parameters. A more detailed explanation of this was introduced in Part 5. The nose wheel comes then, checking the tires as well as looking for possible oil leaks from the hydraulic system, feeding the brakes and shock absorber. The aircraft nose and radome (where the radar antenna is located) is checked, making sure that there are no bird impacts (1). The Pitot tube condition is checked as well (2). The Pitot tube is a device that measures the total pressure, another very important physical quantity used by the Air Data Computer to compute the true airspeed as we've also seen in Part 5. Here are the right (secondary) static cores, checked as well. On the aircraft underbelly, we check that nothing is obstructing the ram air inlets. They can supply the aircraft with ambient air in case of a failure occurring in the Electrical system (with the ram air turbine driving an emergency generator) or in the Air conditioning system, or supply additional air if cabin smoke removal is necessary. The wing leading edge and slats must be free of any kind of damage such as bird impacts. Here's the right engine (look at this beauty : as real as it gets) : further checking for damage or leaks... ... and close-up to the fan and engine inlet, which must be totally clean; checking for possible bird impacts or bird remains. Below the right wing: looking for possible hydraulic or fuel leaks, checking the ailerons... The right main gear: checking the brakes for possible leaks, checking the tires, the shock absorber position. Tail and APU exhaust: checking the elevators, rudder, still looking for damage or leaks. The underbelly's antennas are checked also. The engines' exhaust is checked in the same way as their inlet. A last external look before... ... joining the flight deck and getting prepared for the flight! The cockpit preparation, whom main operation consists of programming the Flight Management System, is made before each flight while the aircraft is still at the gate. The FMS is programmed through the MCDU (the nice keyboard that Boeing pilots call 'FMC'), the several stages of this sequence have already been deeply introduced in Around the world 2006-2007's previous parts. The new topic I'd like to introduce now are the checklists. Checklists are compulsory system checking procedures every pilot cannot get away from, which are provided for each phase of the flight. Every aircraft type has its own specific checklists. In the meantime, checklist procedures may slightly vary from one airline operator to another for the very same aircraft type. Usually, the Captain asks for one checklist. The First Officer then states the several checklist points, with the CPT answering 'checked' (CHKD), 'ON/OFF', etc. or giving a figure following the required answer for the checklist point. All the checklists will then be introduced for this short flight. As said in this project's introduction, these checklists were worked out considering real world ones. The checklists provided here are meanwhile not to be used in real world operations. Bold font will be used for the checkings that are actually simulated, while regular font will be used for the checkings that are only applicable to the real world, though given here for realism purposes. Blue will be used for the optional settings and the figures that would vary from one flight to another. After the checklists, each checklist point will be explained and illustrated, if necessary. A briefing is a verbal agreement made between the two pilots. There is one briefing that must be executed at least before take off (we'll do that here before engine start) and another one before beginning the approach. The briefing usually takes the following steps in mind : the pilot in command ('who' is flying the aircraft for takeoff or landing, either the CPT or F/O, and makes the takeoff or landing decisions), the take off runway, the aircraft configuration (takeoff power, flaps, anti-ice etc...), the route (SID, STAR, ...), the destination airfield facilities (runway lights and runway length, available taxiways to vacate the runway etc.) and, off course, the actions that would be engaged if any malfunction, failure or any other unforeseen event occurs. The CPT will usually make the briefing, and will conclude by asking the F/O : 'No questions ?'. If the F/O agrees and if everything is clear for him, he will answer 'No questions.' and the briefing is complete. So let's proceed with the departure briefing for today's flight, which is made just after obtaining the Clearance delivery from Tampa tower : CPT: My takeoff runway 18R, FLEX takeoff with Packs ON and Anti-ice OFF, Flaps CONFIG 1. Any malfunction before V1 I make the decision 'Stop or Go'. If we stop I monitor the brakes, speedbrakes and reverse and we'll stay on the runway. Any malfunction after V1, I fly, no actions below 400 feet excepts gear retraction, we climb straight ahead to 1700 feet FRA*, accelerate, retract the flaps and climb safe to at least 2000 feet, asking for radar vectors to runway 18R ILS for a return to Tampa with a normal weight landing. Now, if everything is normal, that will be a TAMPA THREE vector departure : immediate right turn on track two zero zero after take off (I'll ask for selected lateral guidance) and then we should be radar vectored to our first waypoint, climbing to the first altitude cleared by ATC, which is 12000 feet... * Flap Retraction Altitude F/O (checking the FCU altitude window, already tuned to the desired altitude): Set. CPT: ... with autoflight managed vertical guidance. Any questions? F/O: No questions. CPT: Okay, so we may proceed with the Before start checklist. BEFORE START COCKPIT PREP.....................................COMPLETE BRIEFING.........................................COMPLETE PAX SIGNS........................................ON (1) FUEL QTY.........................................26 420 KG CHKD (2) T/O DATA V BUGS..................................SET (3) ALTIMETERS.......................................QNH 29.21 X-CHKD (4) WINDOWS/DOORS....................................CLOSED (5) BEACON...........................................ON (6) THRUST LEVERS....................................IDLE (7) PARKING BRAKE....................................SET (8) Let's come back to these several checklist points: The passengers signs (NO SMOKING / SEAT BELTS) switches (1), located on the overhead panel, have 3 positions : ON, AUTO, OFF. Note that nowadays, smoking is forbidden on board at any time in almost every airliner in the world, the NO SMOKING sign should then always remain switched on. If switched to AUTO, the SEAT BELTS signs will illuminate automatically when slats are extended or landing gear is down. Here, we've switched them to ON, keeping direct control of that function. The SEAT BELTS signs must obviously be set to ON or AUTO before engine start. The fuel quantity (2) is read directly from the ECAM display once the tanks are filled in. Almost 26.4 tonnes of fuel are required for today's flight, a rather short leg for the A330 (fuel planning was sooner introduced in Part 4). Lower ECAM FUEL page, giving the detail of the fuel load. Only the wing tanks are filled in for this short flight. The total fuel quantity (Fuel On Board) is displayed on both Upper and Lower ECAMs, as we can see on the following image. The PSS Airbus Pro IFR panel, where we can check both ECAMs simultaneously (engines are not started yet, as well as the APU). The takeoff data V bugs (3) are supposed to be set on the standby analog anemometer (located between the Nav Display and the standby horizon as you can see on the image) following the V1, VR and V2 values. This was a very important step in the classic airliners that relied on analog gauges only. Nowadays, this must still be done on the standby instrument, considering the very unlikely failure of the electronic displays (the PFDs in this case). Off course, we cannot do that on our simulated panel, this is why this checklist point is not written in bold. The altimeter setting (4), provided by ATC as well as ATIS and deeply introduced in Part 5, is QNH 29.21 in Hg (989 hPa) for today. In the real cockpit, there are two altimeters (CPT + F/O), three if we add the standby one. They are then cross-checked in the real operation, while we have only one possible altimeter setting here (CPT), the standby altimeter knob being not functional. The cockpit windows and all aircraft doors (also including the hold and cargo doors) closing (5) is checked thanks to the Lower ECAM DOOR page. A door that is still opened would be displayed in red. The beacon (6) is the red exterior light flashing on the top of the fuselage and on the underbelly. The aircraft also has strobe lights, which are flashing white and are located on the wing tips as well as on the tail cone. The Nav lights are constant, there is a red one on the left wing tip and a green one on the right wing. The Nav and Logo lights (the latter is lighting up the tail logo) are only used at night, but the beacon must be switched on at any time. This is why it is included in the Before start checklist. The Overhead's Exterior lights panel, from which the landing lights are also activated. The thrust levers (7) must be on the IDLE (neutral) position. This is the obvious rule for any jet or turboprop aircraft before engine start. Finally, the parking brake (8) is checked as set. It could also be released for the pushback if the pushback action has been requested and is to be shortly engaged. The pedestal with the thrust levers (idle) and parking brake control (set). Now ready to leave Well, the sun is setting very quickly here... a fact that once surprised me the first time I visited Florida, arriving from the old continent. We're pretty close to the Ecuador and at 8:30 pm (0:30 GMT) it begins to get dark, while the extreme northern latitudes are now enjoying the midnight sun. At the end of my second (and latest up so far) visit to Florida, dating back to June 1998, I remember to have left Tampa Intl at sunset while huge thunderstorm clouds were gathering in the sky with sporadic showers. These circumstances provided an incredible light and atmosphere that I would never have imagined to be able to recreate in Flight Simulator almost 10 years later. This virtual departure from Tampa is then dedicated to that memory, with a further thought for my family living there. Passenger's feeling just before pushback. In Part 3, we have thoroughly reviewed the engine start sequence. So let's directly continue with the After start checklist, taking place after pushback and engine start and before requesting the taxi clearance from ATC. AFTER START ANTI-ICE...............................OFF (1) ECAM STATUS............................CHKD (2) PITCH TRIM.............................ZERO (3) RUDDER TRIM............................ZERO (3) GROUND EQUIPMENTS......................REMOVED GROUND CREW............................CLEAR Wing and engine anti-ice (1) is, not surprisingly, not requested for our departure in a warm Florida summer evening. In the ECAM status (2), we must check that everything is normal (no warning or caution messages) and that both engines are stable. Upper and Lower ECAM (E/WD and SD), the System Display here showing the secondary engine parameters. Pitch and rudder trims (3), which can respectively be adjusted thanks to the black and white 'discs' located on both sides of the thrust levers and the RUD TRIM knob on the pedestal (see above), are both set to zero. I usually leave the pitch trim to its default value. Because of the excellent flight dynamics of the POSKY A330 model, the 'Home' and 'End' keys (the pitch trim usual key assignment in Flight Simulator) are very rarely used during takeoff. The pitch trim setting is displayed on the Lower ECAM Flight controls page, as we will see shortly in the Before takeoff checklist. Ready to taxi. F/O: Tampa Ground, Horizon two zero zero six heavy, request taxi. ATC: Horizon 2006 heavy, taxi to and hold short runway one eight right by taxiways Alpha three and Whiskey. Contact Tampa Tower on one one nine decimal five when ready. Taxiing out while a Delta 767-300 is decelerating runway 18R. The Before takeoff checklist should be made before lining up on the departure runway. Usually, pilots will perform it in the leaving aircraft queue in a view to make their waiting less long. More seriously, here are the several points that must be reviewed: BEFORE TAKEOFF FLIGHT CONTROLS.....................CHKD (1) FLIGHT INSTRUMENTS..................CHKD FLAP SETTING........................CONFIG 1 CHKD (2) TCAS................................ON V1, VR, V2, FLEX TEMP...............150, 156, 157, FLEX 50 (3) CABIN CREW..........................ADVISED ENGINE START SELECTOR...............NORMAL PACKS...............................ON (4) ECAM TAKEOFF MEMO...................'TAKEOFF NO BLUE' (5) The flight controls (1) are the moving surfaces that are used to steer or slow down the aircraft once airborne. They include the ailerons, elevators, rudder and speedbrakes and are driven by the Hydraulic system, to be introduced in the next part of Around the world 2006-2007. Not a bad idea to check them before the flight anyway. To do this, Airbus provides a further easy-to-use interface available through the System Display F/CTL page. Pilots can check the control surface movements on the screen while operating the flight commands (sidesticks, rudder pedals and speedbrakes lever) since they cannot see the control surfaces from the flight deck. SD Flight controls page. Here, all the speedbrakes are extended and the rudder is in the 'full right' position, while the ailerons are currently left to their neutral position. Flaps (2) can be set to CONFIG 1, 2, or 3 for takeoff on the A330. The PSS MCDU defaults to CONFIG 1 in the Performance Take off page (introduced in Part 4). The flap setting for take off will depend on the takeoff weight (TOW), the available runway length and airfield elevation. Greater TOW, shorter runways and higher airfields will mean a higher flap setting as we'll also see later on this trip. Today, we're almost 50 tons below the MTOW and we've a long runway so the flaps are set to CONFIG 1, which is actually CONFIG 1+F (Slats + Flaps) as explained in Part 4 as well. The takeoff speeds and FLEX temperature for a derated take off (3) are reviewed also. Please refer to Part 4 for a fully detailed description of these. V1, VR and V2 will be manually entered in the MCDU following performance tables in the real aircraft while they are kindly computed by the software here. The two air conditioning packs (4) are fed by the Pneumatic system and supply conditioned air to the aircraft cockpit and cabin. We'll see that in more details in Part 7. We'll also see that in particular conditions, packs are sometimes switched off during take off, while we have the normal situation here with packs ON. Finally, here's another very smart Airbus feature. The takeoff memo (5) is a checklist in the checklist and contains several further items required prior to takeoff. It is automatically displayed in the Upper ECAM two minutes after the second engine start. Completed items are displayed in green while uncompleted items are shown in blue. Take off memo: auto brake must be set to maximum in case of an aborted take off (not completed), passengers signs must be ON (already checked in the Before start checklist), ground spoilers must be armed (also in case of an aborted take off), flaps are set to their takeoff config. The last item 'T.O CONFIG... TEST' requires a push of the T.O CONFIG button on ECAM control panel. That will simulate (this is then a simulation in the simulation here) application of takeoff power and generate appropriate warnings if something is not properly configured. The takeoff memo will disappear once takeoff power is set. When every item is completed, 'Takeoff no blue' can be enunciated to conclude the Before takeoff checklist and pilots just have to wait for the takeoff clearance. Holding point Rwy 18R. We'll get the takeoff clearance once this landing Southwest 737 has vacated the runway. Look at the sky... amazing if we think about the earlier versions of MSFS. Lining up for an immediate takeoff. CPT: I have controls ? F/O : You have controls. Photoreal scenery, almost real clouds... I'm not really in a hurry to try FSX by now... So long Tampa... note the BA 777 taxiing out for departure. Immediate right turn after takeoff. Tampa downtown in the distance. Climbing away above the Old Tampa Bay with the Courtney Campbell causeway below, heading towards Clearwater. Left and right passenger views as we cross the coast... ... and Clearwater Beach as a farewell to the Sunshine state... so long Florida! This departure story could not be concluded without a further FS2004 sunset! We're directly bound to Mexico now. AFTER TAKEOFF/CLIMB LANDING GEAR.................UP FLAPS........................RETRACTED PACKS........................ON ALTIMETERS...................STD X-CHKD (1) We see that the After take off/climb checklist is executed after the departure phase, when passing the transition altitude where the altimeters (1) must be set to the standard reference of 29.92 in Hg. However, when the transition altitude is rather high (the United States are precisely a good example for this with 18000 feet), the checklist can be made before and pilots will simply agree saying 'still QNH' instead of 'standard', assuming that STD will be set later once passing the transition altitude. The night crossing of the Gulf of Mexico was uneventful and there was not much to see excepts the darkness, so let's directly jump to the approach briefing to Mexico. Let's imagine that the First Officer will be the pilot in command now, and then plays the role of the Captain. This is very frequent in airline operation, in a view to strengthen the F/O's experience as well as the CPT – F/O team relationship. The approach briefing mostly consists of reviewing the standard arrival, approach charts and airport diagram for the destination. It usually takes place before reaching the top of descent point. F/O: Approach briefing to Mexico... that should be a LUCIA ONE standard arrival and we've already programmed it in the MCDU... CPT (accessing the MCDU F-PLAN page): ... checked. F/O: ... so we'll first cross Sierra Lima Mike VOR/DME at 16000 feet or otherwise instructed by ATC... then we proceed on track two five six towards RADEL until reading 12 miles from the DME (minimum safe enroute altitude 14000 feet), after that left turn on track one five six towards Sierra Mike Oscar VOR/ DME, which is expected to be crossed at 12000 feet. From there, we are likely to be radar vectored for runway zero five right ILS. Otherwise, we continue straight ahead on track one six zero (MEA 9700 feet) until localizer interception. Final approach altitude is 8800 feet. The ILS frequency one zero nine decimal one and localizer course zero five two are already set in the MCDU... CPT (checking the MCDU RADIO NAV page): ... checked. F/O: ... and we have two additional navaids, Mike Whiskey NDB on the runway axis... CPT: ... three seven zero... set. F/O: ... and Mike Echo Xray VOR/DME on the airport... CPT: ... one one five decimal six... already set also as VOR two. F/O: ... Runway zero five right is 3900 meters long, with a PAPI to the left and a Short Approach Light System, High Intensity Runway Lights, everything we need. We'll most probably vacate the runway by taxiway Echo or Foxtrot. In case of a missed approach : we climb on Mike Echo Xray VOR/DME radial zero four zero until DME six, then we turn left to intercept Sierra Lima Mike VOR radial one five eight to join Sierra Lima Mike holding pattern at 11000 feet and expect ATC instructions. Weather is pretty nice : clear skies, eight kilometers visibility and a light wind from the east. That should be an easy landing... any questions ? CPT: No questions. Descending. The STAR path that has just been reviewed and is programmed in the FMS clearly appears on the Nav Display. The huge orange spot in the distance is Mexico City built up area, where 20 million people live. APPROACH BRIEFING.......................COMPLETE ECAM STATUS....................CHKD ALTIMETERS.....................QNH 29.91 X-CHKD AUTO BRAKE.....................OFF (1) ILS/APP AIDS...................SET (2) MDA/DH.........................SET (3) SEAT BELTS.....................ON The Approach checklist is made 20-30 miles from the destination, when the expected arrival procedure and landing runway are confirmed. The autobrake (1) can be set to Low, Medium, Max or OFF for landing. Autobrake is an automatic system that I use very rarely in Flight Simulator, while it is usually used in airline operation. With autobrake active, pilots just have to monitor the thrust reverse to slow down the aircraft after touchdown. The ILS and approach aids frequencies (2) are set here through the MCDU RADIO NAV page. The ILS frequency and course are automatically set once a landing runway has been chosen for the arrival airport (for a more complete description of flight planning, please refer to Part 2). The decision height (DH) (3) is 284 feet for the ILS Rwy 05R. As we've seen during the Anchorage landing (Part 4), de decision height is read directly from the approach chart and is set through the MCDU Performance APPROACH page. At the decision height, 'MINIMUMS' will be automatically announced and the pilot in command will say 'Landing' if he decides to continue. Let's directly proceed with the Landing checklist, to be reviewed once established on final. LANDING CABIN CREW................. ADVISED AUTOTHRUST..................SPEED ECAM LANDING MEMO...........'LANDING NO BLUE' (1) The landing memo (1) is working similarly as the takeoff one and is automatically displayed prior to landing, below 1500 feet AGL with gear down. The required items are : landing gear down (nobody should contradict me with this), passengers signs ON, ground spoilers armed and flaps set to FULL or CONFIG 3, the two possible landing configurations on the A330. As usual, we've chosen the default flaps FULL configuration for this landing. The landing memo with two uncompleted items. 'Landing inhibit' on the right means that some ECAM messages are inhibited during landing. Arming the ground spoilers (Pedestal) will automatically deploy the speedbrakes at touchdown. Landing memo once completed Landing checklist completed, cleared to land, approaching the decision height. F/O: Landing! CPT: checked. Reaching the gate and engines shutdown. 'Aeropuerto Internacional de la Ciudad de Mexico' as a welcome message. SHUT DOWN BEACON.....................OFF FLAPS......................RETRACTED ECAM STATUS................CHKD PARKING BRAKE..............SET Leg 26: Mexico City, Mexico – St Maarten, Netherlands Antilles Here it comes! St Maarten is the world's most famous spot for planespotting. This is where the landing gear of arriving aircraft passes a few feet above the hats and sunshades of the Maho Beach's tourists. We'll see that FS2004 provides us with the opportunity to recreate that ambiance once again. Exceptionally, and for the very first time in these series, I decided to let the default FS2004 flight planner plot the route for me, simply specifying the departure and arrival airports and selecting the 'Hi altitude airways' option. I was fairly satisfied with the result. I printed the flight plan and here's how it looks in the standard format used up so far (with a standard departure added from the origin) : From MEXICO CITY/LIC BENITO JUAREZ INTL (MEX/MMMX) to ST MAARTEN (PHILIPSBURG)/PRINCESS JULIANA INTL (SXM/TNCM) Alternate TFFR POINTE-A-PITRE MMMX05L APN3A APN UJ30 NAU UTZ MID UJ9 CZM UR640 SIA UW6 BENET UG633 CDO UB520 ANTEX B892 MAZ JOSHE COY R760 GOUDA TNCM09 Distance 2078 nm (3844 km) The flight path will include Merida, Cozumel, Grand Cayman; Montego Bay in Jamaica, the south of Haiti and the Dominican Republic, San Juan and finally St Thomas. As a more singular waypoint, we'll also pass near the Chicxulub place in the Mexican peninsula of Yucatan. Next to Merida, this is the well known location that is said to have been the scene of an asteroid impact that might have triggered the dinosaurs' end some 65 million years ago. But let's not dwell on these – though very interesting – palaeontology matters right now and go back to the flight for an immediate takeoff. Airborne after a rather long takeoff run (Mexico airport elevation is 7316 feet above sea level). Smog is also topical at Mexico, mostly because of road traffic, making the town one of the most polluted in the world. The mountains that surround the built up area create a basin where the pollutants remain and are not easily evacuated. Passing abeam Chicxulub, north of Merida. Don't look for a circular shape, even in the real world : the Chicxulub Crater, which is estimated being from 140 to 200 kilometers wide, is buried under a one kilometer thick layer of sediments. The Earth and time have erased the traces of the disastrous event that occurred here a very long time ago. Grand Cayman (FS2004 default scenery) The only approach available for Princess Juliana Intl is the VOR DME Rwy 09. With the almost constant good weather prevailing here, ILS facilities are not much required anyway. Though the airport can accomodate wide bodies up to the B747-400 (and what about the A380 ?), the runway is very short, only 2180 m (7152'). This is why, if not being a big problem for arriving aircraft, leaving wide body aircraft cannot take off with a full fuel load needed for example for a transatlantic flight. KLM and Air France, both serving St Maarten, then make a further stop in the Caribbean prior to flying back to Europe. End of descent, St Maarten island is straight ahead. Last correction before being established. Well, this is a non-precision approach: no localizer, no glideslope! (ND set to VOR mode) Autopilot is disengaged, autothrust: SPEED; landing gear already down and locked. CPT: Flaps full! F/O: Speed check... flaps full. Touchdown in paradise in less than 10 seconds! Maho Beach here we are! Not an easy landing though. Because of the short runway, we must not be too high in a way not to miss the touchdown zone. Being too low could be a serious threat for the people on the beach. Anyway they're here for the show and duly warned: 'LOW FLYING AND DEPARTING AIRCRAFT BLAST CAN CAUSE PHYSICAL INJURY'. We've a light crosswind in the meantime. Also with a special tribute to this beautiful free add-on scenery. First, here's the swimmer's impression as we hit the beach... The same moment captured by a beach spotter In the shadow of the monster... I'm trying to imagine what feeling would generate an A380 landing here, if it does ever happen. Flight Simulator at its best!!! I'm sure that they don't have any sexy girls in the real flight simulators used in airline training... Braking action. Thrust reverse is usually cancelled below 60 kts. We had a nice touchdown but we were too much to the right. Anyway we don't seem to have caught some beach umbrellas or other unusual objects. A successful landing then! Using the first turning pad to backtrack the runway... note that the nose wheel is almost perpendicular to the aircraft. Leg 27: St Maarten, Netherlands Antilles – Pointe-à-Pitre, Guadeloupe (France) The shortest leg of Around The World 2006-2007 will conclude this 6th part. Guadeloupe is a small butterfly-shaped island belonging to France. Le Raizet airport can accomodate any aircraft type and offers a 3505 m (11499') long runway with an ILS. We don't have to worry much about the landing this time then. Flight Plan From ST MAARTEN (PHILIPSBURG)/PRINCESS JULIANA INTL (SXM/TNCM) to POINTE-A-PITRE/LE RAIZET (PTP/TFFR) Alternate TFFF FORT DE FRANCE TNCM09 TIKAL A517 BIMBO BIMBO3K TFFR11 Distance 148 nm (274 km) Flight time 0:40 Despite the fact that there is high terrain ahead runway 09, which is commonly used for takeoffs at St Maarten, it seems that no official SID is published for that airport. Considering the missed approach procedure as well as real flight videos available on the web, ATC should always vector the aircraft southwards immediately after takeoff. In that way, aircraft will turn right to a 160° heading, climb and get clear of terrain. For our flight today, we'll even keep that heading since this is the track towards our first waypoint. Only 8.8 tonnes of fuel are required for this very short flight. A FLEX takeoff with flaps at CONFIG 2 is planned from runway 09. Here's how the Before takeoff checklist is looking like this time : BEFORE TAKEOFF FLIGHT CONTROLS.........................CHKD FLIGHT INSTRUMENTS......................CHKD FLAP SETTING............................CONFIG 2 CHKD TCAS....................................ON V1, VR, V2, FLEX TEMP...................144, 150, 152, FLEX 35 CABIN CREW..............................ADVISED ENGINE START SELECTOR...................NORMAL PACKS...................................ON ECAM TAKEOFF MEMO.......................'TAKEOFF NO BLUE' Immediate right turn after take off. We've a very low gross weight and therefore a current very steep climb rate of 4800 ft/min Already at 3000 feet with the airport still visible. Already also above the S (slat retraction) speed of 172 kts, flaps are then set to UP. Proceeding to TIKAL with a last very nice view of St Maarten island (note the two big cruise ships on the right). Localizer capture at Pointe-à-Pitre. I was a bit lazy this time and let the autopilot do the job. CPT: Gear down! F/O: Speed check... gear down. This was though a manual landing. Pointe-à-Pitre, Pôle Caraïbes new terminal apron, as real as it gets. We'll rest here for a while before continuing our journey towards South America. Cédric De Keyser Brussels, Belgium cdk@ngi.be
  9. Part 5: Visiting North America Hi everyone, and for those among you who are joining us for the first time, we're flying the A330-200 aircraft (Project Open Sky model and PSS Airbus Pro 2D panel & avionics), following an easternly direction across the globe and visiting various FS2004 sceneries - mainly provided as add-ons - as well as focusing on some technical aspects of our flight. We've already visited Europe, Middle East, Asia, Australia and Pacific and are now almost half the way of the entire trip, at the antipodes of Brussels, Belgium, where the journey began and will finish. Tahiti in French Polynesia was the last Pacific destination visited, and this is where our aircraft is awaiting its next sector. In this part, three destinations in North America will be visited, and they are all located in the United States. Further technical topics will also be introduced, mainly in the first leg of this article. So ladies and gentlemen, fasten your virtual seatbelts once again and enjoy your virtual flights! Leg 22: Papeete, Tahiti, French Polynesia - Los Angeles, California, United States This route is very frequent with commercial carriers linking French Polynesia with the mother country: aircraft make a technical stop in Los Angeles before going further to Paris, with a total flight time of almost 20 hours. The Tahiti - Los Angeles route doesn't provide many diversion airports along the way : once leaving French Polynesia, no more dry land is to be seen until hitting the American coast. This is why this route will usually be operated by four-engined aircraft such as A340 or B747 in the real world, while twin-engined aircraft like the one we are flying will need a special ETOPS (Extended Twin engine Operations) approval to operate across the Pacific. This PPT-LAX flight, as well as the Anchorage-Honolulu leg that took place in Part 4, can be made with an ETOPS-180 minutes approval. We'll go deeply into the extended twin operations in the last part of Around the world 2006-2007, when we'll cross the Atlantic ocean. Our destination, Los Angeles Intl, is one of the busiest airports in the world and the third in the United States (considering the yearly number of passengers) after Chicago-O'Hare and Atlanta. That will be a good opportunity to introduce the TCAS system and see how it overall works. But before this, we'll first focus on the altimeter instrument and altimeter setting, another important point for any flying machine. Finally, headwind conditions set above the North-eastern Pacific in the last part of the flight will give us the right time to examine the aircraft speeds and see the difference between indicated airspeed, true airspeed and ground speed, and how they are measured and calculated by the aircraft systems. In the meantime, the IRS navigation system will be introduced. A few mechanics laws and some mathematical formulas will be needed then, making this article looking more serious than it is actually. Flight Plan From TAHITI-FAAA (PPT/NTAA) to LOS ANGELES INTL (LAX/KLAX) Alternate KSFO SAN FRANCISCO INTL NTAA04 EMIRI1C EMIRI ORARE G575 FICKY FICKY.LEENA3 KLAX25L Distance 3637 nm (6728 km) Flight time 7:50 Ready for pushback on Faaa airport main apron. Another good airport scenery add-on, which made me remember the breathtaking and ahead of its time 'Tahiti Scenery' released by Wilco Publishing ten years ago, for Flight Simulator 98. Prior to contacting the tower to obtain their IFR clearance, pilots usually listen to the ATIS provided for the departure airport. ATIS (Automatic Terminal Information Service) is a continuous broadcast of recorded information including Greenwich Mean Time (GMT, also known as 'Zulu'), weather, active runway(s), available approaches and other NOTAMs (Notices to airmen). The ATIS message is updated where any significant change occurs in the information, such as weather and active runway(s). A letter designation at the beginning of the message progresses down the alphabet each time the message is updated and starts at 'Alpha' each day. Here's what Tahiti ATIS said: TAHITI AIRPORT INFORMATION QUEBEC - 17:00 ZULU - WIND: 216 AT 5 - VISIBILITY: GREATER THAN 20 MILES - SKY CONDITIONS: FEW CLOUDS AT 4300' - TEMPERATURE 26 - DEW POINT 25 - ALTIMETER 29.21 - ILS RUNWAY 4 IN USE - LANDING AND DEPARTING RUNWAY 4 - VFR AIRCRAFT SAY DIRECTION OF FLIGHT - ALL AIRCRAFT READ BACK HOLD SHORT INSTRUCTIONS - INFORM CONTROL ON INITIAL CONTACT YOU HAVE QUEBEC The interesting piece of information on which we'll focus now is the altimeter setting. Since the birth of aviation, the altimeter principle of operation has remained the same (this is also valid for the other fundamental instruments, including the artificial horizon, anemometer, variometer and magnetic compass). Since the atmospheric pressure decreases with altitude, this physical quantity has been chosen to calculate aircraft altitude. The altimeter is then basically a barometer which measures a pressure called the static pressure. The static pressure (noted Ps) is the air pressure that is independent of aircraft airspeed and must then be measured with a nil airflow speed. This is schematically done by the following very simple device: STATIC PRESSURE PORT In fact, the altimeter will give the difference (or the distance) between this measured pressure (Ps) and a reference pressure (noted PO), which is chosen by the pilot using an adjustment knob. The altimeter will 'calculate' the altitude difference corresponding to the (PO - Ps) value, using the standard atmosphere laws. The standard atmosphere model provides pressure and temperature as mathematical functions of the altitude, with pressure and temperature at sea level respectively assigned to 1013.25 hPa (hecto Pascals) or 29.92 in Hg (inches of mercury) and +15°C. The classic analog altimeter, nowadays often only used as a standby instrument, has a complex mechanical system transmitting the pressure difference to the needles moving around an altitude scale graduated in feet. The reference pressure choice is nothing else than the altimeter setting. Increasing the reference pressure will increase indicated altitude, and inversely. We do not need to be a weather expert to know that the atmospheric pressure often vary throughout the day and from one day to another. In that way, if the pilot wants to know his height above ground level, PO must be set to the current atmospheric pressure existing on the ground. This pressure is called QFE. To know his altitude above sea level, PO must be set to the atmospheric pressure existing at sea level (zero altitude). This pressure is called QNH. QNH is the reference pressure used around airports and is provided by the airport meteorological service. Pilots are informed of the current QNH by ATC as well as ATIS. In our case, is we come back to the ATIS message, the QNH is 29.21 in Hg. This is what we set in the altimeter setting window located on the EFIS panel. In the meantime, the altimeter setting will also appear on the PFD. As we see, the altimeter setting knob also provides the hPa unit, preferably used by the metric system. This 29.21 value (which is equivalent to 989 hPa) is actually very low and is associated with the 'Building storms' weather theme that was chosen for the first part of our flight. If the altimeter is set to the local pressure conditions while approaching or leaving one airport, it would be hazardous for ATC and airline pilots to update the altimeter setting following the various weather conditions encountered all along the flight. This is why, above a given altitude called the transition altitude, every aircraft must use the same altimeter setting, called the standard (STD) setting with reference pressure equal to 29.92 in Hg. Above the transition altitude, which vary from one country to another, but it is most of cases far below the cruise altitude, aircraft altitudes are renamed as flight levels (FL), in hundreds of feet. Flying at FL350 will mean at 35000 feet with standard altimeter setting. ATC will distribute aircraft among various flight levels and then maintain vertical separation among them. The usual vertical separation is fixed to 2000 feet between FL290 to FL410, but can be reduced to 1000 feet in RVSM (Reduced Vertical Separation Minima) airspace, therefore increasing the number of aircraft that can fly safely in a particular volume of the sky. RVSM is currently implemented in much of Europe, North Africa, Southeast Asia and North America, as well as over the North Atlantic and Pacific oceans. Specially certified altimeters and autopilots are required to fly in RVSM airspace, this is anyway the case for most of airliners. During climb, once leaving the transition altitude, which is 9000 feet in Tahiti controlled airspace, the QNH setting will be boxed and will flash on the PFD, advising the pilot to pull the altimeter setting knob for standard reference. 'STD' will then appear in the altimeter setting window as well as on the PFD. Once flying below the transition altitude during descent (that will be 18000 feet for the U.S.), 'STD' will flash on the PFD and pushing the knob will revert to QNH. Turning the knob will select the new QNH setting told by ATC. Passing the transition altitude (9000') during climb: pushing the altimeter setting knob for standard reference (29.92 in Hg) The variometer (which measures vertical speed) principle of operation is similar to the altimeter's, but without reference pressure needed. In this case, the variometer measures the static pressure variation by unit of time (PS2 - Ps1) / (t2 - t1) and converts it to vertical speed in feets per minute. Rangiora atoll, located 192 nautical miles North of Tahiti, stretching on 70 km (43 miles) from West to East, is the biggest atoll in Polynesia, and the second by size in the world. Such islands, which were once active volcanoes, are now threatened by global sea level rise. This outside view reveals one of the two passes of Rangiora, where the lagoon is connected to the Pacific waters. Rangiora VOR/DME is the last ground navaid that the flight path crosses before hitting the US coast, some 3450 nautical miles away. To perform accurate navigation on such oceanic flights, aircraft can only rely on their own navigation equipment. In the meantime, the aircraft goes beyond radar coverage for Air Traffic Control and must then, like in the cross-Atlantic operations, make regular position reports to the appropriate oceanic center located on dry land. In our case, that would be Tahiti Oceanic in the first part of the flight, up to N03° 30' latitude (just above the Equator), then Oakland (San Francisco) Oceanic for the remaining leg. Flying offline with FS2004 default ATC doesn't provide any oceanic operations modeling, so we won't go further into these special procedures here. The aircraft navigation system, for its part, is for sure modeled. Though the GPS satellite positioning system is now more and more used worldwide, the IRS is still the main navigation system used by airliners, since it is totally independent of the outside world. The IRS (Inertial Reference System) purpose is to provide the necessary information needed for navigation, including aircraft position (latitude, longitude), ground speed, true heading, ground track and drift angle. The IRS is a dead reckoning system, where estimating of current position is based upon a previously determined position and measured velocity or acceleration, time, heading and the effect of wind, as we'll see below. There are usually three IRS systems installed on airliners, so that if one of them is 'derivating', its influence on the mixed IRS position will be lowered. In each IRS system there is an inertia station which consists of a platform and is horizontally maintained thanks to three gyroscopes Gx, Gy, Gz. Gyroscopes, which are basically made up of a high speed rotating disc, have the property to keep the 'memory' of an initial direction, whatever the external stresses to which they are subjected. This is why the artificial horizon also works with a gyroscope, the initial direction being the earth's vertical in this case. But let's close the brackets and come back to the point. To go further we have to introduce the aircraft trihedron which is a 3-D referential attached to the aircraft, with the roll axis (X), pitch axis (Y) and yaw axis (Z). On the inertia station platform two accelerometers are installed. The first one measures the aircraft acceleration on the aircraft X axis (Ax) and the second one on the Y axis (Ay). Since the platform is horizontal, the accelerations are measured in the horizontal plane. Fundamentals of analytic mechanics tell us that meaning that if we integrate two times the aircraft accelerations following X and Y we will calculate the aircraft's new position in the horizontal plane. Meanwhile, the aircraft is moving on the Earth's surface, which is a sphere and not a plane. The IRS' navigation calculator must then convert the measured accelerations in the aircraft's trihedron to the Earth's trihedron. The latter is defined thanks to the Earth's center, the True North, the local vertical (connecting the plane with Earth's center) and the local horizontal (which is perpendicular to the local vertical). The calculator will perform orthodromic navigation, meaning that the shortest or great circle routes will be computed, and send its signals to the Flight Management System. The aircraft's initial position (POS init) must be known by the calculator: this is why the IRS alignment is made before the flight. Pilots will enter the aircraft's parking position on the MCDU INIT Page according to the airport diagram. As we've seen in Part 2, the initial position latitude and longitude fields are kindly automatically filled by PSS. The initial conditions needed to solve the kinematic equations also include the initial speed of the aircraft, which is of course zero. Nowadays, IRS may also be (re-)aligned inflight, thanks to the 'GPS Align in Motion' system, using GPS real time information and providing as much accuracy as classic stationary align procedures. The IRS navigation accuracy currently provides a less than 2 nautical miles error for a one hour flight time. Left: to align the IRS before the flight, virtual pilots just have to press LSK 3R since the parking position (LAT, LONG) of the aircraft is automatically filled. Right: the POSITION MONITOR Page seen during flight, where the average position calculated by the 3 IRS is displayed on the MIX IRS row. In real life, pilots will refer to this page to make position reports during oceanic flights. The IRS calculates the ground speed (GS) by integrating measured accelerations. The result is a vector (defined by a magnitude and a direction) whom magnitude will be displayed on the Nav Display (for example, 500 kts). Ground speed is the speed of the aircraft relative to the ground. True airspeed (TAS) is the speed of the aircraft relative to the air in which it flies, the physical speed of the aircraft relative to the moving air mass. It is sometimes named aircraft velocity. In still air conditions (zero wind) and horizontal flight, it is equal to the ground speed. During windy conditions, which occur in most of times, a headwind subtracts from the ground speed (TAS > GS), while a tailwind makes ground speed greater: GS > TAS. Winds blowing from other angles to the aircraft heading will have a headwind or tailwind component, as well as a crosswind component, perpendicular to the aircraft. Headwind is favourable in takeoff and landing but occurring during cruise, it will increase flight time as well as fuel burn. Ground speed and true airspeed vectors are linked by the following relationship: where is the wind speed vector. Considering those vectors as forces, the ground speed is then the resultant of aircraft velocity and wind force. In this diagram, known as the wind triangle, the wind is blowing from the sector ahead of the aircraft, there is then a headwind component that makes ground speed lower than true airspeed. The diagram considers the horizontal flight condition (parallel to the ground) and neglects updrafts and downdrafts winds, which occur perpendicular to the ground. True airspeed direction, which is the true heading, is also calculated by the IRS thanks to the gyroscopes of the inertia station, which can detect the yaw angular variations. True airspeed magnitude computation is a direct application of aerodynamics' laws. First, the Mach number is calculated. Mach number (M) is defined as the ratio between the true airspeed and the speed of sound. We just have: where 'a' is the speed of sound in the air around the aircraft. It has been demonstrated that M is a function of the differential pressure and the static pressure: The differential pressure (PT - PS) is the difference between the total pressure and the static pressure. We've already introduced the static pressure (PS) which is independent of aircraft speed. The total pressure (PT), also known as impact pressure, is the air pressure measured in the direction of airflow, and therefore depends on aircraft true airspeed. Total pressure is measured by the Pitot tube device, which is mounted facing forward. If we come back to the Mach number definition, we see that the true airspeed is simply obtained following TAS = M x a, meaning that if we know the speed of sound at current altitude, the problem is solved. Mother Aerodynamics has also demonstrated that the speed of sound in the air only depends on the air static temperature following (with a in knots and TS in Kelvins). Static air temperature (TS or SAT) is the still air temperature in the vicinity of the aircraft. Unfortunately, it is impossible to measure the static temperature of a fluid in motion. This is then the total air temperature (TT or TAT), or impact temperature that is measured thanks to a temperature probe similar to the Pitot tube. The total air temperature expresses that the air is compressed with an increase in temperature, therefore it will always be greater than static temperature during flight. Hopefully, Mother Aerodynamics (repeat) provides us with a further formula giving the static temperature as a function of the total temperature and Mach number: That's great, guys, we should make it to L.A.! The Air Data Computer (ADC) that inputs PT, PS and TT, will compute the true airspeed. The coupling IRS-ADC is named ADIRS (Air Data Inertial Reference System). With the ground speed and true airspeed vectors known, the wind magnitude and direction can be directly computed, if we simply subtract the true airspeed from the ground speed, the vectorial relationship displayed above becoming As we've seen, because of the wind force, the direction of movement of the aircraft, or ground track, is not the same as the aircraft true heading, simply defined as the direction with which the aircraft longitudinal axis is aligned and referenced to the True North direction. Therefore, the pilot must adjust heading to compensate from the wind in order to follow the desired ground track. In light private aircraft, the pilot will manually calculate the headings for each leg of the trip, using the reported wind directions and speeds supplied by the meteorological forecasts. On a modern glass cockpit airliner, the navigation calculator will do the job and compute the wind correction angle in real time. Ground speed, true airspeed, wind magnitude and direction are displayed top-left of the Nav Display. Unless the pilot switches on 'TRUE NORTH REF' (not modeled by PSS), which may for example be needed on the high latitude polar routes, the ND will actually not show the aircraft true heading but the heading referenced to the magnetic North, which will vary from True North according to the local magnetic declination. Finally, the indicated airspeed (IAS) is read from the airspeed indicator of the aircraft, located left of the Primary Flight Display in a glass cockpit and showing speed in knots (kts) i.e. nautical miles per hour. IAS (often noted KIAS with reference to the knots unit) is directly deduced from the differential pressure (PT - PS). It is the solution of Bernoulli's equation applicable to a perfect, compressible gas in a subsonic flow. Having the opportunity to play with my 'MathType' editor for the last time, here's the monster: where aO and PO constants are respectively the speed of sound (around 661 kts) and static air pressure (29.92 in Hg) at sea level. This formula is though showing us that the anemometer, which measures IAS, is calibrated to the standard sea level conditions. That means that at sea level and standard pressure, the indicated airspeed will be equal to true airspeed while it will differ from it at air densities other than the standard air density (which is equal to 1). Air density decreases with altitude, temperature and is also affected by moisture content. Indicated airspeed, however, is the reference speed in aircraft operation, as we have also seen in the previous legs: the aircraft take off speeds, approach speeds, structural limiting speeds and stalling speeds, collected as V speeds, are dependent of indicated airspeed, irrespective of true airspeed. Also, speed limits, that they are imposed by ATC or appear on the approach charts, are also related to IAS. We'll conclude this rather long theoretic presentation with an ironical, but rather sad remark: the science and equations that have been applied to aviation and made it become true were mainly established by men of genius who died tens of years, or even centuries before the first aircraft officially took the air. Close-up to the various quantities that we've introduced, displayed on the PFD, ND and Lower ECAM (here put at the normal Upper ECAM location), as we're concluding our Pacific crossing. We simply read: Indicated airspeed: 267 kts ; Mach number: 0.82; Ground speed: 415 kts, True airspeed: 469 kts; Wind @ 53 kts blowing from the 44° sector, with a predominant headwind component which subtracts from the groundspeed; Total air temperature: -27 °C and Static air temperature: -57 °C, the ambient temperature actually at our current altitude of 38000 feet (11400 m). Our approach to Los Angeles Intl is made via the LEENA3 standard arrival with the FICKY transition, a waypoint still located offshore some 260 nautical miles away from the airport. This is the longest standard arrival path I know up so far. The STAR is leading to the Seal Beach VOR, from which radar vectoring is expected for localizer capture. We'll land on runway 25L, one of the four parallel runways provided by the airport. About to make our first contact with the United States @ 4500 feet Still at 4500 feet, now approaching Seal Beach on the last leg of the standard arrival Federal Aviation Administration approach chart (public domain) Reduced for illustrative purposes - DO NOT USE FOR REAL WORLD NAVIGATION ILS approach to Los Angeles, showing the four runway system with simultaneous approaches authorized on both the northern (either 24R or 24L) and southern (25L or 25R) runways. Traffic configuration during our flight was: landings on 25L and 24R, takeoffs from 25R and 24L, probably the most usual situation here considering airfield situation and runway lengths. Arriving from Seal Beach VOR, we'll intercept the localizer at HUNDA intersection, thus having a shorter final leg than other approaching aircraft arriving from the East. This Nav Display shot taken after crossing Seal Beach VOR (SLI) during approach is a perfect opportunity to quickly introduce the TCAS equipment of our aircraft. TCAS (Traffic Collision Avoidance System) is operating independently of ground-based equipment as well as Air Traffic Control and is conceived to enhance air safety by acting as a 'last resort' method of preventing mid-air collisions that may have escaped ATC vigilance. The TCAS-equipped aircraft monitors other aircraft in its vicinity and assesses the risk of collision by interrogating their own transponders. Therefore, non-transponding aircraft will not be detected. With TCAS active, traffic is displayed on the ND up to 40 nm distance and within 2700 feet vertically. Other aircraft will be represented by a white diamond with relative altitude to own ship, in hundreds or feet. If contact aircraft is climbing or descending, an arrow is added beside the symbol to indicate this. For example, the contact seen in the added yellow circle is currently some 25 miles away, 2000 feet above our aircraft and is still climbing. The array of aligned aircraft seen on the right are already established on final. Distance to an intruder aircraft associated with a collision threat is based on time-to-go, rather than distance-to-go. In that way, a 40 seconds time-to-go before a possible collision with an intruder aircraft will trigger a Traffic Advisory (TA). In this case, the TCAS is calculating a risk of collision, but the encounter could resolve itself. An aural message 'Traffic, Traffic' is enunciated, advising the pilots to closely monitor nearby traffic. If the time-to-go goes below 25 seconds, a Resolution Advisory (RA) will demand avoidance manoeuvres in the vertical plane: 'Climb, Climb' or 'Descent, Descent'. Unfortunately, traffic advisories are not modeled by the PSS software (remember the 80% of the real functions modeling...). The TCAS switch (providing Standby, TA only or TA & RA settings) is located on the pedestal, close to the transponder panel. Proximate intruders will be indicated by a white filled diamond, TA intruders by an amber dot and RA intruders by a red square. No intruders were reported during our approach to L.A., but perhaps it will happen in a following leg. In fact, MSFS default ATC and AI traffic engine are rather well done but their reliability is several orders of size below the real world security level, this is why TA and RA situations actually often happen: we'll see the explanation of the 'miracle' occuring while approaching LAX below... Localizer capture The same moment seen from the flight deck, with downtown Los Angeles straight ahead. Looking closer to the Nav Display, we see that most of approaching aircraft are actually bound on the other landing runway: they are aligned with Rwy 24R, slightly above our approach path, while ATC has cleared us to runway 25L. This explains why no conflict with another aircraft was encountered, what a chance! Simultaneous ILS approaches are common with airports that have sufficiently spaced out parallel runways. Together with a Northwest A320 established on 24R. Still the rush our on Rwys 24L/24R (see the TCAS symbols still displayed on the ND), almost nobody in our approach corridor, what an easy landing!... We seem to have a preferential treatment from ATC, but I guarantee that the pope is not on board. Finally down, this last shot concludes the most 'technical' leg of Around the world 2006-2007. LAX air traffic controllers have to deal with one of the most busiest skies in the world. Two simultaneous aircraft are now getting airborne: a Southwest 737 from Rwy 25R and a further aircraft from Rwy 24L. Leg 23: Los Angeles, California, United States - New York, NY, United States This flight will leave L.A. at dawn and cross the United Sates in less than five hours. The flight will fly over Las Vegas, pass north of the Grand Canyon and south of Denver and Chicago. Our approach to John F. Kennedy airport of New York will provide us good views of Manhattan. Flight Plan From LOS ANGELES INTL (LAX/KLAX) to NEW YORK/JOHN F. KENNEDY INTL (JFK/KJFK) Alternate KEWR NEWARK INTL KLAX25R SEBBY1.DAG DAG J146 FJC STW LENDY LENDY5 KJFK13L Distance 2915 nm (5392 km) Flight time 4:50 The flight path uses the J146 high altitude airway, which actually originates at Los Angeles and ends at New York. LAX-JFK is for sure one of the busiest routes in the country domestic network. Our takeoff from runway 25R at Los Angeles, towards the sea, is to be followed by an u-turn and we will cross Seal Beach VOR again, like during our arrival procedure. From Daggett VOR, we will remain on the same airway until we reach the eastern coast. So long L.A. Left turn abeam Santa Monica VOR, to join Seal Beach VOR as next. City of lights... Ten minutes after engine start @ 14000 feet (4200 m) 45 seconds later, now @ 16000 ft and about to reach Seal Beach. MegaScenery USA (see credits) is one of the very few photographic scenery add-ons that provide both day and night textures. Flying over Las Vegas and Mc Carran Intl airport just after sunrise. Good job for the FS2004 standard scenery. Las Vegas is behind as the Sun begins to scorch hot on the Colorado plateau, with Virgin river on the left. Kanab Creek, just north of the Grand Canyon. The airway is unfortunately bypassing the famous place. Federal Aviation Administration approach chart (public domain) Reduced for illustrative purposes - DO NOT USE FOR REAL WORLD NAVIGATION Our approach to JFK will cross La Guardia VOR/DME, to be followed by the ILS Rwy 13L. The 1515' obstacle located right on the runway axis is the Empire State Building. Our flight path will pass a few miles north of it. Enigma: in the LENDY5 standard arrival to Kennedy that was observed, ending at La Guardia from which radar vectors are expected to final approach course, LENDY intersection, located only 14 miles west of LGA, is to be crossed at FL190. La Guardia should then be reached at 2000 feet. Did I read well ? I'm afraid so. Well, ladies and gentlemen, please get prepared for a STEEP descent: 17000 feet within 14 nautical miles, that means 1214 feet every nm or... h'm... a 24,6% slope and a descent rate of more than 6000 ft/min if we comply with the 250 KIAS constraint of the arrival. I would suggest to add 'SPEEDBRAKE USE MANDATORY' on the STAR chart. To comply with that steep descent profile, we hadn't much choice and had to use the autopilot selected vertical speed vertical guidance mode, as well as autothrust selected speed guidance (250 KIAS). Here, the selected 6000 ft/min vertical speed value was flashing amber/green, meaning that we were at the limit of an excessive descent rate. Indicated airspeed is slowing down to the target value, but only thanks to the speedbrakes. Okay, we've almost made it. I don't know how is the ambiance in the cabin after the 'dive' but the passengers may now enjoy the scene. FS2004 developers did it well also here: concluding the descent with a great view of Central ¨Park. Speedbrakes are still extended. Another view, now revealing the typical outline of the Empire State Building, which is sadly Manhattan's tallest skyscraper again since September 11, 2001. Houston, we've a problem. Here's a perfect example of the situation that was described in the previous leg. Left, TCAS would provide a Traffic Advisory message. Center, a collision could occur in less than 25 seconds: TCAS would enunciate a Resolution Advisory. Right, here's the 'intruder': in real life, the consequences of a collision with such a single prop light aircraft would be almost as terrible as with another airliner. In this flight, the collision would not have occurred: despite ignoring the TCAS alert since the RA messages are not modeled, the private aircraft bypassed us, more than half a mile on the left. After a steep descent and passing close to a mid-air collision, we're trying to establish ourselves on final: too fast, too high, not aligned yet. Perhaps I should apply for another job after landing. Leg 24: New York, NY, United States - Tampa, Florida, United States We finally kept appearances and landed safely at New York so I'm very pleased to announce that Around the world 2006-2007 goes on. For this article's last leg, we'll visit Florida and fly the approach that I had once the chance to experience in real life as a passenger, since a part of my family lives there. Tampa Intl airport is the third airport in Florida (after Miami Intl and Orlando Intl) and serves the Tampa Bay region. Centrally located on the west coast of the state, near the Gulf of Mexico, Tampa Bay's population, also including St Petersburg and Clearwater, is 2.5 million people. Huge residential areas, mainly made of bungalows and criss-crossed by thousands of streets, spread over the land with the only 'peaks' in the landscape being the towers of St Peterburg and Tampa's downtowns. Flight Plan From NEW YORK/JOHN F. KENNEDY INTL (JFK/KJFK) to TAMPA INTL (TPA/KTPA) Alternate KPIE ST PETERSBURG-CLEARWATER INTL KJFK31L SEAVW2 CRI JOANI J79 SBY J209 SAWED J121 CRG J55 INPIN LAL BRDGE BRDGE5 KTPA36L Distance 952 nm (1760 km) Flight time 2:20 We will take off from JFK's longest runway and immediately turn left on the SEAVIEW 2 departure. The flight path will follow the east coast of the United States and hit the Florida border near Jacksonville. Towering thunderstorm clouds are expected on arrival, that will be a further opportunity to appreciate the first-rate FS2004 weather engine. Lining up Rwy 31L. The Empire State Building is still visible in the background but the departure sequence will - not surprisingly - avoid Manhattan island, here located straight ahead. For this short flight, less than 1/3 of the runway length was used for takeoff! Passing a colleague near Charleston (this was an A320 from US Airways). In such a case, the relative velocity between the two aircraft is one and a half time the speed of sound ! Already towering clouds as we're about to cross Florida's border We're now above the Sunshine State, near Daytona Beach and starting descent. Another encounter, though still too far to be detected by the TCAS. This B767-300 from Delta Airlines was approaching Orlando Intl. Passing INPIN and heading towards Lakeland VOR. Below are a few of the 10,000 Florida lakes. Proceeding to Lakeland. We're bound for runway 36L at Tampa and expect a moderate crosswind. The other airports appearing on the Nav Display are Orlando Intl (KMCO), Sarasota-Bradenton Intl (KSRQ) and St Petersburg-Clearwater Intl (KPIE), our alternate for today. Note that I've modified the PSS airport database so that only airports that can accomodate the Airbus A330 are displayed. There are actually far more airfields in the area. Federal Aviation Administration approach chart (public domain) Reduced for illustrative purposes - DO NOT USE FOR REAL WORLD NAVIGATION The topography of the Tampa Bay is clearly depicted on the IFR approach chart. Its northern part is actually split into the Old Tampa Bay (left) and Hillsborough Bay (right). We'll capture the localizer at LAGOO IAF. Passing BRDGE at 8000 feet and starting the last leg before localizer capture. We're now reaching the final approach altitude of 2600 feet, a few seconds before turning right to final, while the sky seems to get darker above the Tampa Bay. The Gandy Bridge carrying the US92 road is one of the three bridges that cross the Old Tampa Bay. Now fully established for runway 36L. Horizon 2006 heavy, cleared to land runway 36 left, wind 320 degrees, 16 knots... Autopilot is disengaged, we'll perform a manual landing. Tampa skyline in the background This excellent airport scenery add-on also provides 3D approach lights. I confirm that these ones are accurate! Slightly too much to the right. Probably because of the crosswind, or concentrating on the screenshots, or both! Nice correction as we touch down right on the runway centerline. And Tampa here we come... you may further appreciate the perfect modeling of the airport... Vacating the runway to taxi to the Airside F terminal. Left: the panoramic restaurant and the control tower, we can also see the (here red and blue) typical monorail shuttles that connect the airsides to the main terminal, called 'Landside'. We also have 3D taxilights... I really love this airport. In the next leg, we will enjoy it at sunset! This landing at Tampa concludes the 5th part - and the longest article of Around the world 2006-2007 (it was supposed to be the shortest, with only 3 destinations, but the technical stuff made up for that a little bit). In the next issue, we'll visit Mexico and a few pearls of the Caribbean. I will also introduce the Checklists and perform an external walkaround of the aircraft, just like in real life. Thank you for joining me on these three further legs in the United States and I hope you'll board the A330 again as the adventure goes on. Cédric De Keyser Brussels, Belgium cdk@ngi.be
  10. Part 4: Visiting Australia & Pacific Welcome again everybody on this round the globe trip flying the A330-200 aircraft and visiting the vast virtual world. We've already seen various landscapes and tackled many technical aspects of our flight, but there is still much more to see. Through lack of time, and so as to limiting the articles size, however, some scheduled destinations will unfortunately have to be cancelled in the future of this project. That should not garble the variety of regions to be visited and the global flight path introduced in Part 1 should remain almost the same. For example, stops in Bali, Indonesia and Adelaide, Australia were scheduled between Hong Kong and Sydney. We'll fly directly from Hong Kong to Sydney in the following leg, that will be in the meantime the first long range route of our trip. Leg 17: Hong Kong, PR of China – Sydney, Australia Though being also efficient on medium haul routes, the A330 wide body airliner is first of all a long range aircraft. We'll then fly a true long range sector now, with a 9 hours flight. From HONG KONG INTL (HKG/VHHH) to SYDNEY/ KINGSFORD SMITH INTL (SYD/YSSY) Alternate YSCB CANBERRA VHHH SANDI1D SANDI DOVAR A583 ZAM A461 AMN R340 TASHA A464 OMUBI B587 NBR UH209 SCO H39 BOREE BOREE3 YSSY Distance 4110 nm (7600 km) Cruise alt. FL 350 Cruise spd. Mach 0.82 The aircraft Zero Fuel Weight calculation was introduced in Part 2. Let's see now how to calculate the fuel quantity we need for this flight. To do this, we'll use the PSS fuel planner – a very easy to use software, a simplified tool designed for flight simulation only. First, the route and alternate distances are provided by the MCDU, once a flight plan is completed or loaded: The alternate distance is simply the distance between the destination and alternate airports (as shown by the blue dotted line on the ND), since we cannot specify any alternate flight plan with the MCDU modeled by PSS. We just read: route distance: 4109 nautical miles (rounded to 4110) and alternate: 127 miles (rounded to 130). Next, the APU Time is the estimated running time of the APU. Taxi Time should be far less than 20 minutes since we'll leave Hong Kong at dawn, before the rush hour, but the higher is the estimation, the higher will always be the safety margin. I always set the same 20 min Holding Time at the destination, but knowing that MSFS default ATC doesn't handle holdings... Route Contingency is a further additional enroute time which could occur because of nearby traffic avoidance or serious weather skirting. I always leave 0 there: offline flying doesn't provide much ATC or weather surprises... Additional fuel Reserves is though filled (5 tonnes set), as well as the scheduled cruise altitude. Setting the weather myself, and usually only surface winds, the 'Prevailing Winds' section is often ignored. The very last thing to do in real life, when this is perhaps the most important thing in flight planning, and in particular in the cross-Atlantic flights, where high altitude streams may have a dramatic impact on fuel burn. The aircraft Zero Fuel Weight, which was calculated in Part 2, is the last figure filled. Clicking 'Calculate Required Fuel' will compute the fuel quantity we need for the flight. The 61949 kg result will be rounded to 62000 kg or 62 tonnes. The PSS utility also computes Taxi, Takeoff and Landing weights (that will also be done by the MCDU) – if TOW or LW were above MTOW or MLW, they would be displayed in red. Because the PSS fuel utility is unfortunately independent of FS2004, we have to use the latter's default aircraft Fuel & Payload utility to fill the tanks. Lower ECAM Fuel page just after engine start. The 62 tonnes of fuel could be filled in the wing tanks, the center tank is still remaining empty for this flight. Taxiing out while Hong Kong is awaking – 6:10 local time. Lining up runway 25R for an immediate takeoff Prior to taking off for the 17th time, let's focus a while on the very special Airbus thrust levers and autothrust system. Though looking like any other airliner controls, the Airbus thrust levers have an unique way to work. They move between different detents called gates. Four gates are available: IDLE (0), CL, FLX/MCT and TO/GA. The range between the IDLE and CL gate is called the manual range and works like on any other airliner, with engine thrust being proportional to lever angle. But as we will see, it may not be used during flight, and then only on the ground while taxiing the aircraft or monitoring the engines just before applying take off power. Maximum takeoff power is available through the TO/GA (Take off/Go around) gate, while the FLX/MCT gate will provide a reduced thrust takeoff. In that case, computed FLEX thrust will be based on an assumed temperature (always greater than the current ambient temperature) at which the needed (and then lower) takeoff thrust is calculated. Reduced thrust takeoffs will always be preferred for economical and structural reasons when runway length, TOW and airfield situation permit. Moving the levers to the FLX or TO/GA gate will automatically arm the autothrust (A/THR) system, and 'A/THR' will appear in blue on the PFD's Flight Mode Annunciations. With autothrust armed or active, the A/THR button on the FCU illuminates. At thrust reduction altitude, usually set to 1500 feet AGL, 'LVR CLB' will flash on the PFD and the levers are retarded to the CL gate. Autothrust then automatically comes active ('A/THR' turns to white on the PFD) and will automatically control thrust according to any thrust demand. This is why the levers are normally left in the CL gate throughout the whole flight. The levers will then NOT move as the thrust is automatically adjusted like on Boeing and other airliners. Through the CL gate, several autothrust modes are available following the flight phase and pilot's choice. The CLB mode (THR CLB will appear on the PFD) will be automatically used during climbs. CLB thrust will be equal to the climb thrust available at the current ambient conditions. In the SPEED / MACH mode autothrust will control the engines to maintain selected or managed airspeed / mach number, following the altitude. The approach speeds can also be entirely managed through the SPEED mode and MCDU Approach Phase, we'll see that later in a following leg. Finally, the IDLE (THR IDLE) mode commands idle thrust and is used during Open descents. Just before touchdown, 10 feet above the runway, the cockpit voice will announce 'RETARD!', the levers must then be retarded to the IDLE gate. Doing this will automatically de-activate the autothrust system and provide idle engine rate. In the meantime, the A/THR button will go out. Moving the levers through the REV range will apply desired reverse thrust after landing. Thrust reverse is usually cancelled once the aircraft has decelerated to 60 knots. Flight envelope protection is provided by Alpha floor autothrust mode, which will engage regardless of A/THR status and commands TO/GA thrust to aid recovering the aircraft from low speed and too high angle of attack conditions. Let's hope that we will not have the 'opportunity' to illustrate this in the following flights! The thrust levers moved to the FLX/MCT gate for a reduced thrust takeoff. On the PFD flight mode annunciations, 'MAN FLX 42' confirms that a FLEX take off is performed, with a 42°C assumed temperature. This temperature is also visible on the upper ECAM, where the computed FLEX thrust is also displayed with EPR = 1.69. We see that current EPR is 1.60 (for engine 1), and increasing to the 1.69 value commanded by the autothrust system, as shown by the blue command arcs. On the PFD speed tape, the arrow extends to the speed that will be attained in 10 seconds at present acceleration. A quick calculation shows that the latter is then equal to 2 m/s², meaning only 0.2 g. Not really the acceleration of the lifting off space shuttle anyway! At thrust reduction altitude (which defaults to 1500 feet AGL), 'LVR CLB' is flashing and thrust levers must be retarded to the CL gate. Thrust reduction altitude, as well as FLEX take off based temperature, are specified on the MCDU Take off performance page (see Leg 18). Take off is completed. The PFD now shows the expected 'THR CLB' autothrust climb mode. Note that the A/THR annunciation in the autoflight status column is now white, meaning that autothrust is active. We've just passed the thrust reduction altitude: the engines EPR is now decreasing to the computed thrust limit value (EPR = 1.46) associated with the climb mode. Note that the blue 'CLB' above the thrust limit figure will not turn to 'CRZ' once reaching cruise altitude like on Boeing planes: the thrust limit is strictly linked to the thrust lever gate and will only appear if autothrust is active, that means with the levers moved to the CL, FLX or TO/GA gates. Farewell to Hong Kong, left turn heading South on the SANDI 1D departure. Still climbing and already cleared to our cruise altitude The PFD shown when the managed cruise speed of Mach 0.82 is reached, with autothrust MACH mode active. Sydney, as well as other destinations that will be found in this fourth part, was already visited in a first round the world trip in 2003. Since the aircraft and sceneries that were used in that time now seem to date back to the stone age, it should be interesting to come back to those places and see how they look today. The ILS rwy 16R, the most usual approach to Kingsford Smith Int'l, will be performed. With its 13000 feet or 3962 m, runway 16R is one of the longest of the Southern hemisphere; it it said to be a 'diversion' landing facility for the above-mentioned space shuttle. The destination, which has a 2 hours time lag with Hong Kong, was reached just before sunset. Another thing to point out here, the equator was crossed for the first time in the trip. Final for the 'City of Brides' @ 2500 feet Cannot miss the typical shape of the Opera with this shot – now @ 2000 feet, 7 miles more to go Close the the 'One hundred' radio altimeter call, note that autothrust is still active. 21240 Kg of remaining fuel, this is very comfortable. Leg 18: Sydney, Australia – Agana, Guam (USA) Already back for a while to the northern hemisphere with a second crossing of the equator, in this leg we'll focus on aircraft performance, controlled through the MCDU. The route to Guam, a Micronesian island belonging to the United States and located near the Mariana trough, will include Brisbane on Australia's Gold coast, then Port Moresby in Papua New Guinea. Quite a long leg again with a route distance of 2967 nautical miles or 5490 km. Flight Plan From SYDNEY/ KINGSFORD SMITH INTL (SYD/YSSY) to GUAM INTL (GUM/PGUM) Alternate PGSN SAIPAN INTL YSSY KAMPI1 KAMPI ENTRA H133 CAS H66 JCW H185 BN O26 CORAL O18 KELPI B220 PY B586 ZEEKE PGUM Aircraft performance is an important step in the cockpit preparation process and will also be managed by the MCDU. The flight is divided into several phases with each phase having its own performance page: TAKE OFF, CLIMB (CLB), CRUISE (CRZ) , DESCENT (DES), APPROACH (APPR) and GO AROUND. Pressing the PERF key on MCDU calls up the performance page for the current flight phase. Next phases are also available using the 'NEXT PHASE' prompt, but phases already flown are not. Though each flight phase can then be separately called up, aircraft global performance can be controlled through one single parameter called the cost index (CI). With an effective range of 0...100, cost index is used in economy speed computation. Lower values result in lower speeds and lower fuel consumption, higher values gives higher speeds and then increased fuel costs. MCDU's default cost index value is 50, I'll set 80 for this flight. The cost index can be specified on the INIT page, as well as on the CLB, CRZ and DES performance pages. MCDU INIT page #1, where the Cost Index and Cruise flight level are entered. If temperature at the cruise flight level is not entered by the pilots, the FMS automatically calculates it using a standard atmosphere model. In Part 2, we have seen how the Zero Fuel Weight and Block fuel were calculated and entered on the INIT page #2. With the Cost Index, Cruise FL, ZFW, Block fuel and assumed temperature as main entries, the FMS will automatically compute engine thrust and flight envelope limits, economy speeds for all phases of flight and all the parameters required for automatic flight. The TAKE OFF performance page is where the take off speeds, departure airport transition altitude, thrust reduction altitude, take off flaps setting and assumed temperature for FLEX take off are entered. The take off speeds V1 (take off decision speed), VR (rotation speed) and V2 (takeoff target speed) are not automatically computed and must be entered by the pilots following performance tables. If not entered, a red 'SPD SEL' flag is displayed above the PFD speed scale. Hopefully, PSS will kindly compute the T/O speeds here if the user clicks on the corresponding line select keys. Now with the take off speeds filled (note that V2 is equal to VR with 161 kts or 186 mph or 298 km/h). Take off speeds will usually be announced by the First Officer (pilot non-flying) during take off: 'V One' ... 'VR' or 'Rotate' ...'V Two'. For those like me who don't really remember what V1, VR and V2 speeds precisely mean, here are the definitions compiled after a quick internet search: V1 is then the Takeoff decision speed, the minimum speed where it will be possible to continue the takeoff after an engine failure. This is also the maximum speed at which it will be possible to bring the aircraft to a complete stop within the remaining runway length if takeoff is abandoned. Therefore, if one engine fails after V1, takeoff must be carried on and the problem treated once airborne as an inflight emergency. VR is the Rotation speed where the pilot in command initiates rotation to lift off aircraft attitude and climb away with the scheduled takeoff performance. VR must be greater of equal to V1. V2 is the Takeoff safety and Initial climb speed, the minimum speed at which climb can be continued safely. With Airbus, V2 is also called the Take off target speed. An engine failure happening between V1 and V2 is then critical, but this is an extremely rare event, because of engine reliability and seeing that V1 and V2 are in most cases close to each other (for our current flight, V2 is even equal to VR). Anyway, aircraft crew are trained to face such extreme situations, easily modeled in (real) flight simulators. The transition altitude is also automatically set according to the PSS database (we'll focus on transition altitudes and altimeters in a following article). The default values for thrust reduction, engine out acceleration altitudes and FLEX take off temperature are kept. The flaps setting defaults to position 1, and we'll also keep that setting. Airbus also takes off with flaps at position 2, when less runway length is available for example. Note that the Airbus flaps lever is not marked in degrees like on other airliners but with very simple numbered positions. Lever positions are UP, 1, 2, 3 or FULL. Position 1 will only command the slats extension in flight with indicated airspeed above 215 kts (CONF 1). On the ground (before take off), and in flight below 215 kts, slats and flaps will be extended at position 1 (CONF 1+F). Flaps lever on the Pedestal (shown in position UP) On the TAKE OFF page, the FMS also displays the computed minimum flap retraction speed (F), minimum slat retraction speed (S), and green dot speed (O), which is the maneuvering speed in clean configuration (with flaps and slats retracted). These speeds also appear on the PFD speed scale and will vary throughout the flight, since the aircraft weight and balance vary also. Hmmm... interesting AI traffic miracle: the very high approaching 747 did succeed on its landing runway 16R a few seconds later! ... while this one left just before us as flight QF64. Note the CONFIG 1+F for flaps setting on upper ECAM. The PFD shown during take off roll and approaching V1, as shown by the speed tape. The magenta triangle shows the managed reference target speed of V2 + 10, which is commanded by the Speed Reference System (SRS), a vertical guidance mode automatically engaged at take off ensuring optimum climb performance.The RWY lateral guidance mode is also automatically engaged, it keeps ground track equal to the departure runway heading. After take off, approaching the green dot speed. Slats and flaps are retracted (flap lever in position UP). The new managed target speed is now 250 kts, we're already in the CLIMB phase. Left, the PFD shown when reaching the cruise altitude of FL360. The target airspeed is then the managed cruise speed of Mach 0.82 displayed on the MCDU CRZ performance page. The red speed tape lower limit (called VMAX) is the aircraft maximum operating speed in clean configuration at this altitude. Above Papua New Guinea jungle with Port Moresby behind us. The MCDU Progress (PROG) page shown here allows selecting a new cruise altitude, monitors optimum and maximum cruise flight levels and checks navigation accuracy. We can see that the current optimum cruise flight level (FL402) is now 4000 feet or so higher than our current level. At this optimum altitude, aircraft performance will be better and fuel burn lower. Pilots may then ask ATC to obtain a higher level clearance in such case. This Progress page is then strictly different from Boeing and other airliners FMC's 'Progress' page. The PFD and MCDU performance page shown during descent. Current managed target airspeed is 267 kts. The APPROACH phase is activated by pressing LSK 6L. A confirmation will be asked by the MCDU that will then display the APPR performance page. Approach phase activation is made following the pilot's valuation, but will usually occur between 20 and 30 miles from the destination airport. The APPR page is similar to the TAKE OFF page with the minimum flap retraction, slat retraction and green dot speeds displayed in the center column. Note that they are all different compared with the take off phase. A further speed, the minimum selectable speed (VLS), is displayed. A bit greater, the computed approach speed (VAPP) will be 146 knots for this landing. This is the speed that should be reached before touchdown. Destination airfield QNH, temperature, wind as well as Minimum Descent Altitude (or Decision Height) for the landing runway can be entered also, but I confess that I often leave these fields blank. Finally, the flaps setting for landing is also chosen here: Airbus A330 may land with flaps at CONFIG 3 of FULL. I usually leave the default FULL setting here also. Flying with autothrust managed speed engaged, the APPROACH phase is a very 'smart' feature provided by Airbus. When APPR phase becomes active, the managed speed guidance will automatically decelerate the aircraft to maneuvering speed in current configuration until 10 feet above the ground. In that way, if APPR phase is activated in clean configuration, speed will decelerate to the green dot speed and managed target speed will continue decreasing once flaps are extended. When flaps are set to CONFIG 1, speed will slow to S speed ; once in CONFIG 2 speed will then slow to F speed. When the landing flap configuration is reached (CONFIG 3 or FULL), the speed will finally slow to the approach speed VAPP. Since the autothrust and autopilot systems work indenpendently (we will focus on the autopilot system in the following leg), autothrust can then be used when manually flying, and, in particular, flying an approach. Keeping the managed speed active on the approach is up to my mind the easiest and safest way to fly, unless ATC demands lower or higher speeds (which never occurs though with FS2004's default ATC). In real life, however, Airbus pilots seem to prefer to de-activate the autothrust system if flying manually. Guam approach to runway 06L begins at the ZEEKE IAF (last waypoint of the flight plan), from which a 7 DME arc from the Nimitz VOR/DME (located on runway axis some 3 miles from the airport) is followed at 2600 feet. The 7 DME arc was a bit 'skipped' on its end as I concluded with a visual approach. The PFD captured during approach. We're flying with managed speed guidance, selected vertical and lateral guidance (ALT and HDG). Flaps have just been set to CONF 2, speed is then decreasing to F speed. Still on the speed tape, the double orange stroke represents the maxiumum speed for the next (greater) flaps position (CONF 3 in this case). Above, the red tape now shows the forbidden speed range for current flap position. Localizer capture – now flying manually, flaps FULL, autothrust still engaged and already at VAPP (146 kts or or 169 mph or 270 km/h). The Pacific atmosphere is perfectly rendered by the add-on scenery... ... also with this second shot taken in the evening of our arrival, with an approaching thunderstorm. Leg 19: Agana, Guam (USA) – Anchorage, Alaska, United States Prior to visiting further Pacific islands, connecting two extreme locations is proposed on this 19th leg. Since it took place in February, the weather contrast will be even better, with bad winter conditions at the destination, requiring full autopilot approach capabilities. In the meantime, we'll go deeply into the Airbus autopilot main features here, making up the last technical matter that will be tackled in this fourth part. The route is not a straight line across the Pacific, but it will first head towards Japan, then right to the Bering Sea, the flight path passing south of the Kamtchatka peninsula and north of the Aleutian Islands. Finally, the Alaska chain of mountains peaks will be seen emerging from the clouds during descent. Another thing to say, the international date line is crossed in this flight. Flying eastbound, the arrival date is the preceding day of the departure one! Flight Plan From GUAM INTL (GUM/PGUM) to ANCHORAGE INTL (ANC/PANC) Alternate PAFA FAIRBANKS INTL PGUM HAMAL B586 OTTER KAGIS A590 AMOTT AMOTT5 PANC Distance 4369 nm (8082 km) Cruise alt. FL 340 Cruise spd. Mach 0.82 Flight time 9:20 The Airbus Autoflight system is a part of the Flight Management System (FMS) and controls Autopilot (AP), Flight Director (FD) and Autothrust (A/THR) systems. The Autothrust system was introduced in Leg 17 and we'll not go deeply into the Flight Director here, let's just say that the pilot can manually fly the aircraft following the Flight Director commands, which tell through the PFD what the Autopilot would do if it was controlling. As said above, Autopilot and Autothrust systems work independently and A/THR can then be used when manually flying. On Airbus aircraft, Autopilot can be engaged immediately after take off. The Autoflight system operation modes are selected using the Flight Control Unit (FCU), centrally located on the glareshield. As we'll see it is very different from the Boeing Mode Control Panel (MCP) and provides the typical and unique Airbus autoflight controls. The autoflight operation modes are displayed as Flight Mode Annunciations (FMA) on the PFD. The FCU seen before startup, with the first altitude cleared by ATC selected. The FCU provides four knobs that can be rotated, pushed and pulled (in this PC flight simulation, these functions are available through the mouse buttons). Left is the knob which controls airspeed (SPD) through the A/THR system. Second to the left (above the 'LOC' button) is the heading (HDG) knob which controls lateral guidance. The two knobs on the right provide vertical guidance, with the altitude (ALT) sand vertical speed (V/S) knob. If a knob is pulled, the pilot takes direct control of this function, and the selected value in corresponding FCU window becomes a target. This is called the selected guidance. Turning the knob will modify the target value. In that way, pulling the airspeed knob in flight will capture aircraft current airspeed, and selecting another speed by turning the knob will make A/THR reach that speed. Regardless of selected speed, A/THR will however not exceed minimum or maximum aircraft speed limit for current configuration. With selected speed guidance, the target speed will be represented by a cyan triangle on the PFD speed tape. This is selected speed guidance. In the same way, pulling the lateral guidance knob will engage HDG mode and capture aircraft current heading, and turning the knob will select a new heading, the aircraft will turn towards the new target in the direction of knob turn. This is selected lateral guidance. If altitude selected in ALT window is above current aircraft altitude, pulling the altitude knob will engage the Open Climb (OP CLB) selected vertical guidance. In this mode, the aircraft will climb directly to selected altitude, and no flight plan constraints will be honored. The target airspeed will be maintained by controlling aircraft pitch and autothrust will maintain climb thrust (THR CLB mode). Now, if altitude selected in ALT window is below current altitude, pulling the altitude knob will engage Open Descent (OP DES) mode, in which the aircraft will descent directly to selected altitude. The target airspeed will also be maintained by controlling aircraft pitch, while idle thrust (THR IDLE mode) will be commanded. When approaching selected altitude, the aircraft will level off and autopilot vertical guidance will switch to ALT mode. If a knob is pushed, the control is given to the Flight Management System which can guide the aircraft according to all its computations and the information provided by the pilots through the MCDU, including the route, aircraft Zero Fuel Weight and performance options, as we've seen in the previous legs and articles. This is the managed guidance. If a function is in managed guidance, a white dot appears in the corresponding window on the FCU, and the window becomes dashed. The altitude window, however, is never dashed, and the vertical speed knob (see below) doesn't provide a managed guidance function. Pushing the SPD knob will activate managed speed guidance. Managed speed guidance will make autothrust control the FMS computed speed following current flight phase, and will comply with speed constraints and limits if the flight plan constraints are honored. The managed target airspeed will be represented by a magenta triangle on the PFD, if the target is inside the displayed scale. Otherwise, the triangle is replaced by a magenta numeric readout above or below the scale. Pushing the HDG knob will provide managed lateral guidance (NAV mode). With this mode engaged, the aircraft will follow the flight plan entered in the MCDU. This is then analog to Boeing's 'LNAV' function. NAV mode will be automatically armed on the ground after a route is entered in the MCDU, and will then automatically engage after take off once autopilot is engaged. The NAV mode is then the default lateral guidance mode once airborne if a flightplan is entered in the MCDU. The managed vertical guidance, engaged by pushing the ALT selector knob, will provide automatic vertical control of the aircraft, following the vertical profile associated with the flight plan. CLB and DES managed vertical guidance modes will be used during climb and descent, with flightplan constraints observed. If the aircraft levels off at an altitude constraint, the ALT CST mode will engage. When reaching the cruise altitude, the ALT CRZ mode engages. Airbus managed vertical guidance can be compared to Boeing's autopilot 'VNAV' function. The 'VNAV' function, however, handles both FMC vertical and speed guidance on a Boeing airliner, when, as we've seen, speed and vertical guidances work independently with Airbus. Lateral and vertical guidances, though being engaged by distinct knobs, are not strictly independent. In that way, managed vertical guidance requires also managed lateral guidance to be engaged. Wishing a managed descent will then not work if flying with the HDG lateral guidance mode, but with the NAV mode well. The vertical speed knob, for its part, works a bit differently. Though being also pushed or pulled, it doesn't provide any managed guidance. The V/S selected vertical guidance mode can be engaged in two ways, with autothrust maintaining target airspeed. Pulling the V/S knob will capture and maintain aircraft current vertical speed, while pushing the knob will engage V/S mode with zero vertical speed, which results in aircraft levelling off (see the 'PUSH TO LEVEL OFF' notice close to the knob). The selected vertical speed can be changed by turning the selector knob, and the V/S window remains dashed unless V/S mode is engaged. The Airbus has actually two identical autopilots (AP1 and AP2), which are engaged or disengaged by pressing the corresponding button on the FCU. The two autopilots cannot be engaged simultaneously: selecting AP2 will automatically disengage AP1, and vice versa. During ILS approaches, however, both autopilots can be engaged for enhanced accuracy, as we'll see and the end of this flight. The following flight will then illustrate most of the autopilot functions that were introduced here. Most of flight phases will be flown with managed lateral and vertical guidance, while selected lateral and vertical guidance will be used for the initial approach. With bad weather conditions and poor visibility at the destination, both autopilots will be engaged on the ILS final approach. Managed speed guidance will be used throughout the whole flight. FCU and PFD Flight Mode Annunciations seen after takeoff. AP1 has just been engaged, and Open Climb selected vertical guidance mode has been engaged by pulling the ALT selector knob.The NAV managed lateral guidance mode, which was automatically armed before takeoff, is now automatically engaged. On the PFD, active vertical and lateral guidance modes are shown in green, while armed modes are displayed in blue. This is now the case of the ALT mode, to which the OP CLB mode will switch when reaching selected altitude. With FLEX power set, the autothrust system is armed and will become active once we reach the thrust reduction altitude and retard the thrust levers to the CL gate, as we've explained in Leg 17. Levelling off at cruise altitude of 34000 feet, with the FMA showing MACH │ ALT CRZ │ NAV modes. The Nav Display shown when approaching the Top of Descent point. The magenta dot close to AMOTT represents a speed change. In this case, this is the point in the computed descent profile associated with the flight plan, where the altitude will go below 10 000 feet and speed will then be restricted to 250 kts IAS. Contrary in the Boeing's VNAV vertical guidance, the descent will not start automatically from cruise altitude when reaching the Top of descent (T/D) point computed by the FMS. Airbus pilots must then, once reaching T/D, select a lower altitude in the FCU altitude window and push the altitude selector knob if wishing a managed descent. This is what we'll do here. Left, the PFD shown just when the managed DES mode is engaged (when a new mode is engaged, it is boxed in white for a few seconds). The 'MORE DRAG' message means that managed guidance is currently unable to keep target speed. Partially extending the speedbrakes would solve the problem, but the autopilot will usually do it well on its own: right, the airspeed is now just in the middle of the managed descent speed range represented by the two brackets. Close to the altitude tape is the Descent Path Indicator that shows the aircraft's vertical deviation to the computed descent path and is working just like a glideslope: we were too high on the left shot, just on the descent path on the right one. At FL250 (descending to FL180), 113 miles from destination, with northern lights in the sky! At 56 miles from destination, 11 000 feet, still descending and about to penetrate the cloud layer The autopilot LOC (for Localizer) and G/S (for Glideslope) modes can be used during ILS approaches and will allow the aircraft to carry on the approach in poor visibility conditions. Pressing the LOC button on the FCU will arm the LOC mode and track the localizer signal. Pressing the APPR button will arm both LOC and G/S modes. LOC and G/S modes can only be armed when an ILS frequency is tuned. After localizer and glideslope interception, LOC and G/S modes become active. As a quick reminder, the ILS (Instrument Landing System) is made up of two signals, the Localizer and the Glideslope (or Glider Path), whom imaginary planes intersection provides the ideal descent path towards the landing runway. ILS deviation (and possible additional distance information provided by a Distance Measuring Equipment or DME) are precisely displayed on the Nav Display with ROSE ILS mode set. Localizer and glideslope deviations are also available on the PFD. LOC and G/S modes can then be armed before ILS interception, but ILS capture will be made with autopilot selected vertical (V/S) and lateral (HDG) guidance here. Once the localizer is intercepted, LOC mode will be engaged ; and once the glideslope is intercepted, APPR button will finally be pressed, engaging both LOC and G/S modes. Initial approach, descending to the beginning of final approach altitude of 1600 feet using the V/S selected vertical guidance mode (selected vertical speed is 1000 feet/min). We're turning left, trying to capture the localizer with current selected heading of 10°, symbolized by a blue triangle on the ND's horizontal situation indicator. The blue and green arrows added on the ND respectively show the localizer and glideslope deviations, the ND being set to the ILS mode selected on the EFIS panel. Beginning of final approach: the glideslope is intercepted and APPR button is pressed, automatically turning off the previously pressed LOC one (not shown here). Both LOC and G/S modes are now active, and the second autopilot can be and is then engaged. 'AP1+2' appears on the PFD Flight ModeAnnunciations fifth column showing autoflight status. The fourth column shows the approach capabilities: we're tuned to an ILS which supports up to the CAT IIIC instrument approach that has no decision height and no runway visual range limitations. We are however flying a common ILS approach now (ILS Rwy 06R) with a 200 feet decision height, set through the MCDU and also displayed on the PFD. The Decision Height (DH) is the height (above ground level or AGL and measured by the radar altimeter) at which, during an ILS approach, decision must be made to continue the approach or execute a missed approach. If the required visual reference is not established at the decision height, a missed approach must be initiated. When reaching the decision height, the cockpit synthesized voice will announce 'MINIMUM' in addition to the altitude callouts made below 400 feet. The Airbus A330 autopilot is capable of performing a full automatic landing if LOC and G/S modes are still engaged at 400 feet above the ground. These modes would then switch to the LAND mode which provides both lateral and vertical guidance, maintaining localizer and glideslope. The FLARE (reducing vertical speed prior to touchdown) and ROLLOUT (at touchdown) modes would follow, and the 'only' thing that the pilots would have to do is to retard the thrust levers 10 feet above the runway and execute braking action once on the ground. In real life, full automatic landings in very low visibility conditions require specially equipped aircraft and appropriately qualified crew. I've tried to simulate such automatic landings several times, but the result was each time a rather 'heavy' touchdown, meaning that all the passengers were brought home safe and sound but also that the undercarriage would have sent an incicive complaint letter to Horizon Dreams Airlines later if it had been able to. This is why a manual landing is performed here. With the poor, but not dreadful visibility conditions on arrival, the automatic approach will lead us to short final. At about 350 feet QNH or a bit more than 200 feet AGL – which is the Decision Height – both autopilots are disengaged, but autothrust managed speed remains active as usual. At 500 feet, approach lights in sight, both autopilots still engaged. The poor visibility is mainly due to heavy snowfall. Short final, close to the decision height. Autopilot LAND mode engaged, but both autopilots were disengaged less than one second later to conclude with a manual landing. On the PFD, the red tape against the altitude scale represents the ground, with ground level based on radar altimeter, while the upper limit of the orange tape against the speed scale is the speed at which Alpha floor flight envelope protection mode would become active, just below the minimum selectable speed (VLS). Safely down. Hope that the passengers have brought something warm to put on in their suitcases. Anchorage is a frequent technical stop for Asian carriers operating intercontinental routes across the Pacific. These two 747-400 are taxiing out for departure. The newest generation ultra-long range aircraft such as the Airbus A340-500 or Boeing 777-200LR do not need to refuel here any more. Leg 20: Anchorage, Alaska, United States – Honolulu, Hawaii, United States Back to the Pacific islands now, the two remaining legs of this 4th part will visit the 'hot spot' volcanic archipelagos of Hawaii and French Polynesia. The route between Anchorage and Honolulu will not be a straight line across the Pacific, but a path first huging the Canadian and American western coasts, some 160 nautical miles away (B453 airway), then finally heading towards Hawaii (A332 airway) after a 90 degrees right turn abeam of the state of Oregon. A twin-engined flight from North America to Hawaii needs an ETOPS–180 minutes approval, meaning that the diversion time is extended to 3 hours in case one engine fails during flight. We will go deeply into the ETOPS (Extended Twin Engine Operations) in the last part of Around the world 2006-2007. Flight Plan From ANCHORAGE INTL (ANC/PANC) to HONOLULU INTL (HNL/PHNL) Alternate PHTO HILO INTL PANC ANC3 NOWEL J805 MDO B453 KYLLE HEMLO A332 ABSOL R463 MAGGI CHAIN SAKKI PHNL Distance 3465 nm (6410 km) Cruise alt. FL 390 Cruise spd. Mach 0.82 Flight time 7:45 As number one for takeoff, a classic Boeing 737-200 powered by first generation twin spool turbojets - a rather rare sight today. Horizon 2006 heavy, taxi into position and hold. Lining up runway 06L. Airborne in a nice winter morning, with Asian MD-11 and 747-400 in the background. Right turn on the ANC3 departure, which occurs once being 9 miles away from Anchorage VOR. Deep blue... Honolulu approach will be the LDA/DME Rwy 26L, a 45° offset approach procedure beginning at SAKKI IAF and concluding with a visual landing. The localizer path comes rather close to the Honolulu skyline, just before the final left turn. Federal Aviation Administration approach chart (public domain). Reduced for illustrative purposes – DO NOT USE FOR REAL WORLD NAVIGATION On the localizer track, some 10 miles away (left) and beginning the final turn (right). Final turn almost completed: note the ND course, still set to the localizer course, making almost a 45° angle with current heading. Leg 21: Honolulu, Hawaii, United States – Papeete, Tahiti, French Polynesia Further palm trees for this last leg, Tahiti is the biggest island of French Polynesia, as well as the 'youngest' one in the Society Islands archipelago, stretching from West to East in the very middle of the South Pacific. The flight path look is this time nothing else than a straight line, crossing the Equator for the third time in our trip. The main special feature of this flight is the distance of the alternate airport, Rarotonga Intl in the Cook islands, located 617 nautical miles (1140 km) from the destination. Almost each populated island in the Pacific has its own airfield, but very few of them can actually accomodate widebody airliners. The alternate distance, which is filled in the fuel planner as we've seen in Leg 17, will then mean a great additional fuel load. Flight Plan From HONOLULU INTL (HNL/PHNL) to TAHITI–FAAA (PPT/NTAA) Alternate NCRG RAROTONGA INTL PHNL PALAY2 PALAY V7 MOANA V1-7 IAI B595 TIAMA ARONA ARONA1M NTAA Distance 2430 nm (4495 km) Flight time 5:30 Taxiing to runway 26R holding point while a colourful MD-82 is waiting for its takeoff clearance. Nice CB cloud formation seen during descent Short final, flying the VOR Rwy 22 approach. Landing runway 22 at Faaa airport doesn't provide any ILS but has one advantage: the available length between runway treshold and the only taxiway connecting to the terminal is longer, then backtracking the runway is not necessary after a reasonable landing run. Still interesting clouds effects in the sky... We've now reached the end of Part 4 and are already almost half the way of our trip around the world. Part 5, which should be shorter than this one, will visit North America with three selected destinations in the United States. Cédric De Keyser Brussels, Belgium cdk@ngi.be
  11. Part 3: Visiting Middle East & Asia I’m pleased to welcome you again as we proceed with this round the world flight review, which began quite a while ago when we left Brussels, Belgium and will now fly longer legs between a few selected Asian destinations. You've probably noticed that 'Around the World 2006' title has switched to the more appropriate 'Around the World 2006-2007', seeing that, as already mentioned in Part 2, the project takes more time than expected and will then also take place in this new year. A good opportunity though to give a rather new look to the articles as well as the project’s logo. In the meantime, a new aircraft livery will also be introduced in Leg 12. The new Flight Simulator X has now been released for several months, and though having upgraded to a new computer recently, I’m still flying with FS2004. The latter, which had 'ruled' for nearly 4 years, offers an incomparable array of add-ons and doesn’t need the NASA supercomputer to provide decent frame rates. But let’s now board our aircraft again, which is waiting for us on the sunny Athens airport. In this part, you’ll still see the usual short explanations about navigation and IFR procedures, while other Airbus aircraft systems will be basically introduced, including a more detailed focus on the jet engine. Leg 11 : Athens, Greece – Tel Aviv, Israel A short leg again to begin with this third part – not more than 650 (nautical) miles or 1200 km, the longest one though up until now. Engine 2 just before pushback and engine start We’ll take off from runway 21L (southbound), fly the VARIX One Foxtrot Standard Departure, and then head towards the famous Rodos Island. From there, almost a straight line direct to Tel Aviv, with nothing but the great blue sea below. Approach of Ben Gurion airport will be classic, with the ILS Rwy 12 that is one of the easiest approaches in the area, as we’ll see below. Flight Plan From ATHENS-ELEFTHERIOS VENIZELOS (ATH/LGAV) to TEL AVIV-BEN GURION (TLV/LLBG) Alternate OJAI AMMAN LGAV VARIX1F VARIX UL995 RDS UL609 SOLIN UH2 RIMON SIRON LLBG Prior to taking the air again, I think that it’s now justifiable, after 10 successive legs, to wonder how we actually start the engines of our A330-200 aircraft. Starting the engines of an Airbus airliner is easy. The main reason for this is that engine start, like many other Airbus systems, is a partial automatic procedure. To explain the procedure, I propose to start from the 'cold and dark' cockpit configuration. This is a simple procedure indeed, but we will take some time here to wander from the point and focus on some of the concerned systems. First of all, we have to supply the aircraft with electrical power. Before engine start, the aircraft can supply its own DC electrical power coming from onboard batteries (BAT 1, BAT 2, APU BAT). The DC electrical system supplies 28 Volt DC and it is mainly used to start the APU, or supply the aircraft when other sources are unavailable. When their voltage goes below a certain level, the batteries will charge from the AC electrical system driven by the engines – just like a car battery ! The AC electrical system provides 3 phase 115/200 Volt, 400 Hz AC provided by engine driven generators installed on each engine. A further generator installed on the APU is used to provide AC power before engine start (and after engine shutdown) or in case of loss of one or the two engine generators. And finally, in case of total loss of electrical power during flight, the aircraft can be supplied by an emergency generator driven by the RAM air turbine, using the high speed air flow to provide power a bit like a wind engine. APU and engine generators will automatically work once the concerned engine runs, if their corresponding switch on the overhead ELEC panel displays no light. In this configuration, APU generator will also automatically stop once engine generators power become available (or external power is connected). Pilots may still disconnect any generator from the electrical system by switching it off ("OFF" will illuminate). On the ground, the aircraft can also be supplied by external power. We’ll use the aircraft onboard system to start the engines. The 3 batteries are switched on. By the same time, the avionics and the main panel CRT screens come alive. It’s now time to switch on the fuel pumps, but let’s see first how is roughly working the fuel system. On the A330 type, the fuel is contained in one center and two wing tanks. Because of in flight structural reasons, the center tank is usually filled last and used first. The wing tanks are divided into inner and outer cells which are connected by transfer valves. The engines are fed from the inner cells. There are two main fuel pumps and one standby pump in each inner tank. The main pumps all work in normal operations. If a main pump fails or is switched off, the standby pump takes over. The two center tank pumps work as long as there is fuel in the center tank. Fuel transfer from the center tank to the inner cells is controlled by inlet valves, which top up the inner cells while there’s still fuel in the center tank. After that, once one inner cells goes below a preset level, transfer valves open to allow fuel from the outer cells to flow into the inner cells. In addition to that, a crossfeed valve connects the left and right fuel systems, allowing both engines to be fed by both wing tanks, or one engine to be fed by both wing tanks in case of engine failure and single engine situation. Fuel transfer and valve operations work automatically during flight. The Flight Management System computes the best fuel load balancing in real time for the best aircraft performance. This was once the job of the Flight Engineer. Nowadays Airbus pilots are however always informed by ECAM messages, and can still manually operate on fuel transfer using the Overhead's FUEL panel. Now that we’ve demonstrated that fuel pumps may be useful for the engines, let’s switch them to ON! On the picture, left and center systems have already been set to ON. You'll notice that the center tank pumps show 'FAULT' : this is normal, since there's no fuel in the center tank needed for this new short flight. The next step is to start the APU. The APU (Auxiliary Power Unit) is a small, single spool (N) jet engine located in the aircraft tailcone. APU, which is now common with every modern airliner, allows the aircraft to be independent of external pneumatic and electrical power supplies. The APU can then provide bleed air for engine start and cabin air conditioning and has its own generator to provide AC electrical power (see above). APU can be started on the ground as well as in flight. Starting the APU works almost the same as switching on a lamp. Switching ON the APU MASTER SW button (blue "ON" illuminates) arms the APU system for automatic startup sequence and opens the APU air intake flap. Just below, the START button will initiate automatic startup. When completed, a green 'AVAIL' will illuminate and will also appear on the upper ECAM, meaning that APU is available. The latest image shows both upper and lower ECAM after APU start. Now that the APU is running, we can use its bleed air for engine start. High pressure air (as well as electrical power) is needed to start the main engines. Bleeding air into the engine will initiate the spool rotation until it reaches a preset rate at which ignition will occur. Some technical background about the jet engine is not superfluous here before going further. The turbofan jet engine which is powering our aircraft, as well as most of nowadays airliners, is an evolution of the twin spool turbojet engine. A spool is a couple compressor – turbine mounted on the same shaft, and then rotating at the same speed. The compressor and turbine are in most cases a succession of stages. Each stage includes a rotor grid which is integral with the shaft. The rotor grid is a disc fitted with a great number of rotor blades. In modern engines, the rotor blades pitch is variable as a function of the air flow to optimize performance. Each rotor grid is followed by a stator grid, whose purpose is to straighten up the flow to the axial direction of the engine. On most modern engines, the stator vanes pitch is also variable. Each grid will modify the air flow direction and speed. The intake air will cycle throughout the engine. On the basic single spool engine (like the one that powered the first generation Boeing 707 or DC8), the cycle includes the compression, combustion and expansion. During the cycle, air pressure, volume and temperature change, linked together following thermodynamics laws. The compressor will make the first step. Air pressure and temperature will increase. In the combustion chamber, which is inserted between the compressor and the turbine, compressed air will be mixed with fuel by a complex mixing system. The fuel combustion will considerably increase gasses temperature as well as volume, while pressure will remain almost constant. And finally, gasses will first expand in the turbine driving the compressor, and then complete their expansion in the nozzle, providing the rear thrust that will propel the aircraft in the opposite direction, as result of the well known reaction law. The temperature will decrease during the expansion phase, giving the exhaust gas temperature (EGT) which is an important engine parameter to be controlled by the pilots, with the turbine materials thermic constraints in mind. A dramatic and sudden increase of EGT will result of an engine fire. The twin spool turbojet (dating back to the sixties) has two concentric shafts rotating at different speeds. A good example is the PW JT8D engine, which powered many aircraft models including B727, B737-200, DC9 and MD80. The low pressure spool (N1) includes the low pressure (LP) compressor and the low pressure turbine. The high pressure spool (N2), located between the LP compressor and the LP turbine, includes the high pressure (HP) compressor and the high pressure turbine. N1 spool rotation rate is often the main driving parameter of the engine, while N2 plays a part during engine start. As an example, take off rate on the CFM56-3B1 (powering the B737-300 and A320 families) will bring N1 to 5175 RPM and N2 to 14460 RPM. Meanwhile, N1 and N2 rotation rates will not be directly displayed as RPM (revolutions per minute) in the flight deck but as a percentage of a maximum rate. Jet engines are characterized by two maximum rates: the maximum take off performance (TO), which is the highest, but limited to a 5 minutes time interval; and the maxi-continuous performance (MCT), which is lower but unlimited in time. Because the gauge range exceeds 100% for the engine rate, this is probably the MCT constant that is used as reference. The intake air is sucked in by the LP compressor. Unlike on the single spool engine, a part of the intake air will be derivated during the LP compression phase and will NOT be driven to the combustion chamber, therefore bypassing the normal cycle. There are then two air flows on such engine: the cold stream that bypasses the hot gasses generator and the hot stream which goes through the normal cycle. This introduces a new parameter: the bypass ratio, which is defined as the ratio between the derivated air quantity and the normal cycle air quantity, and can then be seen as cold stream air quantity hot stream air quantity. For a twin spool turbojet, the bypass ratio is roughly equal to 1. Note that for a single spool engine, it will be equal to zero. We can demonstrate that increasing the bypass ratio will increase engine performance, reduce fuel burn as well as engine noise. The turbofan engine is a direct application of that concept. In a turbofan, the first stage of the LP compressor, which sucks in the total intake air, is an oversized rotor grid, called the fan. The first turbofans powered the B747, DC10 and L1011 Tristar in the seventies, to be followed by the Airbus A300-B1. The bypass ratio, as well as the compression rate are greatly improved. The bypass ratio of the first turbofans was close to 5. The big turbofans of the new generation have a bypass ratio equal to 6, with a fan diameter close to 3 m. The General Electric/Pratt & Whitney GP 7200 and Rolls Royce Trent 900, designed for the A380, are currently the biggest and the most efficient engines on the market. The global thrust provided by such engines is mainly provided by the fan. The fan produces from 70 to 75 % of the engine thrust. It can then also be seen as a streamlined propeller driven by a first generation twin spool turbojet. Besides, only the fan blowed cold stream air will be used by the reverser system. Rolls Royce engines have a distinctive feature: they have 3 spools: N1 (LP), N2 (IP for Intermediate Pressure) and N3 (HP). In this case, the fan acts as the LP compressor on its own. The following diagram shows a generic twin spool turbofan engine longitudinal section, where you'll easily locate many of the components that were introduced here. Aircraft engine performance evolution always sees greater bypass ratio, greater pressions, greater temperatures, lower noise emissions, lower fuel burn and lower environmental impact. For example, higher temperatures in the turbine inlet (approaching 1500°C) are nowadays possible thanks to better materials as well as a complex cooling system allowing the blades to work above their melting point. The fan size, and therefore the bypass ratio, however, have a upper limit. The engine cannot grow indefinitely since it must still be able to be installed on the aircraft and the bigger is the fan, the greater will be its aerodynamic drag. Now that we're more familiar with the jet engine – and if you are wondering whether we'll once reach Tel Aviv – let's continue with the startup sequence. We'll perform an automatic start using the APU bleed air for both engines. Engine start usually takes place during the aircraft pushback. Switching ON the APU BLEED (overhead AIR conditioning panel) will allow blowing high pressure air into the engine, and more precisely, into the High Pressure spool N2 (that would be N3 on a RR engine). On the A330, engine #1 (left wing) is usually started first. Not difficult to remember anyway. Checking APU BLEED is ON, we set the ENG START selector to IGN/START on the pedestal. Next, we set the ENG MASTER switch 1 to ON. N2 spool will start rotating (monitor N2 rate increase on the upper ECAM). Once N2 reaches a preset rate, which is commonly 20% for every jet airliner, fuel is injected into the combustion chamber and ignition occurs, the complete engine cycle can start. While opening the fuel cutoff lever for each engine is necessary on Boeing planes, fuel injection will be done automatically here at 20% N2 and pilots just have nothing more to do. Engine 1 startup. Note the light smoke. Once engine 1 is stable (monitor N1, EGT, N2 and fuel flow on the upper ECAM ), setting ON the ENG MASTER switch 2 will start engine 2 in the same way. The following picture shows the E/WD (upper ECAM) once both engines are started and pushback is completed. ENG START selector is then set back to NORM mode. APU bleed is switched off, but we will leave APU running until we're airborne and above 10,000 feet. APU & APU BLEED should be started again after landing, so that the aircraft can still be powered after engine shutdown. So, if we sum up, to start the engines of our A330 we just had to 1) set BAT 1, BAT 2, APU BAT to ON 2) switch ON the fuel pumps 3) start the APU 4) check APU GEN, ENG 1 GEN, ENG 2 GEN "no light" 5) set APU BLEED to ON 6) set engine start selector to IGN/START 7) set ENG MASTER switch 1 to ON once engine #1 stable, set the ENG MASTER switch 2 to ON 9) once engine #2 stable, set the engine start selector back to NORM 10) set APU BLEED to OFF Busy runway 21L holding point: Iberia A320, ATR42 and B737-300 from Olympic and a further Learjet will leave before us. Because of the very brief engine start explanations, this picture's purpose is only to remind that we didn't forget to start the engines. Take off completed, left turn towards VARIX Greek coast – farewell to Europe. Being eastbound, approach to Tel Aviv is easier than parking your car between two others. According to Jeppesen SimCharts 2004 database, there are no published STARs for Ben Gurion airport. The approach begins at SIRON, last fix of the flight plan and located right on runway 12 axis. We're then directly bound on the final leg, and incidentally overflying the whole city. The descent. Approaching SIRON. A second sunset approach is on its way. A major clouds and light effects upgrade was one of the best FS2004 new features. Tel Aviv – Jaffa by night. Established on the BG ILS, airport and runway in sight! Welcome to the Holy land. The following sequence 1) set ENG MASTER switch 1 to OFF 2) set ENG MASTER switch 2 to OFF 3) switch off the fuel pumps 4) switch off APU BLEED 5) set APU MASTER SW to OFF 6) switch BAT1, BAT2, APU BAT to OFF ... will shut down the engines and come back to the 'cold and dark' situation. Leg 12: Tel Aviv, Israel – Tehran, Iran Though political matters are not to be discussed in this round the world trip review, this 12th leg linking the two countries by the air has of course some symbolic meaning. Also taking in mind the real world events for realism purposes, the flight path, which is avoiding Lebanese and Iraki airspace, will not really look like a straight line: The following flight plan was made using an old Jeppesen HI/LOW altitude enroute chart for the Middle East, dating back to 1997! ... but its waypoints were though 'digested' by the MCDU. From TEL AVIV-BEN GURION (TLV/LLBG) to TEHRAN-MEHRABAD INTL (THR/OIII) Alternate OIFM ESFAHAN LLBG NAT3C NAT J15 ATLIT GALIM H4A DAVAR ATS TIROS UB17 VELOX UR18 ALSUS UR78 NIKAS R55 BAN W6 ALE H55 TUSYR VB36 GAZ UVW701D EZS VG81 UMH G8 ZAJ R11 MIVAK MIVAK1A OIII The flight plan flies over Aleppo in Syria; Elazig, Van and Uromiyeh in Turkey and then Zanjan in Iran. At Tehran, the usual ILS approach to runway 29L will be followed. But it's now time to reveal the new livery of the aircraft! I guess you cannot wait any more, so here it is! Yes I was really bored with the previous painting and I wanted something else. Only the tail logo, winglets and engines painting remain the same. Talking about the engines, you've probably noticed that they have changed also. Our A330, a brand new aircraft actually, is now powered by Rolls Royce engines. The aircraft was ferried from Toulouse via Brussels to carry on with the round the world trip (the ferry flight is not related in this article – it is quite long enough!). Airbus A330 customers have the choice between three engine variants to fit out their aircraft: General Electric CF6, Pratt & Whitney PW4168 or Rolls Royce Trent 700 turbofans. The RR Trent engines powering the Airbus A330 provide 302.5 kN (68,000 lbs) thrust and are a little more powerful than the GE CF6 engines. They have also a typical complete streamlining with a common exhaust nozzle which helps the exhaust gasses (cold and hot streams) mixing with noise reduction purposes. The reverser system is also different (we'll see it in action in a following leg). As we've said above, RR engines have a three spool system N1, N2, N3. Don't worry, I will NOT resume the whole engine start sequence with these new engines: it remains exactly the same if we specify that the high pressure spool is now N3, instead of N2. The main engine driving parameter, however, is no more the N1 rate but a parameter called EPR or Engine Pressure Ratio. EPR is defined as the ratio between the total pressure at the turbine exhaust and the total pressure at the compressor intake (for a turbofan engine, that will be the fan intake). We can then see EPR as hot stream pressure EPR = ──────────── intake air pressure. Note that on the ground, if the engine is stopped, both pressures will be equal to the atmospheric pressure and we'll have EPR = 1. During normal engine operation, EPR is greater than 1. If one engine is stopped during flight, we'll have EPR < 1. Upper ECAM showing the RR engine parameters during engine 2 start. Note: the "N.WHEEL STRG DISC" warning message is normal and means that the nose wheel steering is disconnected during pushback. The ND in ARC mode showing the route that goes round Lebanese and Iraki airspace. Over the Zagros mounts @ 35,000 feet, 140 miles ahead of Zanjan Reproduced with permission of Jeppesen Sanderson, Inc. NOT FOR NAVIGATIONAL USE ©Jeppesen Sanderson, Inc. 2006 Reduced for illustrative purposes only For ILS approach to runway 29L, we'll come from Rudeshur NDB on the MIVAK1A standard arrival. Right-sitting passengers will enjoy the Tehran scenery on final. Note the rather high elevation of the airfield Base leg at 7200 feet, turning left to final and descending to 6600 feet. The 5036 foot hill visible on the chart just below the approach path appears on the left shot. Tehran is built at the foot of the Elburz Mounts, the city is smoothly rising towards the mountain. The city heights benefit from less air pollution and cooler temperature in the summer, this is also where the lucky comfortably off people live. Fully established on the ILS. Leg 13: Tehran, Iran – Dubai, United Arab Emirates Last destination in the Middle East for this 13th leg, Dubai is one of the most modern cities in the area, its skyscrapers seem to have sprung up from the desert as a symbol of the wealth provided by the oil industry. Because of the foreseen depletion of the oil reserves in the medium term, Dubai is already turned to the future with the development of other resources like tourism, trade and new technologies. The flight plan is far more direct this time, a 678 mile line crossing Iran with the cities of Esfahan and Shiraz, then a short crossing of the Persian Gulf. The alternate airport, Sharjah, is so close to Dubai Int'l that it should not be mistaken with it! Dubai approach is similar to and as easy as Tel Aviv's. From TEHRAN-MEHRABAD INTL (THR/OIII) to DUBAI INTL (DXB/OMDB) Alternate OMSJ SHARJAH OIII RABAM1A RABAM UP574 PAPAR LOPEG LOPEG1V OMDB The final approach seen from the ground... ... and the flight deck, flying the RNAV ILS Rwy 12L. Dubai skyline for this fourth sunset – unfortunately, some textures are missing. Our virtual logo lined up with the real Emirates and Saudi Arabian ones. Leg 14: Dubai, United Arab Emirates – Kathmandu, Nepal Back to more tricky approaches on this 14th leg, Kathmandu is located in the Himalayas' spurs and is therefore surrounded by mountains. Probably because of the very poor means of the country, Tribhuvan airport doesn't provide any ILS equipment but only one VOR/DME approach. Icing on the cake, the latter VOR/DME was not working in the FS2004 scenery. Not very serious though, since the Airbus onboard navigation system can provide all the distance and bearing information we need through the NAV display. Flight Plan From DUBAI INTL (DXB/OMDB) to KATHMANDU/TRIBHUVAN INTL (KTM/VNKT) Alternate VECC KOLKATA OMDB EGSOS ULUPO NADNI A791 JI G214 RK G452 TIGER G452E DPN R460E LLK G589 SMR SIMARA VNKT The flight passes over southern Iran, Pakistan, then Delhi and Lucknow in India. The SIMARA standard arrival from SMR VOR will lead to NOPEN intersection, that should be crossed at 11,500 feet. Sunrise over India Reproduced with permission of Jeppesen Sanderson, Inc. NOT FOR NAVIGATIONAL USE ©Jeppesen Sanderson, Inc. 2006 Reduced for illustrative purposes only NOPEN is precisely the initial approach fix for the VOR DME Rwy 02, which is the only available landing runway here. The (out of order) KTM VOR/DME being almost located on the airport (0.6 mile ahead of runway threshold), the 'VNKT' last waypoint of the flight plan – the destination airport itself – will play that role. After flying this leg, I realised that choosing the KTM VOR (if absent from FS2004 scenery, still there in the PSS MCDU database!) instead was of course better, but the most obvious ideas sometimes don't come when they should. Nevertheless, we'll only depend on the information provided by the aircraft navigation system – a wrong IRS alignment, in fact, would be deadly in this case. In real life, the aircraft would probably have to divert to the alternate, but once again, we are just simming here: the approach can be carried on, the virtual electronic system has 100% reliability. Looking closer to the approach chart, this is actually not the most difficult one. Just a level descent with no offset – the main difficulty here, with no ILS signal, is that there's no glideslope to tell us if we are 'too low' or 'too high' precisely. From NOPEN, which is crossed at 11,500 feet thanks to an altitude constraint inserted in the flight plan, we'll use the autopilot selected mode to comply with the approach descent profile. Once the runway is in sight, we'll conclude with a visual approach. To do this, however, we will have to comply with the minimums specified at the bottom of the approach chart. First, the Minimum Descent Altitude (MDA), 5120 feet in our case (meaning only 807 feet above ground in the local terrain configuration), is the altitude in a non-precision approach below which descent may not be carried on without visual reference. Also, cloud ceiling must not be below 800 feet and visibility must be greater than 1500 meters. We'll see that all these conditions will be gathered. NOPEN is behind, approach begins. Scattered clouds with ceiling at at 6000'. Between D13.0 and D10.0 fixes, descending to 9500' (AP selected mode). We are lucky: airport already in sight in the cloud break! Back to the right passenger view when we reach the 9500' level. Visual approach, autopilot off. We're now below the MDA, but with full visual reference. Still too high and too fast: note the 4 white PAPI lights and the rather high descent rate. This looks better. PFD speed tape: the managed final approach speed of 140 kts will be reached just before touchdown! Leg 15: Kathmandu, Nepal – Phuket, Thailand The first exotic destination for leg 15, Phuket is often associated with a distant paradise for western tourists, but was also badly hit by December 26, 2004 tidal wave. To take off from Kathmandu, a special standard departure must be observed. A bit like for Sion in the first part and Ajaccio in the second one, aircraft must first execute a loop to get some altitude and get clear of terrain. With take off from runway 02, the IGRIS One Bravo SID (which is here plotted on the terrain map provided by FS2004) is first a left turn that proceeds along (or remain within) a 5 miles distance arc from KTM VOR, this time included in the flight plan. IGRIS intersection, at the end of the procedure, must be crossed at or above 10,500 feet. The SID also requires a minimum climb gradient which is easily observed by the A330, still far below its MTOW for this medium haul flight. From KATHMANDU/TRIBHUVAN INTL (KTM/VNKT) to PHUKET INTL (HKT/VTSP) Alternate VTSS SONGKHLA VNKT IGRIS1B IGRIS D20KTM R325 CEA M770A BUBKO M770R OBMOG L515R IKULA LANNO LANNO1A VTSP IGRIS1B SID: flying the 5 DME arc On the KTM – IGRIS leg, already above 10,500 feet with the Himalayas' peaks in the distance. SID completed, passing IGRIS. Thrust reverse in action after landing in Phuket with the VOR DME runway 09 approach. Taxiing to the gate while another wide body takes off from the same runway. Leg 16: Phuket, Thailand – Hong Kong, PR of China Back to a beautiful (and freeware!) photographic scenery to conclude this third part, I'll provide many screenshots all the approach long to the new Chek Lap Kok airport of Hong Kong. The former Hong Kong international airport, Kai Tak, now closed and located in the city center, used to be the pilots' nightmare with the most dangerous approach worldwide. The new airport is built on an artificial island some 20 miles west of the old one and offers far more conventional approaches. Westbound approaches, however, like the one that will take place here, have their paths going through a very mountainous landscape. Flight Plan From PHUKET INTL (HKT/VTSP) to HONG KONG INTL (HKG/VHHH) Alternate VMMC MACAU VTSP STN1A STN W10 BKK A1 DAGON DAGON1B VHHH The route includes Bangkok in Thailand and Danang in Vietnam, then the South China Sea. The DAGON One Bravo standard arrival ends at Tung Lung VOR where the ILS Rwy 25L approach will begin. I set cloudy weather in Hong Kong, a usual fact here, but with a good visibility in a way to enjoy the view. Reproduced with permission of Jeppesen Sanderson, Inc. NOT FOR NAVIGATIONAL USE ©Jeppesen Sanderson, Inc. 2006 Reduced for illustrative purposes only Approach base leg @ 7000', 2.3 nm from TD VOR, descending to 4500' Proceeding on the base leg, now @ 5700', 3.7 miles from TD VOR, with the former Kai Tak airport in sight. Between TOLOE and LOTUS: localizer capture @ 4500' Now on final – this beautiful scenery uses the Google Earth free version textures. At 3900' with the mountain located north of the final approach corridor under the right wing At 3170', 10 miles from destination Less than 8 miles to go, airport in sight. 'Horizon 2006 heavy, cleared to land runway 25L, follow the Boeing triple seven on the runway' The preceding aircraft (right) has vacated the runway, landing can be carried on. A few seconds from touchdown Just like the first shot of the leg, but 1422 miles or 2630 km farther. This concludes Around the World 2006-2007 Part 3. In the next one that will travel across Oceania and Pacific we'll have the opportunity to fly the first true long range sectors, while other aircraft systems and further cockpit preparation will be introduced. Any comments or questions about these flight reviews are still greatly appreciated. Cédric De Keyser (Belgium) cdk@ngi.be
  12. Part 2: Visiting Europe (South) This article proceeds with the around the world flight project on an Airbus A330-200 that was introduced sooner in Part 1 and will now visit some popular destinations around the Mediterranean. Prior to going further on the following legs, I wish to mention that because the trip began in the second half of year 2006 and each stage (mainly including flights, flight reports, and then online publishing) tends to take more time than expected, “Around the World 2006” could then probably last until spring or summer 2007! Please don’t close this window though, I guarantee that we are making this round the world trip flying a plane, not driving a car or even walking! Leg 4: Geneva, Switzerland – Nice, France After the rather eventful third leg and mountain flying in Switzerland, this following one could once again make the sick bags use topical for the most sensitive passengers – for the very last part only, as we will perform a special approach and strong crosswind landing at Nice. This 4th leg will start at dawn But before boarding the ship again, let’s talk a little about our aircraft loading. Aircraft weights are very important parameters which are indispensable for the Flight Management System initialization process made before each flight. First of all, let’s consider the passenger & baggage payload. We’ll use the Load Editor kindly provided by PSS, which is a simplified software calculating the aircraft Zero Fuel Weight. We’ve selected the A330-200 powered by GE engines, in two class configuration as aircraft model. Please note however that we’re actually flying a Project Open Sky aircraft, and not the model provided by PSS – the ZFW calculated here is correct but will then slightly vary from the figure used in the simulation. 217 passengers are seating in economy class – all the passengers actually for this special trip, since the business class has been accomodated as rest room for all the flight attendants, tour guides and reserve pilots, 26 people in all. In the underbelly we have 16.7 tonnes of baggage and no cargo. The load editor then computes our 155 tonnes or so Zero Fuel Weight. With an empty weight of 120.3 tonnes, that means a payload of a bit less than 35 tonnes. Aircraft loading has actually been slightly adjusted to obtain these round figures, which will have to be each time set in the MCDU as well as the FS2004 payload manager (working independantly). We’ll assume that this ZFW will remain the same all along the trip, unless we lose some passengers or baggage on the way. The second step is of course considering the fuel, unless we plan to use our A330 as a glider from origin to destination. For our short flight from Geneva to Nice, following the flight plan displayed below and taking additional reserves in mind, we need 9 tonnes of fuel (detailed fuel planning will be introduced in a following article). The Zero Fuel Weight (ZFW) and fuel quantity are the only weights needed by the MCDU in the initialization process. Though the initial total fuel quantity (block) is physically measured by fuel gauges in the tanks and displayed on the lower ECAM (SD) fuel page, it must also be manually entered in the MCDU. The latter then computes an estimation of the Take-Off Weight (TOW) and Landing Weight (LW). Pilots must check that they are beyond the aircraft maximum tolerances. MCDU INIT page #2, where ZFW and Fuel Qty (BLOCK) are entered. We'll keep the default 0.2 T value given for Taxi Fuel. If a valid flight plan is loaded, Takeoff Weight and Landing Weight are then computed by the FMS, as well as Trip Fuel and Time. Lower ECAM FUEL page, before engine start. FOB (Fuel On Board) displays the total fuel quantity, which is equal to the BLOCK value before the flight. Aircraft Gross Weight (GW) will appear on every SD page. Note: Fuel Used figures are wrong and should show 0. This is probably due to a light dissension between PSS and FS2004 software. So, let’s sum up (you may refer to the aircraft technical characteristics that were given in the Part 1 introduction) : ZFW = Empty weight + Payload = 120.3 + 34.9 = 155.2 T (MZFW 168 T) Initial Fuel Qty = BLOCK = 9 T GW = ZFW + BLOCK = 155.2 + 9 = 164.2 T or 164200 Kg TOW = GW – Taxi Fuel = 164.2 – 0.2 = 164 T (MTOW 230 T) Trip Fuel = 6.4 T LW = TOW – Trip Fuel = 164 – 6.4 = 157.6 T (MLW 180 T) Further cockpit preparation will also be introduced in the following legs and articles, but let’s now go back to our flight. We will take off from runway 23 and follow the BALSI One Alfa SID connecting to the UN852 airway. We’ll level off at 23,000 feet but not for a long time. At Nice, we may expect a strong wind from the south and a special visual approach procedure. Flight Plan From GENEVA (LSGG/GVA) to NICE/COTE D’AZUR (LFMN/NCE) Alternate LFML MARSEILLE/PROVENCE LSGG BALSI1A BALSI UN852 GIROL UY30 MEDOK AMFOU AMFOU3R LFMN PFD and ND seen during the Standard Departure. We’re this time in the CLB managed vertical guidance mode, in which the flight plan speed and altitude constraints are honored during climb. We’ve just passed 10,000’, and then now accelerating to the managed target airspeed of 298 kts from our previous 250 kts IAS. The ND, set in ARC mode, displays navigational information in the sector ahead of the aircraft. With the 160 miles range set here, we can nearly see the entire (short) active flight plan. The blue and white arrows respectively show the Top of climb and Top of descent points, whose positions are automatically calculated by the FMS. Circles are drawn around waypoints with associated constraints. The closest French airport is currently Lyon – Saint Exupéry (LFLL), some 40 miles northeast. Sunrise over the somewhat hazy French Alps. Chambéry and the tip of Lac du Bourget down there With its 420,000 residents, Grenoble is the only European important city (as well as Innsbruck in Austria) to be surrounded by high mountains. Seen from the sky, the built-up area seems to be split in half by the Chartreuse massif. Nice/Cote d’Azur airport has two parallel runways, 04L/22R and 04R/22L. Runways 04L and 04R are equipped with ILS since they are the most commonly used runways for landing. Today, however, a 20 kts south wind with gusts at 40 kts (75 km/h), known as “sirocco” in the Mediterranean area, will make us land on runway 22L. In this way, we’ll fly the special BLUE BAY procedure, which is a curved visual approach avoiding high terrain less than 3 miles from runway treshold. Reproduced with permission of Jeppesen Sanderson, Inc. NOT FOR NAVIGATIONAL USE ©Jeppesen Sanderson, Inc. 2006 Reduced for illustrative purposes only As we may see on the chart, the visual approach begins at “D5.1 NI”, close to the November Charlie NDB. In fact, the first part of the approach will lean on the AMFOU 3R Standard arrival directly followed by the ILS DME Rwy 04L (045° 109.95 NI). Once being on the localizer and reading 5.1 miles from runway treshold (D5.1 NI), we switch to the BLUE BAY visual procedure for runway 22L. A shown on the shart, we should keep the useful distance information provided by the DME throughout the approach. Of course, I realised that the DME was not working during the simulation. A software surprise probably thought in a way to make things more spicy – this could meanwhile also happen in real life. I decided to carry on the approach, using the November Charlie NDB instead of D5.1 NI, then visual reference only, following the topographical information provided by the chart and starting the turn back a little while after abeam threshold 22L. The result was some kind of a 11/20 marked landing, with a steep descent rate on final, difficulties to align with the runway and late touchdown. The crosswind had naturally got something to do with it. Runway 22L is nearly 3 kilometers long so hopefully we could safely stop and even vacate it before the last taxiway. Last turn, joining the 225° track. The four PAPI lights are white, we’re then still too high. Close-up on the NAV display once on final. The yellow index shows the actual aircraft heading while the green diamond displays current aircraft ground track, which is different from heading in this particular crosswind condition. Present wind is at 25 kts, coming from the 176° sector, which is roughly the South. You may also see the difference between the Ground speed (GS) and True airspeed (TAS). Not the best trajectory indeed. In the meantime, an Easyjet 737 is taking off from Rwy 22R. The 11/20 landing. Note the bank angle of the aircraft: left main gear has only just touched down, while the nose gear is still in the air. Because of the late touchdown, reversers are already in action. Welcome to the French riviera. The following leg will be (at least) somewhat quieter. Leg 5: Nice, France – Madrid, Spain For this leg, I wish to introduce the MCDU programming concerning the flight plan. This Nice to Madrid route will then be used as an example, but the process will remain analog for any other route. The flight plan has been made using Jeppesen enroute charts, as said in the introduction. In real life operations, pilots usually get a computed flight plan dispatched by a ground service, but they will always take the classic paper enroute charts covering their flight with them on the flight deck. The computed flight plan sheet includes several technical information and figures (such as fuel planning, time, alternate info, waypoints coordinates, altitudes, etc.), but the scheduled route will always have the following appearance (given here for our current flight): LFMN STP9W STP UT24 PADKO UM984 DIVKO UN852 MAMES UN975 RAMON UH120 TERSA TERSA1B LEMD At the ends of the sequence are the ICAO (the International Civil Aviation Organization) 4-letter codes for departure and destination airports: LFMN for NICE/COTE D’AZUR and LEMD for MADRID/BARAJAS If a Standard Instrument Departure (SID) is observed, it will appear directly after the departure airport. This is well the case now: we will take off from runway 22R and fly the SAINT-TROPEZ 9 Whisky SID, which doesn’t leads directly to the Saint-Tropez VOR (STP) but makes a few turns over the sea in a view to get some altitude, probably because of security and noise abatement reasons. From STP, we’ll follow the high altitude airways until reaching the last waypoint of the route. If we remain on the same airway through several waypoints, they will not appear in the flight plan sequence. For example, there are several waypoints between MAMES and RAMON but they’re all located on the UN975 airway. This is very useful for the Flight Management System programming: we only have to specify the airway and its own database will insert the intermediate waypoints, assuming that we enter a valid waypoint/airway combination. In some cases, we can remain on the same airway during hundreds of miles and cross nearly the whole of Europe! Waypoints are now in most of cases 4-letter intersections that are not physical ground objects but simply geographical coordinates. VOR (for Very high frequency Omnidirectional Radio range) equipment is still topical on the continents, but the better and better accuracy of aircraft onboard navigation systems (IRS and GPS systems that’ll be tackled at the end of this series) has now made them less indispensable during enroute flight in modern airliners. TERSA intersection is the last waypoint of the flight plan. From there, we’ll fly the TERSA 1 Bravo Standard Arrival, leading to the Perales VOR (PDT), right on runway 33 axis. ILS Rwy 33 approach will conclude this flight. So, let’s see now how we put this data into the MCDU: The MCDU, seen here entirely, is then the pilot’s interface with the Flight Management System. It contains a display screen, line select keys (LSK) and a keyboard. It will always have this basic configuration, whatever aircraft type. If we look closer, however, available pages, keys and functions will vary from one aircraft manufacturer to another. In that way, it is quite different from Boeing’s FMC. The “PROG” page, for example, does not provide the same information as the “Progress” page typical with Boeing. The keyboard input appears on the bottom line, called the scratchpad. Left (1-6L) and right (1-6R) LSK are used to insert information from scratchpad into corresponding field. On the INIT Page, Subpage #1 shown here, we must insert the departure and destination airports, alternate airport (Madrid – Torrejon in this case). Flight number, cost index (see later) and cruise altitude can be inserted here also. LAT and LONG fields contain the origin airport/parking stand geographical coordinates needed for IRS alignment. Though they must be filled in by pilots in real life (the data appearing on the airport diagram chart), FS2004 kindly provides the exact figures automatically. If we push the F-PLAN key, we’ll access the flightplan main page. We can then take care of the route and come back to the other important MCDU preparation later (weight, fuel, performance, etc.). Origin and destination airports only appear now. The scheduled flight plan must be filled in between them. The MCDU though already computes the distance between LFMN and LEMD. In fact, it calculates the great circle arc using the coordinates of origin and destinations airports available in its database. Great circles are intersections between the Earth sphere and planes passing by its center. A plane is entirely defined by 3 points, which are the origin, destination and Earth center in this case. The great circle arc is then the shortest way from two points located on the Earth’s surface. Though airways, and in particular the oceanic and polar routes try to lean on great circles, they’ll always provide longer paths. Once our flight plan will be completed, we’ll find a greater distance than the now indicated 516 nautical miles. To insert the Standard Departure, we press the LSK 1L to access the available runways and SIDs for Madrid – Barajas. This introduces another difference with Boeing, where departure and arrival information is specified through a different page (DEP/ARR). Once on the Departures subpage, we select the desired runway pressing LSK 5L. The MCDU will then display the available SIDs for the selected runway. We select the STP9W SID and then insert it in the active flight plan by pressing LSK 6R. Back to the flight plan main page, we see that several waypoints generated by the SID have been added. Speed and/or altitude constraints are automatically added also. Now, let’s see how we insert the waypoints and airways. The flight plan has been completed up to MAMES waypoint. From there, we want to fly to RAMON. If flying directly, we would just have to type RAMON on the scratchpad and then insert it after MAMES using LSK 3L. But we have to follow the UN975 airway; this is as simple as that: once pressing LSK 2L... ... we access the Lateral Revision subpage from MAMES where we use the VIA/GO TO entry: we want to go to RAMON via the UN975 airway, so we type UN975/RAMON on the scratchpad and insert it pressing LSK 2R. The MCDU then goes back to the main flight plan page, which is now displayed in yellow meaning that this is a temporary flight plan. To make it become active, we must still press LSK 6R. The “INSERT” function of the MCDU is similar to the Boeing FMC’s “EXEC” key. Once the insertion is confirmed, we come back to our active flight plan and we see that several waypoints have been added, leading to RAMON.We may even check that on the ND, set in PLAN mode. And we proceed like this up to TERSA. From there, we select the ILS 33 and the TERSA1B STAR in the same way as for the departure. Selecting the expected landing runway is important since the MCDU will also set the ILS frequency, if available, as well as the ND course (equal to runway heading) automatically. Once the STAR is inserted, we delete a possible last discontinuity before LEMD using the CLR key, and this completes the flight plan. A good thing to do is to save it, so that we may call it back if we unfortunately encounter a software problem or whatever and have to resume the whole flight. Once we’ve filled in the INIT pages completely (inserting ZFW and BLOCK, as explained in the previous leg), the MCDU will fill in all the remaining dashed fields, showing the estimated speed/altitude at which every waypoint shall be crossed, as well as flight time, route distance (now showing the greater value of 566 miles) and estimated fuel on board at destination (EFOB). Once airborne, the flight time (showing here 1 hour and 24 minutes) will switch to the Estimated Time of Arrival (ETA), using GMT (Zulu) reference. EFOB is often underestimated before the flight and should show higher values once reaching cruise altitude and speed. The information provided by this FLIGHT PLAN page is now similar to the Boeing’s FMC PROGRESS page. Another interesting feature to point out here: while the same page (F-PLAN) provides both flight plan editing and “progress” information with Airbus, these different functions are monitored by two distinct pages (LEGS and PROG) with Boeing. And let’s go back to live screenshots now. This flight was uneventful as expected – we could however enjoy a zenithal view of Barcelona and the arid landscape of Castile on the approach. Reaching the holding point for runway 22R. Aircraft spotters (only) would feel in Heaven in the background buildings. Crossing BCN VOR – Barcelona shore from 31,000 ft! Madrid-Barajas approach: a few miles before Perales VOR Landing runway 33, which is crossed by runway 36R also visible here. Last meter of the flight. The marshaller (the yellow guy between the Iberia plane and ours) looks really small in front of the A330 machine! Leg 6: Madrid, Spain – Malaga, Spain The second Spanish destination of our trip is probably Costa del Sol’s most popular spot; approach into Malaga will also provide us typical views of Andalusia landscape. We’ll take off at dawn, observing an initial climb-out preliminary SID from the new 36L runway. Flight plan From MADRID-BARAJAS (LEMD/MAD) to MALAGA (LEMG/AGP) Alternate LEAL ALMERIA LEMD MONTO3W MONTO UN864 BAMAR LEMG Reproduced with permission of Jeppesen Sanderson, Inc. NOT FOR NAVIGATIONAL USE ©Jeppesen Sanderson, Inc. 2006 Reduced for illustrative purposes only The SID and its initial climb-out phase can be programmed in the MCDU, which will also insert the same speed and altitude constraints as the ones specified on the chart (see above). Using autopilot managed vertical guidance (CLB mode), managed lateral guidance (NAV mode) and managed speed after take off will make the aircraft follow the correct path and remain beyond speed restrictions, so that pilots can concentrate on other important things such as the latest news. Joking apart, the approach into Malaga will be the ILS DME-Alpha Rwy 14, the localizer being captured just after BAMAR IAF. A routine procedure, though we have some high terrain in both sides of the approach corridor. MCDU F-PLAN page once the SID has been inserted. Speed and altitude constraints corresponding to the chart’s specifications are displayed in red Taxiing out in front of the Iberia maintenance hangars. Holding point runway 36L. Lining up. Note the SID legs and altitude constraints on the ND. The 240 kts speed limit in the initial climb is represented by the magenta dot. Malaga approach: approaching BAMAR Final runway 14 Outside temperature: 30°C! Leg 7: Malaga, Spain – Ibiza, Balearic Islands, Spain For this new short flight, we’ll enjoy the first sunset arrival of our trip. Ibiza, one of the three main Balearic islands (the second one in size after Mallorca), has been a well known holiday destination in the Mediterranean since the first charters arrived there in the early seventies. Being nowadays world famous for its night life, Ibiza is known as the “party island” and must certainly be a more pleasant place than London Underground's disused stations. Flight plan From MALAGA (LEMG/AGP) to IBIZA (LEIB/IBZ) Alternate LEPA PALMA DE MALLORCA LEMG MGA UN851 BRUNO BRUNO1N LEIB The departure procedure from runway 14 will first lean on the LOJAS One Alfa SID, but will leave the latter once crossing Malaga VOR (MGA) and proceed on the UN851 airway. That will make us fly runway heading until being 9 miles away from the airport, then turn back to MGA and then head towards Alicante, crossing the Sierra Nevada mountains. Powerful takeoff - Already above 1000 feet. Proceeding on runway heading. The BRUNO One November STAR ends at Ibiza NDB (IBZ) – from there, we turn back above the sea and proceed with the ILS Rwy 24 approach. The nice approach chart that displays nearly the entire island is also provided here. Reproduced with permission of Jeppesen Sanderson, Inc. NOT FOR NAVIGATIONAL USE ©Jeppesen Sanderson, Inc. 2006 Reduced for illustrative purposes only Ibiza ILS Rwy 24 approach – arriving from the west, we’ll have to follow the holding pattern from IBZ NDB prior to reaching runway axis. Approaching IBZ NDB, still in full AP managed modes. The airport is straight ahead. Short final, with a light crosswind. Flying manual, but autothrust still engaged. Nice modeling of Ibiza airport and vegetation here Leg 8: Ibiza, Balearic Islands, Spain – Ajaccio, Corsica, France Let’s proceed with holiday destinations in this 8th leg. Corsica, called “The island of beauty”, enjoys both French and Italian influence, though keeping its own identity and a strong independance feeling. The great hikes that can be made in its mountains are famous. Flight Plan From IBIZA (LEIB/IBZ) to AJACCIO-CAMPO DELL’ORO (AJA/LFKJ) Alternate LFKB BASTIA LEIB MJV1E MJV UN851 NEGAT HORRO LFKJ Takeoff runway 24 from Ibiza. The large water surfaces on the right of the picture are the Las Salinas saltbeds, which are filled with seawater that is dried by the sun and leaves the salt deposited ready for collection. Reproduced with permission of Jeppesen Sanderson, Inc. NOT FOR NAVIGATIONAL USE ©Jeppesen Sanderson, Inc. 2006 Reduced for illustrative purposes only For jetliners, runway 02 is the only available landing runway at Ajaccio, seeing the relief north of the airport. A rather common approach however, it will begin from the HORRO IAF in our case and then hug the coastline. Localizer capture at D5.4 AJO. Runway already in sight. Passenger... ... and outside view once established. Weather: obviously nothing significant to aviation! Short final, landing clearance, light crosswind. Ajaccio seems to be a French St Maarten! You’ll have to wait a little more though to see Maho beach, later scheduled in this journey. Leg 9: Ajaccio, Corsica, France – Lamezia Terme, Italy Further focusing on photographic sceneries with this 9th leg and proceeding with warm and sunny weather at the destination. Don’t worry, that will not remain like this during the entire trip. If the two remaining legs of this second part will also be mainly related with screenshots, we’ll come back to more technical explanations in Part 3, as there are still many systems and features to get a general view of. We have however stormy weather for our departure from Ajaccio. Take off is planned from runway 02, but is to be directly followed by a tight left turn back to the Ajaccio Bay to get clear of terrain. Once reading a 236° radial from a NDB (Non Directional Beacon) located on the airport, we’ll turn back again and proceed to Bastia, as specified on the BASTIA 2 Charlie SID. Standard departures in mountainous areas often look like this, the flight path making several loops before reaching the airway - this was already the case with Sion, visited in Part 1 of Around the World 2006. Flight Plan From AJACCIO/CAMPO DELL’ORO (AJA/LFKJ) to LAMEZIA-TERME (SUF/LICA) Alternate LIRN NAPLES LFKJ BTA2C BTA UM728 VENTO UL182 SOBRI B35 CDC LICA Size does matter...but ATC will let the Cessna single prop leave before us. Taxiing out to runway 02. Godzilla is airborne. Immediate left turn, back to the sea. Not a good moment to confuse LEFT with RIGHT anyway. U-turn completed, heading south and already approaching 6,000 feet Further climbing (now at 10,000 feet) and starting a second U-turn to proceed to Bastia Reaching FL270. The famous “GR20” footpath snakes somewhere below. About to leave Corsica and above Bastia-Poretta airport. Weather is already getting more clear! With this shot, you may also appreciate the perfect photographic resolution of the scenery. Reproduced with permission of Jeppesen Sanderson, Inc. NOT FOR NAVIGATIONAL USE ©Jeppesen Sanderson, Inc. 2006 Reduced for illustrative purposes only The approach to Lamezia will begin at CARAFFA VOR/DME – arriving from the west on the B35 airway bound directly to CDC (no STAR), ILS Rwy 28 will make us fly the third and last U-turn of the flight. Not a dangerous approach at all, but a colourful approach chart means though that there is high terrain in the vicnity of the airport and thus described track must be carefully observed. On the base leg, after passing D9.0 CDC and descending to 3500’ for localizer capture. Now fully established on LAM ILS. Welcome to Calabria, welcome to Italy! Leg 10: Lamezia Terme, Italy – Athens, Greece Last leg entirely located in Europe, and a latest opportunity to see some photographic scenery again, before coming back to more standard scenery design in Part 3. We will fly to the brand new Athens – Eleftherios Venizelos airport, built some 20 kms east of the urban area and now replacing the old Hellenikon single runway airport since March 2001. Flight Plan From LAMEZIA-TERME (SUF/LICA) to ATHENS-ELEFTHERIOS VENIZELOS (ATH/LGAV) Alternate LGTS THESSALONIKI LICA CDC5B CDC UL689 CRN UM601 RUTOM UG8 RILIN RILIN1C LGAV Take off runway 28. Left or right view, enjoy the beach! Turning back to CARAFFA VOR/DME. Caraffa is behind, still climbing. Still nice scenery below but... ... flight simulation does have limits. Left : Lamezia Terme Photo Real scenery (see credits). Right: FS2004 standard scenery. Athens approach, already ligned up with runway 03L. Note the usual smog layer above the city, located behind the hills. Interesting sun effect on short final Olympic kingdom. And we’ve now reached the end of Around the World 2006 Part 2. In the next one, we’ll begin flying longer and longer legs, proceeding to the Middle East and Asia. Cédric De Keyser Brussels, Belgium cdk@ngi.be
  13. Part 1: Introduction & Visiting Europe (North) Introduction I'm pleased to welcome you on a new virtual trip that will take us over the World and travel through some of the interesting features of what nowadays scenery, landscape and aircraft modeling can provide for PC flight simulation. At the dusk of the (long) Flight Simulator 2004 era (as the next FSX version is now released), we'll give a glance at several - payware or freeware - high quality scenery add-ons developed for FS2004 (including detailed airports, landclass, high resolution terrain mesh and photographic sceneries) but we'll also sometimes give the word to FS2004 standard scenery to see how Microsoft has done the job. We'll visit the five continents and the review will be split into eight parts, the first being the one you're reading now : Part 1 : Introduction & visiting Europe (North) Part 2 : Visiting Europe (South) Part 3 : Visiting Middle East & Asia Part 4 : Visiting Australia & Pacific Part 5 : Visiting North America Part 6 : Visiting Central America & The Caribbean Part 7 : Visiting South America Part 8 : Visiting Africa, Indian Ocean & return As you may see, we'll follow an easternly direction across the globe and naturally visit very different and even extreme locations that'll be revealed as soon as the trip progresses, but you can already have a rough idea of the whole stuff with the following map : Map source: Wikipedia free encyclopedia Some of you will perhaps notice that we'll visit countries where commercial operations are still possible in real life (at the time these lines are written) but that may be, in real life again, in conflict with other neighbouring or distant nations (which can also be visited in this journey). No political, religious or military matters will appear here as we will only care about interesting places, landscapes and the universal aspects of civil aviation. This journey is supposed to take place within the summer 2006 season but will probably last several months depending on my availability and unforeseen events. Passengers are prepared for a looong trip but they are virtual anyway and the advantage of virtual passengers is that they never complain in case of delay or any other trouble. The tour will have Brussels, Belgium as origin seeing that this is my home airport. The airline is purely fictional, and some of you may already know it since preceeding reviews. The whole trip will be made on a widebody Airbus A330-200 aircraft. As a counterpart to the high realism level of the sceneries, many efforts will be made to give as much realism as possible concerning the flight. In that way, we'll have, all over the review, the occasion to focus on some theorical aspects such as : aircraft systems, aircraft instruments, flight planning, Flight Management System, IFR procedures, TCAS, ETOPS, ... Many of that topics will be illustrated. Real life (looking like) approach charts will illustrate some of the procedures that'll be flown, and in particular dangerous approaches in mountainous areas. Besides, many screenshots will be given with embellishment purposes only, including my favourite passenger views. The theory that'll be set out in this series of articles is without any pretension and'll probably often look like elementary A, B, C for real airline pilots and even keen flightsimmers, but could nevertheless be less obvious for newcomers in the flight simulation community. For the most demanding among you, the whole "theory" should not be expected in the first articles, as they will probably be the most "pictorial" ones. We will have and take the time to share the technical stuff among the eight stories. In this one, we will however tackle Airbus general philosophy, (quickly) focus on some instruments and show some specific and official IFR procedures. Please note that because of off-line flying, I can only use MSFS standard ATC which diverges from official procedures in most of cases and doesn't handle oceanic clearances and holdings (at busy airports) either. No realistic ATC communications should then be expected here. For the same reason, the real weather function cannot be used and weather will each time be manually set by me using the "Customize weather" menus (clouds & precipitation, visibility, surface wind). Various weather situations will be generated along the flight, but fully realistic settings (eg. the realistic pressure according to the other weather settings) could lack in most of cases. On the other hand, I'll later provide you with realistic checklists. Horizon Dreams' A330 checklists sheet has been worked out considering real data coming from both Airtours International and SN Brussels Airlines (cockpit DVD's) checklists for the same aircraft type. An interesting and strange thing to point out here is that checklists procedures may vary from one airline to another for the very same aircraft type. This sheet, whom different stages will be detailed later, can then be seen as a "merging" of the two airlines checklists, considering the most appropriate and convenient sequences that can be applied in the simulation. Flight plans will be precisely given for each leg. Though the routes will be displayed here looking like the computed ones that are faxed to the flight deck in real life operations, they'll all be made manually using Jeppesen (High altitude) enroute charts. People among you who would like to fly the same legs themselves later will easily be able to load them in any Flight Management Computer given the standard format used. A good way to immerse in realistic flightsimming is to use a high-quality aircraft add-on. For a reasonable price, we can nowadays experience high-level PC simulation for almost every modern aircraft on the market, and even for older types no longer in service. With such products, developed by very high skilled people, we can enjoy photorealistic panels where between 80 and 90% of the real functions and switches are modeled. Of course, further studying is requested once we want to fly a new aircraft. For our trip, we'll then fly the Airbus A330-200 type, powered by General Electric CF6 engines and (fictionally) registered as OO-HZH (Oscar Oscar - Hotel Zulu Hotel), the "Oscar Oscar" code being the country identifier for every Belgian registered aircraft. The entire flight will be coded as HZD2006, callsign will be "Horizon two zero zero six heavy". For this occasion, a special "Around the World 2006" logo was painted on the left side of the fuselage. Panel & avionics will be provided by Phoenix Simulation Software A330/A340 Professional (payware), while the aircraft model is coming from the Project Open Sky aircraft designers (freeware). For this plane, I've preferred to use the POSKY aircraft model in place of the one provided by PSS because of flight dynamics and general display purposes. A few minor changes were made in the original Aircraft.cfg of the POSKY aircraft for full compatibility with the PSS panel. Having been flying with the Boeing 737-700 type only (modeled by PMDG software) on short and medium routes for several months, the A330-200 was chosen and added to my single aircraft "fleet" in May 2005 to start high capacity charters and long range services. Being common with Boeing environment, the transition to the Airbus philosophy can be quite disconcerting for the student pilot, but quickly shows that it also has its advantages. It's a matter of taste. In this review, I'll sometimes compare Boeing and Airbus when the situation allows it, showing the differences and analogies. A few historical and technical background about Airbus commercial airplanes... The European aircraft manufacturer whose head office is located at Toulouse - Blagnac airport in France is a now a consortium of Aerospatiale (France), Deutsche Aerospace (Germany), British Aerospace (UK), CASA (Spain) and Belairbus (Belgium). Airbus' first model, the A300-B1, was launched in the early seventies. This was the first widebody twinjet to appear on the market. The following A310, which began flying in the early eighties, featured a reduced capacity, longer range derivative of the A300 and updated systems. The A320 narrowbody type which took the air in 1987 introduced one of the Airbus warhorses: the fly-by-wire technology. Airbus aircraft are no longer flown with yokes but with computer game looking-like joysticks (named sidesticks). They send electrical signals to the flight computers which drive the hydraulics to control the surfaces. In the "former" system, which is however still used worldwide (and in particular by Boeing), pilots send mechanical signals by classic cables, those signals being amplified by the hydraulics that drives the surfaces. The A320 family (which now comprises, from the shorter to the longer variant : the A318, A319, A320 and A321) also introduced the glass cockpit revolution : this technology now concerns the whole airliner market (as well as the high level General aviation and, in the future, even light aircraft). On a glass cockpit aircraft, analogical gauges are replaced by an EFIS (Electronic Flight Instrument System) which commonly provides six CRT of LCD screens displaying flight information in most convenient form, each screen integrating several instruments. The Captain and the First Officer have both a PFD (Primary Flight Display) and a ND (Navigation Display), the engines and aircraft systems displays being located at the center of the panel. Airbus talks about ECAM (for Electronic Centralized Aircraft Monitoring) while Boeing says EICAS (for Engine Indicating and Crew Alert System) but this is the same thing. On Airbus aircraft, the upper ECAM screen displays engine, flaps setting, fuel quantity and alert information and is named the E/WD (Engine/Warning Display) ; the lower ECAM displays the various systems parameters and is known as the SD (System Display). Classic mechanical backup instruments are still provided (anemometer, artificial horizon and altimeter). The Flight Management System (FMS) integrates the several calculators which provide lateral (or surface) and vertical navigation as well as aircraft systems (including engines) management. The interface between the pilot and the FMS is the MCDU (for Multifunction Control Display Unit in Airbus terms ; Boeing says FMC) which is programmed before the flight and can be reprogrammed at any time during the flight. The Flight Control Unit (FCU ; Mode Control Panel or MCP with Boeing) integrates the Autopilot (AP) and Flight Director switches and communicates with the MCDU. With AP properly engaged, a whole flight can be run following the programmed MCDU information. In this case, we say that the FMS is flying the aircraft in managed mode. We'll later be talking about managed speed, managed vertical guidance and managed lateral guidance. The autopilot can anyway still be used following the "classic" way, giving the hand to the pilot who selects the desired IAS/Mach, heading, altitude or vertical speed. This aircraft is then flown in the selected mode. We will go deeply into those topics in the following articles. Airbus A330 flight deck. We see that the CPT and F/O have both their own PFD, ND and EFIS control panel working independantly. Two MCDU interfaces are also provided, though they are of course driving a single system. Note: this is the PSS A330 aircraft model virtual cockpit The A330(-300) and A340(-300) models where launched coincidentally with the minimum structural changes for two or four engines. Airlines can choose between the twin-engine A330 for the lowest cost on medium to extended range routes, and the four-engined A340 for the best operating flexibility on long and very long range networks. A330 and A340 flightdecks are very similar and nearly identical, introducing the famous Airbus' Cross crew qualification which dramatically reduces the type rating duration (and costs) from one type to another. In that way, it takes 8 working days to switch between a A320 family aircraft and the A330/A340, and from 1 to 3 days only to switch between the A330 and A340 qualification. The two latest additions to the A330/A340 family were the A340-500 and A340-600. The latter features an ultra-streched fuselage giving a capacity comparable to the Boeing 747. With its 16700 kilometers range, the A340-500 is currently the longest range aircraft on the market, also flying the longest 18-hours scheduled flight between Singapore and New York. The 555-seats, double-deck A380 made its first flight in April 2005, unveiling the world's largest passenger aircraft. The A350 program is intended to compete with Boeing's 787 Dreamliner, that will set new standards in operating speed, efficiency and passenger comfort on the long range market. The A350 is due to make its maiden flight in 2012. ... and the A330-200. The A330-200, launched in 1995, is the newest member of Airbus' widebody twinjets and is a longer range, shortened development of the A330-300. It shares near identical systems, airframe, flightdeck and wings, the only major difference for the observer being the fuselage length, which is 4,70 m shorter. Tail and empennage, however, have been enlarged to compensate for the loss of moment arm with the shorter fuselage and another important change is the addition of a center fuel tank. The aircraft that will fly us throughout the entire trip But that's enough talk. It's now time to board the ship, start the adventure and fly the first leg. We are in the first two weeks of July and northern Europe has now been enjoying warm and sunny weather for several days. A very good opportunity to start this round the world trip in clear skies. Leg 1: Brussels, Belgium - London, United Kingdom The first around the world flight review that was proposed by your servant more than 3 years ago flew directly to the United States in the first leg. This time, we will first take some time to discover some of Europe's beautiful landmarks, mainly reproduced here as high quality sceneries. London - Heathrow, one of Europe's busiest airports, was chosen as the first destination. This short flight will lead us above the North of Brussels, Belgian coast, the Channel and the approach into Heathrow will provide us good views of the Thames and the city. Brussels - National Departures terminal a few hours before HZD2006 gets airborne. The first passengers for Around the World 2006 arrive at Horizon Dreams' check-in desks. Flight Plan From Brussels-National (EBBR/BRU) to London-Heathrow (EGLL/LHR) Alternate EGKK London-Gatwick EBBR DENUT1C DENUT UL610 LAM LAM3A EGLL We'll take off from runway 25R, follow the DENUT One Charlie SID (for Standard Instrument Departure), make a few right turns to join Nicky VOR/DME in a view to avoid a prohibited area located in the North of Brussels and comply with noise abatment procedures ; DENUT intersection will follow and then we'll fly straight ahead to Lambourne VOR/DME via the UL610 airway. At Lambourne, which shall be crossed at 7,000 feet as specified in the Lambourne Three Alfa STAR (for Standard Arrival) we'll begin the approach into Heathrow. Quick reminder: SIDs and STARs are compulsory tracks which connect the airports with the airways. At busy international airports, SIDs and STARs will relieve ATC from aircraft guidance along those predeterminated tracks, which help to divide up the traffic flow and, in some cases, respect noise abatment procedures. SIDs and STARs may also be in force in mountainous areas to keep aircraft clear of terrain during the departure and approach phases. SIDs and STARs do not systematically exist for each airport and, even if available, STARs may sometimes be replaced or completed by radar vectoring at busy airports. In this case, ATC will handle each aircraft to make it follow its own approach path once it penetrates the radar vectoring area, often defined as a circle of about 30 nm radius centered on the airport. > Brussels Clearance Delivery, Horizon 2006 heavy ready to copy IFR, clearance to Heathrow... >> Horizon 2006 heavy, cleared to Heathrow as filed. Fly runway heading, climb and maintain six thousand. Departure frequency is 122.5, squawk 0561. Contact ground on 121.8 when ready to taxi. > Brussels Ground, Horizon 2006 heavy, ready to taxi >> Horizon 2006 heavy, taxi to and hold short runway 25 right via taxiways India 9, Echo 4, Foxtrot 4, Whisky 3 and Whisky 4. Contact Tower on 120.770 when ready Brussels airport is now slightly recovering a good health, recording more aircraft movements and passengers each year, figures that were dramatically lowered after September 11 and Sabena's demise in 2001. In FS2004, however, in the heart of the summer season and with AI traffic set to 100% we're still number one for takeoff, so let's go fast and relate this first flight without waiting any more. Ready to go? Airborne! Note the early rotation due to the very low fuel load needed for the flight to London Right turn on the DENUT1C SID Bruges historical city seen from 20,000 ft and Zeebrugge port, an important centre of economic in Belgium The Scheldt estuary in the distance Leaving the Belgian coast (Ostend city & airport). The Nav Display a few seconds before passing the Top of Descent point, abeam of Dover Descending over English countryside Passing Lambourne VOR/DME. Approach begins. Some of you will perhaps recognize their golf course ! Reproduced with permission of Jeppesen Sanderson, Inc. NOT FOR NAVIGATIONAL USE © Jeppesen Sanderson, Inc. 2006 Reduced for illustrative purposes only The ILS approach procedure into Heathrow Rwy 27R. From Lambourne VOR in our case, we follow the 234° track descending to 2,500 ft to localizer interception, that should be executed just above the Thames Flying over the Docklands on track 234° London here we come! Passengers can enjoy, from left to right : Kensington Gardens - Hyde Park, The Green Park and Buckingham Palace Localizer capture. Bottom-right: the disused Battersea Power Station, which provided London with electrical power until the eighties Short final, cleared to land. Despite excellent weather, we're il full automatic Approach mode for this first landing. Leg 2: London, United Kingdom - Amsterdam, The Netherlands Those who expect long range flights will be rather disappointed again with this second leg and will have to wait a little more for the longer routes that are scheduled. With its 236 nautical miles (436 km) distance, this new leg across the sea will take us a bit more than 60 minutes from pushback to shutdown, just a period of time to serve a cold drink to the passengers once airborne. We'll take off frow runway 27R and follow the Brookmans Park 6 Foxtrot Standard Departure, which makes an U-turn and flies back over the northern suburbs of London. We leave the English coast above Clacton VOR/DME beacon, then proceed to REDFA waypoint, somewhere in the North sea. From REDFA, we'll fly the REDFA Standard Arrival for Schiphol which leads to SUGOL, Initial Approach Fix (IAF) still located offshore. From SUGOL, we may expect radar vectors for runway 18C approach. A further notice about Radar vectoring : such procedures are more and more used by ATC on busy international airports. At Schiphol, for example, pilots shall expect radar vectors between IAFs and interception of final approach for each landing runway. The official standard routes, which of course still appear on approach charts, are now intended to be used in case of communications failure only. FS2004 standard ATC (in the approach phases) could be interpreted as radar vectoring but I'd say NO since it will always make you fly the basic right-angled shape of Downwind, Base and Final segments, often with too long and unrealistic distances, never taking the airfield situation, surrounding topography and nearby traffic in mind. This is why, when radar vectoring is in force in real life, I'll take some freedom to choose my own path or fly visual approaches when weather permits. In fine, and in a way to make a link with a previous subject, we may say that radar vectoring is a very suitable situation for the autopilot selected mode use. Flight Plan From London-Heathrow (EGLL/LHR) to Amsterdam-Schiphol(EHAM/AMS) Alternate EBBR Brussels-National EGLL BPK6F BPK UM185 CLN UL620 REDFA REDFA EHAM Holding point Rwy 27R. A BA 747-400 is nicely greeting us With such a short flight, and considering the 12,800 ft or 3900 meters available on the takeoff runway, we obviously perform a derated thrust takeoff, known as "FLEX" takeoff in Airbus terms. Once again, we'll go deeply into this feature in the following articles. Anticyclonic weather is still topical all along the way so we are likely to enjoy the landscape below from takeoff to landing. We're airborne for the second time, with a second immediate right turn to observe the SID track The PFD and ND shown during the BPK6F Standard Departure. On the PFD, the speed tape shows an Indicated airspeed (IAS) of 253 kts, and increasing as shown by the yellow acceleration vector. We're slightly above the current managed target airspeed of 250 kts as shown by the magenta triangle. Altitude tape shows 7330 feet with Standard reference (STD) - we are already above the transition altitude and climbing to the selected Flight level 130, at the current vertical speed of 4300 ft/min. A higher level clearance should be soon given by ATC. On the top of the PFD is the Flight mode annunciator (FMA), showing current autothrust and autopilot modes. We're currently in the Open Climb selected vertical guidance mode, in which we climb directly to the selected altitude using autothrust THR CLB mode to maintain climb thrust. With this mode, no flightplan (and, in our present case, SID) speed and altitude constraints are obeyed. This is why we're slightly above the 250 kts speed limit normally in force below 10,000 ft, as honored by the FMS. We're also in the NAV managed lateral guidance mode, which makes us follow the flight plan route entered on the MCDU. The ND is in ROSE NAV mode, which displays aircraft position with reference to the active flight plan route, moving map with selected type of datbase objects (airports, navaids or waypoints) and other useful information such as Ground speed, True airspeed, wind direction & speed and information about active flightplan waypoint, including distance and Estimated time of arrival (ETA). TCAS is also working, showing 3 other aircraft in the 10 nm radius vicinity, though no one of them is currently representing a collision hazard. Nice scenery below... Remember the FS4 era? We're about to complete the SID's initial turn. Already at 10,000 feet (3000 m) Passing Clacton... so long England! Now at cruising altitude of 21,000 ft (FL210) After a few minutes above the North sea we switched between London and Amsterdam air traffic control center and could already start a managed descent leading to SUGOL IAF. From there, once reaching the coast, a full visual approach with a rather short final leg was performed for runway 18C. Initially flying with AP selected lateral and vertical guidance, the last turns and final approach were flown manually, though remaining with autothrust engaged and managed speed. We're in radar vectoring area, base leg for Rwy 18C visual approach. The aircraft is now manually flown to capture runway axis. North of Haarlem. This industrial zone's smoke stacks look pretty close! Typical Dutch crops below. Amsterdam - Schiphol is a very big airport. It has 6 runways, among which 5 can accomodate airliners. The latest 18R/36L "Polderbaan" runway was added recently. Spotter's impression of our second landing Welcome to Amsterdam... seeing the aircraft in the background, we've obviously landed on the good airport. Leg 3: Amsterdam, The Netherlands - Sion, Switzerland - Geneva, Switzerland This very special leg will introduce an original flight procedure that would flirt with prohibited operations in real life, because of security reasons. We will then take all the advantages of flight simulation here, so ladies and gentlemen, fasten your seatbelts and get prepared for a thrilling flight ! Two destinations appear in the title. People among you who know Sion airfield may think that your virtual pilot is crazy because Sion could not even accomodate the A320 type. In real life, this little airport located in the Rhone valley and the Bernese Alps has only General aviation traffic, mainly linked to the nearby famous ski ressorts, as well as gliding activity. The fact is that we'll simulate an approach to the airport, but once on short final we'll perform a go around, leave the valley observing a high performance departure SID and then proceed to Geneva, some 90 km to the West where we'll land normally this time. The main purpose of this leg is to focus on what is, up to my mind, one of the very best scenery ever developed for Flight Simulator, both including high resolution terrain mesh and photorealistic textures, making Switzerland look incredibly real. This sounds nice, but how could we actually program the MCDU for such a flight ? Without going deeply into details, let's say that a possible way to do so is to load as main flight plan the Amsterdam - Sion route, and then specify Geneva as alternate airport. On a real MCDU, or more advanced but (very) expensive software available for flightsimming, a secondary flight plan connecting the destination airport with the alternate can (must) be loaded also. Unfortunately, PSS software doesn't provide this feature. If 80% of the real functions are modeled, we're in the 20 remaining ones !... We can only specify the alternate ICAO four-letter code, the secondary or alternate flight plan simply being the Destination (1) - Alternate (or Destination 2) leg. This is why, if we want to have also a managed flight from Sion to Geneva, following a specific route that will not fly us straight into a mountain, we'll have to save the corresponding flightplan in the MCDU database, and then call it using the CO RTE function of the MCDU once needed. This "flightsimming" solution will work rather fine here but will therefore diverge from real practices. This third leg is then splitted between two distinct flight plans: From Amsterdam-Schiphol(EHAM/AMS) to Sion (LSGS/SIO) EHAM LEKKO1R LEKKO UB31 NIK UA24 REMBA UL607 ABUKA UN850 TRA G5 FRI SANET MOT LSGS From Sion (LSGS/SIO) to Geneva (LSGG/GVA) LSGS SIO SANET FRI FRI5A LSGG The MCDU INIT page #1 once the first flight plan is loaded. ALTN RTE entry is unfortunately not modeled and will remain dashed. The first route is not a straight line and will make us cross Belgium for a last goodbye. We'll take off from runway 36C "Zwanenburgbaan" and fly a LEKKO Standard Departure from Schiphol, turning back to the South. Trasadingen VOR/DME, located near Zurich will be our first Swiss waypoint. We'll then proceed to Fribourg VOR/DME on a Low altitude airway (G5), then head southwards to Sion and fly the IGS Runway 25 approach that will be displayed below. Approaching the holding point for Rwy 36C. The 747-300 will fly before us. Rather high pitch for this third departure The Meuse valley in Belgium. In the river loop is the city of Huy, the Tihange Liège city, at the confluence of the Meuse and Ourthe rivers Nuclear power plant cooling towers appear on the left, near the aircraft nose This is already Switzerland. Below is the Reuss valley. Top-left: Zurich - Kloten airport. The Swiss Alps in the distance. Approaching Fribourg. Thun Lake over there The IFR approach into Sion is the IGS Rwy 25. IGS (Instrument Guidance System) is similar to ILS (Instrument Landing System) but, while the ILS is intended to lead the aircraft to the runway treshold, the IGS signal, which is like the ILS including both localizer (surface nav.) and glideslope (vertical nav.) will lead to a distant point from which the approach should be carried on as a visual procedure. If the ILS signal always coincide with runway axis, the IGS will often have an offset and then diverge from it. The world's most famous (and dangerous) IGS approach was Hong Kong - Kai Tak (now closed) IGS Rwy 13 with a 47° offset, making aircraft negociate a very tight turn on short final and over a very dense urban area. In our case, the danger is not really coming from the only 6° offset but from the surrounding very high terrain well - we're in the heart of the Alps! Reproduced with permission of Jeppesen Sanderson, Inc. NOT FOR NAVIGATIONAL USE © Jeppesen Sanderson, Inc. 2006 Reduced for illustrative purposes only IGS approach into Sion. From Fribourg VOR (FRI), we reach SANET fix that should be crossed at or above FL170. From there, we proceed on track 095° to Montana VOR/DME (MOT) and descend to FL170 or maintain altitude. We check that the ILS frequency is set to 108.35 MHz and course is set to 247°. We'll observe the CAT C aircraft approach category since this is the highest available. Aircraft approach categories are given following the approach speed range of each aircraft. CAT A will be for the slowest ones (light aircraft), CAT E for the fastest (heavy aircraft). Following the ICAO rules, CAT C applies for aircraft with an initial approach speed range of 160 - 240 knots and final approach speed range of 115 - 160 kts. With our aircraft in our current weight configuration (further details about aircraft weights and loading will be given later), we can meet the CAT C requirements, though we'll have to be careful with speed and flaps setting to remain in the category throughout the approach. From MOT, we remain on the 095° radial, descending to 16,000 ft until reading 21 nautical miles from the VOR. After that, we turn back to capture the localizer. At ALETO fix, glideslope should be captured on its turn, and we follow then the IGS signal, working like an ILS/DME. We can possibly engage AP Approach mode on the IGS, but once reading 7.5 nm on the DME (D7.5 ISI), we must leave the instrument approach and proceed with a visual procedure, as shown by the little arrows on the chart. Approaching SANET. Serious things are beginning now. We're a bit too fast and have to spread the speedbrakes. SANET is behind us, proceeding to Montana. Here's the Rhone valley. Now on track 095°, descending to 16,000 ft. Flaps already in CONFIG 2. Lötschental valley and Wilerhorn peak (3307 m - 11,022 ft) below Still heading 95°. Nice view of Grosser Aletschgletscher glacier originating from Jungfrau mountain We have now reached D21.0 from Montana VOR and begin the turn back for localizer interception Left passenger view when we're about to capture the localizer We are now on the IGS track, localizer & glideslope intercepted. This is looking like a common ILS approach. Runway in sight! We're not aligned yet, because of the IGS offset Visual procedure leg, autopilot off. This runway is too short indeed ! We're getting prepared for the go around. A very unusual opportunity for Sion spotters I guess... The go around is initiated by moving the thrust levers to the TOGA gate, which commands autothrust to provide fixed maximum takeoff / go around thrust. We'll then fly the Fribourg High Performance Departure SID that requires minimum climb gradient of 760 ft/min up to 7200 ft then 286 ft/min up to 10,400 ft. Though our aircraft can effectively be considered as a high performance machine, we'll have to be very careful again with climb rate, speed and flap/slat retraction. The first leg of the SID is actually similar to the missed approach procedure is this case. We must first follow the 235° radial from Sion VOR/DME, proceeding on the valley axis until being at 20 miles from the VOR (D20 SIO), or reaching the safe altitude of 13,000 ft whichever is earlier. By then, we turn back to Sion VOR and continue climbing. Flying over Sion again, we head northwards to Fribourg VOR via SANET (with a minimum crossing altitude (MCA) of 17,000 ft), coming back on the outward path. At Fribourg we'll already get prepared for the ILS DME Rwy 23 approach in Geneva with a Fribourg 5 Alfa STAR that will make us cross Geneva Lake. As shown by the following map, this short flight is actually the longest way round! Background: FS2004 built-in map Go around, gear up, turning left on track 235° for the high performance SID Climbing to 13,000 ft. Current IAS is 170 kts, climb rate at 1300 ft/min. We're complying with the SID specifications. Still on track 235°. Entremont Valley, 11 miles from Sion These mountains are 2900 m (9,670 ft) at their highest point. We're above 10,000 ft and will likely reach 13,000' before D20 SIO Turning back to Sion VOR/DME. We're now above 13,000 ft and safely clear of terrain. Note that the slats are still extended. Down there: Dent de Morcles (Morcles Tooth) mountain, 2970 m (9,900 ft) We've left the high Alps. Now passing Fribourg, descending to 7,000 ft and heading to St Prex VOR/DME, located near Lausanne. Below: Lac de la Gruyère Last minutes of the flight, Geneva approach: passing Lausanne, on the northern shore of Geneva lake. Proceeding over the lake, we're already on final for runway 23 Genève - Cointrin, South apron. Captain may smile, this was quite a successful leg! And this already concludes the first part of Around the World 2006. I hope you've enjoyed it and that you'll join me again on the following stories. In Part 2 we'll visit some further European destinations around the Mediterranean, focusing on other high quality sceneries. Credits The following flight simulation software was used to make this review: Main Microsoft Flight Simulator 2004 A Century of Flight (patched) AI Traffic add-on Ultimate Traffic by Flight1 Software Aircraft add-on A330/A340 Professional developed by Phoenix Simulation Software (PSS), distributed by Just Flight Project Open Sky Airbus A330-200 version 2 for FS2002/2004 Payware scenery add-on VFR Photographic Scenery East & South-East England developed by John Farrie (Visual Flight) and Getmapping PLC, distributed by Just Flight Switzerland Professional by Mailsoft - Flylogic Freeware scenery add-on Belgium 7000 (Belg7000) VFR scenery version 2.3 by Fred. Bridoux Belgium terrain mesh scenery by Jean-Gabriel Laurent Antwerpport scenery version 2 (add-on for Belg7000 enhancing Antwerp port and the Belgian coast) by Johan Thiers Brussels - National airport scenery version 3.2 (beta) by Robert Buysen Brussels - National AFCAD2 file for Robert Buysen's scenery by Thierry Caestecker Ostend airport scenery by Benoit Facon & Hans Vandale The Netherlands 2000 scenery version 2.91 by The Netherlands 2000 Design Team Genève - Cointrin airport scenery by Daniel Gauthier Utilities FSUIPC version 3.48 by Pete Dowson Active Camera 2004 version 2.0 by Guillaume Darier & Serge Baye Replacement runway black texture by V. Nauta Flight simulation, Real aviation, general information documents, websites and other references : PSS A330/A340 Professional manual & tutorial JEPPESEN SID, STAR, Approach charts, Airport diagrams, High & Low altitude Enroute charts Approach charts reproduced here (SIMCharts by Jeppesen designed for use with FS2004), courtesy of Jeppesen Jeppesen SIMCharts legend & glossary Formation Pilote : Instruments de Bord (Th. du Puy de Goyne, A. Roumens & P. Lepourry), Cépaduès Editions, Toulouse, France Airbus official website www.airbus.com Airliners (W. Green & G. Swanborough), Bloomsbury Books, London, UK www.airliners.net Project Open Sky A330-200 aircraft repaint in Horizon Dreams livery and real photograph taken at Brussels - National by Cédric De Keyser Digital editing and fictional elements added to the photo by Cédric De Keyser Horizon Dreams fictional advert added on the photograph uses Microsoft Windows 2000/XP (FR) default background bitmaps "Dune" and "Tropiques" Around the World 2006 logo uses a reduction of the Earth model provided by Orbiter 2006 Space Flight Simulator by M. Schweiger Michelin road map of Switzerland (used for some geographical information in the third leg) Any comments about this first part or suggestions concerning the following ones are welcome. Cédric De Keyser Brussels, Belgium cdk@ngi.be
×
×
  • Create New...