Roads and approaches
I-35I-240Kilpatrick Turnpike approaches
Location, roadway change, and source
I-35 motorcycle crashes
After an I-35 motorcycle crash, fix the exact road story before a later project map, work plan, advisory, or lane pattern is mistaken for crash-time proof.
Exact point, actual condition, and time frame
Evidence to protect after an I-35 motorcycle crash.
An I-35 label does not identify the crash point, responder, road holder, project, contractor, lane setup, device, camera, record, or condition at that time. Preserve what each source actually shows, then test whether a temporary change, active job, maintenance activity, emergency response, or permanent layout belongs in the file.
Data honesty
OHSO 2021 Crash Facts reported many Oklahoma motorcyclists in crashes on city streets and interstate highways. This page uses that source for road-class context; it does not publish corridor-specific crash totals.
Source: Oklahoma Highway Safety Office, 2021 Highway Safety Crash Facts Book, Section 5 (Motorcyclists in Crashes). Data year 2021; source availability checked August 28, 2026.
Investigation themes
Questions to answer after I-35 motorcycle crashes.
The recurring I-35 proof problem is time mismatch: a later map or finished roadway is used to describe an earlier lane pattern, or the word “construction” substitutes for the device, location, sequence, and source that actually mattered. Preserve the supported before/at/after distinctions.
Crash point before project label
Record the nearest exit, mile marker, crossroad, direction, lane, ramp, shoulder, frontage-road relation, and source for each detail. A city name, corridor map, or broad project boundary may orient the search without fixing the crash point.
Observed change before explanation
Describe the supported device, lane shift, surface, barrier, sign, lighting, queue, equipment, worker, emergency vehicle, or missing/obscured feature without guessing why it was there or who controlled it.
Public and private source split
Separate collision and responder material from ODOT planning, construction, traffic/design, and records routes—and from contractor, dashcam, witness, tow, motorcycle, gear, insurer, and medical sources that may sit elsewhere.
Official source routing
Build the I-35 change record without inventing a work zone.
Current ODOT I-35, construction, work-plan, live-traffic, traffic-engineering, and records pages can identify present plans, tools, categories, or project leads. They prove neither that work was active at the crash point nor a crash-time layout, device, contractor, custodian, recording, retention, access, responsibility, fault, jurisdiction, deadline protection, or representation.
Step 1
Fix the point and sequence from safe originals
From material already available, record direction, nearest exit/mile marker/crossroad, date/time, lane/ramp/shoulder, each movement in order, contact points, final positions, responder, report number, EMS, tow destination, and source for each detail. Keep estimates and conflicts visible. Never return to active traffic, enter a work area, approach equipment or damaged vehicles, or postpone care to gather detail.
Step 2
Describe the change before naming its cause
Preserve lawful originals showing a specific lane shift, merge, closure, barrel, barrier, sign, marking, surface, edge, light, queue, worker, equipment, or emergency setup. Record where and when it appeared and who observed it. Appearance alone establishes no active ODOT project, contractor, maintenance operation, responsible entity, violation, notice, causation, or fault.
Step 3
Test current project tools against crash time
Use Forward 35, the construction map, work plan, live-traffic page, and Traffic Engineering only as separate leads. A study or programmed project may be future-facing; a current map, camera, advisory, standard, or data form is not proof of the earlier setup or of a retained record. Save the exact URL, title, date checked, project/job identifier if supported, and what the source did and did not show.
Step 4
Route records without collapsing the holders
Keep the Service Oklahoma report, DPS/OHP categories, OHP audiovisual route, ODOT request, local responder, and private sources in separate rows. Add a project, contractor, subcontractor, inspector, traffic-control, tow, motorcycle, gear, insurer, or medical holder only when a source supports it. A request guarantees no record, preservation, access, timing, response, deadline protection, or representation.
Official sources
Use the current map and agency instructions.
Sources reviewed 2026-08-28.
ODOT Forward 35
Current ODOT strategy and project-information gateway for I-35 from Oklahoma City to the Texas line; its stated scope and planning material are not crash-time condition proof.
Open sourceODOT construction updates
Current project and construction coordination map gateway; a later map entry or absence does not establish the crash-time setup, activity, holder, or record.
Open sourceODOT eight-year work plan
Current and archived programmed-project plans; a planned project or schedule does not prove work was active, unchanged, or present at the crash point.
Open sourceODOT current traffic conditions
Current traveler-camera and advisory gateway; a live view or present advisory does not establish historical coverage, recording, retention, or availability.
Open sourceODOT Traffic Engineering
Current traffic-count, collision-data, design-data, standard, and transportation-management-plan routes; each category requires its own supported fit and time frame.
Open sourceODOT highway and bridge records
Current ODOT request route requiring useful location, project, map, and date details where available; it excludes City, County, court, and private material outside ODOT holdings.
Open sourceService Oklahoma collision report
Current statewide collision-report form and instructions; official identifiers belong in that verified process, not Rider First's first-contact form.
Open sourceDPS open-record categories
Current DPS route for listed investigation categories; collision reports, other agencies, and OHP audiovisual material follow the separate routes stated there.
Open sourceOHP camera and dispatch audio
Current OHP audiovisual guidance; it promises no recording existence, coverage, retention, completeness, access, or delivery.
Open sourcePreserve evidence
What to save after I-35 motorcycle crashes.
Original source material for direction, exit/mile marker/crossroad, lanes/ramps/shoulder, movement order, contact points, final positions, traffic control, temporary changes, and witness vantage
Specific devices, markings, surfaces, barriers, signs, lighting, queues, workers, equipment, emergency setups, and exact dated project/map/advisory queries or no-match results
Collision, responder, roadway/project, private-video, tow, motorcycle, helmet, gear, vehicle, repair/total-loss, insurer, and medical materials with separate custody notes
Records to ask for after an I-35 crash.
- Service Oklahoma collision report plus the supported local or DPS/OHP investigation, CAD, vehicle-examination, audiovisual, photograph, or other category
- ODOT location, project/job, plan, traffic-control, construction, maintenance, inspection, traffic/design, advisory, or roadway material only when a source and time frame support that lane
- Lawful private contractor, dashcam, witness, tow, motorcycle, gear, vehicle, insurer, and medical sources maintained independently from public planning tools
First moves after an I-35 crash.
- Write the exact crash-point and traffic-sequence card from each source while leaving conflicts, estimates, and unknowns visible.
- Describe any apparent roadway change before labeling it construction, maintenance, emergency traffic control, a project, or a responsible entity.
- Open separate collision/responder, roadway/project, private-video, tow/custody, physical-proof, insurance/property, and medical rows; save originals and dated source trails.
Local connections
Cities and courts along I-35.
Cities tied to this corridor
What should I save after an I-35 motorcycle crash?
Save the motorcycle, helmet, gear, photos, witness names, police information, tow records, medical records, insurance messages, and corridor-specific proof such as original source material for direction, exit/mile marker/crossroad, lanes/ramps/shoulder, movement order, contact points, final positions, traffic control, temporary changes, and witness vantage.
Who investigates I-35 motorcycle crashes?
The right agency depends on the exact crash location. An I-35 motorcycle crash may involve Oklahoma Highway Patrol, city police, sheriff records, EMS, tow providers, hospitals, or turnpike-related records depending on where it happened.
Do corridor crash patterns prove who was at fault?
No. Corridor patterns help identify records and evidence to preserve. Fault in a specific crash depends on the vehicles, witnesses, roadway, injuries, insurance, and proof from that crash.
Next step
If the crash happened here, describe the exact road story.
For a focused review, share northbound or southbound travel, nearest exit/mile marker/crossroad, date and approximate time, lane/ramp movement, what looked different or temporary, responder, report number, tow holder, and sources already saved. Leave medical records, identity documents, passwords, project portals, and uploads out of the first message.
For accepted motorcycle-injury matters, attorney fees are contingent on recovery and governed by a written engagement agreement.
Request a case review