AVCON CAME I.4-Rev1
AVCON CAME I.4-Rev1
AVCON CAME I.4-Rev1
Continuing Airworthiness
Management Exposition
(CAME)
This document is the property of, and contains proprietary information of Avcon Jet AG. This
document is delivered on the condition that it is used exclusively to evaluate the contents
therein and it shall not be disclosed, duplicated, or reproduced in whole or
in part without the prior written consent of:
Avcon Jet AG
Wohllebengasse 12-14
1040 Vienna
Austria
www.avconjet.at
Approved under ref. AT.CAMO.A-117 (Ref. AOC A-117) by Austro Control GmbH, as
Competent Authority of Austria, a member state of EASA
Continuing Airworthiness Management Exposition CAME
Document Issue 4, Revision 0 © AVCON JET AG, 2021. ALL RIGHTS RESERVED
INTENTIONALLY
LEFT
BLANK
Table of Content
Revision List
Issue 4
Rev. Revision Date Revised by
0 02.08.2021 GRM
1 21.03.2022 DOC
Additionally, the revision is also made available to following parties by sending an electronically copy to
them via e-mail:
2. AOJ fully supports the principal of Just Culture. The objective of our Just Culture policy is to foster an
environment whereby employees and related contractors are empowered to report any safety risk
without fear of retribution, in the clear understanding that the Company accepts that errors and
lapses of judgement may occur and that staff, in the course of their normal, expected duties, do not
intentionally commit such errors. Additional information from occurrences shall not be used to
attribute blame or liability to front line staff or other persons for actions, omissions or decisions
taken by them that are commensurate with their experience and training and for any purpose other
than the maintenance or improvement of aviation safety.
3. Employees who make honest mistakes or misjudgements will not incur punitive action – provided
that they report such incidents in a proper, timely fashion, and cooperate with any subsequent
investigation. The only exceptions to this general non-punitive policy are where the actions or
omissions involve negligence, reckless disregard or a failure to report safety incidents or risk
exposures. An employee who acts irresponsibly in one of these ways is potentially exposed to
disciplinary action. An employee compliance with reporting requirements will be a factor to be
weighed favourably in the Company’s decision making in such circumstances.
4. The primary responsibility for safety rests with the Accountable Manager. However, safety is the
concern of everybody.
5. The AOJ method of collecting, recording and communicating information obtained by the reporting
system has been developed to protect, to the extend permissible by law, the identity of any
employee who provides safety information.
22.03.2022
Dated ..............................Signed ...............................................................
Christian Hrauda
Accountable Manager and Chief Operations Officer
Signed .....................................
Dated 22.03.2022
......................................
Christian Hrauda
Accountable Manager
Signed .....................................
Dated ......................................
Alexander Vagacs
Chief Executive Officer
AOJ holds an AOC with approval Number A-117 for commercial air transport. The related Camo
approval is granted under approval number AT.CAMO.A-117. The aircraft operated on the AOC of
AOJ consist of various types of aircrafts, which allows AOJ to provide the best solution for the
customer to serve a worldwide operation.
All offices of AOJ relevant for the AOC operation including its CAMO office are located at:
Wohllebengasse 12-14
A-1040 Vienna
The main task of the AOJ Camo is the management of the aircraft operated under its AOC. AOJ Camo
holds the following privileges, limited to the types of aircraft, listed in Section 0.2.3 of this exposition:
1) the organisation remaining in compliance with Regulation (EU) 2018/1139 and its delegated
and implementing acts, taking into account the provisions related to the handling of findings
as specified under point CAMO.B.350;
2) the competent authority being granted access to the organisation as specified in point
CAMO.A.140;
3) the certificate not being surrendered or revoked.
The termination, suspension or revocation of the air operator certificate automatically invalidates
AOJ`s certificate in relation to the aircraft registrations specified in the air operator certificate, unless
otherwise explicitly stated by the competent authority.
Upon revocation or surrender, the certificate shall be returned by the AM to ACG without delay.
Currently all locations of AOJ are under the oversight of ACG and no oversight tasks are performed by
another competent authority.
Further details about the management structure of AOJ are detailed in Section 0.4 of this exposition.
Regardless of the legal and financial independence from other companies, due to common
shareholders involved, the companies Avcon Jet AG (AOJ), Jet24 GmbH (Jet24) and Avcon Jet Malta
Ltd (VCJ) are sharing resources or are having subcontracting arrangements in place with each other
as defined in 5.3. Specifically shared resources for ACo and AE are only in place between AOJ and
Jet24. Any other arrangements are covered by subcontracts. If resources are shared this must be
accounted for in a combined manpower plan. Where this is the case, this is defined in 0.3.14 of the
applicable organization`s exposition.
Since the initial issue of this revision, the processes between the mentioned companies are
harmonized wherever possible which allows more efficient processes in case of shared resources or
subcontracting, improves in regards to human factors principles and allows the mutual recognition of
certain procedure trainings as defined in this exposition in case personal is moving between the
organizations.
d) Consortia
This paragraph is not applicable.
Gulfstream GVII AMP-AVCON-CZE-GVII Small Fleet OK-VOS No Yes CTP Invest, spol s.r.o. 21 Mar 22 Part M
Gulfstream GVI AMP-AVCON-G650 Small Fleet OE-LIV No Yes AOJ N/A Part M
ATTENTION: This table shall be revised each time an aircraft is removed from or added in the list.
*Operated under 83bis agreement. Deviating procedures may be applicable for paragraphs 1.1.2, 1.2.3.d, 1.4.1, 1.7, 2.11, 4.5, 4.8.1.a and 4.9 of this exposition.
Following Aircraft Types AOJ is approved for, but does not currently manage, including the privilege to carry out airworthiness reviews:
• Bombardier CL600-2B19
• Cessna 525A
• Cessna C680
• Hawker 900XP
• Airbus A320 Family
• Gulfstream G150
• Dornier 328
• Cessna C560
• Cessna C680A
0.2.5 Facilities
AOJ is located at Wohllebengasse 12-14, 1040 Vienna. The Management including the AM is located
at the 4th Floor. The Camo Office is placed in various rooms at the 3rd Floor as follows:
• The working places of the PCA and deputies are located in the “Postholder” office (3-03)
together with other Postholders of AOJ
• The working places of all AE are placed in the “Engineering” office (3-04)
• The working places of all ACo are located in the “Red Ops” office (3-10)
• The ARS is located in Office 3-02
• The CM and Safety Manager are located in 3-09
• The continuing airworthiness records are stored at:
o “Archive” (3-05),
o In shelfs next to the working places of the AOJ CAMO Employees, and
o In the basement (not shown on below plan)
The meeting rooms at the 4th Floor can be used by AOJ CAMO on demand. The complete facility offers
sufficient space for continuing airworthiness record storage and working places. The below plan gives
an overview about the rooms:
A change of any management personnel must be reported to the competent authority as specified in
Section 0.5.
All members of AOJ Camo required fulfilling a minimum level of knowledge, experience and
qualifications, depending on their position. Please refer to the trainings policy in 0.3.15 for detailed
requirements.
He also has corporate authority for ensuring that all the operations of AOJ can be financed and
carried out to the standard required to maintain the air operator’s certificate of AOJ.
This includes particularly having appropriate arrangements (e.g. in regards to facilities, material and
tools, sufficient competent and qualified personnel, subcontractor arrangements, maintenance, etc.)
in place and ensuring the financing related to those arrangements.
The AM also holds the position of AM in the operational part of the AOJ AOC.
The AM has the ultimate financial responsibility for all continuing airworthiness activities performed
in accordance with this exposition and under the Camo approval of AOJ.
The AM establishes and promotes the safety policy as shown in 0.1.1 of this exposition and is holding
the direct safety accountability.
The AM nominates the persons described further in 0.3.1 to 0.3.3 and 0.3.5 to 0.3.6.
If the AM changes, it is required, that the new AM signs the corporate commitment stated in section
0.1.1.
• Utilize a record system to document the management activities and store these records for at
least 5 years;
• Perform initial and recurrent competence assessment with personnel described in 0.3.4 (see
section 0.3.15), update the training schedule after each competence assessment or as
necessary and organize the relevant trainings;
• Administrate the personnel files of all AOJ Camo employees as described in section 0.3.4;
• Verify proposed AltMoCs for compliance;
• Verify amendments to this exposition i.a.w. 0.5 or 0.6 and ammendments to any other
manuals (included but not limited to AMPs);
• Perform all tasks in regards to the reliability programme as defined in section 1.10.;
• Run the compliance monitoring system including contracted and subcontracted activities and
perform all related tasks i.a.w. section 2.8;
• Verify any update to the manpower analysis;
• Verify new or revised maintenance contracts;
• Monitor the closure of findings, their root cause analysis and related preventive actions; and
• Monitor regulation changes, distribute them, implement audits at their effective date and
audit their implementation accordingly.
• Liaising with Austrocontrol regarding compliance and auditing.
Details of the required qualifications of the CA are defined in 0.3.15. In deviance to the competence
assessment of other personnel, the assessment of the CA is performed by the CM.
If no audit has been performed by one CA within a period of 24 month, the CA shall perform another
audit under supervision of the CM, before the next audit is performed by this CA
Details of the required qualifications of the MSO are defined in 0.3.15. In addition to the competence
assessment of other personnel, the assessment of the MSO must be attended by the SM.
In case a deputy is defined for a position in section 0.4, this person shall take over the responsibilities
in case of longer absence for limited time.
In case no deputy is defined for a position in section 0.4, the holder of this position is responsible to
nominate a deputy before his absence.
The absence from the office is not necessarily an absence in sense of this paragraph, if the person is
able to continue fulfilling his tasks and responsibilities in a remote way (e.g. during business trips).
a) Deputy PCA
In case of longer absence of the PCA, a deputy PCA shall take over his duties for a time up to one
month. If the PCA is constantly absent for a time exceeding this period, the PCA shall report this to
ACG, including the reason and the expected duration of his absence. If the PCA is not able to do this,
connected to the reason of his absence, the AM shall perform this reporting to ACG.
b) Deputy CM
Currently no deputy CM is defined. In case of longer absence, the CM shall therefore define a person
to take over the CMs duties before the leave.
c) Deputy SM
In case of longer absence of the SM, a deputy SM shall take over his duties for a time up to one
month. If the SM is constantly absent for a time exceeding this period, the SM shall report this to
d) Deputy MSO
Currently no deputy MSO is defined. In case of longer absence, the SM shall review the situation and
need to supersede the MSO temporarily. In such case the MSO may be replaced by a person fulfilling
the relevant requirements and after an internal assessment up to a period of 3 months.
Subchapters 0.3.10 to 0.3.12 list the persons, which perform airworthiness tasks under the
supervision and responsibility of the PCA.
As the PCA is the ultimate responsible person within AOJ Camo for all airworthiness tasks performed,
the PCA shall control and coordinate the tasks performed by the below described groups of persons.
The PCA shall organize regular Camo Meetings in order to collect all relevant information about the
fleet and give advises to the Airworthiness Controllers and Airworthiness Engineers. All ACo and AE,
which are present in the office at the dates of the meeting, shall attend. Nevertheless, the ACo and
AE shall at any time immediately inform the PCA about any issues, which require the PCA`s
immediate decision or attention.
0.3.12 Subcontractors
Subcontractors are used to perform continued airworthiness tasks, if the internal manpower is not
sufficient or if the AM decides to use subcontractors for other reasons.
Depending on the sub-contract itself, the tasks performed by the subcontractors may consist of the
ACo tasks, the AE tasks, or both for specific aircraft. The extent of the subcontracted work is defined
in each subcontract.
Continuing Airworthiness Management Exposition CAME
Document Issue 4, Revision 1 © AVCON JET AG, 2021. ALL RIGHTS RESERVED
Part 0 General Organisation, safety policy and objectives 0.3-10
0.3 Management personnel Iss 4, Rev 1
21. Mar 2022
Competence assessment of subcontractors is done IAW training policy in 0.3.15 as required by the
role of the subcontractor (ACo, AE, or both).
Section 5.3 gives a detailed overview about subcontractors and the subcontracted part of the work.
In order to allow the PCA to keep the overview and authority over the continued airworthiness tasks
performed by subcontractors, they shall either attend the regular meetings as described in 0.3.11 or
send a bi-weekly report to the PCA. The subcontractor reporting form (Form 5.1.01) gives guidance
about the minimum content of such report. The report shall be reviewed by the PCA or an ACo or AE
dedicated by the PCA to review the reports on his behalf. Depending on the extent of the report the
review may be carried out to 100% or by a sampling appropriate to the extent of the report. In case
AOJ Camo disagrees with the planned actions, the PCA shall inform the subcontractor accordingly.
Beside the bi-weekly reports, the subcontractors shall involve the PCA in any major decision, which
may affect the airworthiness of an aircraft or in any other decision, which requires the PCAs
immediate attention. In AOG situations or in case of MEL application, the subcontractor shall inform
AOJ Camo immediately by e-mail. The notification shall include the aircraft registration and all
relevant details about the event. The PCA or an ACo or AE dedicated by the PCA to supervise AOG
situations on this aircraft shall monitor the actions taken and shall involve himself in case of any
disagreement with the actions planned by the subcontractor.
Subcontractors are not allowed to modify or change any approved procedure. All subcontractors
have to follow the procedures described in this exposition. Changes to approved procedures in the
AMPs, if their development is subcontracted, can only be performed if the PCA agrees on the change.
Maintenance Records shall be made available by the subcontractor to AOJ Camo, either digitally or in
hardcopy, as defined in the subcontract.
AOJ shall only sub-contract to organisations which are specified by ACG on AOJ`s current EASA Form
14.
The SM shall include the subcontracted activities when identifying the organisation`s safety risks in
accordance with section 2.1
The subcontractors shall at any time give ACG access to their facilities. This is also defined in every
sub-contract itself.
Dep. PCA
Training
MSO
PCA
ACo
ART
ARS
CM
SM
CA
AE
CAME*
Internal training about Came procedures
AMC5 CAMO.A.305(g)/(a) X/2 X/2 X/2 X/2 X/2 X/2 X/2 X/2 X/2 X/2
AMC1 CAMO.A.305(c)/(f)
EASA Part M and Part CAMO*
Regulation Training X/2 X/2 X/2 X/2 X/2 X/2 X/2 X/2 X/2 X/2
AMC5 CAMO.A.305(g)/(a)
Aircraft Type Familiarization Training
Within 24mth
Level 1 General Familiarisation of one X X X X X X
type in the fleet or compareable systems
AMC1 CAMO.A.310(a)(3)t
Maintenance Programmes*
internal training on actual AMPs, held by X/2 X/2 X/2 X/2
PCA or AE
Maintenance Programme Development
Course
Development and requirements of X/3 X/3 X/3
maintenance programme
AMC4 CAMO.A.305(g)/(d)
Reliability Training
AMC4 CAMO.A.305(g)/(d) X/3 X/3 X/3
Fuel tank safety Phase 2 / recur.
Within 12mth X/2 X/2 X/2 X/2 X/2
Appendix III to AMC4 CAMO.A.305(g)
Fuel tank safety Phase 1
Within 6mth X X X X X X X X X
Appendix III to AMC4 CAMO.A.305(g)
Quality and Compliance Management
AMC4 CAMO.A.305(g)/(c) X
Internal Safety and Reporting Procedure
Training X/2 X/2 X/2 X/2 X/2 X/2 X/2 X/2 X/2 X/2
AMC5 CAMO.A.305(g)/(a)
Safety Training including human factors
AMC3 CAMO.A.305(g) including GM1 X/2 X/2 X/2 X/2 X/2 X/2 X/2 X/2 X/2 X/2
and GM2 to it.
Safety Continuation Training Customized
Training based on last 24mth occurences
and safety matters done by SM X/2 X/2 X/2 X/2 X/2 X/2 X/2 X/2 X/2
AMC5 CAMO.A.305(g)/(b) and AMC1
CAMO.A.202/(c)(3)
Training for staff involved in internal
investigations X/2 X/2 X/2
AMC1 CAMO.A.202/(b)(5)
Auditing Principles
X X X X X X
Airworthiness Review Staff Training
X
Maintenance Tracking Tool
Training or experience based evaluation
on Campsystems or other used tracking X X X X X X X X
tools
Dep. PCA
Training
MSO
PCA
ACo
ART
ARS
CM
SM
CA
AE
Practical CAMO Training (10 working
days) X
LTH 77 4.2
Practical Training in a contracted
maintenance organization (5 working
days) X
LTH 77 4.2
*This training is required before repetitive interval, if major changes to procedure or regulation are
published.
Dep. PCA
Experience/Knowledge
MSO
PCA
ACo
ART
ARS
AM
CM
SM
CA
AE
Basic understanding of EASA Part M and
Part CAMO X
Relevant knowledge, background and
satisfactory
experience related to aircraft continuing X X X X
airworthiness management
Working knowledge of EASA Part M and
Part CAMO X X X X
Demonstrate a complete understanding
of the applicable regulatory
Requirements (Part M, CAMO, 145, 21,
bilateral agreements, national
requirements, AMC20, etc.) X X
Note for ARS: “Relevant parts of initial
and continuing airworthiness
regulations”
Demonstrate relevant knowledge,
background and applicable
experience related to the activities of
AOJ CAMO including knowledge and
experience in compliance monitoring
Note for SM and MSO: “understanding of X X X
management systems, including
compliance monitoring systems;
operational experience related to the
activities of the organisation”
practical experience and expertise in the
application of aviation safety standards X X X X
and safe operating practices
a comprehensive knowledge of relevant
parts of operational requirements and
procedures; AOJ's operations
specifications and the need for, and X X X X
content of, the relevant parts of AOJ's
operations manual.
Relevant parts of operational
requirements (EASA Ops) and procedures X
(OMs, ODs, etc.)
knowledge of Human factors principles
and safety management systems based
on the EU management system
requirements including compliance
monitoring and ICAO Annex 19 X X X X
Note for SM and MSO “knowledge of
ICAO standards and European
requirements on safety management”
5 years of relevant work experience, of
which at least 2 years should be from the
aeronautical industry in an appropriate
position X X X X X
Note for ARS: “5 years of experience in
continuing airworthiness”
Dep. PCA
Experience/Knowledge
MSO
PCA
ACo
ART
ARS
AM
CM
SM
CA
AE
a relevant engineering degree or an
aircraft maintenance technician
qualification with additional education.
Note: for ARS “acquired an appropriate
licence in compliance with Annex (III)
Part-66 or an aeronautical degree or a
national equivalent”
The above may be replaced by 5 years of X X X X
experience in addition which cover an
appropriate combination of experience
in tasks related to aircraft maintenance
and/or continuing airworthiness
management and/or surveillance of such
tasks
thorough knowledge of the
organisation's CAME X X X X X
knowledge of maintenance methods X X X X
at least 5 years of experience in
continuing airworthiness X
Satisfactory completion of an
airworthiness review under the
supervision of the competent authority,
or under the supervision of another AOJ
ARS as ART.
NOTE: Airworthiness Reviews carried out
under Avcon Jet or International Jet X
Management are mutually accepted by
the other organisation for such
supervision effective from the approval
of this issue of this exposition due to
equivalence or similarity of processes
acceptable under AMC2 CAMO.A.305(g)
been involved in continuing
airworthiness management activities for
at least 6 months in every 2-year period,
or conducted at least one airworthiness
review in the last 12-month period or X
conduct Airworthiness Reviews under
Supervision to restore recency
requirements.
safety management experience X
an understanding of risk management;
an understanding of safety investigation
techniques and root cause X X
methodologies;
understanding and promotion of a
positive safety culture X X X
interpersonal and leadership skills, and
the ability to influence staff; X
oral and written communications skills;
data management, analytical and
problem-solving skills X X
Compliance Auditors
Maintenance Safety
Officer [ref. to section 2.8.6]
Markus Grafl
Andre Weber Jürgen Körber Jürgen Körber
(Nominated Person
(Nominated Person (Nominated Person (Nominated Person
Continuing
Groundoperations) Flightoperations) Crewtraining)
Airworthiness)
Sub-Contractors
[refer to section 5.2]
Deputy PCAs
Airworthiness
Review Staff
Airworthiness Controller
Airworthiness
Review Trainees Airworthiness Engineers
Sub-Contractors
[refer to section
5.2]
Deputy PCA
Name: Christian Dollberger
Nationality: Austrian
Mobil: +43 676 83211 887
E-mail: [email protected]
SM – Safety Manager
Name: Martin Pühringer
Nationality: Austria
Mobil: +43 676 898 717 751
E-mail: [email protected]
Changes listed above shall only be implemented following the approval by ACG.
Any other member of AOJ Camo may suggest changes directly to the PCA or by the use of the SMS
system.
Such amendments shall be prepared by the PCA or his deputy and signed in section 0.1.2 by the AM
and CEO. The PCA may also dedicate the preparation of a Came revision to any properly qualified and
experienced employee of AOJ Camo. In this case the PCA shall give guidance about the content of the
revision and review the prepared amendment. Following the PCA`s review, the amendment is sent to
the CM for a compliance review before the revision is sent to ACG for verification and approval. As
applicable such amendments shall be accompanied by an EASA Form 2 when sent to ACG. If findings
are raised by ACG during the verification process, the PCA is responsible that the findings are closed.
As soon as ACG approves such amendment, it shall be distributed to any member of AOJ Camo and
the recipients according the distribution list in the introduction section of this exposition. The
exposition and the received approval shall be stored as described in this section and the old revision
shall be archived to avoid any confusion about the most actual revision.
In the case of a planned change of a nominated person, the revision shall be submitted to ACG at
least 4 weeks before the date of the proposed change or at the earliest opportunity in case of
unforeseen changes.
In order to keep the revision system traceable, all revisions shall be stored in digital.
The approval of the latest amendment approved by ACG and Form 5.1.05 of the current amendment
(if applicable) shall be stored electronically or in hardcopy.
No original hardcopy of the Came exists. However, it is acceptable that any member of AOJ Camo prints
his own copy for reference. In this case the individual person is responsible to check if his copy matches
the current version of the Came.
Additionally the PCA shall send each revision to the addresses listed in the distribution list in the
administrative section of this exposition. When distributing the revision, the survey function of outlook
is used to confirm receipt and the confirmation list is stored together with the revision.
The folder on the server shall also contain the approval as well as all connected forms and the historic
Came revisions and issues as far as they are available.
The person, who prepared the revision, shall be responsible to store the documents on the server as
described and distribute the revision as per the distribution list on the beginning of this exposition.
a) Identification of Revisions
Each version of the exposition shall be clearly identifiable. Therefore a numbering system, consisting
of 3 parts has been established:
(1) Issue Number:
This number shows the number of the issue. A new issue number is only used if the majority of the
exposition has changed or complete new processes have been implemented in the majority of the
chapters.
A numerical system is used. The number 0 indicates the original issue and each issue the number is
raised by 1.
A new issue requires prior approval i.a.w. 0.5 of this exposition
(2) Revision Number:
A new revision number is given anytime a change requiring prior approval is done. A numerical system
is used. The number 0 indicates the original revision of the issue and each amendment or revision the
number is raised by 1.
(3) Revision Letter:
A letter is used to indicate any change done i.a.w. section 0.6 of this exposition. Each revision approved
by ACG shall not carry any letter. The first amendment that does not require prior approval is indicated
by the capital letter A. Each time such amendment is done, the letter should be raised in alphabetic
order. If Z is reached, a letter combination can be used. So e.g. following Z would be AA, AB, AC, [...],
AZ, BA, BB, BC, etc.
b) Highlighting of Changes
A short summary about any changes applied, shall be listed in the Highlights of Revisions and the
revision shall be included in the revision list. For any revision the record of revisions is amended,
regardless if it is a change requiring prior approval or a change not requiring prior approval. Once an
amendment is approved it shall not be deleted or edited in the highlights of revisions or the revision
list anymore by any further revision.
In case of a complete re-issue it is acceptable, but not required, to start the records of revisions again
to help for a better overview.
If the content or format of a page is significantly changed (not significant means e.g. correction of typos
if the meaning is not changed, correction of formatting errors, etc.), the complete section shall carry
the revision number of the amendment that leaded to the latest change. A section is defined by the
second level subchapter (e.g. 0.6).
All sections shall be listed in the list of effective pages with its issue, revision number and revision
letter. In addition the number of pages for each section shall be indicated in the list of effective pages.
Where a process is documented in another manual separately from this exposition, but is a process
required to be described in the CAME, the applicable pages are added to the LEP of this exposition
with it`s revision status. Whenever the relevant part of the external manual changes, the CAME is
revised as well and the applicable page is updated in the LEP.
Any change itself shall carry a revision bar on the righthand side of the text or graphic to indicate where
on the affected page the content or format had been changed.
This example text shows how the change is highlighted. This does not necessarily mean this sentence
had been changed in the current Came revision.
• Removal of registration marks in section 0.2.3, if this does not affect the scope;
• Adding of Registration mark in section 0.2.3 within the already approved scope;
• Changes of manpower resources if the manpower analysis leads to a satisfactory result;
• Changes to the list of contracted maintenance organisations if it does not affect the scope;
• Removal of ARC Staff in Section 5.2, if this does not affect the scope;
• Correction of typos;
• Editorial changes;
• Reduction of List of Airworthiness Review Extension Staff (Section 4.8.2) if the scope is not
affected;
• Changes in references to external manuals or implementation of changes approved by ACG as
part of the revision of another manual (e.g. change of nominated person flight operations
previously approved as part of an OM-A revision);
• Modifications to Forms, affecting the Layout, amending the content by additional items, etc..
Note: In this case, Section 5.1 shall be changed together with the Form, to show the revision
letter of the form and the form shall be replaced; and
• Changes to contact details of the same person (e.g. new mobile phone number)
• Removing an aircraft from a subcontractor setup if manpower permits and as long as it is not
the last of the type subcontracted
• Adding an aircraft to a subcontractor setup if the type of aircraft is already approved to be
subcontracted to the specific subcontractor
• Changes to internal procedures other than those listed in 0.5
Such amendments of this exposition are also prepared as described in section 0.5.1 with the
exception that it is not sent to ACG for approval.
Such amendments require a 4-eye principle preparation. This means it is either prepared by a deputy
PCA or other properly qualified personnel and reviewed by the PCA, or prepared by the PCA and
reviewed by the deputy or other qualified personnel.
During such amendment not requiring prior approval, the revision number is not raised, but a letter
for the revision status is added. This letter remains until the page is revised by any future revision.
Also the list of effective pages shall be updated during each amendment.
Instead of the approval by ACG, the revision is prepared and distributed to the CM and the SM for
their review together with form 5.1.05 on which the changes are documents.
The CM performs a pre-audit of the procedures outlined in sections 0.5 and 0.6 of this exposition and
for compliance with regulatory requirements. Potential findings are communicated to the PCA who is
responsible to implement the corrective actions as applicable and re-distribute the revision to the
The SM performs a risk analysis for the implemented changes and performs a management of
change process. In case of a positive outcome the SM also signs form 5.1.05 accordingly.
Once Form 5.1.05 is signed by all parties, the PCA distributes the revision i.a.w. section 0.5.1 and
sends the revision to ACG for information together with the completed form 5.1.05.
The revision takes effect immediately upon distribution. However, if ACG disagrees with the changes
or the verification that it does not require prior approval, the revision is revoked and any
implemented changes have to be undone.
Any AltMOC requires approval by ACG prior it can be implemented into the approved processes and
used.
Before a proposed AltMOC is submitted to ACG for approval i.a.w. CAMO.B.120, an internal
documented evaluation has to be performed. For this purpose form 5.1.06 is used.
The PCA fills form 5.1.06 with all required details such as reference to the regulatory requirement,
any already existing AMC or AltMOCs, a description of the proposed procedure, reference to the
internal process (e.g. CAME, AMP, etc.) that is planned to be changed, personnel involved in the new
procedure, outcome of the review for compliance with the actual regulation by the CM and details
about the risk assessment performed by the SM together with the MSO. As required the SM and
MSO may establish a safety action group to perform a more detailed analysis.
Once form 5.1.06 is completed and signed by PCA, SM and CM, it is sent to the AM for final internal
approval. The completed form is sent to ACG together with any relevant attachments for approval.
As soon as ACG notifies AOJ that the alternative means of compliance is approved and may be
implemented, the related procedures are implemented by the relevant revision process of the
applicable manual following a pre-audit of the CM, the second part of Form 5.1.06 is filled and signed
and the AltMOC is listed in section 5.7.
Each TAL page has a sequence number and 4 carbon copy pages:
• Original Page
remains in the book;
• Green Copy
For Maintenance Facilities (if needed);
• Pink Copy
For Camo;
• Yellow Copy
For Accounting; and
• Blue Copy
For Ops
In addition to the TAL itself, the technical log system on the aircraft also contains the hold item list
(HIL) (Form 5.1.08) and the dent and repair chart (Form 5.1.09). These two documents are kept in the
TAL retainer together with the TAL.
The HIL is a list of all open defects, carried forward in accordance with the deferred defect policy in
accordance with section 1.8.(c), except structural defects such as dents and except temporary
repairs.
All temporary repairs, permanent repairs with any possible effect on future repairs or carrying
limitations and acceptable structural deferred defects are recorded on the dent and repair chart.
Information about details when the next scheduled maintenance is due is also considered to be part
of the aircraft technical log system. However, this part is managed via the software “Fl3xx”. The data
entered into Fl3xx by the ACo is automatically printed on each crew briefing. This ensures that the
crew has got the most accurate information for each flight. The ACo has to update this information in
“Fl3xx” within reasonable time after each maintenance event.
The crew is also responsible to report any occurred defect via the Techlog system. The ACo is
responsible to control and monitor this procedure. In case of any problems, the ACo shall report this
to the PCA, who as required contacts the NPF.
Any defect, which could affect the airworthiness of the aircraft, shall be primarily recorded in the TAL
in the field “discrepancy” at the line of the applicable leg. On the right hand side next to the
discrepancy, the crew shall sign the entry. The text of the entry shall be chosen in a way to give the
most appropriate and detailed information as possible and shall clearly identify the affected system.
The crew shall inform the responsible ACo about each entry.
Defects accidentally entered by the PIC into the technical remark/discrepancy column may be
cancelled by him with a clear line and sign of. Wrong entries could be technical malfunctions
following operational mishaps or wrong root cause analysis.
In case the entered defect can be deferred in accordance with section 1.8. of this exposition, it shall
be entered into the hold item list or the dent and repair chart as applicable.
Entries into the dent and repair chart usually require a maintenance action. This could be a
temporary repair or a measurement and evaluation against approved data in order to ensure that
the dent is within approved limits. The ACo is responsible to update the dent and repair chart
accordingly and to provide an updated version to the crew. The original chart, which is utilised by the
ACo is stored in digital on the Server in the aircraft folder.
In case of hold item list entries, they are either made by a contracted maintenance organisation or
directly by the flight crew, depending on the nature of the defect (see also 1.1.1.c). In case an item is
transferred to the HIL, this shall be documented on the righthand side of the discrepancy in the field
for corrective actions. An appropriate reference to the HIL item number shall be made and the crew
or certifying staff shall sign the transfer accordingly. In case of MEL items, the MEL code shall be
referenced in the applicable field next to the discrepancy. The ACo receives a copy of the HIL from
the crew or the contracted maintenance organization prior flight. Only upon satisfactory verification
that the techlog and HIL item(s) was/were filled accordingly, an internal release to service
information is distributed including all possible instructions or impacts to the operation resulting
thereof.
If a defect is not transferable, it must be fixed before any further flight. In such case the contracted
maintenance organisation shall enter the corrective action into the applicable field and the certificate
of release to service section shall be used to release the aircraft. Separate release to service
certificates attached to the TAL instead are only acceptable if they are attached to the TAL in a
permanent way. Additionally at least a reference to the attached release to service certificate shall
be made in the corrective action field.
Further maintenance records with more details are kept as defined in section 1.3.2.a.
The TAL itself and any changes to it are approved by OM-A Chapter 8.1.11 and OM-A appendix C
section C.1 as well as part of chapter 5.1 of this exposition. AOJ Camo and AOJ flight operations are
therefore responsible to organize the approval of any changes to the TAL. The PCA is responsible to
gain the approval of the TAL on Camo side before it is used.
The HIL and the dent and repair chart are approved as part of this exposition (Form 5.1.08 and Form
5.1.09), and AOJ Camo is therefore responsible to organize the approval of any changes. Before these
documents are sent for approval, the PCA shall send it to AOJ Operations compliance monitoring
manager and AOJ Nominated Person Flight Operations (NPF) for verification. As soon as the revision
is approved, it shall be sent to [email protected] for information.
If an aircraft is operated under 83bis agreement, the MEL may be approved by the authority of the
state of registry or the state of the operator as specified in the applicable implementation letter.
a) General
The Minimum Equipment List (MEL), approved by ACG, permits dispatch of the airplane with certain
items or components inoperative provided an acceptable level of safety is maintained by appropriate
operation, by a transfer of functions to another operating component, or by reference to other
instruments or components providing the required information.
The MEL contains only those items of airworthiness significance which may be inoperative for AC
dispatch, provided limitation and appropriate procedures are observed. Equipment obviously basic
to airplane airworthiness such as wings, rudder, flaps, etc., is not listed and must be operative for all
flights. Any item related to the airworthiness of the aircraft and not included in the MEL are
automatically required to be operative for aircraft dispatch.
Equipment obviously not required for safe operation of the airplane, such as galley equipment,
entertainment system, etc., are defined as “Passenger Convenience Items” and are not required to
be operated for dispatch of the aircraft. These items can be entered into the HIL without due date.
b) MEL Categories
Depending on the category of an MEL item, the due date for the corrective action shall be defined:
Category A
Items in this category shall be repaired within the time interval specified in the remarks column of
the operator’s approved MEL;
Category B
Items in this category shall be repaired within three (3) consecutive calendar days, excluding the day
the malfunction was recorded. For example, if the defect has been recorded at 26.01.2013, 10:00
a.m., the three day interval starts at 27.01.2013, 00:00 a.m. and ends at the end of 29.01.2013. The
time is considered to be UTC, equal to the recorded times in the TAL;
Category C
Items in this category shall be repaired within ten (10) consecutive calendar days, excluding the day
the malfunction was recorded; or
Category D
Items in this category shall be repaired within one hundred and twenty (120) consecutive calendar
days, excluding the day the malfunction was recorded
Attention: The due date is calculated starting from the date of defect occurrence (TAL entry), but not
from the date when the defect has been deferred.
c) Application
In case of defect, the crew or the contracted maintenance organization may use the MEL to
determine if an item applies for MEL usage. In any case the ACo is contacted and the application of
the MEL item is discussed. In case an MEL item is applicable, it must be evaluated if operational
restrictions or maintenance actions are required.
Depending on the aircraft type and the approved MEL, following restrictions or actions may be
required:
• (O) indicates a requirement for a specific operations procedure which must be accomplished
during planning of and/or when operating with the listed item inoperative. These
procedures are and/or obeyed usually accomplished by the crew. The crew is responsible
that this procedures are followed;
• (M) indicates a requirement for a specific maintenance procedure which must be
accomplished prior to operation with the listed item inoperative. Procedures requiring
specialized knowledge or skill, or requiring the use of tools or test equipment must be
accomplished by maintenance personnel. The ACo is responsible to have this item ordered
at a contracted maintenance facility and to have the maintenance action documented
properly;
• (M*) defined as specific selected maintenance procedures for flight crews which must be
accomplished prior to operation with the listed item inoperative. These procedures are
accomplished by either maintenance personnel or flight crews. These items do not exist in
every MEL and are subject to the applicable MEL approval. This kind of items may require a
specific training for the crew. In this case AOJ trainings department monitors the training
requirement for the crew. The ACo is responsible to organise that this task is performed,
either by a crewmember or by a contracted maintenance facility.
When all required actions have been set accordingly, the item is transferred to the HIL and the due
date is set accordingly. The transfer to HIL shall be mentioned in the corrective action section of the
TAL. If no (M) item is required this may be performed by the crew or by a contracted maintenance
organisation. For (M) items only a contracted maintenance organization is allowed to transfer the
item to the HIL.
An extension can only be granted once for maximum 100% of the original time limit.
When an item has been extended, it shall be stated in the rectification column. Even if the MEL
extension form has already been signed earlier in order to allow the extension, the extension shall
only be entered at the due date or at the first flight day after the due date. In order to extend the
item on the HIL, the original item shall be closed using the following or a similar wording “MEL item
extended internally – refer to item X”. The closing date shall be the original due date. A new line will
be opened with the extended item. The entry date of the new item is again the due date of the old
item (not one day after). The item should be opened with a wording indicating that it is the same
item as above. The new due date shall be set according to the internally approved extension form.
“Category A” items must not be extended at any time without agreement of ACG.
Any maintenance performed on the fleet managed by AOJ Camo shall be performed in accordance
with the applicable maintenance program and shall only be done by maintenance facilities approved
under EASA Part 145.
Any type of aircraft listed in the table in Table 1 of section 0.2.3 requires a maintenance programme.
1.2.2 Content
The Aircraft Maintenance Programmes (AMPs) are primarily based on the recommendation of the TC
Holder of the relevant Aircraft. It shall describe all maintenance requirements including their
variations and tolerances, and a reliability programme if applicable.
The requirements for each aircraft fleet shall primarily be based on the TC Holders instructions and
other sources as described in Section 1.2.3.a.
Each maintenance Programme consists of at least two parts. The first part is a document, which
explains the background, the basis, the sources and other important information about the
maintenance requirements and how AOJ Camo and the contracted maintenance facilities have to
ensure they are followed.
For the structure of the first section, AMC M.A.302(d) and Appendix I to AMC M.A.302 shall be used
as guideline.
The second part is a detailed list of all requirements, which is an export from the electronic tracking
programme, such as Camp, CMP, Cescom, etc.
For specific procedures for the use of campsystems, refer to Chapter 6 of this exposition.
1.2.3 Development
a) Sources
As mentioned above, the primary source for each AMP is the TC Holder instructions, while the
Airframe Publications are considered to be the leading document. The Airframe Publications give
further information about other (S)TC Holder instructions to be consulted or not. The following list
gives examples of typical publications, provided by the Airframe Manufacturer:
• MRB Report;
• MPD;
• MPM;
• TLMC;
• AMM Chapter 4 and 5;
• STLMC/SMM; or
• Any other relevant publication listed in the TCDS
Not all of the mentioned documents are used by all manufacturers and depending on the different
manufacturers, various names for the documents may be used.
If not clearly defined, at least Manufacturers Publications for Components with own Type Certificates
(e.g. Engine, APU) are consulted.
Following Publications are typical examples for documentation that needs to be consulted in addition
to the Airframe manufacturer’s publications:
Further Requirements for the AMP are resulting from national or operational requirements, such as:
• LTHs;
• LTAs; and
• EASA Air Ops
• CS26
• operational specific information as per AOC (e.g. ETOPS, non-ETOPS, RVSM, etc.)
• CDCCL requirements
• Etc.
b) Responsibilities
The designated AE develops the initial AMP and monitors the need for an AMP revision as described
in paragraph C of this section.
The ACo of an aircraft has to inform the AE after each maintenance event, if modifications or repairs
have been done, which could require an AMP revision.
In case an AMP revision is necessary, the AE shall, in cooperation with the PCA, determine if it
qualifies for an indirectly approved revision in accordance with paragraph (4) of this section, or if a
directly approved revision is necessary.
The PCA shall reviews and accepts each revision before it is sent to the CM for verification and
internal approval.
After verification by the CM, the AE rectifies all internal findings if there are any and afterwards
submit the AMP to the competent authority as described in paragraph (4).
The record keeping of AMP related documentation, including direct and indirect approvals is handled
by the AE.
c) Manual Amendments
The AMP is a dynamic document, requiring a continuous monitoring and revisions.
Additionally the need for an AMP revision shall be evaluated in following cases:
• Any of the sources described in Section 1.2.3.a or in the AMP itself is revised;
• A modification (e.g.SB) is performed which could change a task interval or applicability, given
in the manufacturers publication under a condition (e.g. applicable for AC pre‐SB xx);
• An upgraded P/N or S/N of a part is installed as per IPC, which has an effect on the LLC
requirements;
• An STC or other modification which includes ICAs is incorporated;
• A repair, which could lead to permanent limitations or check requirements, is performed;
• New requirements (e.g. national requirements, EU-Ops/EASA-Ops Requirements, etc.) are
published or revised;
• The reliability programme (refer to section 1.10) requires the revision of the AMP to
introduce a new task or de-escalate a task;
• An aircraft is added to or removed from the AMP;
• The registration mark of an aircraft changes; and
• Other reasons, such as changes in operating environment, major change in utilization, new
experiences on the operator side, change in the operational approval, etc. require an AMP
revision
In case of administrative Tasks are added to the tracking programme, no immediate revision of the
AMP is required. The new administrative Tasks will be listed in the list of applicable tasks of next AMP
revision
In order to monitor the need for AMP revisions, the AE as well as the ACo shall be aware of the above
listed conditions, which could lead to AMP revisions.
The AE shall use the revision status checklist (Form 5.1.12) to perform a check of the currently
published and currently available Manual Revisions against the current status of the AMP. This check
shall be done each calendar month. The actual version of Form 5.1.12 shall be stored in the fleet and
engineering folder.
In case of a revision or new publication of any source of the AMP, the AMP shall be revised and
submitted to the competent authority. The revision shall be finished not later than by the end of the
second month, following the month when it has been found during the revision check.
The ACo shall inform the AE about the installation of modifications or repairs latest during the
paperwork check, defined in section 1.3.2.b when the maintenance record checklist (Form 5.1.13) is
filled out.
In case of modification or repair that include any ICA relevant to the AMP, the AMP shall be revised
and submitted to ACG within 3 month following the date of CRS of the modification or repair
installation. If the modification or repair includes a requirement due earlier than 3 months after the
referred CRS, the limit for the AMP revision is the first due of the introduced task
To track the revisions properly, the same numbering system as described for the Came (see section
0.5.1.a) shall be applied. An example for a correctly named revision would be: AMP-AVCON-TYPE-I.3-
Rev.5.B
Most types of changes to the AMP require the direct approval by the authority. However, for
following cases, AOJ Camo may internally issue a revision of an AMP, approve it indirectly and track it
by a suffix, added after the revision number as defined in 1.2.3.c:
• Changes based on approved (S)TC holder data, especially but not limited to the following
cases;
o Changes to data which have already previously been a source of this AMP;
o Corrections of errors which constitute a non-compliance with current version of
approved data;
o Ammendments necessary by changed task applicability between different options
both allowed by the approved data. (e.g. caused by change of Partnumber of pre- or
post-mod status, etc.);
o Adding of tasks based on new repairs or newly installed modifications (SB, STC, etc.)
or
o Removal of tasks resulted from repair/modification that has been removed (e.g. if a
previously repair or temporary repair is removed by part replacement or finally
repaired with changed or removed ICA.
• Wording Changes based on directly approved AMP changes if they are of later approval date
than the section replaced, limited to the following:
o General wording changes which are not specific to the type or kind of operation (e.g.
AMP revision procedure, general repair policy, etc.);
o Type specific wording changes based on an other AMP which is based on the same
TCDS
• De-Escalation of intervals as result of the reliability programme. Escalations and de-
escalation of structural tasks do not qualify for indirect approval;
• Removal of an aircraft from the AMP;
• Adding of an aircraft to AMP if
o an AMP for an aircraft of the same type is already approved and;
o if the additional aircraft is new or imported from an EASA memberstate;
• Closing the condition of a conditional approval granted temporarily by ACG or internally
during the indirect approval process.
• Tasks given as guideline or optional by the OEM or tasks defined in the AMP as
administrative tasks;
Before any revision is approved, the AE verifies all changes against the above listed privileges. If all
applied changes are covered by above list, the AMP qualifies for indirect approval process. The AE
suggests such fact to the PCA. If the PCA agrees, the AE prepares the revision and sends it to the PCA
for a detailed review.
If the revision requires a direct approval, the AE shall send it to ACG and request the verification and
approval of ACG after the review and acceptance by the PCA. When sending the revision to ACG, the
AE shall enclose an application signed by the PCA or deputy.
Revisions, which qualify for an indirect approval, shall be prepared in the same way as revisions,
which require the direct approval of ACG, but additional procedures described below need to be
followed.
The AE shall prepare the first page of the indirect AMP revision approval form (Form 5.1.14).
Depending on the changes applied, the PCA or deputy has to check all changes of the revision against
the appendix of Form 5.1.14 applicable for the type of changes.
Any findings of the PCA or deputy shall be recorded in this list. In case of findings, the open findings
are sent back to the AE for correction. The AE shall implement the corrections and answer the
findings on the Form. The PCA or deputy is responsible to check all corrective actions and finally
accept them. As soon as all findings are closed, the revision is sent together with the completed form
and applicable appendices to the CM for verification. The verification of the CM shall focus on the
compliance with regulations and approved procedures. Specific attention of the CM shall be paid on
the applicability of the indirect approval process itself and if this process was properly followed.
Any findings of the CM shall be communicated to the PCA and the AE in written. The AE is
responsible to correct the findings raised by the CM.
The AE shall thereafter distribute the revision together with the signed Form 5.1.14 within 10 days to
ACG for information as outlined in the Distribution list. If ACG disagrees the indirect approval, the
AMP revision shall be revoked and sent for direct approval to ACG.
In case a new aircraft is added to the AMP and not all tasks have been listed in the AMP yet or other
points of the checklist in Form 5.1.14 are not fully met, the PCA may consider a temporary
conditional approval of the AMP.
In case a temporary approval is considered, this condition has to be stated in the approval section of
form 5.1.14. In order to ensure the condition does not affect safety, the PCA has to consult the Safety
Manager to perform a risk analysis for the condition. The completed and signed risk analysis shall be
included to the AMP approval and transmitted to ACG together with the AMP and the completed and
signed Form 5.1.14.
A conditional approval can only be issued on temporary basis. The time limit for the temporary
approval is defined by the PCA, but shall not exceed the first maintenance due date affected by the
condition (e.g. if certain tasks are not included in the AMP or certain tasks do not meet all
requirements, the next due date of this task shall be the maximum limit of the conditional approval).
In case an AMP is temporarily approved under such condition, the limit of validity of the temporarily
approved AMP shall be tracked in IQSMS by the CM as a finding.
If the finding is not closed by the deadline, the AMP shall become invalid for the affected aircraft and
the aircraft is not considered airworthy anymore. In such case the PCA shall ground the aircraft and
inform all relevant departments and the AM by e-mail.
No AMP revision shall be distributed before either the direct approval is received or the indirect
approval process has been finished and ACG has been informed accordingly.
The latest direct approval and any indirect AMP revision approval, applying to this directly approved
revision shall be stored in the fleet and engineering folder.
The old AMP revision, stored on the server in digital, shall be moved to an old revision folder and the
actual one shall be stored directly accessible in the AMP folder in word as well as in pdf. If a revision
is in progress it shall be based on a copy of the original word file, which shall be stored in another
subfolder of the actual AMP, called “work”.
Form 5.1.14 and all applicable appendices shall be stored in the fleet and engineering folder by the
AE.
The records contain documentation about all performed flights, including date, destinations, flight
times and flight cycles as well as all maintenance performed including components replaced,
modifications performed, repairs performed and documentation of any scheduled and unscheduled
maintenance performed. Additionally general records about each aircraft are held as applicable (e.g.
engine condition trend reports, aircraft related contracts, etc.).
All maintenance related documentation and all utilisation records are stored chronologically. For
maintenance records, all available records of a maintenance event shall be stored together with the
release to service document of the aircraft and the certificates of all components installed at this
time.
On some aircraft the manufacturer provided logbooks for engine, airframe and APU may be used.
This mainly depends on the wishes of and agreements in place with the owner. However, these
usually do not provide as many details about the work performed, as the maintenance records
described in Section 1.3.2.a and are therefore not part of the mandatory maintenance record
keeping procedures. The Volume IV of the Maintenance Records of each aircraft shall be seen as
detailed logbook.
Ground Operations personnel is responsible to enter the flight times and cycles into the software
“Fl3xx”. The total times and cycles are compared between the TAL and the software on a monthly
basis. In case of any discrepancy, the error is investigated and as applicable, crew or maintenance
facility is requested to correct the error on the TAL.
Any member of AOJ Camo has got access to the software at his working station.
Additionally to the monthly checks by ground operations personnel, the ACo is responsible to
compare the times, whenever any maintenance action is performed, to ensure that the hours and
cycles on the CRS are correct. If any mismatch is recognized, he shall contact the ground operations
to clarify where the mistake happened and to correct the software or the TAL accordingly.
Further the ACo is responsible to regularly update the hours and cycles of each aircraft in the
applicable tracking programme in order to maintain an accurate maintenance due list.
Additionally to the e-mail copies of the TAL, the pink original carbon copies of each TAL are collected
and sent to AOJ Camo. Those original copies are stored by AOJ Camo, as described in section 1.3.2.
On different aircraft types, depending on their AMP, specific usage data such as freon hours or APU
starts and hours are required to be recorded. Depending on the aircraft type, this information is
either provided regularly by the crew by the use of the applicable field on the TAL or read out by
1.3.2 Records
a) Record keeping system
The AOJ Camo record system consists of different types of folders, including the hours and cycle
records, a main file with all general aircraft information, a file with maintenance records, etc.
Depending on the age of the aircraft, each file may consist of several single folders. All folders
referred to in this section exist in hardcopy. For some items (e.g. insurance certificates) electronic
copies may exist additionally.
Below is a brief description of the details regarding the record keeping system:
This file is not available in hardcopy anymore, but is electronically stored on the server in folders
specific to each aircraft listed in 0.2.3. This file at least contains the following content as a scan copy:
• All ACG issued certificates
• Current Insurance
• Radio Station License
• ELT Registration, Selcal, assigned mode S Code
• Current Weight and Balance and all calculated amendments thereto
• As applicable any modifications including applicable approvals, ICAs, AFM Supplements, etc.
or completion manuals and customized placard listings
• As applicable any repairs and the current Dent and Repair Chart of the aircraft
Additionally, there is also some optional or commercially relevant information stored in the same
folder as for example:
• Bill of Sale and Customs Documentation
• Copy of previous and not anymore needed Export CofAs
• Handover and Takeover lists including those for e.g. optional loose equipment
• Compliance checklists for e.g. CS26 or CAT.IDE
• Commercial Contracts and subscriptions of the aircraft
• Emergency Equipment lists (in addition to the primary status in Camp) or Pax briefing card
copies
• Any acceptance flight protocols from the past
• Additional Documentation received at aircraft delivery such as e.g. Flammability reports,
Delivery AD/SB/Part Status, Electrical Load Analysis, Paint specifications, etc.
• Relevant Correspondence
• Any other documentation deemed relevant by the ACo
This documentation is at least retained 3 years after the relevant aircraft has left AOJ`s fleet.
Continuing Airworthiness Management Exposition CAME
Document Issue 4, Revision 1 © AVCON JET AG, 2021. ALL RIGHTS RESERVED
Part 1 Continuing airworthiness management procedures 1.3-3
1.3 Continuing airworthiness records: responsibilities, Iss 4, Rev 0
retention and access 02 Aug 2021
Volume II – Reserved
Volume II is reserved for any other records deemed necessary by AOJ Camo to be stored.
Volume II does not have any requirements to retain it. Depending on the content, the PCA takes the
decision how long the records are retained.
The fleet and engineering folder shall exist for each fleet only. No single folder is created for each
aircraft. The fleets are defined as per the table in section 0.2.3. The AE is responsible to maintain and
update the fleet and engineering folder. This folder shall contain the following as applicable:
The fleet and engineering folder need to be retained at least 3 years after a fleet is not managed by
AOJ anymore.
A WO shall be issued for any scheduled or unscheduled maintenance performed on the aircraft.
Generally the ACo is responsible to issue WOs for his aircraft. During his absence another ACo takes
over his duties. In certain cases, also an AE may issue a WO in coordination with the responsible ACo.
For the issue of the WOs, the content shall be defined by a report, created from the maintenance
tracking programme. Unscheduled items may be included as discrepancy or squawk (or different
name, depending on the tracking programme). The used tracking programme is defined in the
specific AMP.
The report from the tracking programme shall be accompanied by the workorder cover sheet (Form
5.1.15a), which give further information, refers to the applicable tracking programme WO and carries
the signature of the AOJ Camo personnel, which issued the WO.
Each WO shall be defined by a unique number. The number shall be created by the registration
without the “OE-“ in the beginning, followed by a 6 digit code, created from the date (YYMMDD) and
one subsequent number, used if more than one WO is issued the same date.
As a specific example, the second WO, issued for OE-ISM at 19.07.2013 would be numbered ISM-
130719-2
Upon receipt of the workpackage, the ACo shall within reasonable time control the workpackage for
completeness and correctness and update the tracking programme accordingly. If support for the
update of the tracking programme is provided by the tracking programme itself, the ACo shall control
any updated items on a 100% basis.
The established maintenance record checklist (Form 5.1.13) shall be used as guideline. The filled-out
checklist shall be included to the workpackage as coversheet in Volume IV of the record system. It is
acceptable for small maintenance events, consisting of a few tasks only or consisting of servicing
actions only, that the workpackage checklist is used as guideline, but not filled out and stored.
Form 5.1.13 contains a section to be completed prior flight. Only upon satisfactory completion of all
items listed in this section the internal release to service information is distributed within AOJ.
For specific procedures for the use of campsystems, refer to Chapter 6 of this exposition.
c) Preservation of records
Any records described in section 1.3.2.a shall be stored in the AOJ Camo Office, in a way that it is safe
from environmental stress or damage and protected from theft.
The complete AOJ Camo office is equipped with smoke and fire detection system.
The office of AOJ is locked. Every room of the Camo office itself can be locked as well. Only personnel
of AOJ have got access to these offices.
The Camo office is located in the 3rd floor and therefore not exposed to any risk of flood.
The hardware for electronically stored data is located in the server room of the facility shown in
section 0.2.5. An external company is responsible for the IT infrastructure and ensures a regular
backup to an external server.
In case an owner terminates the contract with AOJ Camo, but does not nominate a new Camo, the
records are handed over directly to the owner.
In any case, the handover shall be documented by the use of the handover protocol (Form 5.1.16).
In the unlikely case that AOJ or AOJ Camo goes out of business and for any reason, the handover
cannot be performed in an appropriate way or an aircraft remains without another Camo, the
aircraft records shall be handed over to the aircraft owner.
When Campsystems has been used as maintenance tracking programme, at time of transfer the
“ezVault” feature is used to retain a clone copy of the aircraft for 3 more years. For commercial
reasons it is important that the ACo ensures the 3 years are being subscribed and pre-paid at the
time of phase-out to ensure coverage by the customer. Camp shall be notified at this time that it
shall terminate automatically after this time.
Continuing Airworthiness Management Exposition CAME
Document Issue 4, Revision 1 © AVCON JET AG, 2021. ALL RIGHTS RESERVED
Part 1 Continuing airworthiness management procedures 1.4-1
1.4 Accomplishment and control of airworthiness directives Iss 4, Rev 0
02 Aug 2021
1.4 Accomplishment and control of airworthiness directives
AOJ Camo regularly checks for any published ADs, verifies them, orders them as applicable and keeps
the AD status of each aircraft up to date. The following paragraphs outline the process, which is
applied to fulfil this obligation.
The applicable authorities for each type are defined in the relevant AMP. Generally the applicable
authorities are ACG, EASA and additionally as per ED Decision 2019/18/ED of 03.06.2019, the
authority of state of design for a design of or a design change related to an aircraft, engine, propeller,
part or appliance which has been validated by EASA, or before 28.09.2003, by an EASA member
state, unless EASA has adopted a different decision.
Additionally, the webpage of ACG and EASA is checked by the AE for any measures in an immediate
reaction to a safety problem and any other recommendation issued by EASA or ACG. Furthermore,
the Risk Assessment is managed by the SM under OMM chapter 3.8.2.
Aircraft operated under a 83bis agreement may require the implementation of ADs issued by the
state of the operator in addition to these issued by the state of registry. The applicable
implementation letter for each aircraft gives details about the applicable ADs. This is also
implemented into the applicable AMP`s AD section.
The check shall be performed each calendar week. The signature of the responsible AE on the AD
check record (Form 5.1.17) every week documents the check. In exceptional cases, the AE may
extend the interval to bi-weekly. In any case the check shall be performed between the current date
and inclusive the date of last documented check.
The continuously filled form 5.1.17 shall be stored in the fleet and engineering folder as described in
section 1.3.2.a
As a redundant source, each AE shall subscribe to the applicable authorities` e-mail distribution lists,
applicable to the types he is responsible for.
If an AD is applicable, but the mandated actions (e.g. SB incorporation, previous revision of AD, Part
replacement that meets the intent of the AD, AFM/AMM/TLMC/… incorporation etc.) have already
been performed before the effective date of the AD, it depends on the industry standard of the
specific aircraft type and the engineering judgement of the AE how it is entered into the Status.
If an AD is applicable, the due date(s) shall be set accordingly. Repetitive ADs are either tracked in the
tracking programme as single ADs to be performed or as a task which is part of the maintenance
programme. If it is tracked as task inside the maintenance programme, it has to be clearly marked to
ensure no extension applies. In this case the AD itself can be left without due date and a reference
shall be made that it is task controlled. In this case the AD shall be tracked without due date in the
status and a remark (e.g. “task controlled”) shall be made.
ADs requiring the implementation of a task (e.g. due to revision of CMRs in the manufacturers
publications), the AD is not considered repetitive itself, but shall be tracked with its due date until
the tasks are implemented into the AMP i.a.w. section 1.2.3.c of this exposition. Afterwards a remark
of incorporation at the AD is sufficient to document the compliance. No Part 145 CRS for such ADs is
required.
ADs requiring an operational action (e.g. implementation of specific pages into the AFM or MEL) shall
be communicated to the responsible person in the flight operations department (e.g. fleet chief) via
e-mail and [email protected] shall be set in copy. The AD can be considered complied,
when the responsible person replies back that the action has been set. The AE shall document this
into the tracking programme by an appropriate remark or by printing the relevant e-mail as pdf and
attach it to the AD in the tracking programme.
ADs applying to completely different aircraft or to components, which are not allowed to be installed
on this type of aircraft at all, are not required to be tracked as “not applicable”.
When the ADs have been put into the tracking programme by the AE, the ACo is responsible to order
their incorporation at contracted maintenance facilities and update the AD in the tracking
programme accordingly when it has been complied.
It is supposed, that the ACo is informed about the due dates of ADs by the regular check of the due
list. However, for ADs and especially emergency ADs with very short compliance times, the AE shall
inform the ACo and PCA about the newly published AD.
For specific procedures for the use of Camp for AD tracking, refer to Chapter 6 of this exposition.
When appropriate and necessary, amendments to the Maintenance Programme will be done in
accordance with section 1.2 by the AE and submitted to the competent authority.
Additionally to the reliability programme, the annual review of AMPs is performed according chapter
1.2.3.c. For aircraft not applicable to reliability monitoring, the annual review shall be the main basis
for the analysis of the effectiveness.
The following procedures are general. For the specific use of Campsystems, wherever the use of a
tracking programme is referred, see Chapter 6 to this exposition.
This also applies to cases where a Service Bulletin indicates that it has been published in anticipation
of an Airworthiness Directive (AD), to be issued by the competent authority (EASA, ACG or other
authority acting as State of Design) at a later stage. The process and documentation are described
under section 1.4.1.
However, as defined in the specific AMP for each type, certain modifications are treated the same
way as mandatory modifications (e.g. ADs) by AOJ Camo. This typically includes the above mentioned
documents, on which mandatory compliance is indicated or which are published as “alert” SBs or SLs.
All other SBs, SLs or equivalent are reviewed carefully by the AE. Three more general categories of
them could be found and require different actions.
Warranty allowances or special warranty programme due dates, as well as the expiry of the aircraft
warranty shall be considered when looking at costs and benefits.
The influence of in service experience or the reliability monitoring process (see section 1.10) may
lead to a change of the decision at a later stage.
If the costs are not clear it is an appropriate way to set a due date to an upcoming maintenance
event and review the decision when the costs are quoted by a maintenance facility. If it is denied
afterwards, the due date may be removed. A statement in the tracking programme might be useful;
b) Optional Publications
Publications with absolute optional character are not given a due date. Examples are modifications
published for specific needs or owner wishes to give them a legal basis and avoid costs for
engineering for each single customer. Typical examples are installation of a second ELT, Changes to
passenger convenience items, etc.
These modifications are reviewed upon request of the owner or if the need for a modification is
given by any other reason; and
c) Informational Publications
This are typically publications with additional information about topics, but without any
recommended modifications or checks for the operator.
This also includes publications, which are typically published by engine manufacturers, indicating a
specific status of spare parts upgrades (in accordance with the IPC), but do not permit or require any
action on their own.
This type of publications shall only be incorporated into the tracking programme as deemed
necessary by the responsible AE. If incorporated, no due date or comment is required, except if the
AE considers it useful.
Any SB found during the monthly Service Bulletin Evaluation is entered in the risk management tool
of IQSMS and undergo a probability/severity analysis. Attention shall specifically be paid to the
“reason” section of the relevant SB that describes the situation addressed by the SB which typically
gives the information required for this. If the risk prior SB evaluation is not within acceptable limits,
the SB shall be treated as mandatory, regardless of the categorization by the OEM. The analysis
remains saved in IQSMS. No hardcopy of the risk assessment exists.
The risk assessment is not necessarily specific to each aircraft, but in any case it must be carried out
for every specific SB found during the monthly check.
In this case a Part 21 organisation is either contracted directly or via a contracted part 145
organisation to develop an appropriate modification.
The modification has to be installed by a part 145 organisation to the standards given by the relevant
engineering documentation provided by the Part 21 organization. It is also the responsibility of the
Part 21 organisation to define the modification as major or minor.
All major modifications performed have to be properly documented in the aircraft records.
If a modification leads to new ICAs, the ACo shall inform the AE that verification is necessary, if an
AMP revision is required, even though the AE is usually already involved in major modification
projects at an earlier stage.
Further processes or communication may be required by the ACo as detailed on Form 5.1.13 which is
completed after the installation following any maintenance as described in section 1.3 of this
exposition.
In case of aircraft operated under a 83bis agreement, the applicable implementation letter may
include provisions concerning information about repairs or modifications carried out to the state of
registry. If this is the case, the ACo shall submit the repair or modification data to the competent
authority i.a.w. the letter.
If the pilots discover a defect, it shall be entered into the TAL and reported to the responsible ACo
immediately. This kind of defects is called Pireps.
If the defect is discovered by the contracted maintenance organisation during any scheduled or
unscheduled maintenance activity, they are called Mareps. Mareps are documented on the relevant
workreport. The contracted maintenance organisation however also informs the responsible ACo
immediately by the means defined in the applicable maintenance contract.
In case an aircraft has got a defect that does not qualify for a deferment i.a.w. the procedures
outlined in this exposition and is not grounded by Crew or maintenance organisation, the PCA is
entitled to remove the aircraft from service. Such decision is communicated internally by the PCA by
e-mail and shall be sent at least to dispatch, flightoperations and AM.
1.8.1 Analyses
The ACo is responsible to review all defects and verify them for their airworthiness impact as well as
any deferment possibilities as well as operational or commercial impacts when continuing operation
with a deferred defect.
The ACo shall ensure that all reported defects are contracted to be rectified by an approved
maintenance organization within appropriate time. The defect shall be entered into the applicable
tracking programme of the aircraft and a workorder shall be issued in accordance with section
1.3.2.b.
The verification of the defects may also require long term activities such as maintenance programme
evolution or the implementation of non-mandatory modifications. The need for long term actions is
verified in accordance with the approved reliability programme as described in section 1.10.
Findings of corrosion which exceed Level 1 (i.e., Levels 2, 3) must be reported to the relevant
authorities and the manufacturer.
Further the specific AMPs are giving guidance about potential additional reporting requirements.
Additional liaison may be required by the reliability process as stated in chapter 1.10.
In this case, the ACo will review the MEL and will verify the possibilities and restrictions which apply.
In case the aircraft is with a Part 145 organisation, this organisation shall be consulted for their
professional advice as well.
Besides the MEL a deferment of a defect may be based on other approved data such as the AFM of
the aircraft, the AMM or SRM.
In cases where the OEM supplies an approved CDL, typically as part of the AFM or as stand-alone
document, such items can be used to defer a defect. The documentation of a CDL item is performed
equivalent to an MEL Item as described in 1.1.2.
In case there is no due instruction for CDL items, the rectification of the defect shall be performed in
a reasonable and timely manner taking into account the utilization, location and next due
maintenance.
In case an item does not affect the airworthiness or safe operation, but is not listed in the MEL (e.g. if
the crew enters into the TAL “carpet dirty” or “scratch in leather of #2 passenger seat”), the
responsible ACo may decide after consultation with the PCA to defer this defect as well. In case the
effect on the safety or airworthiness is not clear, a contracted part 145 maintenance organisation
may be consulted.
Any open item on the HIL needs to be accepted by the operating crew. The formal acceptance of the
crew is documented by their signature for the pre-flight inspection.
Defects such as cracks and structural defects that are not addressed in the MEL or an other approved
document may only be deferred after review by an approved Part 21 design organisation in
accordance with 21.A.445 and 21.A.443 or by measures given in bilateral agreements between EU
and other states or authorities or other regulatory environments.
Any deferred defect except structural defects (e.g. dents) and temporary repairs shall be
documented in the HIL (Form 5.1.08) accordingly. Any deferrable structural defect as well as
temporary and permanent repairs will be entered into the dent and repair chart (Form 5.1.09). Any
permanent inspections or limitations arising from that will be implemented into the AMP by the
responsible AE as described in section 1.2.
The approval of ACG is required any time a deferred defect is outside the limitations of approved
data (e.g. NTO). If the repair is approved under Part 21, no further approval is required.
AOJ will seek to ensure by its technical expertise and practices that the minimum number of open
deferred defects exists. All open deferred defects will be monitored by the ACo and their earliest
possible rectification is scheduled.
This exposition describes the general process for different fleet sizes. The table in section 0.2.3 gives
further advice, which process is applied on which fleet.
While small fleets are analysed on an event based process, large fleets have got a complex
programme in place to identify the problematic areas properly without the need to review each
single item. For fleets below six aircraft, the complex process is not sufficient as not enough data is
available.
Each individual AMP shall also give further information about the fleet specific details relevant to the
reliability analyses of the specific fleet. However, the general process shall not be altered from the
process described in this exposition. Details described in the relevant AMP are:
The prime objectives of the reliability programme are to reduce the feasibility of an AOG, to increase
flight safety, to reduce the cost for unscheduled maintenance and to keep the aircraft availability
high. Therefore, the reliability programme has three key elements to archive that goal:
o to identify the critical items and to recognize the need for improvement actions;
o to establish what improvement action is needed; and
o to determine the effectiveness of that actions
Particularly with regards to the reliability process, it shall be obeyed by the ACo, that all reliability
relevant information is included. Pireps shall be entered upon receipt of the TAL entry. Mareps shall
be entered latest upon receipt and during the control of the workpackage.
The description of the defect shall at least match the description used by the pilot in the TAL or the
description used by the certifying staff of the contracted Part 145 organization, or may include a
more detailed description of the defect and the troubleshooting required.
The description of the corrective action in the tracking programme shall include the corrective action
performed and the replaced P/N and S/N as applicable. For easier tracking, the replaced P/N and S/N
shall be booked in the tracking programme in relation to the discrepancy/squawk when possible.
Further data related to the squawk/discrepancy may be entered into the tracking programme.
In CAMP, Pireps are marked as “PILOT REPORTED” and Mareps are marked as “TECHNICIAN
REPORTED” in the pull-down menu for the discrepancy type.
In CMP, the field “Facility” is used to either enter “Marep” or the name of the contracted Part 145
organization for Mareps or to enter “Pirep” or “Crew” for Pireps.
The end of the half year period shall be defined as 30th of June and 31st of December. In order to
ensure all data are included, especially Mareps recently detected during maintenance at the end of
the half year period, the export from the tracking programme shall be done at the end of the
following month (31st of July and 31st of January).
ATTENTION: Only aircraft, which have been managed by AOJ Camo for the full monitored 6 month
period shall be considered. The consideration of any other aircraft, left after the first months of a
period or joined the fleet within the period would result in misleading data.
After the exported data from the maintenance tracking programme are transferred into the fleet
reliability data sheet. The AE is responsible to review the data for correctness and amend it by any
missing information, which is required to perform the analyses.
Different reports may be generated in a later phase of the process from this sheet by using a filter of
the fleet reliability data sheet or hiding columns as applicable.
The first step of the preparation of the data shall be a review by the AE for items, which are not
relevant for the reliability monitoring. Such items may be administrative items logged as
discrepancy/squawk, cleaning items, servicing, part replacements due to normal wear (typically for
brakes or tires), etc. Such items can be deleted from the list. The final list shall only include reliability
relevant data and shall be sorted by ATA chapter.
This process shall take place within the next 2 weeks after the data has been exported and the fleet
reliability data sheet has been created and reviewed.
No classic alert level system is used by AOJ Camo, but mainly based on engineering judgement,
following the process defined further in this chapter. Therefore, reliability significant items are
defined in a different way. Generally, on a small fleet all items are reviewed, while on large fleets
certain trends and values will lead to the areas, which need deeper investigation and a detailed
review. Below described are the details for the different fleet sizes:
An issue occurring only once in the observed 6 month period on one of the aircraft of the fleet is not
necessarily reliability relevant data. However, issues on complex systems, which are not checked by
scheduled maintenance or other means of monitoring, might be defined by the AE as reliability
relevant in addition to repetitive defects described below, based on the Aes engineering judgement.
If a defect is occurring on more than one aircraft in the fleet or has occurred more than one time on
the same aircraft during the observed period, it can be considered as repetitive defect.
Issues occurring several times subsequently, but it is obvious, that only the last action solved the
defect finally, are considered as single defect in regards to reliability monitoring.
If a defect requires long term troubleshooting and is finally rectified by the replacement of a part,
this part shall be considered as failed. Parts, which were previously replaced during this process, shall
not be considered. The defect shall only be considered ones.
If a defect occurs on different positions (e.g. LH and RH) on the same system or part, it shall be seen
as two events, except if it occurs together at the same time on the same aircraft with the same root
cause (e.g. multiple tire burst).
Even different defect description might be one single event. If e.g. FMS 2 and EGPWS fails and the
issue is solved by the replacement of the modular avionics unit, it shall be considered as a single
defect to the replaced unit only, even if reported via two TAL entries.
The process of the analysis is not a part reliability review of a specific P/N, because different P/N can
be installed on the same position as alternate. The only purpose is the identification of similarities
between the events. For a review in regards to part reliability, there are not enough data available on
small fleets.
Any defects, identified by the review above as repetitive, shall be marked in the fleet reliability data
sheet in the column (“significant”).
The indications for defect rates are given by the look on different graphical displays. The fleet
reliability data sheet contains automatically created graphs about total Defects per ATA chapter, 6
month trends of flight hour related and total number of defects, and flight hour related and total
number of defects for each ATA chapter displayed on a monthly basis to see their trend.
Additionally for the large fleets, a report of removed parts is printed from the tracking programme.
For aircraft tracked in CAMP, the MTBUR Report is used. For aircraft tracked in CMP, the Mean Time
To Removal Report is used. From those reports the top 3 components are identified and marked on
the report.
For large fleets, the ATA Chapters identified by the list above shall be reviewed in detail to identify
the defects which cause the significant result of this ATA chapter. These items shall be marked as
significant in the fleet reliability data sheet.
ATTENTION: The increase or decrease in the number of aircraft in a fleet shall be taken into account
when the periods are compared. E.g. if the number of aircraft doubles, it does not show any
significance, if a number of defects is more than twice as described above, but the number of defects
needs to be more than 4 times as high.
Flight hour related defect rates are not affected by the influence of the number of aircraft. However,
long ground times or permanently grounded aircraft shall be considered as well as aircraft with
significantly higher or lower utilisation have joined or left the fleet since the last period.
This reason may be stated during the analyses to close an item without corrective action.
Therefore the responsible AE shall perform a research for possible corrective actions on all significant
items and for the large fleet in addition for the identified top 3 components.
The analyses for proposed corrective actions itself is the same, regardless if the significant items have
been figured out by the large fleet or the small fleet process.
For that purpose, the fleet reliability data sheet shall be filtered to exclude all items, which are not
found significant by the process in paragraph (1) and (2) of this section. A report of these items shall
be printed from the fleet reliability data sheet by the AE for each fleet. This report is called significant
items report. As necessary, the header of the fleet reliability data sheet shall be adjusted to name the
printed report correctly.
During the evaluation for proposed corrective actions, the process in section 1.10.4.(b) shall be taken
as guideline by the AE. This ensures that the analyses during the reliability meeting can be followed
without any delay.
All reports mentioned below in paragraph a and b of this section shall be stored by the AE in the fleet
and engineering folder of the relevant fleet.
b) Final documentation
Following reports shall be created and stored after the meeting:
The open item log shall be created from the fleet reliability data sheet. A filter shall be set
accordingly to display only items, which require further action, but are not listed with a closing date.
If any item of the period before is still open, it shall be transferred to the new open item log;
This log may consist of two pages. The open item log and the current significant items report shall be
filtered to display all items which have been finally closed with the date of the actual reliability
meeting; and
A statement shall be issued by the PCA to state if the currently applied reliability procedure is
effective or if any revision to the progress is needed. If any revision is needed, the statement shall
include a due date.
The effectiveness of the procedure itself shall be based on the adequacy of the procedure itself, the
possibilities to perform the procedure as described in this exposition and the effectiveness of the
corrective actions, which have been initiated by the result of the reliability programme.
The PCA leads through the reliability meeting. Additionally the AE and the ACo shall attend in an
active role. The CM joins the reliability meeting in a monitoring and control function. However, the
CM shall not be involved in any decision taken during the meeting to keep his independence.
o Review of open items of last period. In this phase the open item log of the last period shall be
reviewed if an improvement is visible and if incorporated improvement actions are effective.
It shall be discussed if the item can be closed. The PCA takes the final decision to close an
item, to further monitor an item or to incorporate an other action
Particular attention shall be paid on 1.10.5 before the item is closed. To close an item, the closing
date shall be entered into the applicable column;
o (large fleet only) Short presentation by the AE about the statistical data and the way how the
significant items and systems have been determined;
o Analyses of significant items. In this phase, the significant item report is reviewed in detail.
Depending on the background of the defects, described by the ACo, it shall be decided if
reliability improvement actions are necessary. The process defined in 1.10.4.(b) shall be
taken as guideline to find an appropriate corrective action. The result of this progress shall be
recorded and put into the fleet reliability data sheet to be reflected on the closed or open
item log, depending on the decision made. Any item marked as significant must be
commented accordingly in the fleet reliability data sheet; and
o (large fleet only) Review of the top 3 Part replacements (“MTBUR Report”/“Mean Time To
Removal Report”) and comparison to manufacturer top removal parts. The same analysis as
for the significant items found during any other process applies. In case the part matches an
already analysed issue, the analysis does not need to be done again. The result of the
analyses shall be added to the open or closed item log manually for all reviewed parts.
After the analyses the proposed action shall be written into the applicable column (“Proposed
Action”) of the fleet reliability data sheet, or if the analyses is not completely finished (e.g. further
data needed), the current status shall be mentioned in the relevant column (“current analyses
status”) of the fleet reliability data sheet.
A reference to the current point in the analyses is sufficient to document the analyses process for the
item. Further remarks may be done in the remarks column.
The last step of the reliability improvement is the monitoring of its effectiveness. During the review
of the open item log, it shall be considered, if an action has been proofed to have reduced the
related problem. No item shall be closed finally before this has not been evaluated. This does not
apply for items, where it has intentionally been decided to not set any action.
(1) ACo:
o Feed the applicable tracking programme continuously with any reliability relevant defects,
stating the defect (Taskcard or TAL entry text) and the corrective action, latest 30 days after
the aircraft has been released to service after the defect;
o Ensure any replacements of serialized parts are properly tracked in the tracking programme,
latest 30 days after the aircraft has been released to service after the part replacement;
o Join the reliability meeting and give background information about the defects as needed;
and
o Incorporate corrective actions as outlined in the open items log
(2) AE:
o Review the fleet reliability data sheet;
o Export the data from the tracking programme;
o Prepare the significant items report for the reliability meeting;
o Prepare proposed corrective actions;
o Join the reliability meeting and present the significant items report as well as the proposed
corrective actions;
o Create the reports after the meeting; and
o Store the records in accordance with the procedure
(3) Subcontractor:
The subcontractor shall take over the actions of the ACo or the AE as defined in the subcontract.
(4) PCA:
o Schedule and lead the reliability meeting;
o Taking the final decision if and which corrective action is necessary after discussion during
the reliability meeting;
o Taking the decision to monitor or close an item;
o Distribute all reports after the meeting and advise the ACo about the necessary actions;
o Supervision of all phases of the reliability process; and
o Inform the competent authority as defined in section 1.10.7
(5) CM:
o Taking part in the reliability meeting in a monitoring and control function
The weight and balance report resulting from a weighing or any amendments thereto has to be
distributed within AOJ by the responsible ACo prior any further flight. It shall at least be sent to
[email protected] and [email protected]
If modifications are performed which have got influence on the weight and balance, the
implementation of the modification shall be reported to AOJ operations as well.
AOJ operations utilises a spread sheet with all weighing data and the applied changes to track the
cumulative weight changes since the last weighing has been performed.
Certain modifications or repairs may include the necessity of a physical weighing. In this case the
weighing shall be performed after the incorporation of the modification or repair before any further
flight.
In case the weight and balance cannot be defined in a calculatory way (e.g. painting), an aircraft
weighing shall be performed.
The removal or addition of operational items is administrated by AOJ flight operations department
and does not require a change by a maintenance organization. This includes e.g. the removal of items
if permitted by the MEL (e.g. life rafts). Nevertheless the ACo shall inform all relevant persons and
departments in such case as outlined above.
After the maintenance has been properly carried out, a certificate of release to service is issued and
the aircraft airworthiness certificate remains valid for this flight.
Continuing Airworthiness Management Exposition CAME
Document Issue 4, Revision 1 © AVCON JET AG, 2021. ALL RIGHTS RESERVED
Part 1 Continuing airworthiness management procedures 1.13-2
1.13 Maintenance check flight procedures Iss 4, Rev 0
02 Aug 2021
The core part of the management system framework focuses on what is essential for safety
management, to:
AOJ has defined the processes of the management system in a separate Operator`s Management
Manual (OMM). Especially where processes are used in various areas of AOJ and not only in CAMO,
the below chapters are giving references to the OMM.
Where a process is documented in the OMM, the applicable pages are added to the LEP of this
exposition with it`s revision status. Whenever the relevant part of the OMM changes, the CAME is
revised as well and the applicable page is updated in the LEP.
• identify the causes of and contributing factors to any errors, near misses, and hazards
reported and address them as part of safety risk management
• ensure evaluation of all known, relevant information relating to errors, the inability to follow
procedures, near misses, and hazards, and a method to circulate the information as
necessary.
Reports can be made by any member of AOJ CAMO, subcontractors, contracted maintenance
organizations, crews or any other person via https://safety.asqs.net/ or by sending an email to
[email protected]
Further details about the safety reporting and investigation are detailed in OMM chapter 6.
Occurrence reporting and reportable occurrences see OMM chapter 6.1, for reporting persons see
OMM chapter 6.2 and reporting procedures are described in OMM chapter 6.3.
• AM
• PCA
• SM
• MSO
• CM
• Any other person deemed necessary by AM or a member of the board to deliver valuable
input
The main tasks of the CAMO Safety review board are to:
The responsibility to schedule the regular SRB Meetings lasts with the Safety Manager.
For details of the change management process refer to OMM chapter 3.7.2.
2.8.5 Monitoring that all contracted maintenance is carried out in accordance with
the contract, including subcontractors used by the maintenance contractor
Refer to OMM 4.1.2.5
Note: The related contracts shall be retained for 5 years as defined in 5.3 and 5.4 of this exposition.
Any employee of AOJ may report any kind of occurrence or defect that endangers or lowers flight
safety. Any occurrence listed in Annex I of 2015/1018 is mandatory to be reported by flight crew,
CAMO personal and other staff working under the AOC of AOJ.
Mandatory reports shall be submitted latest within 72 hours from the time when the person
recognizes the occurrence. The employee has fulfilled his personal reporting obligation when the
report has been submitted to the SMS.
The SM is responsible to analyze the report, identify potential safety risks and determine whether a
reporting the authority is required iaw CAMO.A.160, Regulation (EU) No 376/2014 and Implementing
Regulation (EU) 2015/1018.
Any employee submitting a report shall be protected by AOJ’s just culture and no actions shall be
taken against the employee due to mistakes made in connection with the reported event, except in
cases of gross negligence or premeditation.
The safety manager is responsible to handle the report based on the procedures stated in OMM
Chapter 6.1. Investigations are carried out by the SM together with the MSO i.a.w. OMM 3.7.3.4.
Note: Usually the competent authority that shall receive the report is the competent authority of the
state of registry. However, for aircraft operated under 83bis agreement, the reporting to multiple
authorities may be required. The specific agreement for the implementation of the 83bis for a
specific aircraft gives further details about the occurrence reporting. If no details are given in that
letter, the occurrence is reported to the state of registry as well as to the state of the operator.
The PCA is responsible to initiate the contract with an appropriate facility, fulfilling the following
requirements:
If a facility is found to fulfil all of the above listed requirements, a contract may be signed. Before the
contract is signed, it shall be checked against Appendix IV to AMC1 CAMO.A.315(c); by the CM. The
contracted maintenance facility shall be listed in section 5.4 of this exposition and the contract shall
be stored.
It is up to the discretion of the PCA to establish contracts with more than one maintenance facility for
the same type. However, all those facilities shall be in compliance with the above mentioned
requirements.
No maintenance shall be ordered with a maintenance facility, which does not have a contract with
AOJ in place, and is therefore not listed in section 5.4 of this contract, except in following cases:
• Servicing;
• Engine and Component Maintenance which can be managed by one-time workorders; and
• Unscheduled line maintenance
Even if in these cases when no contract may exist, all other requirements in this section shall apply
accordingly.
It should be noted that even where base maintenance is ordered on a case-by-case basis, there
should be a written maintenance contract.
Where no maintenance contract exists, the WO issued i.a.w. section 1.3.2.b may include form
5.1.15b in addition to the WO cover sheet 5.1.15a. If the MRO countersigns the acceptance of the
condition described in 5.1.15b, this can be deemed equivalent to a maintenance contract for the
specific event.
This section is directly related to the privilege listed in section 0.2 of this exposition. The privilege to
carry out airworthiness reviews is directly approved by ACG on EASA Form 14. This privilege is limited
to the aircraft types as described in section 0.2.3 and as stated on EASA Form 14.
If an aircraft is within controlled environment airworthiness reviews have to be carried out every 3
years.
One year after the issuance of an ARC and subsequently one year afterwards, AOJ Camo may extend
the airworthiness review certificate of an aircraft for one more year, if it has not left the controlled
environment (no change of Camo, no change of operator/owner) and if it has been continuously
maintained by approved EASA Part 145 organisation.
If an aircraft has not been in a controlled environment since the last issue of an ARC, a full review has
to be performed.
The airworthiness review certificate will not be extended or issued if AOJ Camo is aware or has a
reason to assume that the aircraft is in an un-airworthy condition.
ARS has to be assessed by the PCA and a co-assessor, before this staff is nominated for acceptance by
ACG. The PCA shall use form 5.1.03 to record the assessment of the person.
Following requirements have to be fulfilled by the assessed person as a minimum before the person
is nominated at ACG:
Appropriate responsibilities means the airworthiness review staff shall either have overall authority
on the airworthiness management process of complete aircraft (e.g. PCA or AM), or is independent
from the airworthiness management process of the specific aircraft (e.g. CM or any ACo or AE not
involved in the airworthiness management of the specific aircraft or type).
This means as example, if the PCA nominates an AE who deals with a specific type of aircraft or ACo
who deals with a specific aircraft registration, the review permit (Form 5.1.30) shall be limited to not
include that aircraft or type. The same limitations shall apply in case those conflicts arise from an
Continuing Airworthiness Management Exposition CAME
Document Issue 4, Revision 1 © AVCON JET AG, 2021. ALL RIGHTS RESERVED
Part 4 Airworthiness review procedures 4.1-2
4.1 Airworthiness review staff Iss 4, Rev 0
02 Aug 2021
additional position of the ARS within another Camo which contracts airworthiness reviews to AOJ
Camo.
A copy of Form 5.1.23 shall be given to the ARS. Form 5.1.23 shall expire latest at the date of the next
due competence assessment.
After a positive re-assessment, the PCA may extend the authorization for 2 more years.
Emergency Equipment (as required by Check of all required emergency equipment (e.g. crash axe,
EASA Air Ops and relevant certification megaphone, life vests, life rafts, first aid kit, flash lights, etc.)
standards) by S/N and expiry date against the record status
Serialized components Sampling of a few easily accessible serialized parts against the
record status
General Condition Inspection of Aircraft at a depth of a pre-flight or walk around
inspection as defined in the related manuals
Evident defects During above listed check, special attention shall be paid on
any repairs or dents not documented in the dent chart
Placards check Sample check of required placards and languages i.a.w. AMM
Ch. 11 or equivalent approved data.
The sampling shall at least include markings of emergency
exits and passenger safety information.
Aircraft Operation Operational actions and checks as deemed necessary by the
ARS. This may include flight control movement checks, engine
run ups or even check flights.
The ARS decides based on his experience, other findings during
his review and regulatory aspects (e.g. national requirements
of the state of registry, or importing requirements).
NOTE: Aircraft Operation shall only be done by authorized
personal (technician/pilot) and upon approval of the operator.
The ARC is valid for 12 month and can be extended twice for a period of another 12 month, if it has
been within controlled environment since the last issue of an ARC.
If the aircraft has been in controlled environment for the last 12 month and is managed by AOJ
Camo, after a full airworthiness review has been performed, the ARS may issues an ARC. EASA Form
15b is used. A draft Form can be found as Form 5.1.19 of this Came.
Within 10 days after the issuance of the ARC, the ARC has to be transmitted to ACG via e-mail.
An airworthiness review certificate cannot be issued nor extended if there is evidence or reason to
believe that the aircraft is not airworthy. All findings must be closed before the issuance of the ARC.
a) Record Check
When extension personnel is ordered by the PCA to perform an extension, a record review has to be
performed. The record review must not be performed earlier than 30 days before the expiration date
of the ARC.
Following items shall be checked as part of the record review:
• Aircraft has continuously been managed during the previous 12 months (since the issue or last
extension of the ARC) by the same continuing airworthiness management organisation;
• 100% check that all maintenance of the last 12 month has been performed by appropriately
approved maintenance organisations and
• 100% check of all CRS against following criteria:
o Correct AMP reference stated;
o Basic details of the maintenance carried out or appropriate reference to workpackage;
o The date the maintenance was completed;
o Correct hours and cycles comparison against “Fl3xx”;
o APU hours and cycles if applicable; and
o Correct identification of organisation and person issuing the CRS.
This record check shall be documented on the ARC extension form (Form 5.1.19). A copy of this form
together with the extended ARC shall be sent to ACG within 10 days.
In case of aircraft operated under a 83bis agreement, the applicable implementation letter defines to
which competent authority the ARC extension need to be sent.
1) The date of issue is the date on which the extension is entered into the certificate;
2) The airframe flight hours at the date of the extension
3) Here the ARES shall sign the extension;
4) The name of the company which issues the extension – this is Avcon Jet AG;
5) If the extension is performed within a 30 days period before the expiry or if it is performed
after the date of expiry, the new expiration date (after extension) is set one year after the
previous expiration date (not one year after the extension is performed). If the extension is
performed earlier, the review pattern cannot be kept and the expiry date is limited to one year
after the issue date of the extension;
6) The reference of the person as per section 4.8.2;
7) The approval reference of AOJ Camo – this is AT.CAMO.A-117.
An airworthiness review certificate cannot be extended if there is evidence or reason to believe that
the aircraft is not airworthy.
When the extension has been issued, the extension form and the extended certificate shall be stored
on the server as defined in section 1.3.
4.8.2 Personnel nominated to extend ARCs (ARES)
The below table shows the staff currently approved to extend ARCs. The reference number for each
person consists of the three-letter-code of Avconjet, the position (ARES for Airworthiness Review
extension staff and ARS for Airworthiness Review Staff) and the three letter code of the person.
• Type Group 1:
Aircraft with MTOW below 5.700kg
e.g. C510, C525, C525A, Premier I, etc.
• Type Group 2:
Aircraft with MTOW 5.700‐ 14.000kg
e.g. C525B, C550, C560XL, C680, LJ45, LJ60, etc.
• Type Group 3:
Aircraft with MTOW 14.000‐ 20.000kg
e.g. CL300, C750, G150, G200, F2000, etc.
• Type Group 4:
Aircraft with MTOW 20.000‐ 70.000kg
e.g. F900, F7X, A318, EMB‐ 145, CL850, etc.
• Type Group 5:
Aircraft with MTOW 70.000‐ 140.000kg
e.g. A320, B737‐ 700, A321, MD83, B757, etc.
• Type Group 6:
Aircraft with MTOW above 140.000kg
e.g. A340, A310, B767, B787, A380, B777, B747, etc.
The specific types AOJ Camo can perform an ARC for, are limited to the aircraft listed in section 0.2.3
of this exposition and on AOJ Camo EASA Form 14.
Airworthiness
Company Type Registrations Engineering AMP
Controlling
BizJet
BD100-1A10 OE-HRS Yes No Yes
Support
G200 OE-HOP Yes No Yes
C750 OE-HOH Yes No Yes
011QCM
EMB135 OE-IBK Yes No Yes
EMB135 OE-IRK Yes No Yes
LJ45
Bombardier LJ60
Aviation BD-100-1A10/11 [email protected]
EDDB x x
Services CL-600-2B16
Berlin GmbH BD700-1A10/11
BD700-2A12
525
Cessna
525A
Düsseldorf
EDDL 525B
Citation
EDDS 525C [email protected] x x
Service
LKPR 560
Center
560XL
GmbH
750
BD-100-1A10
General
CL-600-2B16
Atomics
EDMO BD700-1A10/11 [email protected] x x
AeroTec
EMB-550
Systems
EMB-135BJ
G200
G280
Gulfstream
GIV [email protected]
Aerospace EGLF x x
GV
Ltd
GVI
GVII
BD100-1A10,
G200, EMB-135,
LFSB,
BD100-1A10,
LSGG,U
CL600-2B16,
UWW,
CL600-2B19,
VHHH,
Jet-Aviation F2000EX/LX, [email protected] x x
WSSS,
BD700, GV, GIV-X,
OMDB,
G650, A318,
KCPS,
C525A, C525B,
LOWW
C560, C560XL,
LJ45, C525C
BD-100-1A10
CL-600-2B16
BD700-1A10/11
JetPort
UUWW EMB-135BJ [email protected] x
Technics
GIV
GV
GVI
525
560XL
LJ45
AMC LJ60
EPMO [email protected] x x
Aviation BD-100-1A10
CL-600-2B16
BD700-1A10/11
G280
LJ60
BD-100-1A10
MNG Jet LTBA CL-600-2B16 [email protected] x x
BD700-1A10/11
EMB-135BJ
GVI
BD-100-1A10
BD700-1A10/11
Polar 750
EFHK [email protected] x x
Aviation F7X
F900
F2000
GV
6.1.2 General
CAMP is an online software, which is used for the tracking of maintenance requirements. It is available
365 days, 24hrs under the URL http://www.campsystems.com. The application can be accessed by
each member of AOJ Camo via his workstation by the use of his internet browser.
CAMP maintains a "mirror" system with the capacity to completely recover all data. If the system fails,
users will be automatically transferred to the "back-up" system in two hours. CAMP guarantees that
the system may not be unavailable for over two consecutive hours.
The tracking of all Component requirements, inspection tasks, ADs, SBs, etc. in the software CAMP is
based on item codes. Whenever the word “task” is used in the further description of this appendix,
this may refer to any kind of tracked requirement.
b) Used Aircraft
Used aircraft, tracked in different software before, are as well based on the standard template for the
aircraft type. In addition CAMP offers various interfaces to other tracking programmes in order to
import additional data, such as last compliance values. It is agreed on a case by case basis, if such
interface can be used. In the case of this kind of automatic import via this kind of interface is used, the
status after the import is considered as template only. The dedicated AE must verify all template tasks
and modify this import the same way as for new aircraft, but shall pay additional attention on the
compliance values imported.
In addition, external partners may be assigned with their CAMP accounts directly to specific Avcon Jet
Aircraft, or an administrator may create a user for these partners under the AOJ CAMP Account:
• Subcontractor:
User Account with full writing access, limited to the aircraft subcontracted, or assigned access
as “service center” or as “Camo” to the subcontracted aircraft
• Contracted Maintenance Organisation:
Assignment as “service center” to the aircraft necessary. On a specific Aircraft, the organization
must at least be assigned during the preparation of work and during the duration of the
maintenance, in order to enable them to access important information, such as the aircraft
maintenance programme. The access may be revoked afterwards.
• CAMO Organizations contracted for Airworthiness Review:
As agreed with the organization. A user account with read only access for the time of the
review may be granted, or the organization is assigned as “Camo” or as “service center” for
the duration of the review. Alternatively the review may be carried out based on reports only.
• Other parties:
Other parties, such as but not limited to, consultants, owner representatives, maintenance
reserve programmes, autorithies, asset surveyors, etc. may be granted access. However, all
such parties shall be limted to read-only access with no possibilities to carry out any changes
or updates