13th February 2017
Phone: L Apple Health Data 10:55:04 – 11:01:07 (in 6 mins) 37.81m distance 50 steps (equivalent to 35m)
11:01:07 – 11:28:58 (in 28 mins) no distance no steps
11:28:58 – 11:35:18 (in 7 mins) 11.97m distance 16 steps (equivalent to 11m)
11:35:18 – 11:53:22 (in 18 mins) no distance no steps
11:53:22 – 12:01:05 (in 4 mins) 30.33m distance 44 steps (equivalent to 30m)
12:01:05 – 13:31:40 (in 30 mins) no distance no steps
(The family said the girls left home 13:30, therefore up to that time these are probably simple pottering about).
Phone: unknown #1 12:39:54 pm Cell site or timing advance estimate. Source of radius data: geolocation data from Google. Radius Estimate: approx 60 to 100 yds (FBI 2019 CAST Report)
Phone: BW 12:43 pm pic at Freedom Bridge taken on BW’s phone
Phone: L Apple Health Data 13:31:40 – 13:31:40 (in 0 mins) 23.84m distance 44 steps (equivalent to 30m)
Note the discrepancy: 23m travelled in no time, using 44 steps
13:31:40 – 13:51:08 (in 20 mins) 164.34m distance 33 steps (equivalent to 22m)
Note another discrepancy, L’s steps do not even closely fit distance travelled. 164m would use 234 steps.
(Cecil Testimony on Aug. 1, 2024 P. 5-6 and p. 8-10) 1:31 pm Apple Health begins reporting movement of L’s phone 1:38:49 pm "Several audio outputs" & phone call from L to DG.
1:39:08 pm phone charging
1:39:24 pm L call with DG ends
1:39:30 pm 2nd interaction with messaging app
1:39:45 pm Snapchat viewing
Times start 13:31; must mean that all these times are during the drive to Mears lot. It can’ cover time at the lot, or the walk to MHB, those appear below. AHD is similar to fit bit in that it doesn’t record travelling in a vehicle as movement. The drive to Mears is 5 mins, so 5 mins of these times will not consume any steps or distances walked…. that leaves 15 min and 188m to account for.
KG said they arrived at Mears 13:38, which is 12 mins within this time period. 12 min for a 5 min journey? It still leaves 7 mins, 77 steps, and 188m to account for. The drive was a certainly longer, and let’s say KG was off by a few mins re when they arrived. That would cover the time discrepancy, but it would not explain the 77 steps or the 188m.
If they arrived 13:38 that would leave 13 mins to 13:51. L was on the phone, with it plugged in 13:39, then there is the photo of them in the car, timed at 13:43. so L wasn’t moving until 13:44 at earliest. that might explain 6 mins but we still have 8 mins, 77steps and 188m, to account for BEFORE 13:39 ! So, we now know they detoured somewhere that used 8 mins, 77 steps and 188m. Somewhere that KG chose not hide, OR something occurred at Mears for 8 mins that entailed L taking 77 steps & walking 188m, that KG chose to hide.
Phone: RV 1:26 pm text message sent from RV’s phone
Phone: L Apple Health Data 1:41:44 pm photo posted to L Snapchat acct (Cecil Testimony Aug 1 2024 p5-6 & 8-10)
Phone: L Apple Health Data 1:43:49 pm photo of girls in car posted to L’s Snapchat acct (Cecil Testimony Aug 1
2024 Aug. 1, 2024 P. 5-6 and p. 8-10)
Phone: L Apple Health Data 13:51:08 – 14:00:09 367.03m distance (in 9 mins) 228 steps (equivalent to 160m)
Note another discrepancy, L’s steps do not even closely fit distance travelled. 367m would use 524 steps.
The monochrome photo of MHB was timed at 14:05, the walk to MHB is 8 mins. To take the photo at 14:05 L had to leave Mears by 13:57
at latest. This time band begins at 13:51, OK so far… 14 mins available to get to MHB…. Lots of time.
Mears-MHB takes 8 mins. AHD recorded here 9 mins, which is close enough, BUT Mears to MHB is 531m, not 367.03m. No way, unless L was running, but she clearly wasn’t, as it seems to have taken her 9 mins to move what one could have walked in 5 mins.
Phone: L Apple Health Data 14:00:09 – 14:08:49 (in 8 mins) 152.13m distance 593 steps (equivalent to 415m)
Note another discrepancy, L’s steps do not even closely fit distance travelled. 152m would only use 217 steps.
We have now got A&L 164m from MHB. She must be on MHB by 14:05 to take that monochrome photo. She has 5 mins left to walk 164m.
Note that this is to 14:08, 3 mins past the 14:05 deadline. Say A&L got to the north end of MHB at 14:05 then loitered until 14:08. (Of course, that would mean at 14:08 she was still there, so couldn’t have taken the photo of A halfway across MHB at 14:07, and would’ve had to cross the whole of MHB in 5 mins to be in place to take the 14:13 video – this will be addressed further on)…
Are we saying that in 5 mins L did the remaining 164m ? No. the data says L only went 152m - 12m (40ft) short of MHB ! L couldn’t have taken that photo from there. - Interestingly, A&L were now by the branch-off to a track going to the cemetery (& branching off down near the final crime scene).
Phone: L 2:05 pm Location: Monon High Bridge
Phone: L 2:07:08 pm phone was unlocked
Phone: L 2:07:10 pm accesses Snapchat and is locked again
Phone: L 2:07:20 pm Snapchat and the phone unlocked again. LE claim that this is the last
time ‘L’ unlocked her phone.
Phone: L after 2:07 pm Location: Monon High Bridge
When asked if the photo of A on the bridge was on L's cell phone, Bunner said, "Not that I recalled."
Phone: L Apple Health Data 14:08:49 – 14:18:49 (in 10 mins) 414.39m distance 220 steps (equivalent to 154m)
Note another discrepancy, L’s steps do not even closely fit distance travelled. 414m would use 592 steps.
L is 12m short of MHB at 14:08. She’s missed the window for the monochrome MHB photo and the photo of A on MHB and will now have to rush to be at the south end of MHB to do a video at 14:13. She must now walk the 12m plus all of MHB, a total of 266m. Then stop, to be abducted, at 2:13.
Note that this timing also means BG couldn’t have got onto MHB at 14:08 either, so he is also going to have to race over MHB..
We need to work these AHD figures because they run to 14:18 (10 mins) but we can only use to 14:13 (5 mins) to get us to the south end on time. So, we must first separate the amounts… 14:08:49 – 14:13:49 (in 5 mins) 212.20m distance 110 steps and
14:13:49 – 14:18:49 (in 5 mins) 212.20m distance 110 steps
Next, we must remove a few mins from the latter, to allow time for the abduction…
14:15:49 – 14:18:49 (in 3 mins) 212.20m distance 110 steps
Crossing MHB first; travelled 212m. L’s time is now 14:13, BUT L is still 54m (177ft) short of the south end! Big problem.
Doing the extra 177ft would put L at the south end of MHB, but at 14:17, which doesn’t fit taking a video there at 14:13. Big problem. Let’s pretend we didn’t notice that; L is at the south end of MHB at 14:17. They are now to be abducted, & forced ‘down the hill’, across the drive, into the woods, to and across the creek, and to the final crime scene. There is a remaining 40m distance and 5 mins on the AHD to do all this. Big problem.
Cecil said (Testimony Aug. 1, 2024 (p5-6 & 8-10). L phone AHD reported approx 563m of movement since approx 1:50 pm. He determined A&L walked about 700m –1682 steps – total since 1:31 pm.
Phone: L Apple Health Data 2:08 pm AHD continues reporting movement of L’s phone (Cecil testimony Aug. 1, 2024
p5-6 & 8-10)
Phone: Ron Logan 2:09 pm Cell site or timing advance estimate. Long: E 86 38’ 23.3” Lat: N 40 35’ 21.4” Radius
Estimate: approx 3 to 5,400 yds Source of radius data: phone call to RL’s phone Wi-Fi
location centre point: approx 466 yds from 5858 W 300 N
Phone: L sometime prior to 2:13 pm 5 photos found on L’s phone. In 4 there is a man behind A. None are the 2 posted to
Snapchat at 2:05 & 2:07 pm. 2 were taken in the car. Bunner said he wasn’t aware of
any deleted photos or videos on the phone or through Snapchat as of Feb. 14, 2017. (Bunner Testimony Oct 22, 2024). In 2019, Cecil found 4 of the “images/videos” that were taken on Snapchat, he couldn’t find the 5th (Cecil Testimony on Oct 23, 2024).
Phone: L 2:13:51 PM Source of radius data: geolocation metadata from video on L’s phone (Bunner Report
Feb 15, 2017) Radius Estimate: approx 3 to 5,400 yds. GPS Tracking: Cecil said the
longer the video went on, the more accurate GPS data became. He said L had location data turned on when she was using Snapchat. When the video starts, GPS data generated by L’s phone geolocated near the Delphi High School, but after approx 4 secs, it geolocated back to the Monon Trail. In trial, Cecil changed that to Memorial Park. Eldridge focused mostly on Apple Health data, but she did review the video and agreed with the timestamp and GPS location, but, she didn’t examine it enough to know the location moved.
Video shows L filming herself & A on MHB. At one point, the phone points up and there is no one visible behind A. It has audio of sniffling & a girl saying, "There's no path.” last activity on the timeline. Bunner said after watching this, he took screenshots & sent them to investigators (Bunner Testimony Oct 23, 2024 (Cecil Testimony Aug. 1, 2024, p6).
Phone: L 2:14:41 pm unsuccessful attempt to unlock L’s phone using Touch ID
Phone: L Apple Health Data 14:18:49 – 14:25:22 (in 7 mins) no distance no steps
This would fit the States idea of RA stopping when he saw Weber’s van (a bit too neat though; it looks like they reverse engineered Weber, got him to lie, to fit this stop).
(Cecil Testimony Aug. 1, 2024 p5-6 &. 8-10).
Phone: L Apple Health Data 2:18 pm AHD stops reporting movement of L’s phone after recording a total of 414m since 2:08
Phone: L Apple Health Data 14:25:22 – 14:32:39 (in 7 mins) 50.64m distance 548 steps
14:31 pm (in ? mins) ascended 20ft approx 66 steps
L moved on, 50m in 7 mins, & climbed 20ft. But there is no 20ft climb there, it’s flat. It’s also still a fair way from the creek. Big problem.
(Cecil Testimony on Aug. 1, 2024 P. 5-6 and p. 8-10):
Phone: L Apple Health Data. 2:25 pm. AHD resumes reporting movement
2:30 pm. AHD stops reporting movement of L’s phone after a total of 5m since 2:25 pm
2:31 pm. AHD reports 2 flights of stairs or approx 20ft
Phone: L Apple Health Data 14:32:39 – 15:00:01 (in 18 mins) no distance no steps
(Cecil’s 2019 Report claimed the phone “likely died”).
Phone: L Apple Health Data. 2:32:26 pm & 2:32:39 pm. AHD stops reporting movement of L’s phone
Phone: L 2:33 pm KnowledgeC records L’s screen turning off
Phone: L Apple Health Data 15:00:11 – 15:06:11 (in 6 mins) 0.71m distance 1 step
They stop, some way from the creek, but in clear sight of it, the drive, and MHB, for 24 mins. This is after the state claim RA had panicked and driven A&L to the crime scene on the other side of the creek. Note that this is in no way over the creek. Big problem.
There is no further data from the AHD, everything hereafter are estimates (ranges 3 to 5400yds ! so within 3 miles / 5000m ! Worthless)
Careful calibration of every ft/m min on the Apple Health data and correlating it with every available fact for those times etc ,and adhering to the route the state relied upon, produced an outcome that
does NOT put A&L over the creek at 3:06;
does NOT identify ANY ‘2 storey’ climbing opportunity at the time of the climb;
does NOT put A&L at the south end of MHB at 2:13;
does NOT put A&L in the position necessary for the 2:08 photograph;
does NOT put A&L in the position necessary for the 2:05 photograph;
puts A&L well north of MHB at a time when others were there, but nobody saw them there;
raises serious question on what happened at Mears lot and about where the girls went on the way to Mears lot.
Phone: unknown #2 3:02 pm Cell site or timing advance estimate: (FBI 2019 CAST Report) Source of radius data:
geolocation data from Google Radius Estimate: approx 60 to 100 yds
Phone: L 3:11 pm Cell site or timing advance estimate. Source of radius data: phone call to L’s phone
from DG while crossing Wilson’s Bridge. Radius Estimate: approx 3 to 5,400 yds
Phone: L 3:14 pm Cell site or timing advance estimate. Source of radius data: text message to L’s phone
from DG while parked at Mears. Radius Estimate: approx 3 to 5,400 yds
Phone: DP 3:19 pm Cell site or timing advance estimate. Source of radius data: text received by DP phone
while he was at or near north end of MHB. Radius Estimate: approx 3 to 5,400 yds
Phone: L 3:24 pm Cell site or timing advance estimate. Source of radius data: phone call to L’s phone
from DG while walking the trail. Radius Estimate: approx 3 to 5,400 yds
Phone: unknown #3 3:27 pm Cell site or timing advance estimate. Source of radius data: geolocation data from
Google .Radius Estimate: approx 60 to 100 yds (FBI 2019 CAST Report)
Phone: L 3:22 pm Cell site or timing advance estimate. Source of radius data: phone call to L’s phone
from DG while walking the trail. Radius Estimate: approx 3 to 5,400 yds
Phone: DG 3:33 pm: 3:34 pm Cell site or timing advance estimate. Source of radius data: phone call from DG phone
to TG while walking the trail. Radius Estimate: approx 3 to 5,400 yds
Phone: CMH 3:49 pm Cell site or timing advance estimate. Source of radius data: C uploads photos on her
phone taken at trail while at Mears. Radius estimate: approx 3 to 5,400 yds
Phone: L 3:57 pm Cell site or timing advance estimate. Source of radius data: phone call to L’s phone
from DG while in car at Mears. Radius Estimate: approx 3 to 5,400 yds
Phone: DG 3:58 pm Cell site or timing advance estimate. Source of radius data: phone call from DG phone
to BP while in car at Mears lot Radius Estimate: approx 3 to 5,400 yds
Phone: L 4:06 pm Cell site or timing advance estimate. Source of radius data: text message from BP to
L’s phone. Radius Estimate: approx 3 to 5,400 yds
Phone: L 4:17 pm Cell site or timing advance estimate. Source of radius data: phone call to L’s phone by
BP. phone call named “Number 3” by Bunner’s Report, “Unknown” by Cecil’s Report. Radius Estimate: approx 3 to 5,400 yds
Phone: TG 4:19 pm Cell site or timing advance estimate. Source of radius data: phone call to TG’s phone
while waiting in car at Mears lot Radius Estimate: approx 3 to 5,400 yds
Phone: L 4:30 pm(ish) Cell site or timing advance estimate: Source of radius data: phone call to L’s phone
from BP when BP arrives at trails. Radius Estimate: approx 3 to 5,400 yds
Phone: BP 4:30 pm(ish) Cell site or timing advance estimate.Source of radius data: phone call from BP’s phone
to AT&T while she’s on the trails. Radius Estimate: approx 3 to 5,400 yds
Phone: L 4:47:33 pm Cell site or timing advance estimate. Source of radius data: text sent to L’s phone –
the last SMS message received by it on 2/13 (according to Bunner‘s Report but not
reflected by Cecil’s 2019 Report) Radius Estimate: approx 3 to 5,400 yds
Phone: L 5:00 pm(ish) Cell site or timing advance estimate: Source of radius data: phone calls to L’s phone
from MP while on the trails. Radius Estimate: approx 3 to 5,400 yds
Phone: L 17:44:50 PM Cell site or timing advance estimate: Source of radius data: cell tower data from AT&T.
Location: Wells Street. phone call from KG phone to L’s phone, Blocher said the AT&T
data shows the last contact event between the phone and Wells Street tower was at 17:44:50. According to records there was no contact with the phone after that. He said the data indicated L’s phone no longer in the area, or no longer in working condition; “since there had been no change in the ‘every 15 min update’ we [received] and the last known contact time had not changed since 17:44." Radius Estimate: approx 3 to 5,400 yds.
Phone: L 5:45 pm Eldridge said L’s phone lost contact with a tower at 5:45 pm but he didn’t find evidence
it had been turned off. According to AHD on L’s phone, it continued to log that it was
gathering data, meaning it was on, but wasn’t using data in between those times. Cecil’s report said there were messages coming through during that time frame. Eldridge said there is no evidence that those messages were delivered in between those times, and that the messages sent to L’s phone between 5:44 pm & 4:33 am weren’t delivered. Voicemails left at 5:45 pm were not delivered until Feb 17. "audio output start time"; Cecil said "research is incomplete” and it could mean headphones, a speaker, microphone, a Bluetooth device, etc. Eldridge said it could’ve also been an auxiliary cord for a car plugged into the phone. “I cannot think of any explanation that doesn’t involve humans.” He said L’s phone received a call milli seconds before this item was inserted. (Eldridge Testimony Nov 5, 2024)
Phone: MP after KG attempt to call L 5:45 pm Source of radius data: phone call from MP’s phone to LE while on the
trails to report A&L missing. Radius Estimate: approx 3 to 5,400 yds
Phone: L 5:48 pm Cell site or timing advance estimate. Source of radius data; cell tower data from AT&T
(Defence 4th Franks motion p3-4, para 13). Radius Estimate: approx 3 to 5,400 yds
Phone: RL 7:56 pm Cell site or timing advance estimate. Long: E 86 38’ 23.3” Lat: N 40 35’ 21.4” Source
of radius data: text message sent from RL phone. Wi-Fi location centre point: approx
466 yds from 5858 W 300N, Delphi, Indiana (RL Search Warrant) Radius Estimate: approx 3 to 5,400 yds.
Blocher: “according to my evaluation of data provided by AT&T the last contact event between the cell phone and the tower. at Wells Street was at 17:44:50 hrs. There had been no contact with the phone since then. My interpretation of the information received…..indicates that the cell phone is either (1) no longer in the area, or (2) no longer in working condition”. This conversation appears to have occurred prior to 1:00 am Feb 14, 2017 (Defence 4th Franks Motion p3, para 9-11) (State’s Response to Defence Motion for Hearing p 2).
Phone: L ping 9:0 0pm, 9:15 pm, 9:30pm, 9:45pm Cell site or timing advance estimate. Source of radius data: cell tower data from AT&T. Radius Estimate: approx 3 to 5,4 00 yds. Result: no response
Phone: L ping 10:15 pm Cell site or timing advance estimate. Source of radius data; cell tower data from AT&T.
Radius Estimate: approx 3 to 5,400 yds. Result: no response
Phone: RL 10:16 pm Cell site or timing advance estimate. Source of radius data text message received by
RL’s phone Wi-Fi location centre point: approx 466 yds from 5858 W 300N, (RL
Search Warrant) Long: E 86 38’ 23.3” Lat: N 40 35’ 21.4” Estimate: approx 3 to 3,300-5,400 yds
Phone: L ping 10:30 PM Cell site or timing advance estimate. Source of radius data: cell tower data from AT&T
. Radius Estimate: approx 3 to 5,400 yds Result: no response
Phone: L 10:32:06 pm “audio stops recording”. Cecil’s 2019 Report said this was last signal/ activity from the
phone, and it had likely died at 10:32 pm but then the changed his mind in trial to say
he now deemed the phone to have stayed on until sometime after 4:30 2/14. Eldridge confirmed the #1 logged by L’s phone was wired headphones. He said this means wired headphones were inserted 5:45 pm and removed 10:32 pm. and it could have been wired headphones or an aux cable. (Eldridge Testimony on Nov 5, 2024)
Phone: L 10:45 pm Cell site or timing advance estimate. Source of radius data: cell tower data from AT&T.
Radius Estimate: approx 3 to 5,400 yds Result: no response
Phone: L 10:48:22 pm Cell site or timing advance estimate. Source of radius data: SMS message sent to L’s
phone – this is the last SMS message received by L’s phone on 2/13 (as in Cecil’s
2019 Report but not Bunner’s Report re: L’s phone on Oct 12, 2017). Radius Estimate: approx 3 to 5,400 yds
Phone: L ping 11:00 pm; 11:15 pm: 11:30 pm 11:45 pm: 12:00 pm; 12:15 pm; 12:30 pm: 12:45 pm Cell site or timing advance
estimate. Source of radius data: cell tower data from AT&T. Radius estimate approx 3
to 5,400 yds Result: no response
14th February 2017
Phone: L 4:33:31 am Cell site or timing advance estimate. Source of radius data: SMS message (duplicate
#1) to L’s phone (reflected by Cecil’s 2019 Report but not Bunner’s Report Oct 12,
2017). Radius Estimate: approx 3 to 5,400 yds Source of radius data: cell tower data from AT&T re: SMS message to L’s phone (as in Bunner’s Report re: L’s phone on Oct 12, 2017 but not Cecil’s 2019 Report)
NOT FOR PUBLIC DISSEMINATION UNTIL AUSBROOK AUTHORISES:- just before the messages came in at 04:33, a “Welcome to the AT&T family” message came in. This typically comes in when a new phone joins, or a SIM is changed, that kind of event.
Phone: L 4:33:36am 4:33:37am,: 4:33:38am Cell site or timing advance estimate: Source of radius data: SMS message
to L’s phone (according to ?) Radius Estimate: approx 3 to 5,400 yds
Phone: L 4:33:39 am: 4:33:40 am Cell site or timing advance estimate. Source of radius data: SMS message to L’s
phone (according to ?). Radius Estimate: approx 3 to 5,400 yds
Phone: L after 4:33:41 am Cell site or timing advance estimate. Radius Estimate: approx 3 to 5,400 yds. L phone
stopped receiving notifications. Eldrige said it was in & out of service before 5:45 pm
Feb. 13, 2017, AT&T repeatedly tried to ping L’s phone after 5:44pm on Feb 13, and there was no info it was powered off overnight. He was unable to determine why it didn’t ping from 5:45 pm 2/13 until 4:33 am 2/14, even though it was under A’s back and was stationary. “I can only conclude something external happened to the phone“ (i.e., it could’ve been moved, blocked by metal, blocked from the tower, etc). (Eldridge Nov 5, 2024)
Phone: L 4:34 am There is no activity recorded by L’s phone after 4:34 am on 2/14.
Phone: L ping 7:16 am Cell site or timing advance estimate. Source of radius data: cell tower data from AT&T.
Radius Estimate: approx 3 to 5,400 yds. 1st ping on 2/14 sent to L’s phone by AT&T.
Result: no response. (Defendant’s, 4th Franks Motion Based on Newly Disclosed Evidence p. 3-4, paragraph 13)
Phone: L ping 7:31am: 7:46am: 8:01am; 8:16am: 8:31am: 8:46am: 9:01am: 9:16 am: 9:31am: 9:46am: 10:01am: 10:16am;
10:31am: 10:46am: 11:0 am: 11:16am: 11:31am Cell site or timing advance estimate. Source of radius data: cell
tower data from AT&T. Radius Estimate: approx 3 to 5,400 yds. Result: no responses.
Phone: L ping 11:46 am: 12:01 pm Cell site or timing advance estimate. Source of radius data: cell tower data from AT&T.
Radius Estimate: approx 3 to 5,400 yds Result: no response
Phone: L 12:16 pm Cell site or timing advance estimate. Source of radius data: cell tower data from AT&T.
Radius Estimate: approx 3 to 5,400 yds Result: no response
15th February 2017
Phone: L 3:06 am Cecil said Bunner shut the phone down Feb 15, 2017 which would’ve reset the power
on/off log, Defence asked "We will never know exactly when the phone powered off?"
Cecil agreed. WTHR: The phone's last activity was 4:34 am Feb. 14.
What if we go back to the point just before MHB…
Phone: L 2:07:08 pm phone was unlocked
Phone: L 2:07:10 pm accesses Snapchat and is locked again
Phone: L 2:07:20 pm Snapchat and the phone unlocked again. LE claim that this is the last time
‘L’ unlocked her phone.
A&L were now by the branch-off to a track going to the cemetery (& branching off down near the final crime scene). What if they took that turning? Obviously the 2 photos and video then must be fake, so let’s ignore those and see if movements and distances get us anywhere else;
The available tracks
Phone: L Apple Health Data 14:08:49 – 14:18:49 (in 10 mins) 414.39m distance 220 steps (equivalent to 154m)
2:08 pm AHD continues reporting movement of L’s phone
414m will get L to the base of the cemetery.
Phone: Ron Logan 2:09 pm Long: E 86 38’ 23.3” Lat: N 40 35’ 21.4”: phone call to RL phone Wi-Fi. Location centre
point: approx 466 yds from 5858 W 300 N
Phone: L 2:14:41 pm unsuccessful attempt to unlock L’s phone using Touch ID
Phone: L Apple Health Data 14:18:49 – 14:25:22 (in 7 mins) no distance no steps
2:18 pm AHD stops reporting movement of L’s phone after recording a total of 414m since 2:08
inactivity until 14:25 (7 min) – staying still, perhaps sitting in a vehicle?
Phone: L Apple Health Data 14:25:22 – 14:32:39 (in 7 mins) 50.64m distance 548 steps
. 2:25 pm. AHD resumes reporting movement
2:30 pm. AHD stops reporting movement of L’s phone after a total of 5m since 2:25 pm
14:31 pm (in ? mins) ascended 20ft approx 66 steps 2:31 pm. AHD reports 2 flights of stairs or approx 20ft L moved on, 50m in 7 mins, & climbed 20ft.
The steps far exceed the distance moved. Could this be caused by a phone being moved (shaken?) a lot ?
Phone: L Apple Health Data 14:32:39 – 15:00:01 (in 18 mins) no distance no steps
. 2:32:26 pm & 2:32:39 pm. AHD stops reporting movement of L’s phone
Phone: L 2:33 pm KnowledgeC records L’s screen turning off
Phone: L Apple Health Data 15:00:11 – 15:06:11 (in 6 mins) 0.71m distance 1 step
There is no further data from the AHD, everything hereafter are estimates (ranges 3 to 5400yds ! so within 3 miles / 5000m !