Call-prep brief · checked 2026-07-09
Mountain Line Transit
Grade C · 76.6 / 100
Unchanged since 2026-07-08.
For this call: lead with the grade and the three fixes below, then confirm the feed is current and the NTD details line up. Each fix is framed as a next step, not a failure.
What changed since the last check
- Correctness no change
- Freshness no change
- Rider experience no change
- Realtime quality no change
Top three things to fix
Set wheelchair_boarding to 1 (accessible) or 2 (not accessible) for every stop. A field survey can start with the busiest stops.
176 of 176 stops don't say whether a wheelchair user can board there. Riders who use wheelchairs can't plan a trip when accessibility is marked 'unknown'; apps show no information at all.
Effort: A column in stops.txt; your scheduling software likely has it.
Set wheelchair_accessible on every trip (most small-agency fleets are 100% accessible, so this is often a single default).
1336 of 1336 trips don't say whether the vehicle is wheelchair accessible. Even with accessible stops, riders need to know the bus itself can take them.
Effort: Often one default setting in your export.
Agencies here usually clear this within about 1 week (based on 5 observed fixes).
Add fare_attributes.txt (or Fares v2 files) with your fare structure. If your service is fare-free, ask to have it marked fare-free instead.
The feed contains no fare information. Riders see 'fare unknown' in trip planners and can't budget their trip; visitors are most affected.
Effort: A small file for most flat-fare systems.
NTD certification readiness: Ready
Published at a public URL, valid, and current: the three things the NTD GTFS requirement asks of a feed all hold here. Only your own D-10 certification makes that official; this is a heads-up, not a determination.
- Published Ready
- Published at a public URL.
- Valid Ready
- Passes validation with no errors.
- Current Ready
- Service data covers the next 174 days.
agency_id and NTD ID: Not checked yet. Setting your GTFS agency_id to your five-digit NTD ID is an optional way to line a feed up with its National Transit Database record. FTA links the two on your P-50 form, so it is not a required feed change. We don't have your NTD ID on file, so this is not checked yet.
Key facts
- Feed URL
- http://mountainline.syncromatics.com/gtfs
- Last checked
- 2026-07-09
- Service window
- 174 days of service data remain. Last service date 2026-12-30.
- Feed version
- No deviations
- State
- Arizona
Part of the Arizona portfolio: see where this agency sits among the state's feeds before the call.
A data-quality and completeness read to support an agency conversation. Not an official compliance determination. Rubric v1.1, validator 8.0.1.