Fargo, West Fargo & Cass CountyCriminal defense informationCall 701-929-4886
Fargo and North Dakota criminal defense guide

Cell-Site Location Evidence in North Dakota

Cell-site records can help estimate which part of a cellular network handled a phone’s activity. They do not ordinarily place a person at an exact…

ElementsPenaltiesEvidenceNext steps

Historical CSLI, real-time pings, call-detail records, sectors, timing advance, precision estimates, provider process, Carpenter warrants, mapping, attribution, expert testimony, and suppression

Cell-Site Location Evidence in North Dakota

Cell-site records can help estimate which part of a cellular network handled a phone’s activity. They do not ordinarily place a person at an exact address, room, or point on a map. A reliable defense analysis separates the legal authority used to obtain the records from the engineering questions: what the provider recorded, why the phone connected to that site and sector, how broad the coverage was, what events are missing, and whether the device was actually with the accused.

A tower connection is not a GPS coordinate. Demand the native provider records, tower and sector data, field definitions, time-zone rules, retention information, network changes, mapping inputs, and the analyst’s complete methodology before accepting a colored coverage wedge as proof of location.

Carpenter brought historical CSLI within the Fourth Amendment

In Carpenter v. United States, 585 U.S. 296, 309–22 (2018), the Supreme Court held that a person has a legitimate expectation of privacy in the record of physical movements captured through historical cell-site location information. Government acquisition of at least seven days of those records was a search and ordinarily required a warrant supported by probable cause.

Provider possession does not decide privacy

The Court declined to extend the traditional third-party doctrine mechanically to CSLI. Carrying a phone is indispensable to modern life, and the network generates location-related records automatically. The depth, breadth, comprehensive reach, and retrospective quality of the data made it different from limited bank or dialed-number records.

Carpenter’s holding was deliberately narrow

The Court stated that it was not deciding real-time CSLI, tower dumps, conventional surveillance, security cameras, or business records that might incidentally reveal location. It held that accessing seven days or more of historical CSLI was enough to decide that case. Shorter acquisitions therefore require analysis rather than a claim that Carpenter categorically permits them.

Chatrie confirms that short location acquisition can still be a search

Chatrie v. United States, 609 U.S. ___, slip op. at 2, 10, 29–32 (2026), held that police conducted a search when they obtained limited Google Location History through a geofence warrant. Chatrie did not involve carrier CSLI and did not answer every short-duration CSLI question, but it rejects a universal rule that brief provider-held cellphone-location access falls outside the Fourth Amendment.

The Stored Communications Act supplies process but not the constitutional ceiling

18 U.S.C. § 2703 authorizes specified legal process for provider records. A § 2703(d) order uses a relevance-and-materiality standard below probable cause. Carpenter holds that statutory compliance alone is insufficient when the Fourth Amendment requires a warrant.

North Dakota warrants require cause, nexus, and particularity

N.D.R.Crim.P. 41 governs state search warrants, including electronically stored information. State v. Leavitt, 2015 ND 146, ¶¶ 5–9, explains the required nexus between the place searched and evidence sought. A CSLI warrant should identify the phone or account, offense, relevant interval, records, and why the data probably contains evidence.

Carrier records vary by provider, network, time, and requested category

Call-detail records record network events

A call-detail record can contain date and time, duration, originating and terminating numbers, event type, serving cell, sector, switch, routing, and other fields. Some providers record cell sites at call start and end; others include handoffs or different event types. The provider’s historical field guide is essential.

Data sessions and messages may generate different records

Voice calls, SMS, MMS, packet-data sessions, registration events, and application traffic do not produce identical logs. A smartphone may exchange background data without user action, or an application message may travel over data rather than appear as a carrier SMS. Determine which events are included and omitted.

Cell and sector identifiers must be matched to the correct network state

A site ID in a record is meaningful only when linked to the carrier’s tower list, sector azimuth, technology, antenna configuration, and effective dates. Sites are added, renumbered, relocated, retuned, or decommissioned. A current tower database may mis-map historical records.

Subscriber records and CSLI answer different questions

Subscriber name, billing address, account start, payment source, and assigned number can connect an account to a person. CSLI concerns the network’s handling of the device. Neither alone proves who carried the phone during an event. Shared plans, family phones, business accounts, number porting, SIM changes, and device swaps matter.

Precision or advanced network records may be separate

Some productions include per-call measurement data, timing advance, round-trip timing, angle, network event location, or provider-generated estimates. These are not ordinary sector-only CSLI. The collection method, units, algorithm, confidence, and validation must be established before claiming greater precision.

Retention limits can make the production incomplete

Providers retain different fields for different periods and may overwrite engineering data sooner than billing records. A preservation request can freeze records still held but cannot recreate expired fields. Obtain retention policies in effect, request dates, preservation letters, gaps, and provider statements about unavailable data.

Time zones and daylight-saving adjustments cause recurring errors

Records may use UTC, local network time, switch time, or an export setting. Tower lists and analytical tools may apply another zone. Verify offsets on the event date, daylight-saving changes, and whether a report converted times. A one-hour error can reverse a timeline.

A serving cell does not necessarily mean the nearest tower

Networks choose usable resources, not geometric proximity alone

A phone may connect based on signal quality, antenna direction, terrain, buildings, vegetation, weather, frequency band, power, network load, interference, maintenance, handoff rules, and device capabilities. The closest tower can be blocked, overloaded, pointed away, or operating on a band the phone does not use.

A sector is not a fixed pie-shaped boundary

Analysts often draw a wedge from tower azimuth to illustrate a sector’s general orientation. Radio coverage does not stop at clean lines. Side lobes, back lobes, reflections, downtilt, elevation, and local environment can produce coverage outside the illustration. A wedge is a demonstrative, not a measured footprint.

Rural cells can cover large areas

North Dakota’s open terrain, sparse tower density, long roads, weather, and varied network build can create broad coverage. A connection may place a device within miles rather than at a specific farmstead, vehicle, or room. Urban areas may have more sites but also more reflection and indoor complexity.

One connection is weaker than a consistent sequence

A series of records can support a general movement inference when sectors change in a coherent order. Even then, gaps, network selection, event timing, and alternative routes matter. A single serving sector ordinarily supports only a broad consistency statement.

No record does not prove no presence

A device can be powered on and idle without generating a retained event in the requested records. It can be off, in airplane mode, out of coverage, using Wi-Fi, connected to another carrier, or associated with a different number. Absence should be described with the production’s limitations.

Wi-Fi calling and internet services complicate carrier inference

Calls and messages may travel through Wi-Fi, over-the-top applications, or another linked device. Carrier records may show a service event without ordinary cell-site fields, or no event corresponding to an application communication. Device and provider records should be compared.

A phone can connect across water, valleys, and state lines

Radio propagation follows terrain and antenna conditions rather than political boundaries. A tower across the Red River or farther along a highway may provide the strongest service. Mapping only North Dakota sites can omit realistic alternatives in Minnesota or neighboring regions.

Mapping should expose uncertainty rather than hide it

Plot sites, sectors, and event times from verified source data

The analyst should identify the carrier file, site table, effective dates, coordinates, azimuth, units, time conversion, mapping software, projection, and assumptions. Manually entered coordinates and copied spreadsheets require quality checks. Preserve the working project, not only exported slides.

Do not place the handset at the tower pin

The tower coordinate identifies network infrastructure. It is not the device coordinate. A map showing a handset icon at the tower or along a guessed ray can materially exaggerate precision. Sector-only CSLI generally supports an area or direction of coverage, not a distance.

Drive testing measures later conditions

A test phone can record which cells serve selected routes at a later date. Results depend on network configuration, device, SIM, technology, time, traffic, season, foliage, construction, and weather. Testing can explore possibilities but does not recreate historical radio conditions automatically.

Propagation models require inputs and validation

Software can estimate coverage using terrain, antenna height, power, frequency, clutter, downtilt, and model assumptions. Without carrier engineering parameters and calibration, a polished heat map may be speculative. Disclose the model, inputs, error measures, validation, and sensitivity to changed assumptions.

Analyst qualifications should match the opinion

A detective may competently organize carrier records and plot tower coordinates while lacking radio-frequency engineering expertise to claim street-level precision. Under N.D.R.Ev. 702, expert testimony must rest on sufficient facts, reliable principles and methods, and reliable application. Define whether the witness offers record interpretation, historical-cell analysis, RF propagation, statistics, or attribution.

Daubert focuses on method, not credentials alone

Daubert v. Merrell Dow Pharmaceuticals, Inc., 509 U.S. 579, 589–95 (1993), requires reliable expert methodology, and Kumho Tire Co. v. Carmichael, 526 U.S. 137, 147–52 (1999), applies the gatekeeping obligation to technical expertise. Training certificates do not answer whether the analyst’s conclusion can validly follow from sector-only records.

Use calibrated language

Appropriate testimony may say a record is consistent with a device using a sector that generally serves an area. Claims that the accused “was at” a particular address, crossed an exact line, or followed one route require stronger data and validated analysis. Limiting language should appear on maps and in testimony.

Real-time pings and prospective records present distinct issues

Prospective CSLI is generated for ongoing monitoring

Investigators may ask a carrier to provide repeated device-location updates, sometimes called pings, rather than retrieve already-existing history. The request can use cell-sector data, network-based location, GPS-assisted information, or another provider tool. Identify the actual method instead of using “ping” as a technical conclusion.

Carpenter did not decide real-time CSLI

The Carpenter majority expressly reserved real-time CSLI. Courts have applied search, tracking-device, statutory, and exigency doctrines differently depending on duration and method. Chatrie strengthens the principle that sensitive phone-location acquisition can be a search, but the exact prospective process still requires jurisdiction-specific analysis.

A warrant should define duration, frequency, and data

Prospective authority should identify the phone or account, offense, monitoring period, update interval, location method, precision, return procedure, minimization, and termination conditions. An order authorizing subscriber records should not be treated as open-ended authority for continuous tracking.

Emergency requests require an actual emergency

Providers may disclose records in good faith when they believe an emergency involving danger of death or serious physical injury requires prompt disclosure. Missing-person, kidnapping, suicide, active threat, or similar facts can support urgent assistance. Obtain the request, factual certification, provider response, duration, categories, renewals, and when the emergency ended.

Exigency is limited by scope and time

Immediate location may be justified while danger persists, but continued tracking after rescue, arrest, or dissipation of the threat ordinarily requires proper judicial authority. The State should establish why ordinary warrant procedures were inadequate and why the acquisition matched the emergency.

Tracking can enter constitutionally sensitive spaces

United States v. Karo, 468 U.S. 705, 714–18 (1984), held that monitoring a beeper to reveal information from inside a home implicated the Fourth Amendment. Modern network data can disclose visits to homes, clinics, counsel, religious services, or political activity, reinforcing the need for judicial limits.

Cell-site evidence locates a device estimate, not an identity

Subscriber and user are not necessarily the same

A parent may hold the account while a child uses the phone; a business may own an employee device; partners may share; prepaid records may be inaccurate; and numbers can be ported. Establish device possession during the relevant interval through independent evidence.

SIM, handset, number, and account can change

IMEI identifies equipment, IMSI and related values identify subscriber modules, and a phone number can move between devices or carriers. The production should reveal which identifiers the request targeted and whether swaps occurred. A record for the number may not establish which handset generated it throughout the period.

Possession at arrest does not prove historical possession

Finding a phone with the accused later is relevant, but the defense should test intervening sharing, loss, repair, replacement, sale, theft, and access. Photos, account logins, application sessions, pairing, Wi-Fi history, witnesses, and message content may corroborate or undermine attribution.

Call content and contact labels can mislead

Carrier records generally show numbers and routing, not who spoke. A saved contact name is user-created and can be stale or false. Subscriber data for the other number, recordings, messages, witnesses, and context are needed before attributing participants.

Corroboration should be genuinely independent

Surveillance, license-plate records, receipts, vehicle data, access logs, photos, location services, and witnesses can support a timeline. Avoid circular corroboration in which several maps all derive from the same carrier event or an officer’s initial assumption.

Trial use should match what the records can reliably establish

Authentication does not validate every interpretation

A carrier custodian can authenticate the records as provider data and explain ordinary business practices. That foundation does not prove the prosecution analyst selected the correct historical tower table, converted time properly, interpreted every event field accurately, or drew reliable coverage conclusions. Business-record admissibility and expert reliability remain separate inquiries.

Provider custodians and location analysts have different roles

The custodian may know retention, field definitions, and production methods but lack personal knowledge of radio-frequency conditions at the relevant North Dakota site. The analyst may map data but lack access to internal network engineering. Counsel should identify which witness can support each link instead of allowing one witness to vouch generally for the entire location theory.

Summary exhibits need a disclosed source and reproducible calculation

A timeline or map can summarize voluminous records, but the defense must be able to trace each marker to an admitted row and each conversion to a stated rule. Request the source table, formulas, sorting, filters, duplicates, excluded events, geocoding, tower version, and legend. Demonstratives should distinguish admitted provider data from analyst inference.

Prosecutors should not argue absence beyond the dataset

If requested records cover only calls and texts, the State should not argue that silence proves a phone was powered off or absent. If a provider produced one carrier account, the State should not imply the person had no other device. Cross-examination should establish the request’s limits before the prosecution turns missing records into affirmative proof.

Handoffs require careful interpretation

Some records show a call beginning on one sector and ending on another; some include intermediate network events; some omit them. A change can reflect movement, changing signal conditions, network balancing, or technical behavior. The time between recorded events and the geography of alternative coverage determine how much movement inference is justified.

Calls near jurisdictional borders require complete site data

Fargo-area analysis may require Minnesota towers, and western or northern investigations may require adjacent-state or Canadian-network information depending on roaming and coverage. A carrier production limited to one market or investigator-created tower list can exclude the actual serving alternatives. Obtain roaming fields, market codes, and the complete relevant-site table.

Statistical language needs a real statistical basis

Terms such as “likely,” “most probable,” “consistent only with,” or “high confidence” sound quantitative. An analyst should explain the tested error rate, comparison population, validation data, and method supporting those words. Experience with many records does not turn a subjective impression into a measured probability.

Alternative hypotheses should be tested, not merely mentioned

If the records fit more than one route, address, user, or travel sequence, map the alternatives using the same assumptions. Compare them with surveillance, road travel time, tower orientation, site availability, and event gaps. A fair analysis asks what the data excludes as well as what it is consistent with.

Jury instructions and argument can preserve appropriate limits

The court can restrict the expert to a broad consistency opinion, require uncertainty on demonstratives, prohibit claims of exact location, and instruct that the records concern a device rather than necessarily the accused. Counsel should object when closing argument silently upgrades “consistent with a sector” into “proved he was inside the building.”

Combined-location exhibits must disclose that sources are not independent

Investigators may overlay CSLI, Google records, vehicle telematics, Wi-Fi, photographs, and application data. The display can look like several independent confirmations even when the sources share the same phone clock, account, or derived coordinate. Identify common inputs, different error measures, missing intervals, and whether one source was used to calibrate another before describing the overlay as corroboration.

Defense counsel should audit law, data, analysis, and presentation separately

Obtain the complete legal process

Request preservation letters, subpoenas, § 2703(d) applications and orders, search warrants, affidavits, sworn testimony, emergency requests, consent, provider correspondence, returns, inventories, extensions, sealing or nondisclosure materials, and later derivative warrants. Identify which process produced each field.

Demand native carrier records and documentation

Seek original spreadsheets or text files, metadata, hashes, tower and sector lists with effective dates, switch records, subscriber and device history, field definitions, time-zone instructions, retention statements, precision-data guides, and custodian materials. A detective-created summary omits fields and can introduce errors.

Preserve the analyst’s working materials

Request maps, GIS project files, scripts, formulas, imported tables, cleaned data, excluded records, geocoding, tower-source files, software versions, test results, notes, communications, draft reports, and demonstratives. Reproducibility requires the transformation from provider row to courtroom map.

Build an event-by-event validation table

For every event the State relies on, list source file, timestamp and conversion, event type, number, device and subscriber identifiers, site, sector, azimuth, technology, analyst interpretation, alternative coverage, and corroboration. Flag duplicates, gaps, unexplained codes, and current rather than historical site data.

Challenge overstatement before the jury hears it

Use Rule 702, authentication, relevance, and unfair-prejudice objections to define the permissible opinion. Request a hearing on methodology and qualifications, accurate map legends, uncertainty disclosure, and limits on phrases such as “located at.” A limiting instruction may be appropriate.

Raise suppression under Rule 12

N.D.R.Crim.P. 12 generally requires pretrial suppression motions when reasonably available. Identify duration, historical or prospective method, process used, constitutional shortfall, nexus, particularity, emergency facts, taint, good faith, later warrants, and derivative evidence.

Consider affidavit accuracy and good faith separately

A material intentional or reckless misstatement about precision, duration, phone attribution, retention, or emergency facts may support a Franks v. Delaware, 438 U.S. 154, 155–56, 171–72 (1978) hearing. United States v. Leon, 468 U.S. 897, 914–23 (1984), addresses federal good faith and its limits. Do not let one analysis substitute for the other.

Frequently asked questions about cell-site location evidence

What is historical CSLI?

It is provider-retained information identifying cell sites or sectors associated with past network events for a device or account. Fields and retention differ by provider, technology, and event.

Does Carpenter require a warrant?

For government acquisition of at least seven days of historical CSLI, ordinarily yes. Carpenter expressly left shorter periods, real-time data, and tower dumps unresolved.

Does Chatrie decide short-term CSLI?

Not directly. Chatrie involved Google Location History, not carrier CSLI. It does establish that even limited provider-held cellphone-location acquisition can be a Fourth Amendment search.

Does a cell connection mean the phone used the nearest tower?

No. Signal quality, antenna orientation, terrain, buildings, load, interference, frequency, maintenance, and device capability can cause a more distant site to serve the phone.

Can CSLI place a phone at an exact address?

Ordinary sector-only CSLI usually cannot. It generally supports a broad area or consistency inference. Precision records require separate validation and still include uncertainty.

What does a sector wedge prove?

It illustrates the antenna’s general orientation. Real coverage has no clean wedge boundary and can extend through side lobes, reflection, terrain, and varying network conditions.

Does no call record mean the phone was absent?

No. The phone could be idle, off, on Wi-Fi, in airplane mode, out of coverage, using an internet application, or generating an event not retained or requested.

Are text messages included in call-detail records?

Some SMS or MMS events may appear, but fields and cell information vary. App messages usually travel through data and will not appear as ordinary carrier text content.

What is a real-time ping?

It is a general term for provider-assisted prospective location, which may use sectors, network calculations, GPS assistance, or another method. The exact technology and legal authority must be identified.

Did Carpenter decide real-time tracking?

No. The Court reserved real-time CSLI. Applicable law depends on method, duration, jurisdiction, warrant or order, and exigency.

Can police obtain location during an emergency?

Providers may make emergency disclosures involving danger of death or serious physical injury, and exigent circumstances can justify limited warrantless action. The emergency, scope, duration, and end point must be proved.

Does the subscriber name prove who carried the phone?

No. Family plans, business devices, lending, theft, replacement, and SIM or device changes require independent user attribution.

Can a detective testify as a CSLI expert?

Only within demonstrated qualifications and reliable methodology. Plotting records is different from offering RF-engineering, propagation, distance, or street-level opinions.

Can later drive testing recreate historical coverage?

Not automatically. Network settings, devices, traffic, weather, season, construction, and sites may have changed. Testing should disclose its limits and validation.

What records should the defense request?

Native call-detail data, tower and sector lists with effective dates, field guides, subscriber and device history, time-zone instructions, retention, legal process, provider correspondence, analyst files, maps, scripts, and excluded records.

What is a Franks issue in a CSLI warrant?

It can involve material intentional or reckless misstatements or omissions about precision, duration, attribution, data availability, emergency facts, or what records will show.

Can later warrants be challenged as fruits?

Yes. If an unlawful location acquisition supplied probable cause for a phone, home, or arrest warrant, excise the tainted information and analyze independent source, attenuation, and other derivative-evidence doctrines.

When should a North Dakota motion be filed?

Rule 12 generally requires pretrial suppression when the basis is reasonably available. Technical and expert disclosure should be requested early, with leave sought to supplement after production.

Official authorities cited

Legal information, not legal advice. Cell-site evidence depends on the exact process, provider, record types, network, dates, site configuration, event fields, time conversion, analyst method, uncertainty, attribution, expert foundation, later evidence, and current law.


Call nowChoose a time