University of Bridgeport

Fall 2010

An Object-Orient analysis for Aircraft

Engine Weight Estimation

Course CS 400

Submitted by
Allaeddin Ghaydi ID: 861076 aghaydi@bridgeport.edu
Abdalla Abusnina ID: 862897 aabusnin@bridgeport.edu
Mohamed Ahmed ID:885701 mahmed@bridgeport.edu
 new version from (WATE) code technology
which max FORTRAN and Object Oriented
Abstract: has been becoming important to get the best

The most important issue when result and great design. Using object

except design the aircraft is the weight of oriented program to calculate all the

engine. It’s very important to give the analyses about the engine has been

aircraft the power and the energy to reach improving making aircraft engine powerful

the point that we need. However, excepts try and great full.

always to have something reliable and they

have been using a programming to give
them the correct result. According to NAS Introductions:
Glenn Rashers Center (GRC) computer code
Objected oriented has involved in
has been developed by Boeing aircraft to
difference places in our life; also, objected
estimate the engine weight design and
oriented program has been helping people to
compeer it with other things such as, the
design and invent so many invention at
passenger numbers, and the body weight of
many fields such as, industries, education,
the aircraft. The program which can offer
and arctetuctior. Whenever, the designer
that analysis called Weight Analysis of
want to built a new invention they try to
Turbine Engine (WATE). By the time,
measure the result with one of the languages
Boeing had been using (WATE) with
programming and getting the calculation.
FORTRAN 1979 and at that time. After that
Moreover they see if the new product is
time WATE has been improving when it has
useful or not. One of the huge filed is
been converted to Object Oriented by NAS’s
aircraft industry when they make new air
NPSS ( Numerical propulsion System
plans.
Simulation) moreover, that improvement
has giving to (WATE) program Engine weight is the key parameter

opportunity to calculate the temperature, to build the aircraft because it affects cost

airflow and the pursuer. Furthermore, the and the way how it works. Engine Wight
estimation helps a lot to take the right
decision when the professional designer
design an engine and get the best engine
candidates. At NAS Glenn Rashers Center
(GRC) (WATE) is the first reverence for
them to get the decision. Boeing Company is
the first place establishes the (WATE)
program in 1979 and tries to get the best
design for the engines. Also, calculate with
(WATE) the dimension for engine and other
mechanism. The design samples with (
WATE) up 29 samples then get the analyses
to put it at the date base and Compare them
with tables.
In 1979, considerable improvements
have been made from NAS to the computer
code with McDonnell Douglas Corporation
and that improvement effect construct in far
above the ground. The primary method for
engine method through the code
calculated martial volume and density which
can be affect our engine weight. Other kind
of calculation can be measured by the
(WATE) are martial stress, temperature, and
geometry for the engine. The result for all
the calculation that, we are going to come up
as graph at the computer screen.
We can see obvicly from any
application with objected oriented
improving very fast. As the Glenn Rashers
Center (GRC) mention (WATE) has been
improving when it has been converted to
Object Oriented by NAS’s NPSS
(Numerical propulsion System Simulation) .
Objected oriented was created with software
by people to offer useful applications that
give correct result. The most important idea
behind the objected oriented is classes,
Inheritance and template library; so, the
engine weight modeling design is going to
described with WATE++ Architecture.
WATE++ Architecture:
WATE++ Architecture calculates the weight
and the dimension for the engine; also
WATE++ intended to be fixable and
extensible. Objected oriented helped to
come up with correct result because it use
classes, inherits, polymorphisms. So, when
is they need to measure any unit at engine the
just called the function that do that and
every function at the class calculate the
result consequently. Moreover, there are
three main object types that used at
WATE++ Architecture which are Elements,
ports, and Sub elements
is
Elements can plug into the element sockets. Each sub
element performs detailed computations that
elements is one of primary object
impact the element’s overall calculations.
types that are used in the WATE++
The variable-area-nozzle sub element, for
calculations, which is perform high level
example, can be plugged into the nozzle
component calculations . Elements may
element socket for variable-area nozzle
have many plug locations termed sockets,
computation. Sockets on an element need
into which computational blocks termed sub
not be filled; default values will be used if
elements may be attached. For example, the
left empty.
compressor has a socket into which attached
is sub element does the disk sizing.

Ports

Ports give data connectivity between

elements. And it also used to transfer
information such as radius and axial position
between the elements. Ports also give
Engine Model Input &
mechanical links between two elements. For
example, the connecter between the shaft output:
and compressor and turbine, it could be a
One of the most significant part that Object
port.
Oriented can calculate is the engine model
input and output with WATE++ code which

Elements can be determine the flight condition and

nozzle setting of engine. When they
The third type of primary object is
calculate all the parameters with WATE++,
the sub elements which are perform specific,
they will have the general idea about the
detailed computations. They generally only
behavior of the engine and how they can get
work when connected to sockets. WATE++
every single reaction from the engine.
supports multiple types of sub elements that

Inputs that WATE++
Operating
 Design variable TOCT hurts, this
kind of calculate can determine the
amount of power that the engine
power can give in the highest flight.
 Design fan pressure ratio that known
as ratio of the enters pressure to the
exits pressure
 Nozzle facture specific fraction ˃1
and this factor determine amount of
underexposes
 Power code that can be given the
specific numbers from 10 to 50 that
represent the power engine at the
current flight.
Output Operating:
 Fuel burn rate
 Nozzle exist temperature
 Weight
 Nozzle weight
 Nozzle exit pressure
As a result for these measurements which
can get from WATE++, the engine will be
useful and the air plan will be successful.
CONCLUSIONS:
As it known the Objected oriented
has a large effect and Appearance in many
different areas such as industries,
architecture and even in our daily life. And
one of the main fields, got advantage from
Objected oriented is aircraft in which how to
estimate Aircraft Engine Weight.
In this research an overview of how
the capacities and features of object oriented
is exploited to address the problem and the
shortcomings addressed in the FORTRAN
version, to improve and Development the
maintainability, extensibility, and
architecture of WATE++, an object oriented
engine-weight estimation code.
It has been designed so carefully by
selecting correct and accurate data type
using the object classes to suit the
application.

Finally, compared the result which

calculated by new version with old one to
validate the code. Both of them of give
substantially analogous results, as should be.

References
1. Onat, E. and Klees, G.W., “A Method to
Estimate Weight and Dimensions of Large
and Small Gas Turbine Engines,” NASA
CR–1 59481, 1979.
2. A Computer Code for Gas Turbine
Engine Weight and Life Estimation. Michael
T. Tong, Ian Halliwell, Louis Ghosn, ASME
Journal of Engineering for Gas Turbine and
Power, volume 126, no. 2, April 2004.
3. Anthony A. Giunta. Use of data sampling,
surrogate models, and numerical
optimization in engineer-
ing design. AIAA, 2002.
4. John Hunter and Darren Dale. The
Matplotlib Users Guide, May 2007.
5. NASA Glenn Research Center. NPSS
User Guide, NPSS 1.6.4 REV:AC edition,
August 2007.