Track Patrol Inspection Logger
Walking/hi-rail track patrol log — geometry eyeballs, rail surface defects, joints, fasteners, ballast and ROW findings; offline + GPS.
New track segment inspection
FRA Class 1–5 track: visual inspections 1–2×/week typical (49 CFR 213.233 schedule by class & tonnage); always after storms/derailment-adjacent events.
Field guide: Track Patrol Inspection Logger
A track patrol is pattern recognition at walking pace: the patroller isn't measuring gauge with calipers, they're catching the things instruments only find on their scheduled day — the joint that started pumping after Tuesday's rain, the rail with a fresh transverse glint, the kink that wasn't there last week. This logger encodes patrol vocabulary by system (rail, joints, ties/fastenings, geometry-by-eye, ballast/drainage, ROW) with the two emergency findings — broken rail and washout — hard-flagged for protect-track-first response.
Defect clustering drives the classes: one bad tie is a number, five together under a joint is a slow-order conversation. Drainage observations earn their panel because water is the root cause behind most geometry decay — mud-fouled ballast and blocked ditches today are the surface defects of next month. GPS-pinned entries by milepost build the history that makes capital planning (tie programs, undercutting) defensible.
Field tips
- Walk against current where line of sight is short, and always with proper protection arranged — no finding is worth a patrol fatality.
- Low sun is your instrument: rail-surface defects (squats, head checks) show in raking light that midday erases.
- After heat spikes, look at fixation points (bridges, crossings, turnouts) for lateral kinks — track relieves stress where it's anchored.
Records are stored only in this browser (localStorage) — export regularly. This tool aids field documentation; it does not replace your agency's official inspection procedures or engineering judgment.
Track Patrol Inspection Logger — Walking/hi-rail track patrol log — geometry eyeballs, rail surface defects, joints, fasteners, ballast and ROW findings; offline + GPS. Free, offline-first and GPS-aware: open it on any phone, log in seconds, and hand your GIS team clean GeoJSON.
About Track Patrol Inspection Logger
A track patrol is pattern recognition at walking pace: the patroller isn't measuring gauge with calipers, they're catching the things instruments only find on their scheduled day — the joint that started pumping after Tuesday's rain, the rail with a fresh transverse glint, the kink that wasn't there last week. This logger encodes patrol vocabulary by system (rail, joints, ties/fastenings, geometry-by-eye, ballast/drainage, ROW) with the two emergency findings — broken rail and washout — hard-flagged for protect-track-first response.
How to use Track Patrol Inspection Logger
- 1Enter the line & milepost and tap 📍 GPS to pin the track segment's exact location (or type coordinates).
- 2Work through the track segment checklist — every field matches what a real inspection program records.
- 3Pick a condition on the Track OK / Monitor/program / Slow order candidate / Remove from service ⚠ scale; actionable findings are tallied automatically.
- 4Add notes and log the inspection — it saves instantly to your device, even with zero signal.
- 5Export the round as CSV for your asset system, GeoJSON for the GIS, or print a clean report.
Why use Track Patrol Inspection Logger?
- ✓100% free, no sign-up — built for crews, not per-seat licences
- ✓Offline-first: records save to your device instantly and survive dead zones
- ✓One-tap GPS tagging with accuracy capture on every record
- ✓Exports CSV for asset systems, GeoJSON for GIS, and print-ready reports
- ✓Checklist and guidance aligned with 49 CFR 213
Frequently asked questions
What does FRA 213 require for visual inspection frequency?+
It scales with track class and traffic: most Class 1–3 freight track gets inspected twice weekly to weekly (49 CFR 213.233's table), by qualified inspectors, with records kept. Patrols beyond minimum — post-storm, extreme heat/cold — are standard practice because weather is the great geometry destroyer.
What's the immediate response to a suspected broken rail?+
Protect the track first — get protection established per your railroad's rules (stop trains) before any examination or photography. Then report with precise location. A broken rail under traffic is the direct derailment precursor; everything else in this log queues behind that response.
What is a sun kink and when do I worry?+
Continuous welded rail in compression (hot day, rail laid/adjusted cold) can buckle laterally — a sun kink. Risk peaks on the season's first heat waves. Patrol signs: fresh lateral misalignment, ballast disturbed at tie ends, canted ties. Hot-weather slow orders and patrols exist precisely for this finding.
Why log fouled ballast if trains ride fine today?+
Fouled ballast doesn't drain; wet subgrade pumps; geometry decays in weeks. 'Mud spots' are the most predictive maintenance finding on the list — they name where surfacing gangs and undercutting budgets should go before slow orders write themselves.
Embed Track Patrol Inspection Logger on your website
Want Track Patrol Inspection Loggeron your own site? Paste this snippet into any HTML page — it's free, with no API key or sign-up. The tool loads in an iframe and keeps working exactly as it does here.
<iframe src="https://tooljolt.com/tools/track-patrol-inspection-logger" width="100%" height="640" style="border:1px solid #e5e7eb;border-radius:12px;max-width:680px" title="Track Patrol Inspection Logger — ToolJolt" loading="lazy"></iframe>Related GIS tools
Shapefile to GeoJSON Converter
Convert ESRI shapefiles (.shp + .dbf or zipped) to GeoJSON in your browser — attributes preserved, nothing uploaded. Free, no size games.
● LiveShapefile Viewer
Open and inspect ESRI shapefiles online without ArcGIS or QGIS — feature counts, attributes and GeoJSON preview, 100% in your browser.
● LiveKMZ to KML Converter
Extract the KML from any KMZ file in your browser — see bundled icons/overlays too. No upload, no Google Earth install needed.
● Live