There is something slightly intimidating about sitting in the cockpit of a Boeing 747-200.
Four engines. A flight engineer's panel. Multiple fuel tanks. Hydraulics. Pneumatics. Electrical systems. Pressurization. Engine Pressure Ratio. Navigation systems. And, if you decide to go all the way back to the aircraft's original era, a CIVA INS navigation system that makes modern navigation look almost suspiciously convenient.
This is exactly why I wanted to learn the Felis 747-200 Classic in X-Plane 12.
My goal isn't simply to get the aircraft airborne, engage the autopilot and watch the scenery go by.
I want to understand what the aircraft is doing, why it is doing it, and how all of those individual systems come together to operate a classic long-haul aircraft.
I'm currently using the FMC as my primary navigation method. Eventually, I want to learn the CIVA INS properly, but trying to learn the entire aircraft and a completely different navigation philosophy at the same time would be an excellent way to turn a training flight into a troubleshooting session.
So this article is my journey from being intimidated by the aircraft to finally feeling comfortable enough to operate it.
And eventually, I put all of that learning to the test on DLH100, Frankfurt (EDDF) to Madrid (LEMD).
Why the 747-200?
The 747-200 belongs to a very different generation of aviation.
Modern airliners are designed around highly integrated computers, automation and simplified crew workflows. The classic 747 was also technologically advanced for its time, but its operating philosophy was different.
The aircraft expected the crew to understand its systems.
The real 747-200 flight deck had three crew members:
- Captain
- First Officer
- Flight Engineer
The flight engineer wasn't simply sitting behind the pilots watching gauges.
The position existed because managing a large aircraft's electrical, hydraulic, pneumatic, fuel and other systems required significant attention.
The Felis simulation captures much of that philosophy.
That makes the 747-200 interesting to fly because it isn't just a large aircraft.
It is a large system-management exercise.
Getting Familiar With the Felis 747-200
The Felis 747-200 Classic for X-Plane 12 is built around detailed aircraft systems rather than simply providing a visually accurate 747.
The aircraft includes detailed simulation of systems such as:
- Electrical power
- Fuel
- Hydraulics
- Pneumatics
- Pressurization
- Engines
- Autopilot
- Autothrottle
- EPR-based thrust management
- Navigation
- Flight engineer functions
- EFB-based aircraft management
This means learning the aircraft isn't really about memorizing where every switch is.
It is about understanding how the systems interact.
The easiest way for me to approach that was to break the aircraft into smaller pieces.
Understanding the Aircraft Without Getting Overwhelmed
The biggest mistake I could make would be thinking I have to understand everything immediately.
I don't.
The better approach is to understand what each major system does first.
Once the purpose of a system makes sense, the switches and procedures become much easier to understand.
Electrical
Think of it as:
Source → Bus → Equipment
The aircraft receives electrical power from sources such as generators or external power.
That power is distributed through electrical buses.
Those buses supply the aircraft's systems and equipment.
I don't need to memorize every electrical circuit immediately.
The first objective is simply understanding where the electricity comes from and where it goes.
Fuel
The 747 has multiple fuel tanks and a fuel system designed to supply four engines while maintaining appropriate fuel distribution.
The basic mental model is:
Fuel tanks → Pumps → Fuel distribution → Engines
The complexity comes from how the tanks and pumps are managed.
Fuel management involves more than simply asking whether enough fuel remains.
It also involves:
- Tank sequencing
- Fuel balance
- Engine feed
- Fuel transfer
- Pump operation
- Aircraft weight
- Centre of gravity
- Remaining fuel
The aircraft has a lot of fuel.
But "a lot" is not an aircraft procedure.
Automatic Fuel Management for Long-Haul Flights
For long-haul operations, I also use an automatic fuel-management plugin to reduce repetitive workload.
On shorter flights, manually managing the fuel system is useful because it teaches me what the aircraft is doing.
On longer flights, however, constantly performing repetitive fuel-management tasks can become another workload item competing for attention with everything else happening in the cockpit.
The philosophy is simple:
Let automation handle repetitive tasks while I remain responsible for understanding and monitoring the system.
My long-haul workflow therefore looks something like this:
Felis 747-200
Aircraft and systems
XFirstOfficer
Crew workload and procedural assistance
Automatic fuel-management plugin
Repetitive fuel-management tasks
SimGround Map
Ground and airport awareness
FMC
Current navigation solution
Pilot
Flight management and decision-making
The important distinction is that automation should reduce workload, not replace understanding.
I still want to understand what the fuel system is doing.
The plugin simply means I don't have to spend an entire long cruise repeatedly performing the same fuel-management actions.
Hydraulics
The hydraulic system is easier to understand if you think of it as a power transmission system.
The basic idea is:
Pump → Pressurized fluid → Actuator → Movement
Hydraulic pressure provides the force required to move aircraft components.
Depending on the system, hydraulics support functions such as:
- Flight controls
- Landing gear
- Brakes
- Other high-force aircraft mechanisms
The important thing initially isn't memorizing every hydraulic line.
It is understanding that the aircraft needs a powerful way to move heavy mechanical components.
Hydraulic pressure provides that power.
Pneumatics
Pneumatics deal with compressed air.
A simplified model is:
Engine → Compressed/bleed air → Pneumatic system → Aircraft services
Bleed air can support functions including:
- Air conditioning
- Pressurization
- Engine-related systems
- Other pneumatic services
Again, understanding the relationship between the components is more useful initially than memorizing every valve.
Pressurization
At cruise altitude, the atmosphere is not particularly interested in human survival.
The aircraft therefore maintains a controlled cabin environment.
The basic idea is:
Conditioned air enters the cabin → air leaves through controlled outflow → cabin pressure is maintained
The aircraft isn't simply trapping air inside.
It continuously manages airflow and pressure.
Once that concept makes sense, the pressurization system becomes much easier to understand.
The Engines and EPR
The 747-200's four engines are another major part of the learning experience.
Unlike many modern aircraft where thrust settings are presented primarily through N1 percentages, the classic 747 uses Engine Pressure Ratio, or EPR, as an important thrust reference.
Conceptually:
EPR = engine exhaust pressure compared with engine inlet pressure
I don't need to manually calculate it during every phase of flight.
What matters initially is understanding that EPR provides a reference for engine thrust.
That becomes particularly important during takeoff and climb because thrust limits depend on factors such as:
- Temperature
- Pressure altitude
- Aircraft weight
- Engine configuration
- Takeoff conditions
Performance calculations therefore matter.
A 747 isn't something you casually point down the runway and hope physics has decided to cooperate.
Starting Four Engines
Starting four engines is one of those moments where the aircraft immediately reminds you that you're operating something from another era.
The process involves monitoring engine parameters rather than simply clicking a single "start engines" button.
I'm watching:
- Engine rotation
- Fuel flow
- Temperature
- Oil pressure
- Engine stabilization
An engine start isn't just an animation.
It is a sequence of physical processes that I monitor.
Once all four engines are stable, the aircraft becomes a completely different machine.
XFirstOfficer: Sharing the Workload
One of the most useful additions to my workflow is XFirstOfficer.
My philosophy for using it is simple:
Don't automate the thinking. Delegate the workload.
The real 747 had another crew member sitting beside the captain.
In the simulator, XFirstOfficer helps recreate some of that workload distribution by assisting with routine cockpit tasks, checklists, monitoring, callouts and procedural actions depending on the configuration being used.
That changes how I approach the aircraft.
Instead of trying to personally operate every switch while simultaneously navigating, monitoring engines, communicating and flying the aircraft, I can distribute some of the repetitive workload.
That is especially useful in a classic aircraft because there are plenty of things happening simultaneously.
But the virtual First Officer isn't replacing the pilot.
I still need to understand:
- What is happening?
- Why is it happening?
- What should happen next?
- Is the aircraft behaving normally?
Automation is useful when it gives the pilot more mental space.
SimGround Map: Knowing Where You Are on the Ground
The cockpit isn't the only place where situational awareness matters.
Large airports can become surprisingly confusing when you're sitting several stories above the ground in a 747.
That is where SimGround Map becomes useful.
It provides a real-time view of the aircraft's position and the surrounding airport environment, making it easier to understand:
- Taxiways
- Runways
- Parking positions
- Airport layout
- Aircraft position
For a large aircraft, ground navigation is its own little flight.
You're dealing with:
- Long wings
- Large turning radius
- Taxiway restrictions
- Runway crossings
- Parking positions
- Other aircraft and vehicles
Having a clear map reduces the cognitive load.
It doesn't fly the aircraft.
It simply makes it easier to understand where I am.
FMC First, CIVA Later
This is probably the biggest deliberate decision in my current learning process.
The 747-200 can be flown using the CIVA INS, which is one of the most interesting aspects of operating a classic long-haul aircraft.
But I'm not starting there.
I'm using the FMC first.
Why?
Because there are already enough things to learn.
If I simultaneously try to learn:
- 747 systems
- Flight engineer procedures
- Engine management
- Performance
- EPR
- Fuel management
- Pressurization
- Electrical systems
- Hydraulics
- Pneumatics
- CIVA INS
I'm not really learning.
I'm increasing the number of things capable of confusing me.
So my progression is:
FMC → Aircraft confidence → CIVA INS
Once I'm comfortable operating the aircraft, I'll move toward the INS.
Understanding CIVA INS
The CIVA concept is actually easier to explain than its cockpit implementation suggests.
At its most basic level:
Know where you started + measure how you moved = estimate where you are now
The INS uses inertial measurements to calculate aircraft movement and continuously estimate position.
That makes it fundamentally different from simply following a modern satellite-based navigation solution.
The appeal is that you're operating a navigation system from the era in which long-haul crews had to manage navigation very differently.
But it also means more responsibility.
That is exactly why I want to learn it after becoming comfortable with the aircraft itself.
The Takeoff
The takeoff phase brings everything together.
Before departure, I want to know:
- Aircraft weight
- Takeoff performance
- Engine configuration
- Thrust setting
- Flap configuration
- Trim
- Fuel status
- Pressurization status
- Flight controls
- Navigation setup
The 747 is big enough that every action feels deliberate.
Once the engines are producing takeoff thrust and the aircraft begins accelerating, the scale of the machine becomes obvious.
Then comes rotation.
And suddenly the enormous four-engine aircraft is airborne.
Climb
The climb is where the workload begins to settle.
The aircraft transitions from the intense environment of takeoff into a more predictable phase of flight.
This is where automation becomes useful.
The autopilot can maintain the aircraft's flight path while I focus on monitoring:
- Engines
- Fuel
- Pressurization
- Hydraulics
- Electrical systems
- Navigation
- Aircraft performance
This is also where the aircraft begins to feel less like a collection of switches and more like a functioning machine.
Cruise
Cruise is where the 747 really starts to feel like a long-haul aircraft.
The aircraft settles into its rhythm.
The engines are stable.
The autopilot is flying.
The aircraft is following its route.
Fuel is being consumed.
The crew monitors the aircraft and manages what needs managing.
This is also where my supporting tools become most useful.
My cruise setup
Felis 747-200
The aircraft itself and its detailed systems.
XFirstOfficer
Helps distribute routine cockpit workload.
Automatic fuel-management plugin
Handles repetitive fuel-management tasks during long flights while I continue monitoring the fuel system.
SimGround Map
Primarily useful before departure and after arrival, but still part of the overall operational toolkit.
FMC
My current navigation solution.
CIVA
My future navigation challenge.
The result is a workflow that feels much more like managing a flight than simply flying an aircraft.
Long-Haul Fuel Management
A long-haul 747 flight can involve hours of cruise.
That makes fuel one of the most important things to monitor.
I'm interested in three basic questions throughout the flight:
1. How much fuel did I start with?
This establishes the baseline.
2. How much fuel am I burning?
This tells me whether the aircraft is behaving approximately as expected.
3. How much fuel will I have when I arrive?
This is ultimately the number that matters.
Fuel management is therefore not simply:
"Look at the fuel gauges."
It is continuous awareness of fuel consumption, distribution, aircraft weight and expected arrival fuel.
Automation can help with repetitive tasks, but the pilot still needs to understand the numbers.
A plugin can manage fuel.
It cannot take responsibility for the flight.
The Flight That Changed Everything: DLH100
Eventually, all the learning has to be put into practice.
For me, that flight was DLH100 from Frankfurt (EDDF) to Madrid (LEMD).
It wasn't chosen because it was some spectacularly difficult route.
In fact, that was part of the point.
I wanted a flight long enough to exercise the aircraft's systems, but manageable enough that I could concentrate on operating the 747 rather than spending the entire flight fighting it.
The setup was:
Flight: DLH100
Route: EDDF → LEMD
Aircraft: Felis 747-200 Classic
Navigation: FMC
Crew assistance: XFirstOfficer
Ground awareness: SimGround Map
Fuel management: Automatic fuel-management plugin
This was the flight where I finally felt that everything had clicked.
Frankfurt: Setting Up the Queen
Frankfurt immediately reminded me why the 747 is such an interesting aircraft.
There is a lot to do before the aircraft even moves.
I worked through the cockpit preparation systematically.
Electrical power.
Aircraft configuration.
Fuel.
Hydraulics.
Pneumatics.
Pressurization.
Navigation.
Performance.
Engines.
Instead of looking at the cockpit as one enormous wall of switches, I could mentally divide it into systems.
That made an enormous difference.
Earlier in my learning process, I would look at a panel and think:
"What does all of this do?"
Now I could look at it and think:
"This is the electrical system. This is the fuel system. This is the pneumatic system."
That shift sounds small.
It isn't.
It is the difference between looking at a complex aircraft and understanding a complex aircraft.
Programming the Flight
For DLH100, I stayed with the FMC.
I deliberately decided not to introduce CIVA yet.
That wasn't because I had abandoned the idea of learning INS navigation.
Quite the opposite.
I wanted to learn CIVA properly, and that meant first becoming comfortable enough with the aircraft that I could devote my attention to navigation rather than fighting the airplane itself.
The route was entered.
The departure was prepared.
The arrival into Madrid was planned.
The aircraft was ready.
Four Engines Come Alive
Engine start was one of the moments that made me realize how much progress I had made.
Previously, starting the 747 could feel like a checklist exercise.
Now I understood what I was actually watching.
Engine rotation.
Fuel introduction.
Temperature rise.
Oil pressure.
Stabilization.
One engine at a time, the four powerplants came alive.
The aircraft went from a collection of systems sitting quietly at the gate to a functioning machine.
And somewhere in the cockpit, my virtual First Officer was helping keep the workload under control.
I wasn't trying to touch every control.
I was managing the operation.
Taxiing Out of Frankfurt
With the engines stabilized, I began taxiing.
This is where SimGround Map proved useful again.
Frankfurt is not exactly a tiny airfield where you can simply point the aircraft toward the runway and hope.
The 747's size also makes ground navigation something that deserves attention.
Taxiway.
Hold short.
Runway crossing.
Turn.
Position.
Check.
Move.
The aircraft's wings extend far beyond what your brain initially expects.
Every turn is a reminder that you're driving something with the approximate footprint of a small apartment building.
Eventually, we reached the departure runway.
The aircraft was configured.
The takeoff data was checked.
The engines were ready.
The 747 was pointed toward Madrid.
Takeoff
Takeoff was where everything I had learned started coming together.
The engines spooled up.
Thrust was established.
The aircraft accelerated.
The numbers came alive.
And then:
Rotate.
The nose came up.
The 747 lifted away from Frankfurt.
Four engines pushed the aircraft into the climb.
The landing gear came up.
The aircraft transitioned into its climb profile.
For the first time, I wasn't thinking:
"Am I doing this correctly?"
I was thinking:
"The aircraft is doing exactly what I expect."
That was the moment.
The beast was no longer something I was merely trying to survive.
I was actually flying it.
Climbing Away
The climb was surprisingly calm.
XFirstOfficer helped with the routine workload.
The autopilot handled the flight path.
I monitored the aircraft.
Engine indications.
Fuel.
Pressurization.
Hydraulics.
Electrical systems.
Navigation.
Everything had a purpose now.
Instead of randomly checking gauges because they existed, I was checking them because I understood what they represented.
That is a major difference when learning a complex aircraft.
Cruise: The Moment It Clicked
Eventually, the aircraft settled into cruise.
This was where I noticed the biggest change.
The cockpit suddenly felt familiar.
The systems weren't fighting for my attention.
The aircraft was stable.
The FMC was managing the route.
The autopilot was maintaining the flight path.
XFirstOfficer was helping with routine workload.
The automatic fuel-management system was handling repetitive fuel-management tasks.
And I was monitoring the operation.
I looked around the cockpit and realized something:
I knew what I was looking at.
The panels that had once seemed intimidating now had context.
The fuel gauges told a story.
The engine instruments told a story.
The electrical panel told a story.
The hydraulic indications told a story.
The pressurization system told a story.
I wasn't memorizing switches anymore.
I was interpreting the aircraft.
That, to me, was what finally mastering the beast meant.
Not knowing every single switch by heart.
Knowing enough about the machine to understand what it was telling me.
The Flight to Madrid
The cruise itself was relatively uneventful.
And that was exactly what I wanted.
A well-managed aircraft should eventually become boring.
Boring is good.
Boring means the systems are stable.
Boring means the fuel burn is behaving as expected.
Boring means the engines are happy.
Boring means nobody has accidentally created an aviation incident because they got distracted by the scenery.
The flight continued toward Spain.
I continued monitoring the aircraft.
Fuel management remained in the background.
The route progressed.
The workload remained manageable.
And I had time to appreciate the fact that I was finally comfortable in the cockpit.
Descending Toward Madrid
Eventually, Madrid began to approach.
The cruise phase ended.
The arrival was prepared.
The aircraft began its descent.
This was another useful test.
The aircraft had to transition from the quiet environment of cruise back into a much more active phase of flight.
Speed.
Altitude.
Configuration.
Navigation.
Approach planning.
Fuel.
Everything mattered again.
But this time, the workload didn't feel overwhelming.
I knew what was coming.
Approach Into LEMD
Madrid gradually came into view.
The 747 descended toward the airport.
The aircraft configuration changed progressively.
Flaps.
Speed.
Descent path.
Landing preparation.
The workload increased, but the cockpit still felt under control.
That was another sign of progress.
Earlier, I would have considered a busy approach something to fear.
Now I considered it something to manage.
There is a subtle difference.
Fear says:
"There are too many things happening."
Experience says:
"There are several things happening. Handle them one at a time."
The Landing: -879 FPM and 1.49 G
And then came the part that I probably shouldn't put in the aviation equivalent of a trophy case.
The landing was not exactly textbook.
The recorded touchdown was approximately:
- Vertical speed: -879 feet per minute
- Peak/recorded load: 1.49 G
In other words, the Queen of the Skies did not exactly float onto the runway like a feather.
She arrived.
With conviction.
A 1.49 G touchdown is a substantial impact, and a descent rate of -879 fpm at touchdown is considerably harder than the kind of smooth landing most pilots would aim for.
But strangely enough, this landing was useful.
It exposed the final part of the learning process that I still needed to work on.
I had learned the systems.
I had learned the workflow.
I had learned the navigation.
I had learned the workload management.
But landing a large classic jet smoothly is another skill entirely.
The aircraft can be completely understood and still demand better handling.
And that is an important lesson in simulation:
Mastering the systems doesn't automatically mean mastering every phase of flight.
So yes, DLH100 ended with a fairly enthusiastic arrival.
The runway survived.
The aircraft survived.
My pride survived, although it filed a formal complaint.
What DLH100 Taught Me
The most important lesson from the flight wasn't navigation.
It wasn't fuel management.
It wasn't even the landing.
It was confidence.
Not blind confidence.
System-based confidence.
I knew why I was doing things.
I understood what the aircraft was telling me.
I knew where the workload was coming from.
I knew when automation could help.
And I knew that I was still responsible for the flight.
That is what changed.
The -879 fpm and 1.49 G touchdown also gave me something important: a new training target.
The aircraft systems had started to feel familiar.
Now I could concentrate more seriously on refining my flying.
From Learning the Beast to Flying the Beast
When I first started learning the Felis 747-200, the aircraft felt enormous.
Not just physically.
Mentally.
There were too many systems.
Too many switches.
Too many procedures.
Too many things to remember.
But the solution wasn't to memorize everything.
The solution was to understand the aircraft one system at a time.
Eventually:
Electrical → understood
Fuel → understood
Hydraulics → understood
Pneumatics → understood
Pressurization → understood
Engines → understood
EPR → understood
FMC → comfortable
XFirstOfficer → integrated
Fuel management → integrated
Ground operations → familiar
And then came DLH100.
The flight where all those individual pieces finally became one operation.
The landing wasn't perfect.
Far from it.
But the overall flight demonstrated something much more important.
I could operate the aircraft.
The Next Challenge: CIVA
Mastering the aircraft doesn't mean the learning is finished.
It means I can finally move on to the next layer.
For me, that is CIVA INS.
Now that I have enough confidence with the aircraft itself, I can start learning the navigation system without simultaneously trying to understand the entire 747.
That is an important distinction.
I'm not replacing the FMC because it is easier.
I'm using the FMC as the bridge toward understanding classic navigation.
Eventually, I want to fly the 747 using the kind of navigation workflow appropriate to the aircraft's era.
That will be another challenge.
And probably another article.
The Learning Roadmap
My approach to the Felis 747-200 now looks something like this.
Stage 1: Learn the aircraft
Understand:
- Electrical
- Fuel
- Hydraulics
- Pneumatics
- Pressurization
- Engines
- Flight controls
Stage 2: Learn normal operations
Practice:
- Engine starts
- Taxi
- Takeoff
- Climb
- Cruise
- Descent
- Approach
- Landing
Stage 3: Use automation intelligently
Integrate:
- Autopilot
- Autothrottle
- XFirstOfficer
- Automatic fuel management
The goal isn't maximum automation.
The goal is appropriate workload distribution.
Stage 4: Improve navigation
Continue with the FMC until it becomes comfortable.
Then begin learning:
CIVA INS
Stage 5: Improve aircraft handling
Now that the systems are becoming familiar, concentrate on:
- Smoother approaches
- Better flare timing
- Landing attitude
- Touchdown control
- Energy management
- More consistent landings
Because apparently knowing how the aircraft works does not magically make the runway softer.
Stage 6: Fly longer and more realistically
Eventually, combine everything into realistic long-haul operations.
That means managing:
- Flight planning
- Fuel
- Aircraft systems
- Navigation
- Crew workload
- Weather
- Diversions
- Arrival planning
Learn Manually First. Automate Later.
This is probably the principle I want to keep throughout the entire learning process.
Automation is useful.
Plugins are useful.
The FMC is useful.
XFirstOfficer is useful.
Automatic fuel management is useful.
But none of those things should become substitutes for understanding the aircraft.
The objective isn't to make the 747 behave like a modern automated airliner.
The objective is to understand how the 747 was designed to operate and then use simulation tools to make that learning manageable.
The aircraft remains the aircraft.
The pilot remains responsible for the flight.
The software simply helps distribute the workload.
Final Thoughts
Flying the Felis 747-200 in X-Plane 12 has turned out to be less about learning how to fly a big airplane and more about learning how to manage a complex machine.
The aircraft forces you to think about systems.
The flight engineer concept forces you to think about workload.
The fuel system forces you to think ahead.
The CIVA INS promises to make navigation considerably more interesting.
XFirstOfficer helps distribute routine crew workload.
SimGround Map improves situational awareness on the ground.
An automatic fuel-management plugin can reduce repetitive fuel-management work during long-haul flights.
But the most important part is still the pilot.
DLH100, EDDF to LEMD, became the point where all of those lessons came together.
It wasn't perfect.
The -879 fpm touchdown and 1.49 G landing made that very clear.
But perfection wasn't the point.
The important part was that I no longer felt like I was fighting the aircraft.
I understood what it was doing.
I understood why it was doing it.
I could manage the workload.
I could monitor the systems.
I could navigate the aircraft.
And when something didn't go perfectly, I could identify what needed more practice.
That is what I now consider mastering the beast.
Not becoming perfect.
Becoming comfortable enough with the machine that I can concentrate on improving the details.
The Felis 747-200 is still a demanding aircraft.
But it no longer feels impossible.
And now that I've managed to tame one Queen of the Skies, there is only one obvious next challenge:
learn to navigate her properly with CIVA.
Because apparently learning one 747 wasn't enough. ✈️
Top comments (0)