MCM (Maintenance Control Manual)

The Maintenance Control Manual (MCM) serves as a key document for managing and overseeing aircraft maintenance schedules, ensuring compliance with Transport Canada regulations. It outlines procedures for planning, tracking, and auditing maintenance activities to maintain airworthiness. We provide consultation to help you develop or refine your MCM, ensuring regulatory alignment and operational efficiency.

About our Services

Extensive Expertise Over 20 years of experience working with operators, Transport Canada, the FAA and other regulators.
Regulatory Support We communicate directly with regulators, ensuring you’re never alone when submitting documents. Plus, we take care of the back and forth.
Customized for your Operation We tailor our services to meet the specific regulatory and operational needs of your aviation business.

Take Staff Compliance to the Next Level

Beyond regulatory manual consultation, Nabu Pro leverages its deep aviation expertise to offer a software solution that simplifies and streamlines staff compliance management for industry professionals.

Learn how Nabu Pro centralizes and automates your training, documents and memos.

Discover the features

We use cookies

This website uses cookies in order to enhance the overall user experience.

Take a look at our Cookies Policy for more information.

Customize

Essential cookies

There are some cookies that we have to include in order for certain web pages to function. For this reason, they do not require your consent.

nabu_pro_website_cookie_consent

1 year 1 month 1 day

Used to store the user's cookie consent preferences.
nabu_pro_website_session

2 days

Used to identify the user's browsing session.
XSRF-TOKEN

2 days

Used to secure both the user and our website against cross-site request forgery attacks.
locale

1 year 1 month 1 day

Records the language of the user.
industry

1 month 2 days

Records the industry profile selected to adapt the content on non industry-specific pages.

More details

Marketing cookies

These cookies are used to track visitors across websites, gathering information to display relevant ads and promotional content. They help measure the effectiveness of campaigns, understand user interests, and tailor content to provide a more personalized experience.

bcookie

1 year 1 month 1 day

[LinkedIn] Browser Identifier cookie to uniquely identify devices accessing LinkedIn to detect abuse on the platform
lidc

1 day

[LinkedIn] To facilitate data center selection
li_gc

6 months 1 week 5 days

[LinkedIn] Used to store consent of guests regarding the use of cookies for non-essential purposes
li_mc

6 months 1 week 5 days

[LinkedIn] Used as a temporary cache to avoid database lookups for a member's consent for use of non-essential cookies and used for having consent information on the client side to enforce consent on the client side
li_fat_id

1 month 2 days

[LinkedIn] Member indirect identifier for Members for conversion tracking, retargeting, analytics
li_giant

1 week

[LinkedIn] Indirect indentifier for groups of LinkedIn Members used for conversion tracking
li_sugr

3 months 6 days

[LinkedIn] Used to make a probabilistic match of a user's identity
oribi_cookie_test

30 minutes

[LinkedIn] To determine if tracking can be enabled on current domain
oribili_user_guid

1 year 1 month 1 day

Used to count unique visitors to a website
ln_or

1 day

[LinkedIn] Used to determine if Oribi analytics can be carried out on a specific domain
ar_debug

30 minutes

[LinkedIn] Supports Google attribution reporting API integration to mitigate signal loss

More details

Analytics cookies

We use these for internal research on how we can improve the service we provide for all our users. These cookies assess how you interact with our website.

hjSessionUser_5187404

6 hours 5 minutes

[Hotjar] Persists the Hotjar User ID which is unique to that site. Hotjar does not track users across different sites.
hjSession_5187404

30 minutes

[Hotjar] Enables us to know whether the data set in _hjUserAttributes Local Storage item is up to date or not.
hjViewportId

30 minutes

[Hotjar] Stores user viewport details such as size and dimensions
hjActiveViewportIds

30 minutes

[Hotjar] Stores user active viewports IDs.
_hjCookieTest

1 minute

[Hotjar] Checks to see if the Hotjar Tracking Code can use cookies. If it can, a value of 1 is set.
_hjLocalStorageTest

1 minute

[Hotjar] Checks if the Hotjar Tracking Code can use Local Storage. If it can, a value of 1 is set.
_hjSessionStorageTest

1 minute

[Hotjar] Checks if the Hotjar Tracking Code can use Session Storage. If it can, a value of 1 is set
_hjTLDTest

1 minute

[Hotjar] We try to store the _hjTLDTest cookie for different URL substring alternatives until it fails
__hstc

6 months 1 week 5 days

[Hubspot] The main cookie for tracking visitors. It contains the domain, hubspotutk, initial timestamp (first visit), last timestamp (last visit), current timestamp (this visit), and session number (increments for each subsequent session).
hubspotutk

6 months 1 week 5 days

[Hubspot] This cookie keeps track of a visitor’s identity. It is passed to HubSpot on form submission and used when deduplicating contacts. It contains an opaque GUID to represent the current visitor.
__hssc

30 minutes

[Hubspot] This cookie keeps track of sessions. This is used to determine if HubSpot should increment the session number and timestamps in the __hstc cookie. It contains the domain, viewCount (increments each pageView in a session), and session start timestamp.
__hssrc

30 minutes

[Hubspot] Whenever HubSpot changes the session cookie, this cookie is also set to determine if the visitor has restarted their browser. If this cookie does not exist when HubSpot manages cookies, it is considered a new session. It contains the value “1” when present.

More details