M-346 Flight Test Programme
M-346 Flight Test Programme
M-346 Flight Test Programme
P.CHIMETTO1, G.PASINETTI2
1
Flight Test Manager, Aermacchi S.p.A, Venegono Superiore (VA)
2
Flight Test Engineer, Aermacchi S.p.A, Venegono Superiore (VA)
ABSTRACT
The M-346, an advanced fighter lead in trainer designed and built by Aermacchi, performed its first flight on
15th July 2004 and from the beginning proved the goodness of the design showing excellent performance.
The M-346 hosts two Honeywell F124-GA-200 engines providing approximately 2850 kg of thrust each thus
giving the aircraft a thrust to weight ratio close to one. It is equipped with a fully digital fly-by-wire Flight
Control System giving the pilot the ability to fly carefree in the whole flight envelope. This characteristics, along
with the complexity of the on-board systems, prompted for a test team with both a deep knowledge of the aircraft
systems and a broad understanding of system and aircraft testing and integration. Aermacchi therefore chose to
apply a Concurrent Engineering approach within its M-346 Integrated Product Team.
This paper, following a brief description of the aircraft characteristics, presents the approach to ground and flight
testing adopted by Aermacchi, the organisation put in place to implement such an approach and the test facilities
set up to support the test process.
A summary of the test results along with the lessons learned from the first aircraft test phase is also presented,
with particular attention to the benefits of the chosen test and risk reduction aircraft development approach.
For the M-346 flight test activity and relevant organization breakdown structure, traditional and “collaborative”
approaches have been compared:
TRADITIONAL COLLABORATIVE
Hierarchical organization Flat organization
Ruled by formal procedures Professionally driven
Limited range of action Pro-active attitude
Larger number of resources assigned Highly integrated test team
Narrowed Specialist FTE More Generalist FTE
Aim: collect data and transfer them Aim: collect data and transfer results of analysis
FT Head is responsible for department FT Manager is a process owner
Test success oriented Program success oriented
The choice, in line with the program’s Integrated Product Team concept, was for a collaborative approach. In
particular, the following areas were interested by the new approach:
• FT management: Process-oriented, linked to M346 program milestones, capable to assure:
− Correct workflow of company internal and external contributions
− Consistency among test requirements, A/C configuration, test programs and schedules
− Overall Cost effectiveness of the test activities
• FTE group, located in the experimental department, with a larger group of engineers from the design
department to support dedicated tests in specific areas
• FT data management process re-engineering, with particular emphasis on data analysis tools, both real
time and post flight
The M-346 Flight Test process takes either benefit from past experience, current assets and new dedicated
systems, but it can be faced only using all the company capabilities and technical resources in a collaborative
way while performing the complex flight test process including:
planning, scheduling, test requirements definition, in terms of measurements required, test procedures and data
reduction, FTI design and realization, (both in-flight and on-ground), test A/C preparation and day-by-day
operation, test conduct, test execution, data gathering and results work-out, test analysis and reporting.
Tight co-ordination, common training and detailed preparation required to perform in a safe and proficient way
the test activity is a must. Each phase of the test has to be planned, executed, monitored and reported to the
M-346 Program and to Company’s management.
The Core Team Members are co-located in the same site where the flight test facilities are. The Integrated Test
Team (fig.3) includes:
- the Project Pilot,
- the Test Conductor and his group in charge to organize the daily flight activity and responding for short term
plans, long and medium term plans,
- the ground crew and his chief,
- the flight test engineers responding for technical programs and flight data analysis and reporting,
- the FTI group, responsible for flight and ground data acquisition and recording.
The M-346 FTE group includes a small number of dedicated people to form the core “dedicated” team, and
people from the design department to support specific test activities involving their own systems and/or areas of
expertise. In this way there is the “closure of the loop” between test and design engineers, by moving the
activities Centre of Gravity alternatively from flights to offices, according to the planning, sharing experience,
information, tools and time.
In particular, the “dedicated” Flight Test Engineer figure:
- attends briefings and debriefings as well as monitor test flights in ground station,
- supports FTI people activity,
- process data gathered during the test flights,
- continuously develops test methods,
- participates with the design functions in establishing and issuing test requirements according to design
specification and relevant qualification plans,
- elaborates preliminary test analysis, giving also recommendations for the foregoing activities.
- participates in test reports issuing,
- supports day by day planning of the test activities.
The team has received adequate training, both in terms of flight test instruction, by means of company internal
and external courses before the beginning of the M-346 test campaign. Obviously only the on-the-field
experience and lessons learned really help to create the proper common training, procedural, technical, inter-
personal understanding among the dedicated personnel.
A considerable effort has been and is still being made to bring to the program state of the art flight test analysis
capabilities, ranging from aircraft data acquisition systems to data analysis tools. Particular emphasis is being
placed on the following requirements
• Highly flexible data acquisition system
• Common formats to improve data and application sharing between the design and flight test teams
• Maximise return from real-time analysis to improve time and cost efficiency
• Minimise aircraft dependency from base airfield.
The steps taken and the associated results are detailed in the following paragraphs.
Additional FTI packages are either available or being readied. These include:
• Interim Air Data System – This system, made of a Nose pitot boom with AoA and AoS vanes and two
micro air data computers, interfaces with the Flight Control System providing air data information to the
pilot and the aircraft control laws.
• Flutter excitation system – This system is currently being developed and is designed to interface with the
Flight Control System to provide pre-defined frequency sweep inputs to the primary control surfaces.
As far as data download and storage is concerned, the system already in place was deemed appropriate. This
system is based on a central server where flight test data is accessible as single parameter array files. These files
are generated by the FTI department that decodes the tape recorded by the on board digital recorder into the
proper engineering units. Once the files have been created and loaded to the server the are accessible by almost
any company personal computer either directly as binary files or via a utility that converts the into ascii files.
While this system allows for an incredibly broad access to test data it has three major drawbacks. It is time
consuming, it requires huge amounts of data storage capacity and has limited flexibility. At the time of writing
approximately 2000 of the available 10000 recorded parameters are converted into “spa” files and loaded to the
server. Additional parameters required additional processing by the FTI group.
This prompted for the evaluation of an extension of the current system that would result in a better compromise
between flexibility and performance on one side and broad data access on the other as detailed hereafter.
• Data stored in the original unprocessed format with significant reduction in required storage space
• Configuration control maintained by the FTI group that retains control over the decoding set-up
• All parameters readily accessible via dedicated front ends by flight test engineers
• Basic data analysis tools already within the software
• Integration with current Matlab™ analysis tools
• Capability to export single parameter array files and/or ascii data files retained.
With a target of 800 test flights scheduled on two prototypes and on one pre-series aircraft to support the aircraft
development and type certification process, the M-346 programme represents a new and unique challenge in the
history of Aermacchi. A flight test programme of this magnitude and complexity, put together with the state of
the art and highly sophisticated aircraft systems, prompted the Flight Test department for a broad review of its
procedures and practices.
Efficient management of the massive amount of data to be handled became essential in order to maximise the
return from the flight test activity, an activity that makes up for a considerable part of an aircraft development
budget.
For the M-346 program a set of data management tools, mainly databases, has thus been developed to allow for
an easier, more precise and efficient handling of all the data associated with the flight test activity, covering
activities that range from handling of test requirements to test planning and tracking, from aircraft configuration
management to annual report generation. Their main characteristics are summarised hereafter.
• All the tools have been developed “in house” by the flight test staff and are therefore tailored to the specific
needs of the test department.
• A distributed approach was chosen for the following reasons:
− A broader range of subjects can be covered and linked together, giving a better global picture and
planning capabilities
− Each module can be customised to the needs of its main users
− Modules can be developed independently, provided common standards and interfaces are used
− Once the core system is in place, each single module can be phased in independently from the others,
with a dramatic reduction of the activity backlog and better prioritisation
• All tools are under continuous review to best adapt to the increasing data management requirements.
• Standardisation of procedures and practices among different departments was achieved.
• The databases are designed to easily integrate with data acquisition and data analysis tools in order to
automate the data feeding process and hence minimise the requirement for user inputs. Any database, in
fact, no matter how well designed, can only be as good as the stored data.
• To maximise the tools benefits a web browser based interface was developed. In such a way, test data is
readily accessible and searchable not only by the flight test personnel, but by all of the staff involved in the
M-346 program.
5. ACHIEVEMENTS
At the time of writing a total of approximately 90 flights had been carried out ( more than 75 with the first
prototype and about 15 with the second one). The active collaboration between the flight test and design teams
allowed for a quick and effective feedback from test results into design updates thus allowing the aircraft testing
to proceed at a sustained steady pace. The main achievements to date are detailed hereafter.
• Second prototype first flight on schedule and within less than one year after first prototype first flight. Both
prototypes now in flight test activity.
• Envelope expansion in FCS phase 1 configuration (non-production standard) completed with the aircraft
cleared to a maximum airspeed of 325KCAS/0.65M, a maximum altitude of 35 kft, a load factor range of
-2 to 5 g and an Angle of Attack range of –5 to 20 deg.
• Engines with dual FADEC control functional qualification
In accordance to the risk mitigation policy adopted, the above envelope expansion was performed with the
engines mounting basic Engine
Control Units. Full Authority
Digital Engine Control units
(FADEC) were the installed and
successfully completed all
functional tests including in-flight
windmill and cross-bleed engine
restarts.
• Flutter, Buffet and aerodynamic
model matching
Validation and matching of the
flutter and buffet aircraft models
were successfully completed.
Combined with the results of the
Parameter Identification (PID)
activity, aimed at validating the
aerodynamic data set, this allowed
to funnel revised and more reliable
data into the next design phase.
• Handling qualities assessment of
the bare aircraft showed good
aircraft flying characteristics
allowing the aircraft to be
successfully demonstrated at the
Paris Air Show at Le Bourget. Figure 6 – 1st flight and envelope explored
• Interim air Data system calibration and series ADS (IMFP) data gathering.
The interim air data system was calibrated and showed optimum and reliable performance with errors well
within MIL requirements. The system, linked to the FCS, allowed for safe flight while gathering data for
the production air data system calibration (4 skewed Integrated Multi Function Probes).
• General systems functional tests completed.
Functional qualification of general systems including Hydraulics, Electrical system, ECS, OBOGS was
completed. Braking and Steering systems were tuned and optimised for best ground handling performance.
• Communications
VHF and UHF radio tests were completed showing excellent radio performance with maximum range of
~200 nm at FL 300, slightly exceeding the optical range.
• EMC and HIRF activity completed for flight activity at home and abroad.
• APU installation and ground testing completed.
APU ground testing has been successfully completed allowing re-deployment of the aircraft with no need
for ground assistance.
The next step of the flight test campaign will see the extensive testing of the FCS phase 2 CLM (reversionary
production mode), flutter and buffet tests and a loads campaign that will support the envelope expansion to
572KCAS/0.95M, an altitude of 40 kft and a maximum loading of –3 to 7g. A/C performance will also be
thoroughly assessed and the engines fully qualified.
6. LESSONS LEARNED
In this paragraph some lessons learned in the first period of the test activity are presented.
Combine flight test and design teams throughout the test activity
The involvement of the test team in the ground testing phases greatly improved the team knowledge of the
aircraft and of the designers needs in terms of test results. On the other side, involvement of the design teams in
the test activity greatly improved their knowledge of the operational requirements. The overall result has been to
have better
The M-346 represents a completely new generation of trainer aircraft, with state of the art leading edge
technology that matches more complex and extensive aircraft development programs such as the Eurofighter
Typhoon and the JSF. For the first time in many years an Italian company faces the challenge of thoroughly
testing such an aircraft with a test activity that will see the Company involved in areas ranging from avionics to
buffet, from engines to aircraft agility.
To cope with such a challenge Aermacchi has undergone a deep review of its established test organisation. All
test processes went under deep review in order to make best use of the design and flight test resources. An
extensive effort has also been made to re-engineer the test tools available, from test management to data
acquisition and processing. A considerable emphasis has been put into building a highly skilled team that could
merge experience, enthusiasm and creativity. To date the test team has achieved a competence unthinkable just a
few years ago.
The results obtained from the almost 100 flight test performed so far have been promising, showing the goodness
of the aircraft design. A long way still lies ahead. The success will ultimately depend on the skills of all those
involved in the test activity.
BIBLIOGRAFY
1. P. Chimetto, R. Carabelli, “Collaborative Flight Testing – The Aermacchi M-346 case”, Proceeding of the
14th SFTE European Chapter Symposium, Toulouse 10-12 June 2003.
2. P. Chimetto, R. Carabelli, “Early Flights Achievement with the Aermacchi M346 Advanced Trainer”,
Proceeding of the NATO SCI-162 Symposium, Warsaw 9-11 May 2005.