In This Issue: AMC News
In This Issue: AMC News
Avionics Maintenance
Conference
http://www.aviation-ia.com/amc/
AMC Celebrates 2010 in Phoenix!
The 2010 AMC, hosted by US Airways, was held March 29 – April 1, 2010, at the Hyatt
Regency in Phoenix, Arizona. Forty-six airlines, five airframe manufacturers, and 214 avionics
suppliers and others participated in the meeting. There were 762 registered attendees from 26
countries.
The AMC Vice Chairman, Mark Sorensen, Delta Air Lines presented the AMC Awards:
Science has the Nobel Prize, literature—the Pulitzer, and avionics—the Volare Award. The Volare
Award has become world-renowned as the avionics industry’s highest award for individual
achievement.
Each year, AAI encourages the contribution of ideas, leadership and innovation by allowing individuals
to be nominated for Volare Awards prior to the annual AMC and AEEC. These awards recognize
individuals in airline and supplier organizations for outstanding personal achievement.
The Volare Awards that are offered at the AMC and AEEC allow individuals to be nominated in the
categories of Airline Avionics Maintenance and Avionics Product Support. In addition to these Volare
Awards, AAI presents a Pioneer Award and a Chairman’s Special Award on an as deserved basis.
Over the past 42 years, Volare Awards have been presented to outstanding members of the avionics
maintenance community. The Volare Awards are likely to be the most important award they have ever
received.
And this year is no exception. Today, we are going to present Volare Awards for outstanding
achievement in supporting the aviation world. Since 1968, the AAI has been recognizing those leaders
in our industry that strongly participate in it. Prior to today, there have been 232 Volare Awards
presented to different individuals. When you see one of your peer group walking around with their
award pin, you can rest assured the holder has demonstrated great love and dedication for aviation.
The prestigious Pioneer Award was first bestowed in 1985 and has only been awarded nine
times since then, including today’s recipient. This award recognizes and honors an individual
who has pioneered technical or other innovation which results in a major, long-term impact on
the application of electronics, electrics, or instrumentation to commercial airline operations.
Volare Citation
It is my honor and a great personal pleasure as the President of the Airline Avionics Institute to
present the Pioneer Award to Mr. Jim Terpstra of Jeppesen.
I did not expect this when I showed up this morning, but I appreciate it very much. It is an
industry that has given me a lot, and hopefully I have been able to give back to this
distinguished group. I have been associated with all of you in one way or the other over the
years, and I hope this love can continue. Thank you.
Volare Citation
It is my honor as the President of the Airline Avionics Institute to present the Volare Award, in
the category of Airline Avionics Maintenance, to Mr. Dave Nesseler of Air Wisconsin.
Well, this is really humbling, and I really do appreciate it. When I started in the industry, I had
hair down to the middle of my back and now it’s a little grayer and little bit shorter. I always
remember one of my mentors told me that as a regional jet representative, you have to get in
there and scrap and fight for what’s yours. And we really have such similar objectives that it
just makes sense to me. This is really appreciated and I am humbled. Thanks.
Volare Citation
It is my honor as the President of the Airline Avionics Institute to present the Volare Award, in
the category of Avionics Manufacturer, to Mr. Merritte DeBuhr of Carlisle Technologies/ECS.
What a surprise—38 year of crawling around on airplanes and I never imagined this. Thank
you.
Volare Citation
Most recently this candidate served as founder and Secretary of the AEEC Data Link Users
Forum. He is the outgoing AEEC Executive Secretary responsible for over 200 ARINC
Standards used by all types of aircraft and aircraft systems.
It is my honor as the President of the Airline Avionics Institute to present the Volare Award in
the category of AAI’s Special Award to Mr. Michael Russo of ARINC Industry Activities.
I am definitely humbled and honored by this award, and any achievement I have made has not
been on my own, but with the support of the staff I work with, my colleagues, and those
experts in the industry that contribute and participate so well.
It is my honor as the President of the Airline Avionics Institute to present the Volare Award, in
the category of AAI’s Special Award, to Mr. Roy Oishi of ARINC Industry Activities.
Accepting for this award in Roy’s absence will be Mike Rockwell, Senior Director of ARINC
Industry Activities.
I would just like to say a few words on the behalf of Roy: For those of you that know Roy, he’s
never short on something to say. I contacted him this morning and congratulated him on this
nomination and award and he asked me to pass this message along:
AAI has been the strong industry partner to the AEEC for many years and this recognition is
particularly significant to me. The member companies of AAI have provided the brain power
and muscle for AEEC and indeed for all of ARINC IA. This includes whatever standardization
venue, including COMM/NAV, dataloading, datalink, surveillance, networking, you name it…
The volunteers from the industry never cease to amaze me with their knowledge and
dedication to the industry.
To receive an award in the name of all of those people is indeed an honor. Thank you and best
wishes for a successful week in the dry heat of Phoenix.
In 2002 he was awarded the AAI Volare award, and he has been active on many industry committees,
including the working groups that developed ARINC Standards 625, 626, 627, and 663. He has also
developed many ATA standards that have helped the industry over the years.
Martin, congratulations.
Martin’s Comments:
This year there are 3 airlines that stood for election, with two slots available. The airlines elected were,
KLM and US Airways.
Sam also reported that the South American region will remain vacant as no member airline has
indicated their willingness to stand for election.
The AMC Steering Group met Thursday afternoon. Mitch Klink, FedEx, was elected as Chairman, and
Marijan Jozic, KLM, was elected Vice Chairman.
Mitch Klink, FedEx Marijan Jozic, KLM Sam Buckwalter, ARINC Chris Uphoff,
AMC Chairman AMC Vice Chairman AMC Executive Secretary Air Wisconsin
Greg Devlin, American Jacob Barak, El Al Yasuhiro Kinoshita, Mark Sorensen, Delta
Japan Airlines
Jens Latendorf, Lufthansa Rich Stillwell, United Kevin Kramer, US Airways Doug Mailat, AAI Liaison
An extra special thanks goes out to all our Member Airlines, Corporate Sponsors, and AAI Members.
Please remember, if you don’t fall into one of these categories, contact an ARINC Industry Activities
staff member for information on how you can support the AMC and gain access to privileges that
otherwise you have to pay for.
By now, you should have downloaded the final 2010 AMC Report that transcribes all the dialog spoken
at Open Forum. Please review the items that pertained to your Organization and follow-up on the
commitments made. Part of the final Report is the all important Registration List so you can maintain
your professional contacts throughout the year.
It is never to early to start gathering potential Agenda Items for AMC 2011 in Memphis! Start a folder
that archives your technical issues that are unresolved or are not being resolved to your satisfaction.
This will make it much easier to recall your items when it comes time to write them in January 2011.
Also, please keep in mind we willl be releasing meeting schedules for the Working Groups we have
planned for this calendar year. This is your chance to contribute to our Industry by getting involved and
making a difference.
Mitch Klink
Chairman – AMC Steering Group
The Field Loadable Software (FLS) Working Group meeting will meet on
June 2-4, 2010, in Annapolis, Maryland. The meeting will be co-chaired
by Rod Gates, American, and Ted Patmore, Delta.
ARINC Report 667 has been thoroughly reviewed and should be considered mature at the
conclusion of the June meeting. The following actions will be accomplished:
Review inputs concerning software management from Flight Simulator Training Device
operators
Review Chapters 1-9 for minor editorial changes since last meeting
Review Acronym list and Glossary Appendices for accuracy and applicability
The FLS Working Group will conclude the meeting with a consensus on the maturity of the
document, and following the meeting the Industry Activities staff will prepare a final draft for
adoption consideration.
To sing karaoke till 2 AM in the CMC suite. OK, maybe some of us anyway.
So, why am I speaking about this? Well, if you have ever tried to tell Mitch Klink “no”,
you know why I am up here. The man frightens me to be truthful.
No, I am simply here to share what benefit American Airlines realizes by participating in
the AMC. I am not on the Steering Group. I am not a VIP or industry expert. I am just an
engineer like many of you simply trying to do my very best to successfully maintain and
operate the safest and most reliable and dependable product for our customer.
How does the AMC help with that? Well, to the first point:
Something I started doing a couple years ago was to simply catalogue the published
discussion items that were about specific parts, systems or systemic problems found at
American Airlines.
I now go through every submission, and search our company databases for all of the
manufacturer part numbers listed. I log those that match, or have similar part numbers
in some cases, and I categorize those specific items by the engineering group I think
that may be most familiar with the issue. I also capture the cost/impact data submitted
by the items author.
And what this does is it narrows down the amount of material for the different
engineering groups to sort through, and allow for the specific engineer to address those
items that he or she can effectively handle it. Thus giving them plenty of time to
investigate the impact the issue may have for us, and allow them the opportunity to
gather data to support each issue as is warranted. And of course, time permitting, I
really hope every engineer looks at all of the items.
But, with this tool we can at least feel confident that our subject matter experts are
exposed to the relevant items for us. And this has ultimately increased the participation
at American Airlines, as well has been a benefit for us.
This total is shown at the top of this simple spreadsheet I use to keep track of these
items and can be quite a large number. For the 2010 submissions I logged 101 items
out of the 248+ submissions that were of particular relevance to American Airlines. Of
those where cost impact was submitted, the total was $6.8M. A sizeable potential cost
impact for sure.
And mind you this number is particularly useful in justifying the expense of attending the
AMC, a little free advice there.
Once this spreadsheet is complete, I email it to all of our engineering departments along
with the published discussion items. The individual engineers then use this spreadsheet
as a lookup table of sorts to find the items they are interested in. And then I ask for the
feedback on the specific items and contact them individually to see if there is anything
that I or any other AMC attendees from American may need to share, express, or
defend in the open forum.
And sometimes this actually drums up the participation of the engineers and they come
to the conference to speak to the issues themselves. We always have a pretty full table
here at the AMC open forum.
So, it’s a pretty simple approach but it has been helpful in maximizing the benefit of the
conference for us. You may find a similar approach effective as well. This first benefit is
the discussion items themselves. As I said, there were 101 items that of particular
relevance for American Airlines and of those, 14 were submitted by us. So that means
by participating in the conference we are potentially realizing the benefit of resolving 87
issues we may not have realized we had, or possibly didn’t have time to address and
resolve on our own. Or we may have not had the influence alone to effect a needed
change.
When you look at it this way, it’s almost as if we’re contracting a small army of
engineers and industry experts to resolve issues that we may just not get to. All for the
price of a membership and a couple hotel rooms, it’s a pretty good return on our
investment, I think.
And regarding the 14 submissions we sent in, it is interesting that every year, after the
publication of the discussion items but before the conference actually takes place we
We all want to succeed, and we all want to be a part of the solution. So often just the
knowledge that an item is going to be discussed in the open forum can prompt proactive
resolution from all of the interested parties.
I can think of at least two items in particular this year that I will be announcing that I am
very pleased to have resolved in such a timely manner.
Now many times the issues are on such a scale they cannot be effectively addressed in
this forum, though, and often in these cases, ARINC Industry Activities steps in and
holds working group meetings that respond to these larger issues. These AMC working
groups have developed some great guidelines and standards that have shaped our
industry. They have brought standardization, direction, and resolution to some pretty
complex issues at times. Some great examples that I can think of and that I have even
participated in are the ARINC Report 625 Industry Guide for Component Test
Development and Management, ARINC Report 668: Guidance for Tool and Test
Equipment Equivalency, and the ongoing work of the ARINC Report 672 working group
on No Fault Found issues.
Networking: this in my opinion is one of the greatest reasons to attend AMC. Although
it is kind of hard to quantify, I personally have called on colleagues that I have met at
AMC and “picked their brains” to help resolve problems where we simply may have not
had experience with the product, and we needed that little bit of guidance that you
cannot always find in the CMM.
I can also think of some chance meetings where one might run into that OEM engineer
who developed the product you are struggling with at the moment, but you did not bring
that issue up in the AMC open forum. I know one of our engineers was able to fix a
problem that had him stuck for months after a short ride in an elevator at this same hotel
during the last AMC held here. He recognized one of the elevators occupants’ vendor
badges and struck up a conversation. And he made the contact that got him back on
track with his engineering problem.
Again, it’s hard to quantify and qualify that kind of benefit but it happens all of the time at
AMC.
Industry influence: I cannot say that the AMC has directly been the cause of some the
websites, forums, and the like that the airframers and OEMs have developed. But I
would think that their participation in AMC would at least give them insight to the kind of
Using one of these websites, I was recently shown the fleet reliability statistics being
updated on American’s Boeing fleet, a very useful tool indeed. Certainly developed for a
number good reasons I am sure, but I’m guessing that customer feedback heard at
assemblies like this one at AMC must have had a least some impact on the decision for
companies like Boeing to invest in these great tools.
For some of you, I am preaching to the choir. And I thank you for your past a future
participation in the AMC. You are helping American Airlines operate a better airline. For
those of you participating in the AMC for the first time, or even reading this in the AMC
Report or somewhere else well after the close of the conference I hope you understand
a little bit better the overall benefit of participating in the AMC.
You will solve problems, and you will better your bottom line. You will make beneficial
contacts. This group operates of course by funding from memberships, and by active
participation of the attendees.
In the immortal words of our friend Roger Goldberg, “It’s your conference, and it’s what
you make of it”. Never more true than now.
On 15 April 2010, a volcano under the Eyjafjallajökull glacier in Iceland erupted and
strong winds pushed the ash cloud towards Western and Central Europe. Almost all of
the European airspace from Milan / Italy and north thereof was closed to prevent
another incident similar to British Airways Flight 009 and KLM Flight 867.
This is just a short historical overview about those two legendary flights before
commenting on the European airway crisis of April 2010.
The BA Story:
At 4,100 meters (13,500 feet), they were approaching the altitude at which they would
have to turn over the ocean and attempt a risky ditching. Although there were guidelines
for the procedure, no one had ever tried ditching in a Boeing 747 – nor has anyone
since. As they performed the engine-restart procedure, engine number four started, and
During the ordeal, the windscreen had been virtually sandblasted, and there was
considerable “St. Elmo’s fire” as a result. After reaching its target altitude, Captain
Moody throttled back. However, engine number two surged again and had to be shut
down. The crew immediately descended to and held 3,600 meters (11,800 ft).
As Flight 9 approached Jakarta, the crew found it difficult to see anything through the
windscreen and had to make the approach almost entirely on instruments, despite
reports of good visibility. The crew decided to fly the (ILS). However, the glide slope was
inoperative, so they flew the localizer as the First Officer monitored the airport's
Distance Measuring Equipment (DME). He then called out how
high they should be at each DME step along the final track to the
runway, creating a virtual glide slope for them to follow. Although
the runway lights could be made out through a small strip of the
windscreen, the landing lights on the aircraft seemed to be
inoperable. After landing, the flight crew found it impossible to
taxi, due to glare from apron floodlights which made the already
sandblasted windscreen opaque.
It was found that problems had been caused by flying through a cloud of volcanic ash
from the eruption of Mount Galunggung. The cloud sandblasted the windscreen and
landing light covers and clogged the engines. As the ash entered the engines, it melted
in the combustion chambers and adhered to the inside of the power-plant. As the
engine cooled from not running and as the aircraft descended out of the ash cloud, the
molten ash solidified and enough broke off to allow air to flow smoothly through the
engine allowing a successful restart. The engines had enough electrical power to restart
because one generator and the onboard batteries were still operative.
Engines one, two, and three were replaced at Jakarta, as well as the windscreen, and
the fuel tanks were cleared of the ash that had entered them through the pressurization
ducts, contaminating the fuel and requiring that it be disposed of. After being ferried
back to London, engine number four was replaced and major work was undertaken to
return the aircraft to service. G-BDXH also entered the Guinness Book of Records as
the longest glide in a non-purpose-built aircraft, until the record was broken by the Air
Transat Flight 236 incident.
The crew received various awards, including the Queen's Commendation for Valuable
Service in the Air and medals from the British Air Line Pilots Association. Following the
incident, the crew and passengers formed the Galunggung Gliding Club as a means to
keep in contact. Damaged engine parts from BA 9 are on display at Auckland Museum.
On 15 December 1989, KLM Flight 867 was an Amsterdam to Tokyo flight with a stop in
Anchorage. While descending into Anchorage International Airport, all four engines
failed. The Boeing 747-400, less than 6 months old, flew through a thick cloud of
volcanic ash from Mount Redoubt which had erupted the day before.
All four engines failed leaving only critical systems on backup electrical power. When all
four main generators shut off due to the failure of all the engines, a momentary power
interruption occurs when the flight instruments transfer to standby power. Standby
power on the B747-400 is provided by two batteries and two inverters. The captain
performed the engine restart procedure which was not successful on the first few
attempts and was repeated until restart was achieved. On some of the attempts, as one
or more (but not all) engines started to operate, the main generator would switch back
on. Switching on and off caused repeated power transfer interruptions to the flight
instruments. These power transfers were later verified from the flight data recorder.
Transcript of the conversation with the ATC:
The following transmissions took place between Anchorage Center, the air traffic control
facility for that region, and KLM 867:
Pilot KLM B–747—‘‘KLM 867 heavy is reaching level 250 heading 140’’
Anchorage Center—‘‘Okay, Do you have good sight on the ash plume at this
time?’’
Pilot KLM B–747—‘‘Yeah, it’s just cloudy – it could be ashes. It’s just a little
browner than the normal cloud.’’
Pilot KLM B–747—‘‘We have to go left now. . . it’s smoky in the cockpit at the
moment sir.’’
Anchorage Center—‘‘KLM 867 heavy, roger, left at your discretion.’’
Pilot KLM B–747—‘‘Climbing to level 390, we’re in a black cloud, heading 130.’’
Pilot KLM B–747—‘‘KLM 867 we have flame out all engines and we are
descending now!’’
Anchorage Center—‘‘KLM 867 heavy anchorage?
Pilot KLM B–747—‘‘KLM 867 heavy we are descending now. . . we are in a fall!’’
Pilot KLM B–747—‘‘KLM 867 we need all the assistance you have sir. Give us
radar vectors please!’’
Fortunately, Captain Karl van der Elst and crew were finally able to restart the engines
and safely land the plane. In this case the ash caused more than 80 million USD in
damage to the aircraft (requiring all four engines to be replaced), but no lives were lost
and no one was injured. As of 2010, the aircraft is still in service with KLM.
Back to the future, to April 2010
Since 1989 there has been no significant announcement of a volcanic ash encounter.
Let’s keep it that way.
But maybe those incidents triggered the panic situation in Europe. It is not that I don’t
care about safety, but it looks that there is no significant proof that the volcano under
the Eyjafjallajökull glacier can stop 26,000 flights which fly each day in Europe. During
the days following the start of the eruption, the sky was clear and there was no visible
cloud for three days. It is beautiful spring weather and it is ideal for gardening. It is a bit
strange that those white stripes on the sky are not present. Also, when you drive around
airports, it is disturbing that there is no activity whatsoever.
The Authorities closed the airspace and they were afraid to decide to open it again. Not
only the affected area but the whole airspace was closed. They are talking about safety
but no one knows how much dust particles can be measured 40,000 feet above the
North Sea or Germany. It is just a wild guess that we are in great danger. We don’t
know where the danger is and we don’t know how extensive it is. Visually, it is just a
perfect clear sky.
Being an engineer, I look differently at those events. Looking at the two events in
history, I cannot remain neutral. Simply put, both captains announced that they saw the
cloud. They flew into it and experienced problems as a result of that.
The skies above Europe were clear when approximately 20 test flights were flown by
KLM and Lufthansa. The results of those test flights were uneventful, so logically there
was a much smaller chance of an aircraft experiencing problems due to the volcanic
ash cloud. The question remained after the test flights: how long would the airspace
remain closed?
With regards to flying with a sandblasted windscreen, I can imagine that it is frightening
to fly in without GPS and with sandblasted windscreen. Fast forward just 20 years later,
and there is FLIR and heads-up displays available, which can give pilot enough
confidence that he is landing on the right spot. Also, there is an Electronic Flight Bag
(EFB) with moving maps which can guide pilot very accurately to any place he wants.
If the crew encounters a volcanic cloud, the avionics systems will be there to help the
pilot navigate back and land safely. The only problem he will have is ensuring that
engines are running, although this is a mechanical issue and not an avionics problem If
the airplane has flameouts in all engines, he would still be able to navigate. Even with
no engine power, there will be enough time to glide to the nearest airport. We are
talking about Western Europe and not remote Alaska or Indonesia. There is at least one
airport within a circle of 30 miles anywhere on the continent. There are no significant
mountains to deal with and there is radar coverage over the whole area. It is the best
controlled airspace on earth and we are afraid of a few dust particles? Isn’t that
strange?
Let’s forget all political and management issues. What should the engineer actually do?
1. Investigate if the ATC radar can detect volcanic particles? If yes, limit those sectors
and fly around. Using GPS, the aircraft can fly very accurately around any spot you
wish. That is what we do with cumulonimbus clouds every day.
2. If the ATC cannot see the volcanic cloud, use satellite pictures and limit the flights in
the affected sectors.
3. If there is any doubt for night flights, fly only during the day, but please fly.
4. Monitor the flights and ask pilots to report strange things: unusual clouds, unusual
colors of sunsets, etc.
5. There are millions of meteorology companies and reports. Ask their reports to isolate
possible danger zones.
6. Do some test flights and collect particles for investigation. Check the density of dust
in dangerous areas.
The funny coincidence is that every time they actually need an engineer to provide the
advice of what to do.
ARINC sponsors three committees that develop standards for the airline community:
While AEEC is best known for the development of ARINC standards, over the years,
AMC has taken a lead in the development of many industry standards as well in the
areas of Shop and Test Equipment Standards, Process Standards, Software
Transmission and Management Standards, and Aircraft Maintenance Standards.
For the convenience of our Plane Talk readers, the AMC-developed ARINC standards
are listed below. Persons wishing to order these standards may do so by ordering
online at https://www.arinc.com/cf/store/category.cfm?prod_group_id=1 or contacting
the ARINC Document Department at +1 410 266-4117, or via standards@arinc.com.
ARINC 602A-2: Test Equipment Guidance is an update of ARINC 602 following the
introduction of new digital test equipment standards and the publication of ARINC 608A.
This standard includes specific references to On-board Maintenance Systems (OMS)
and Automatic test Equipment (ATE) used within the maintenance community.
ARINC Report 614: Standard Firmware Loader for Avionics Shops describes the
characteristics of a standard firmware loader for avionics shops. It is capable of copying
digital information into memory devices installed in circuit card assemblies, Line
Replaceable Modules (LRMs) and On-Board Replaceable Modules (OBRMs). It
contains the recommendations of the air transport community concerning the design
and development of firmware loader equipment.
ARINC Report 606: Guidance for Electrostatic Sensitive Device Utilization and
Protection describes the nature of Electrostatic Discharge (ESD) and its effects on
digital avionics equipment. It provides information concerning methods to protect
against ESD damage which could originate in many different ways.
ARINC Specification 608A: Design Guidance for Avionics Test Equipment, Part 1 –
System Definition provides top-level guidance intended for the design of Automatic Test
Equipment (ATE). It includes the definition of hardware and software needed for analog
and digital signal testing using a Test Unit Adapter common interface. This standard
describes the overall ATE system concept as well as the definition of the specific
elements of those systems.
ARINC Report 625-2: Industry Guide for Component Test Development and
Management defines recommended standard practices for developing Test
Specifications (TS) and Technical Support and Data Packages (TSDP) to support
alternate and equivalent implementations for all CMM tests. This report introduces a
new term “Test Implementation Package” (TIP) which is similar to a Test Program Set
ARINC Specification 626: Standard ATLAS Language for Modular Test defines an
airline-recommended subset of ATLAS intended to be used in conjunction with test
systems that are compliant with ARINC 608A. ATLAS is a standard abbreviated English
language used in the preparation and documentation of test procedures that can be
implemented with automatic or semi-automatic test equipment.
ARINC Report 627-2: Programmers Guide for SMART™ Systems Using ARINC 626
ATLAS provides guidance to ATLAS test programmers for developing, writing and
documenting test programs in ARINC 626 ATLAS. This is a companion standard to
ARINC 608A, Design Guidance for Avionics Test Equipment. It provides guidance to
managers and system integrators for standardizing test programs and their
documentation.
ARINC Report 668: Guidance for Tool and Test Equipment (TTE) Equivalency provides
guidelines for the process used to establish the equivalency of TTE and related
procedures other than that recommended by the OEM. Primarily, ARINC 668 is
concerned with equipment specified or recommended for the purpose of performing
specific tasks concerning the airworthiness of an article (e.g., avionics, hydraulics,
pneumatics, mechanical devices, etc).
Process Standards
ARINC Report 431: No Fault Found – A Case Study provides the final report of AMC
Task Group 116 formed to discover the causes of “No Fault Found” in avionics
equipment during test. This standard identifies sources and provides recommendations
for improvement.
ARINC Report 663: Data Requirements for Avionics Component Maintenance focuses
on the many aspects related to component technical data and documentation including
a common understanding of levels one - three maintenance (test, repair, re-
certification). This includes defining the extent and format of OEM documentation to be
delivered to the airline customers to support both the decision and technical
requirements to accomplish level three maintenance; establishing minimum data
requirements to support the airlines' decision relative to the accomplishment of level
three maintenance (test solution, type of repair process, projected MTBF, modification
potential, unit cost, alternative repairs, etc.); and identifying the minimum technical data
requirements to support level three maintenance in airline shops for future avionics
components (test, documentation).
ARINC Report 670: Guidance for Materials, Processes, and Parts Equivalencies states
industry rules and guidelines support/mandate equivalency, but provide very little
guidance on how to realize MPP substitution. Currently, industry guidelines fail to
provide adequate direction to maintenance facilities for material, process, and part
equivalencies. Suitable substantiation procedures to be able to select alternate
materials are demanded by the air transport industry. The purpose of ARINC Report
670 is to provide clear definitions for materials, processes, parts, substantiation
requirements, decision boundaries and limitations, and a standard process for
equivalency determination. This report is intended as general guidance for avionics
maintenance facilities; however, this does not preclude its use for other sectors of
aircraft maintenance as appropriate.
ARINC Report 667: Guidance for the Management of Field Loadable Software
describes effective methods to manage and distribute operation flight software
programs, aeronautical data bases and other forms of software used within an airline
organization. Topics include software acquisition, software receiving, software
distribution and necessary documentation. The FLS management process described in
ARINC 667 is compatible with published FAA/JAA guidance on this subject. Software
suppliers, airline users and regulators will find this document to be a practical and
effective guide.
ARINC Report 673: Guidance for the Use of UHF Radio Frequency Identification
(RFID) defines the minimum requirements for implementation of UHF-RFID for
component management within the commercial air transport industry. The secondary
objective of this document is to define the minimum data set required to allow the free
interchange of information between all organizations involved in the life cycle of the
component. A third objective is to provide guidance for the implementation of UHF-RFID
technology in the airframe and component supply chain and maintenance operations.
ARINC Report 604-1: Guidance for Design and Use of Built-In Test Equipment (BITE)
The primary purpose of BITE is to assist maintenance personnel in the proper
maintenance of avionics systems in a cost-effective manner. A description of a
Centralized Fault Display System (CFDS) is included in this standard. The CFDS
accumulates fault data, presents this data to a maintenance operator, and assists
troubleshooting by performing diagnostic tests and performing verification testing after
installation of a replacement unit.
ARINC Report 644: Portable Maintenance Access Terminal (PMAT) contains the
electrical interface definition, and a functional description of a PMAT. The intent of this
standard is to provide general and specific design guidance for the development of a
PMAT primarily for airline use.
ARINC Report 644A: Portable Multi-Purpose Access Terminal (PMAT) is intended for
use in the airplane maintenance environment allowing remote access to onboard
systems. This standard describes the aircraft interface, operational capabilities and
standards necessary to achieve interoperability with onboard systems, stand-alone
internal or external mass memory devices, and ARINC standard printers.
ARINC Report 669: Guidance for Lead-Based Soldering, Repair and Rework provides
guidance for using industry standards for developing a soldering program tailored to
meet the specific requirements of the user. Moreover, it provides uniform guidance for
maintenance facilities based on industry standards and, therefore, should be accepted
ARINC Report 671: Guidance for the Transition to Lead-Free Soldering, Maintenance,
and Repair provides guidance for the use of international standards for the maintenance
of lead-free electronic equipment. The purpose is to assist manufacturers, maintenance
facilities, and operators to define lead-free soldering requirements and to minimize the
set of lead-free solders, processes, and practices to gain consistency across the
industry.
ARINC Report 672: Guidelines for the Reduction of No Fault Found (NFF) provides
guidance for the removals of equipment from service for reasons that cannot be verified
by the maintenance process (shop or elsewhere) are a significant burden for aircraft
operators. This phenomenon is commonly referred to as No Fault Found (NFF). Many
other industry guidelines have been created in the past addressing NFF. NFF is often
perceived as a shop-only problem or an individual component reliability problem. This is
not true. NFF solutions require an inter-disciplinary effort to identify the true causes and
implement successful solutions. This document describes the most common sources of
NFF and provides guidance to develop appropriate solutions. The sources of NFF are
spread throughout the following four domains:
• Design/Production
• Flight operations
• Line operations
• Shop operations
This report provides a holistic view of the NFF problem based on the above domains
and the following categories:
• Documentation
• Communication
• Training
• Testing
• System/Components design