Evidence review · September 27, 2026

Phone forensics report findings

What the captured Garrett Discovery pages add—and the questions the source records still need to answer.

At a glance

01 / Reported in WCBIA · July 5, 11:47 AM

Location at home was mistaken for Nolan being home

A WCBIA participant says someone saw Nolan’s location at home and consequently thought he had returned. This is direct evidence that the confusion was being discussed; it does not independently establish the person’s actual whereabouts.

What remains unresolved

Physical phone location, Snap Map location, and an account’s activity indicator need separate attribution. A device appearing at home cannot establish that its owner arrived with it.

02 / Supa Seniors and Direct Messages · July 5

Apparent activity raised questions about access

Supa Seniors participants ask about access to the phone or Snapchat login, then discuss the account appearing active at home. An earlier direct message describes a mismatch between recent activity and an older location update.

What remains unresolved

These are observations reported by chat participants, not authenticated session logs. The login sentence has a redacted subject before “have his login”; the visible page does not support the OCR reading “I have his login.” Neither possession nor the person generating activity is established by this exchange.

03 / Direct Messages · July 6, 11:13:47 PM CDT

A later record is classified SENT—but contains no decoded text

The report classifies this entry as SENT and labels it a non-text Snapchat record, content_type=6. Its methodology defines SENT as transmission by the local account. The record is a concrete lead for account/session examination.

What remains unresolved

The cited record does not show someone typing a message or identify the device, session, person, or action that generated it. The report does not explain content_type=6 here. Calling it a message personally sent by Nolan would go beyond the evidence.

04 / WCBIA · July 5, 11:40:28 AM CDT

An early staying account deserves source tracing

A redacted sender describes someone urging Nolan to come aboard, an alleged response that he was staying, and boat trouble accompanied by panic. The wording uses a first-person plural description of the panic.

What remains unresolved

The next message attributes the account to what a redacted person said. Sender identity and source of knowledge are therefore essential before calling it firsthand. This exchange does not contain a confirmed alternate-ride arrangement.

05 / Supa Senior Guyz · July 5, around 12:50 PM

The return-ride question was still unresolved in the chat

After a report that Nolan had not planned to return with a particular group, participants ask whose boat he intended to board and acknowledge that they do not know.

What remains unresolved

This page documents uncertainty among the participants. It does not establish an agreed return trip with an identified boat operator, or prove that no agreement existed elsewhere. The operator’s own account and contemporaneous arrangements remain important.

06 / WCBIA and Supa Seniors

Two original media files could resolve major questions

On July 6, WCBIA participants interpret a shared media item as an argument involving Nolan. Separately, Supa Seniors participants discuss a possible image/video of Nolan at 4:34 and a departure estimate of about 4:37. The group itself qualifies the identification as only a possibility.

What remains unresolved

The PDF shows a media placeholder and the participants’ interpretation, not authenticated audio or a confirmed sighting. Recover the original files, capture times and context before assigning speakers or placing Nolan in the image.

07 / Garrett Discovery reconstruction · July 4

The GPS overlay distinguishes phone use from outside reports

The overlay attributes the last direct phone interaction to Nolan at 2:18:10 PM. It places a reported Sea Tow call at approximately 4:36 PM, explicitly says it was not made from Nolan’s phone, and identifies an independent source. It attributes the 4:39:46 PM bilge message to Morgan Seymour.

What remains unresolved

These are Garrett’s labeled findings. The Sea Tow entry is not proof of an outgoing call on Nolan’s handset. The sender attribution does not establish where Morgan was or how he learned of the boat problem.

Read the report accurately

Five limits that change the interpretation

  • Missing read timestamps: absence of a surviving read event does not prove a message was never viewed. Read timestamps also depend on message direction; group-read attribution requires care.
  • Recovered records: the four pre-WAL records are database-state differences. Garrett expressly does not equate their absence from the current view with user deletion.
  • Roster counts: these identify observed senders, not every silent group member. Garrett says all 208 distinct sender UUIDs were resolved internally to a name or username; public redactions still limit this review.
  • Ordering and clocks: activity order can follow a read timestamp rather than message creation. Garrett did not independently verify device-clock accuracy or timezone integrity.
  • Repeated claims: a story appearing in multiple chats may have a shared source. Repetition alone cannot establish independent corroboration.

Records that could resolve the questions

What to obtain next

  1. Native artifacts and device/session attribution for later outbound records, including the meaning of content_type=6.
  2. Original media associated with the argument discussion and possible 4:34 sighting, with metadata and provenance.
  3. The source behind the WCBIA departure account and that person’s original investigator interview.
  4. Original witness statements and an identified operator/vessel for any claimed return arrangement.
  5. The original report, extraction documentation, Garmin submission and source records behind the GPS overlay.

These are evidentiary follow-ups. The selected entries do not establish responsibility for Nolan’s death.