Two Phillipsburg crossings, two different local locators
A rideshare receipt can show Easton or Phillipsburg without establishing the crossing where another car struck your ride. The Route 22 toll point and Northampton Street are distinct. Identify which road the car occupied when the first contact happened, even if the driver finished the trip on the other side.
| Crossing | Current operator information | Collision implication |
|---|---|---|
| Easton-Phillipsburg Route 22 Toll Bridge | Carries Route 22; cash plaza removed from service in January 2025; tolling point uses E-ZPass or plate billing. | Do not explain a later collision using a cash queue that the source says is no longer in service. |
| Northampton Street Toll-Supported Bridge | Separate crossing south of the Route 22 bridge, connecting Easton and Phillipsburg. | A receipt or app route naming Easton does not identify which crossing you used. |
| Trip receipt versus impact | Trip records document booking/route context. | Record the first vehicle contact separately from pickup, destination and final stop. |
Source check: October 13, 2026. DRJTBC Route 22 bridge; DRJTBC Northampton Street bridge.
A ride request, a pickup and a moving trip are different moments
Suppose you were already seated when the driver pulled away from a stopping place and another car made contact. That hypothetical collision is different from one later in the trip while the rideshare car changed lanes near a crossing. Describe when you entered the car and whether it had started moving before the impact.
Your receipt and app history may help place the trip in time. They do not by themselves show the other vehicle's movement. Save the trip details that actually exist, and explain if the app marked an arrival or start at a time that does not match your memory of boarding.
For a rideshare accident, the driver may have one account of the app and you may have another view from the passenger seat. Keep both subjects clear. Whether the app showed an active trip is a coverage question to review; where the cars were moving is a collision question to reconstruct.
Where did the first impact happen?
A trip may start in New Jersey, cross into Pennsylvania and end in Easton. The collision could happen before the crossing, on it or afterward. State where the first contact occurred if you know, then separately identify where the driver stopped and where you left the car.
A receipt showing an Easton destination does not prove the impact happened in Pennsylvania. A photograph taken in Phillipsburg after the car returned or pulled over does not prove it happened there either. If a location is uncertain, say so and ask what evidence can narrow it down.
Do not choose the applicable law or insurer simply from the state shown on a driver's license plate. Location, policies and the people involved need review together. The river crossing is a reason to clarify those facts, not a basis for promising that one state's rules necessarily resolve the whole claim.
Keep the local rule separate from the disputed movement
Keep the operator's January 2025 cash-plaza change alongside the date of your trip. It prevents a former queue arrangement being assumed for a later collision. For coverage, preserve the app status at the collision, your actual seat and whether the vehicle was carrying you; the general rideshare hub handles policy stages.
Care and the next useful conversation
Call 911 for an emergency or an unsafe scene. Seek medical advice for injuries and follow the treating clinician’s instructions. Do not stop on an active road or ramp to reconstruct a collision.
For treatment payments, work losses, coverage and proposed releases, use the focused guides: New Jersey rideshare accident help.