Serviceability inspections, zone by zone, with every finding on the map
The reporting officer drives the movement area with a phone in the mount. Each zone is checked item by item, each finding is pinned by GPS and photographed, and it becomes a defect before the vehicle is back at the terminal.
Watch the aerodrome walkthrough: start with two runway lights outThe movement area, item by item
Each zone has its own items, with pass, fail or not applicable, a note and a photo. Where a section asks for the QR tag at a zone, the scan, or a skipped scan with its reason, is recorded with the time.
- Runways
- Taxiways
- Aprons
- Runway strips
- Lighting
- Markings
- Signs
- Windsocks
- Fences and gates
- Obstacles
- Wildlife
- FOD
Pinned by GPS
A finding carries the position where it was recorded, wherever the device has a fix, so the works crew drives to the light that is out, not the taxiway it is on.
Photographed
A photo with each finding, stamped with the time. The close-out photo sits beside it when the repair is done.
Findings to defects
A finding becomes a defect with its severity, assigned to the people who fix it and tracked until it is closed.
Due by your rule pack
Inspections fall due from your rule pack and the day’s movements. When one is not done before the first movement, the dashboard says so.
Each site and each facility, from the records you keep
- Worked out from your records
- Each site is Open (from records), Open with restrictions or Closed (from records), from inspections, defects pinned to each facility, lights out, planned closures, works, runway condition, wildlife, obstacles and the NOTAM log. Your own state, with a reason, is shown beside it, never instead of it.
- Facility by facility
- Runways, taxiways, aprons, lighting circuits, PAL, slope indicators, windsocks, frequency units, navaids, gates, fences and obstacles in a facility register, each serviceable, restricted, unserviceable or closed with its reasons.
- What is due today
- Inspections due from your rule pack and the day’s movements, counted against the first movement, with an alert in the dashboard if one is not done in time.
- Changes acknowledged
- A change opens with its cause. A supervisor acknowledges it and records who outside was advised; if nobody does, it goes to managers and then administrators. Planned closures are marked planned and raise no change alert.
The board shows what your records say. The operator decides whether the aerodrome is used. Watch the aerodrome walkthrough.
Lighting rules by market
- Lights out by number
- Lights are numbered in order along each circuit, so a reporting officer taps the ones that are out on the phone, with or without signal, and the board knows when two next to each other are out.
- Australia
- The MOS lighting rules by system size: any light out of a system under 4; 2 of 4 or 5; 3, or 2 next to each other, of 6 to 13; above 13, more than 15% or 2 next to each other. A PAPI or T-VASIS with a lamp out is to be switched off. A breach also shows NOTAM required unless it is recorded as fixed before the next use.
- ICAO markets
- Serviceability objectives by element for CAT I and CAT II and III, no two next to each other, and the stop bar and taxiway centreline rules below 300 m RVR. Elements with no objective use your own.
The request, the number, the reviews and the cancellation
When a facility’s condition is a NOTAM trigger under your rule pack, the board shows NOTAM required until a request is recorded. Then NOTAM requested, active once the number is recorded, review due each day it is not reviewed, and to cancel when the condition clears. Records are never deleted from the log.
Escudo records the request and the number. The NOTAM itself is raised through your usual process.
- Australia: Part 139 MOS, Compilation 7
- New Zealand: Part 139 and AC139-3
- Papua New Guinea: Part 139
- Singapore: Air Navigation (139-Aerodromes) Regulations 2023 (to confirm)
- Malaysia: CAD 14 and CAD 1405 (to confirm)
- ICAO default, also used for Fiji and Hong Kong
- Remote strip
- Helicopter landing site, with NSW, Queensland and Victorian profiles
Each site chooses a pack. Values marked to confirm are confirmed with each customer before they are relied on.
Remote strips
The owner’s inspection on the phone, with the questions pilots ask, and a night set-up to the owner’s own layout. The owner reports the strip ready, ready by day only or not ready, with who and when. Instead of a NOTAM log, the owner records who was told, how and when. The pilot decides whether the strip is suitable.
Helicopter landing sites
The daily inspection, the check before each movement, maintenance and the yearly audit, on the NSW, Queensland or Victorian profile. When the site cannot be used, the board says to tell the operators who use it, and records who was told. The pilot decides whether the site is suitable.
22 templates in the catalogue
Aerodrome
- Aerodrome serviceability inspection
- Safety-critical inspection before the first departure
- NOTAM review
- Night lighting inspection
- Pilot activated lighting and AFRU test
- Wind direction indicator inspection
- Stand-by power test
- Portable runway lights
- The day’s movements
- Apron inspection
- Runway inspection after an event
- Works area / works safety officer inspection
- Wildlife patrol
- Perimeter fence and gate patrol
- Technical inspection (annual)
Remote strips
- Owner’s airstrip inspection
- Night set-up of an airstrip
Helicopter landing sites and heliports
- Helicopter landing site daily inspection
- Helicopter landing site arrival and departure inspection
- Helicopter landing site three-monthly maintenance
- Helicopter landing site yearly audit
- Heliport serviceability inspection
Each template is a representative starting point. Your aerodrome validates it against its own procedures and aerodrome manual, changes it to its own wording, and publishes it. Until then it is a draft.
Runway condition reports, third by third
- Per third, with a suggested code
- For each third of the runway the reporting officer records the contaminant, the coverage and the depth on the phone, with or without signal. The app suggests a runway condition code from them, labelled suggested: the officer assesses the runway and can enter their own code.
- The 25% rule and the routing
- On the Australian pack a third with 25% or less covered is reported as 5, WET. WET goes to ATC only; standing water, slippery wet and other contaminants go to the NOTAM Office and ATC, or to pilots on the UNICOM or CA/GRS. The officer ticks where it was sent, and a report not recorded as sent stays on the board.
- Braking action
- Braking action reported by pilots is recorded against the runway. Two consecutive MEDIUM (or worse) reports since the last runway condition report prompt a slippery wet report, on the phone and on the board.
- On the board
- The runway shows its code by third, the contaminants and where the report went, and a code below 6 restricts it. A supervisor can raise an unplanned inspection for weather that may have changed the runway condition, and a runway condition report meets it.
Escudo suggests the code and records where the report was sent. It never sends a runway condition report.
Works from the MOWP to the handback
- Planned with the MOWP
- Works on each facility with their kind, window and effect: under a method of working plan, time-limited, emergency or with the aerodrome closed. The board reminds you to issue the MOWP 14 days ahead and to request the works NOTAM 48 hours ahead on the Australian pack, and records the NOTAM request and number against the works.
- Briefed and started on the phone
- The works safety officer’s briefing is recorded each day with the name and time. The start is recorded with a photo of the works area, taking in the whole area and the barriers.
- The restore countdown
- Time-limited works count down to the next movement from the day’s movement times: restore 5 minutes before it, and when to start restoring. Restored and resumed are recorded on the phone; works not restored in time raise a works timer event and an alert.
- Handback and the inspection
- Handback takes a photo of the same place, with the start photo beside the camera. It raises an unplanned inspection of the works area, and the area stays restricted until the next serviceability inspection meets it.
Escudo records the works, the works NOTAM request and its number, and what happened on the works. It never issues a NOTAM and never says the movement area is safe: the operator decides when an area is used.
Wildlife, strikes and the reminders
- Observations
- Species, how many, where, behaviour, what was done and the light. A significant concentration not dispersed restricts the facility and, on the Australian pack, is a NOTAM trigger until it is recorded as dispersed.
- Strikes and the report reminder
- A strike with the aircraft, phase of flight, size, damage, engine ingestion and whether the remains were kept. The reminder follows the pack: report to the ATSB within 72 hours, or in Singapore tell CAAS immediately with written notice within 12 hours for an accident and 24 for an incident. A supervisor records when it was reported and the reference.
- Attractants and the plan review
- Attractant sites within 13 km of the aerodrome with their distance, bearing and when last monitored, and the wildlife hazard management plan review at least every 12 months.
- Obstacles and technical inspections
- Temporary and new obstacles with their height and position restrict the board until they go. Technical inspections or the manual validation fall due on the interval you choose from your traffic, with a reminder to record the report to the regulator within 30 days.
Reminders only. Escudo never lodges a report with the ATSB, CAAS or any regulator; the operator reports and records the date and reference. Watch the bird strike film.
Every record an aerodrome inspector asks to see
One site over one period, printed from the board: inspections, findings and defects, the NOTAM log with its reviews, light outages, runway condition reports with their routing and braking reports, unplanned inspections, works with their events and photos, wildlife observations and strikes with what was reported, obstacles, and technical inspections, validations and reviews.
- The data download with its SHA-256 printed on the pack, so anyone can check the file is exactly as made
- For supervisors and above, for any site they can see
- The operator’s own records: Escudo makes no finding and never says the aerodrome is compliant or safe
The aerodrome pack
Inspections by date, the findings and where they were, and the defects and their repairs, for any date range.
- PDF for the reader and spreadsheet for the analyst
- A manifest of SHA-256 hashes, so a reviewer can confirm the files are exactly as exported
- Organised for your own audit file and your regulator’s visit
Start with one aerodrome
We set up your zones and the inspections you run, you validate the templates in your own words, and your reporting officers start the next morning.