Alaska AK
State MLTS rules exist; local 911 implementation is heavily municipal and geography-sensitive. 911 program status should be verified locally.
What matters before you deploy or audit E911 in Alaska
- Municipal ordinance can trigger Alaska MLTS duties for upgraded or newly installed systems.
- The law is unusually specific about location fields: valid address, callback number, office/unit/building, room, and floor.
- Database updates after physical or system changes should be treated as a one-business-day operational control.
How detailed should the dispatchable location be?
No Alaska square-foot exception was identified in the cited section. The practical threshold is whether responders can find the caller using office, unit, room, building, and floor information.
Exact law callouts
Short excerpts are included for orientation. Follow the links for the complete statutory or regulatory text.
Direct 911 dialing
47 C.F.R. § 9.16(b)(1)“without dialing any additional digit, code, prefix, or post-fix”
Covered MLTS environments should support plain 911 dialing from every station with dialing capability. Old PBX habits such as 9-911 are a compliance red flag.
On-site or responsible-party notification
47 C.F.R. § 9.16(b)(2)“must not delay the call to 911”
Security desk, reception, facilities, or crisis teams can be notified, but notification cannot hold or reroute the emergency call before it reaches public safety.
Dispatchable location for MLTS
47 C.F.R. § 9.16(b)(3)“conveying the dispatchable location of the caller to the PSAP”
The enterprise has to maintain usable location records, not merely a billing address or main switchboard number.
Alaska MLTS location detail
Alaska Stat. § 29.35.134(b)(2)“street name, valid address, and business name”
For Alaska sites, do not stop at a street address. Include direct callback, room, office/unit/building and floor detail where applicable.
Alaska update timing
Alaska Stat. § 29.35.134(b)(3)(B)“within one business day after completion of any changes”
Tie E911 updates to telecom, facilities, and floor-plan change management rather than an annual cleanup.
911 context
Alaska's emergency-calling model is shaped by municipal 911 authority, remote communities, long transport distances, and a need for very clean address and callback data. The 2020 legislation summary points to AS 29.35.134 as the core MLTS reference.
911 authority and routing model
Municipalities may require E911 service by ordinance, and MLTS operators must keep ALI information aligned to the Master Street Address Guide where E911 is used. Enterprise sites should identify the municipality or borough responsible for 911 service before assuming a uniform statewide workflow.
Location delivery approach
For enterprise voice, Alaska is less forgiving of vague site descriptions because responders may cover wide territories. Fixed stations should have validated civic address and room/floor detail; mobile or softphone users need a process that reliably updates dispatchable location before emergency use.
Dispatchable location area / square-footage rule
No square-foot maximum was identified in the reviewed source. Alaska instead emphasizes emergency response location data such as office, unit, room, building number, and floor when the MLTS covers multiple floors or buildings.
State-specific differences
Alaska stands out for explicit MLTS database duties: the summary describes callback number, emergency response location, MSAG alignment, direct 911 dialing, and updates after system or physical-location changes, including a one-business-day target after certain changes.
Regulatory references
Privacy and records considerations
911 location records, callback numbers, test-call results, and site inventories should be treated as sensitive safety data. Limit access, keep change history, and align retention with state public-records rules, customer contracts, and incident-response needs.