The bad news first: in Alaska, the standard deadline to sue for a personal injury is usually two years.

If you were hurt in Anchorage, needed rotator cuff surgery, and you're staring at a calendar that's creeping toward that two-year mark, this is not the time to "see how it goes."

That matters even more when the driver who caused the wreck has no insurance at all.

For a remote software engineer, this can feel especially surreal. You spend your weekdays on a laptop in South Addition or out in Eagle River, then do a few delivery runs at night for extra money. One shift on Tudor Road or near the Minnesota Drive ramps, freezing rain turns the Anchorage bowl into a skating rink, somebody without coverage causes a crash, you go down hard, and now your shoulder is shredded.

A torn rotator cuff is not a fender-bender injury. It can mean MRI fights, weeks of useless sleep, surgery, physical therapy, and a shoulder that still doesn't work right when you type, lift groceries, or reach overhead.

The uninsured driver is only the first problem

Most people think the case dies there.

It doesn't.

But it gets messier than it should.

If the at-fault driver has no insurance, the next question is whether there's uninsured motorist coverage available through a policy that actually applies. That can mean your own auto policy. It can also mean a policy tied to the app, depending on exactly what period you were in when the crash happened.

Here's where the shell game starts.

Rideshare and delivery companies love slicing time into coverage periods because each period changes who may have to pay. The labels vary, but the fight usually looks like this:

• Period 1: app on, waiting for a request
• Period 2: accepted a trip or delivery, heading to pickup
• Period 3: passenger in the car or food in the car, actively completing the trip

That timeline is not trivia. It's the whole damn argument.

If you were just online waiting, the app company may point hard at your personal policy. If you had already accepted the order or were mid-delivery, there may be a stronger argument that app-related coverage was in play. And because you're a 1099 contractor, there's no regular workers' comp safety net stepping in for a work injury.

Your personal insurer may try to bail

This is where a lot of Anchorage drivers get blindsided.

Personal auto policies often exclude coverage when the car is being used for delivery work or other commercial activity. The insurer sold you a regular personal policy, not a food-delivery business policy, and they know exactly where that line is.

So you report the crash, mention you were on a delivery, and suddenly the adjuster's tone changes.

If your own insurer denies because you were working, and the app company says you were in the wrong coverage period, you can end up caught between two carriers while your surgical bills keep arriving.

Meanwhile, black ice doesn't care who insures what. From September through April, roads and bridges around Anchorage can glaze over fast, especially after freezing rain. The Seward Highway connectors, overpasses, and shady intersections can turn slick in minutes. That local weather detail matters because insurers love pretending every wreck was "just weather" instead of a driver losing control, following too close, or blowing through conditions like an idiot.

The shoulder injury changes the value of the case

A surgically repaired rotator cuff is not some soft-tissue throwaway claim.

For a remote software engineer, shoulder damage can hit both jobs. Delivery work is obvious: driving, loading, carrying orders, opening heavy doors. But the desk job counts too. Long coding sessions, mouse use, posture, reaching, and sleep disruption can all matter. If surgery sidelined you from your day job or cut your productivity, that belongs in the damages picture.

And don't undersell the timeline. Rotator cuff cases often look worse months later than they did in the ER.

Early records may say "shoulder strain" or "possible tear." Then the MRI lands. Then ortho. Then surgery. Then rehab. By the time the real shape of the injury is clear, a lot of people have already burned precious time dealing with carrier nonsense.

The deadline problem is bigger than just filing suit

In Alaska, that two-year injury deadline is the cliff edge, but there are earlier traps.

Uninsured motorist claims usually require prompt notice under the policy. So even if the lawsuit deadline has not passed, waiting too long to notify the insurer can create another fight the company will happily exploit.

That's why "I was still treating" is not a real strategy.

Neither is "I thought DoorDash or the app would handle it."

The practical questions are brutally simple: what exact date did the crash happen, what exact app status were you in, what policies existed that day, and when were those carriers notified?

If the wreck happened on a delivery and the other driver had no insurance, the money may have to come from uninsured motorist coverage instead of the at-fault driver's nonexistent policy. But whether that coverage exists, and through which insurer, depends on documents people usually don't gather fast enough: the app log, trip records, acceptance time, pickup time, crash report, and every denial letter.

If you're sitting in Anchorage with a shoulder surgery behind you and the two-year mark is looming, the biggest mistake is assuming no insurance on the other side means no case. The second biggest mistake is waiting for the companies to sort it out for you. They won't.