NOTAM

ATI Inspector Form

Aerodrome Technical Inspection (ATI) Inspector Qualification & Experience Validation Form Very few aerodromes I visit take the time to make sure the person or persons who carry out their aerodrome technical inspections meet the qualification and experience requirements laid out in CASR 139.240.

Operations under a safety management system typically demand a higher level of assurance than has existed in the past. You can't rely on tradition or past conduct - you have to examine and re-examine your decisions regularly - its part of the safety assurance, change management and continuous improvement components of a good safety management system.

To assist with making the assessment of a potential ATI Inspector, I've put together this simple form to show how a conscientious aerodrome operator might record such an assessment. The process involves the aerodrome operator seeking evidence (degrees, resumés, references) from the inspector and then either accepting or rejecting this evidence based on the regulatory requirements.

Please feel free to take this form, change it, incorporate it into your manual (or not). Whatever you do, please do something and make sure its recorded. We auditors are a cynical bunch, for us - if it ain't recorded, it didn't happen.

Aerodrome Reporting - in a Flowchart

img_5844a.jpg

Aerodrome Reporting Flowchart - Landscape - v0.2 I like to sit at my computer and draw things, despite the fact that I'm no artist. A couple of weeks ago, I thought I would have a go at putting the various aerodrome reporting requirements, the procedures you might find in that section of the aerodrome manual, into a flowchart to help out anyone who is a bit confused by the various requirements.

It's not easy to get your head around the multitude of requirements especially when a small sentence in some other chapter of the Manual of Standards Part 139 might trigger a whole set of other requirements. To help keep the situation clear, I also added in the Transport Safety Investigation Act requirements, well some of them anyway.

So, I hope this flowchart helps - if not, let me know in the comments below.

Update - with the kind help of fellow Aerodrome Inspectors Darren Angelo and Danny Eatock, I've made a few changes to the flowchart. I hope they may it clearer. Let me know.

What if ... the NOTAM system went down?

A great deal of risk/hazard identification is running through "what if" scenarios. Obviously, the big one is "what if an aircraft crashed?" but others include "what if the lights failed?" and "what if key staff left?" A tweet and associated webpage from the NBAA got me thinking about this scenario - "what if the NOTAM system went down?" Granted, the linked scenario is planned maintenance but it still requires consideration and maybe so does it's unplanned alternative scenario.

How would your aerodrome handle the NOTAM system being down? Do you have sufficient communication systems in place to ensure adequate flow of information to regular aerodrome users? Would you reschedule or abandon airside works? There are plenty of things to consider and the relative importance of each will vary between airports.

Perhaps NOTAM system vulnerabilities should make an appearance on your airport's risk register.