Describe your runway, patrol schedule, and defect categories. Makeform builds a practical checklist for pavement condition, debris, contamination, markings, photos, locations, and follow-up actions.
Route records to email, Slack, Google Sheets, and Zapier.
Sample prompts for the builder
Choose a routine, weather, maintenance, or reopening prompt, then tailor it to local procedures.
Audience
Airport operations staff completing scheduled checks
Format
Mobile checklist with defect branching
Prompt size
359 chars
Example form structure
Mobile checklist with defect branching
Inspector, patrol time, and runway
Weather and observed surface status
Surface condition checklist
Defect location and photo
Action, status, and follow-up owner
Suggested routing tags
No defect observed
Monitor
Action requested
Use runway end, side, centerline offset, and distance fields so crews can find a reported defect.
Step 1
Identify
inspector, runway, segment, time, and conditions
Step 2
Observe
surface, debris, drainage, markings, and edges
Step 3
Locate
position, category, notes, and photos for each defect
Step 4
Route
action taken, notification, owner, and reinspection
Consistent airfield records
Connect each observation to its location and follow-up. Structured questions reduce ambiguous notes.
Guide every patrol through conditions, pavement, debris, drainage, markings, actions, and follow-up.
Pair runway and segment with end, side, distance, intersection, or centerline offset.
For findings, reveal image, action, notification, owner, status, and reinspection fields.
Inspection scenarios
Keep a stable core record, then add questions for the event that triggered the inspection.
Check pavement, debris, contamination, markings, shoulders, and visible fixtures.
Observe water, ice, snow, debris, drainage, heat effects, and review areas.
Record work limits, loose material, tools, edges, patches, markings, and exceptions.
Document inspected areas, exceptions, notifications, actions, status, and next patrol.
Build the workflow
Generate a starting point, apply local inspection terms and action choices, then test the defect branch.
Name runways, patrol triggers, inspection areas, defect categories, and actions.
Show location, photo, notification, and follow-up fields only for reported issues.
Confirm controls, required fields, and location choices on the field device.
Send records to the chosen inbox or sheet and findings to their follow-up owners.
Record quality
A conditional online form keeps required defect and follow-up details beside the original observation.
Field guide
Use these six sections as a baseline, then align fields and choices with local procedures.
Inspection identity
Capture the inspector, start and finish times, patrol trigger, runway, and direction. This distinguishes routine, weather, maintenance, and reopening records.
Operating context
Record weather, visibility, light, precipitation, and surface status so readers understand the inspection conditions. Use local terminology.
Surface checklist
Group checks in patrol order. Include a none observed option and separate categories instead of one notes box.
Defect location
Collect runway-relative references and separate entries for unrelated findings so crews can locate each defect.
Evidence and action
Store photos with the finding's category, location, and action. Record what was removed, communicated, monitored, or referred.
Ownership and closeout
Keep the original observation separate from resolution. Add an owner, status, reinspection time, and closeout note.
Related tools
Connect the routine surface record with broader inspection, equipment, maintenance, incident, and safety workflows using real Makeform tools.
Create a structured aircraft inspection record for a separate maintenance workflow.
Open toolBuild condition checks for airfield tools, vehicles, and support equipment.
Open toolTrack maintenance activity and service notes for operational equipment.
Open toolRoute a reported defect or repair need into a maintenance request queue.
Open toolCapture event details, witnesses, attachments, and internal follow-up in one report.
Open toolGenerate a broader site safety checklist for facilities and operating areas.
Open toolFAQ
Practical answers for teams creating consistent runway inspection records.
It records who inspected, when and where the patrol happened, conditions, pavement defects or debris, finding locations and images, actions, notifications, and follow-up status. The airport still sets its procedures and responses.
Include inspector, times, patrol reason, runway, direction, weather, visibility, surface status, and areas covered. Check pavement, debris, contamination, drainage, markings, shoulders, and visible fixtures. For findings, require location, extent, photos, action, notification, owner, status, and reinspection.
Use runway identifier, end or segment, intersection or turn pad, side, centerline relationship, and a team-recognized distance marker. A map pin can supplement, but not replace, the runway-relative description.
Yes. Conditional logic can show photo, location, category, extent, action, notification, and owner fields only after a finding is selected. Test the branch on field devices.
Yes. Branch from the inspection reason. Routine patrols use core surface checks; weather inspections add water, snow, ice, drainage, and debris; maintenance checks add work limits, tools, loose material, patch edges, markings, and open items.
Use a repeatable group so every finding has its own category, location, description, extent, photos, action, notification, owner, and status. Otherwise, use separate sections or submissions so details stay distinct.
Yes. Makeform supports unlimited free forms and responses, including generating, editing, and publishing. The paid tier only removes the Makeform badge.
No. It provides an editable collection structure. Before publishing, align labels, coverage, timing, response choices, notifications, record handling, and reopening steps with local procedures and responsibilities.
Make every runway patrol easier to follow up.
