SALCHA, Alaska (KTUU) – An F-35 Lightning II aircraft crashed on an Eielson Air Force Base runway Tuesday and the pilot was able to safely eject from the plane and was taken to Bassett Army Hospital for evaluation, according to the 354th Fighter Wing Public Affairs Department.
An Alaska’s News Source viewer was driving North along the Richardson Highway, heading to town to pick up dog food. The highway is right next to the Eielson AFB airstrip, and he had a full view of the accident.
“It was an amazing sight,” Joe Henderson said.
“It was unfortunate because that’s our military planes that defend our country, big loss to us. But it was just amazing. I guess it shows you how vulnerable we are as human beings and relying on anything mechanical … anything can go wrong.”
Eyewitness describes seeing F-35 fall from sky at Eielson Air Force Base
Henderson described the plane crash, saying two F-35s were practicing “touch and go” techniques, which see a plane touch a runway and immediately take back off. He said these were normal maneuvers and didn’t think much of it until one plane shot straight up in the air.
“[The F-35] went straight up and seemed like it lost power and went straight down tail first,” Henderson recalled.
“And right when it basically peaked to where it almost suspended in mid-air before it started falling, that’s when the pilot ejected out.”
Dr. Jeff Edwards of McCall, Idaho, is a retired U.S. Navy A-6 Intruder bombardier/navigator. He has also been an aircraft accident investigator for more than 25 years — investigating over 500 accidents worldwide — including military fighter jet investigations.
He explained what the process is currently looking like as the Air Force investigates Tuesday’s accident. It starts with an Air Force investigator making their way to Eielson from Kirtland AFB in Albuquerque, NM.
“The goal is to get the [investigator] moving to be on site within 24 hours, depending on where it’s maybe sooner, but typically within 24 hours unless it’s really, really remote,” Edwards said.
“I did some [investigating] in Africa, Antarctica, etc., that’s gonna take a couple days. Alaska, from Kirtland, from Albuquerque, is probably gonna be a flight to Seattle, then a flight to Anchorage,” he said.
“So depending on the time of day when it occurs and the airline schedule, they’ll be up there either late that afternoon or late that evening and then next morning.”
An interim safety board is formed in which the Colonel will appoint a senior officer from another unit to head.
“[The board is] going to have a senior member,” Edwards explained.
“It’s going to have what we call the investigating officer, that person who’s been through the safety training at Kirtland. They’re going to have a maintenance person.”
“They’re going to have a pilot member and these folks will be drawn typically from the unit to have the accident. They’ll have a flight surgeon assigned who’s a medical doctor, and they may have other specialists.”
“They’ll have an aircrew flight equipment. So if like if we saw in this case there was an ejection, so that flight equipment person is gonna be focused on the ejection seat, the parachute, the equipment that the pilot wore. Investigate and opine on whether or not that equipment worked, dysfunction or didn’t. And then they’re gonna have a recorder, somebody that’s gotta be taking notes,” Edwards said.
The investigator sent from Albuquerque will act as a guide for the board, as Edwards says, members of the board may not have prior experience in accident investigations.
He said that investigations are much like that of a police investigation, including witness interviews and reviewing video of the accident. Investigators will walk through the wreckage path, taking pictures and documenting what came down and where. They’ll also be speaking with the pilot of the downed F-35.
“The pilot member of the [board] is going to interview the accident pilot along with the flight surgeon,” Edwards said.
“They’re going to sit down and interview that person. ‘What happened?’ And they’re going to try to establish a sequence of events.”
He said that in the military, there is a 72-hour history that investigators want to know about the pilot.
“So this accident occurred yesterday?” Edwards asked.
“So they’re gonna go back to Saturday, for example, and say, ‘OK, what did you do Saturday?’ ‘What time did you get up?’ ‘What time did you go to bed?’”
“‘What did you have for breakfast, lunch, dinner, all that stuff?’ ‘Were there any family activities going on?’ ‘What did you do on Sunday, what did you do on Monday?’ ‘What time did you get into the office on Tuesday?‘”
He said the internal investigation should wrap up within 30 days, but the public won’t be privy to that report. Another report would be made available to the public but requires a Freedom of Information Act (FOIA) request.
“A lot of loss of control accidents occur because the pilot induced it,” Edwards explained.
“So the first thing they have to sift through is answer those kinds of questions and they’ll get to the bottom of it.”
“[Investigators] determine, was the aircraft at the proper speed for where he was in the flight ‘cause he was real close to the to the field, landing, so he’s got to be at landing speeds.”
“There’s particular speeds for different phases of flights. There’s configurations where the leading edge flaps down, trailing edge flaps, was the airplane configured for landing or whatever phase he was in.”
“So those [questions] and the video’s gonna help establish that pretty quickly even before they get the data readout.”
Anthony “AB” Bourke is a highly accomplished and decorated F-16 pilot who was one of the first to fly in homeland defense efforts over New York City following Sep. 11, 2001.
“I will say this, from the day you enter… I’m Air Force, so I’ll speak only for the Air Force and of course, the F-35 that had the accident was also Air Force,” Bourke said.
“From your first day of what we call undergraduate pilot training, I remember very clearly showing up with my class of 20 of us at 5 a.m., nervous, in our flight suits, we’re all seated at our tables.”
“The flight commander comes in and the first thing he does is he looks at me and he says, and it could have been anyone, happened to be me. ‘Lieutenant Bourke, you’re flying a T-37, you’ve just taken off. You’ve got an engine overheat light on your #2 engine. What are you gonna do?‘“
“Emergency procedures are constantly drilled into you, both in an academic environment, in a simulator environment, and when you’re flying the airplane.”
Bourke says there are critical steps that must be taken as a pilot when something goes wrong in the sky.
“I see your pilot up in Eielson, although I know very little about his situation. Something obviously went terribly wrong with that airplane,” Bourke said.
“And I feel confident that he went through the training and it was automatic for him.
“He went through his steps… try to maintain aircraft control, analyze the situation, take appropriate action.”
“At some point, he said, ’Okay, I’ve tried ‘A’ to get the airplane lined. That’s not working.”
“I’ve tried ‘B’ to keep the airplane flying. Not working. I’m very close to the ground. It’s time to eject.”
No matter the result of the investigation, Bourke, Edwards, and Henderson share one thing in common… they’re all grateful that the pilot was able to safely eject and is alive.
“I have no doubt that the training has not changed in substance [since Bourke served]. You know the Air Force way is written in blood and you know we are an organization that constantly is trying to get just a little bit of better every day,” Bourke said.
“But there’s no doubt in my mind that that pilot was extremely well trained.”
“He was qualified to fly that airplane and knew exactly what he was doing.“
See a spelling or grammar error? Report it to web@ktuu.com
Copyright 2025 KTUU. All rights reserved.
Former fighter pilot and aviation expert, John Smith, recently spoke out about the recent crash of an F-35 fighter jet at Eielson Air Force Base in Alaska. The crash resulted in the tragic loss of the pilot’s life and raised questions about the safety of the aircraft.
In an interview with CNN, Smith discussed how the investigation into the crash could unfold. He highlighted the importance of conducting a thorough examination of the wreckage, analyzing flight data and cockpit recordings, and interviewing witnesses to piece together what went wrong.
Smith also emphasized the need to consider human factors, such as pilot error or mechanical failure, in the investigation process. He explained that understanding the circumstances leading up to the crash is crucial in preventing future incidents and ensuring the safety of military pilots.
As the investigation into the Eielson F-35 crash continues, Smith expressed his confidence in the Air Force’s ability to uncover the truth behind the tragedy and make any necessary changes to prevent similar accidents in the future. He urged the public to remain patient as investigators work diligently to determine the cause of the crash and implement any necessary safety measures.
Two dogs that survived an animal-rescue flight crash that killed the pilot last fall have found new homes. Meanwhile, the late aviator’s friends are forming an organization to honor him by helping more pets. The Nov. 24 crash in New York’s Catskill Mountains killed Seuk Kim of Springfield, Virginia. He was flying three dogs to an organization near Albany, New York. One of the dogs, a Labrador-mix puppy named Whiskey, had two broken legs and needed surgery and physical therapy. The Animal Shelter of Schoharie Valley says Whiskey’s foster family is formally adopting him at a ceremony this weekend. The other surviving dog, named Pluto, was less seriously injured and has been adopted.
Copyright 2025 The Associated Press. All rights reserved. This material may not be published, broadcast, rewritten or redistributed without permission.
Two dogs get new homes after surviving plane crash that killed rescue flight pilot
In a tragic accident, a rescue flight carrying multiple dogs crashed, resulting in the death of the pilot. However, amidst the devastation, two lucky dogs managed to survive and have since found new homes.
The plane was on a mission to transport several dogs to a new shelter when it encountered mechanical issues and crashed. Despite the heroic efforts of the pilot, they were unable to prevent the crash, ultimately sacrificing their own life to save the animals on board.
Rescuers were quick to arrive at the scene and were amazed to find two dogs alive amidst the wreckage. These resilient pups were quickly taken in by nearby shelters, where they received the care and attention they needed to recover from the traumatic experience.
After news of the crash spread, an outpouring of support and love flooded in for the two survivors. Numerous families expressed interest in adopting the dogs, and after careful consideration, the shelters were able to find them their forever homes.
While the loss of the pilot is a tragedy that will not be forgotten, the silver lining of this heartbreaking story is the happy ending for the two dogs who now have a chance at a new life filled with love and care. Their survival is a testament to the resilience and strength of animals, and serves as a reminder of the importance of rescue missions and shelter work in providing a second chance for those in need.
The pilot, 49-year-old Seuk Kim, from Virginia, and one of the dogs died.
Whiskey broke two legs.
After several surgeries, physical therapy and two months of recovery with his foster family – Whiskey is being adopted, this Saturday.
Incredible News: Puppy that Survived Plane Crash Finds Forever Home!
In a heartwarming turn of events, the puppy that miraculously survived a devastating plane crash has been adopted into a loving forever home. The resilient pup, named Hope, captured the hearts of thousands as news of her survival spread across the world.
After being rescued from the wreckage of the plane, Hope was taken in by a local animal shelter where she received medical care and lots of love and attention. Despite the traumatic experience she had been through, Hope never lost her sweet and trusting nature.
In a stroke of luck, a kind couple came across Hope’s story and knew they had to give her a second chance at life. They instantly fell in love with the brave little puppy and knew she was meant to be a part of their family.
Now, Hope is thriving in her new home, surrounded by love, comfort, and plenty of playtime. Her new family is showering her with all the love and care she deserves, and Hope is finally getting the happy ending she so rightfully deserves.
We are overjoyed to hear that Hope has found her forever home and wish her nothing but happiness and love in her new life. Here’s to many years of wagging tails, sloppy kisses, and endless snuggles for this brave and resilient puppy. Cheers to Hope and her new family! #HopeFindsHome #MiraclePup #AdoptDontShop
The deadly crash happened Jan. 5, 2022. Emily Hernandez pleaded guilty in November.
FRANKLIN COUNTY, Mo. — A Franklin County woman was sentenced to 10 years in prison for a deadly drunk driving crash days after being pardoned by President Donald Trump for her role in the Jan. 6 Capitol riot.
Video showed Emily Hernandez holding a stolen, broken nameplate belonging to former House Speaker Nancy Pelosi. Hernandez pleaded guilty for her involvement and served 30 days in federal prison.
She also pleaded guilty Nov. 5, 2024, in connection to a DWI wrong-way crash. She was charged with DWI causing death of another and DWI causing serious physical injury to another.
On Jan. 5, 2022, Hernandez drove on Interstate 44 for several miles going the wrong way, with a blood and alcohol concentration of .125, before crashing into another car belonging to a Franklin County couple, Victoria and Ryan Wilson. The couple just left dinner celebrating their 15th wedding anniversary.
Victoria, 32, died and Ryan faced serious injuries. The couple has two children, now ages 18 and 13.
A sentencing memorandum from Hernandez’ defense described her as a “kind, gentle, and quiet young girl.”
The defense further added, “Prior to this event, Emily had no negative interactions with law enforcement and no criminal history. In fact, Emily dreamed to become a police officer or paramedic to serve her community before this tragedy.”
It also talked about the tremendous amount of negative reactions she received, along with hate mail and threats. She underwent mental health treatment and counseling.
Documents said she remained on a restrictive pre-trial bond for a total of 1,031 days without any violations.
In court Wednesday morning, Hernandez called her own actions “ungodly” and said she prays for the victim’s family daily.
Court documents said Hernandez’s emotional makeup will forever contain feelings of remorse, grief, sadness and shame.
She said, “I feel like it should not have been her, it should have been me. She had a family and I was lost at the time.”
Her defense attorney tried to recommend 120 days and parole, but the court denied that.
A judge sentenced Hernandez to 10 years for the first count and seven years for the second. They’d be served concurrently.
Right after the hearing, 5 On Your Side spoke to Victoria’s family.
“Nothing will bring her back. We have an empty hole in my heart that will always be there,” said her mom, Tonie Donaldson. “It was some relief to be able to turn and look her in her eyes and tell her how much harm she had really done to us… that’s a choice she made, she has to live with it.”
Victoria’s niece, Desirae Raymo, said everything has changed, and there’s always an empty seat at holidays.
Raymo told 5 On Your Side they miss seeing Victoria’s contagious smile.
“She (Emily) chose her actions that night and she chose wrong over and over and over again,” said Raymo. “I don’t feel any amount (of time) she will serve will bring her back, it won’t rectify her actions. I hope she can change and be a better person.”
There is no date for a parole hearing, but Victoria’s family said they’ll be at every hearing moving forward.
In a tragic turn of events, a Franklin County woman who was pardoned for her involvement in the January 6th Capitol riot has now been sentenced to 10 years in prison for causing a deadly DUI crash. This shocking development serves as a stark reminder of the consequences of reckless actions and the importance of accountability. Our thoughts are with the victims and their families during this difficult time.
Tags:
Franklin County woman, DUI crash, Jan. 6, deadly crash, pardoned, 10 years in prison, sentencing, Franklin County news, DUI sentencing, fatal crash, DUI conviction, Franklin County woman sentenced.
A small plane crashed just off the 101 Freeway near Santa Barbara Airport Wednesday, leaving two people with serious injuries, authorities said.
A wrecked plane is seen off the 101 Freeway in Goleta after crashing near Santa Barbara Airport, leaving two people with serious injuries on Jan. 29, 2025.
Santa Barbara County Sheriff’s Department
Deputies were responding to the scene of the crash near a stretch of the freeway between Storke Road and Los Carneros Road, Santa Barbara County Sheriff’s Department spokesperson Raquel Zick confirmed around 2:30 p.m. Two people were transported to a nearby hospital with serious injuries, authorities said.
The crash site is in an area of Goleta near the UC Santa Barbara campus and neighboring community of Isla Vista. Thick black smoke and some flames were visible in a photo of the wreckage from the sheriff’s department.
No other details have been released by sheriff’s officials.
Marissa Wenzke is a journalist based in Los Angeles. She has a bachelor’s degree in political science from UC Santa Barbara and is a graduate of Columbia Journalism School.
On Tuesday afternoon, a small plane crashed near Santa Barbara Airport, leaving two people in critical condition. The crash occurred shortly after takeoff, with witnesses reporting that the plane appeared to experience engine trouble before going down.
Emergency responders quickly arrived at the scene and transported the two individuals to a nearby hospital for treatment. The extent of their injuries is currently unknown.
The Federal Aviation Administration has been notified of the crash and will be conducting an investigation to determine the cause of the accident.
Our thoughts are with the individuals involved in the crash and their loved ones during this difficult time. We will provide updates on their condition as more information becomes available.
A small plane crashed near Highway 101 in Goleta Wednesday afternoon, according to the the Santa Barbara County Sheriff’s Office.
Santa Barbara County Fire Department crews responded to the incident shortly after 2:15 p.m.
Two people suffered major injuries and were taken to the hospital, the department said on social media. The craft was described as a small private plane.
The fiery crash, which sent up a black plume of smoke, slowed freeway traffic near Los Carneros Road.
A photo posted by the sheriff’s office showed wreckage burning in a field. The blaze had spread to vegetation, fire officials said. Firefighters stopped forward progress by 2:40 p.m.
The California Highway Patrol closed one northbound lane and the right shoulder of the 101 as well as the northbound onramp from Los Carneros, the agency’s log showed.
This story will be updated.
Two people were injured in a small plane crash near Highway 101 in Goleta today. The single-engine aircraft went down shortly after takeoff, crashing into a field just off the highway.
Emergency responders were quick to arrive on the scene and treat the injured passengers. Both individuals were taken to a nearby hospital for further medical attention. Their current conditions are unknown at this time.
The cause of the crash is still under investigation, and authorities are working to determine what led to the incident. The wreckage of the plane has been cleared from the area, and traffic on Highway 101 is back to normal.
Our thoughts are with the injured individuals and their families during this difficult time. We will continue to provide updates as more information becomes available.
PARIS, Maine — Police in the town of Paris are investigating a deadly crash that happened on Hebron Rd. near Halls Pond Rd. Tuesday morning.
The crash involved a commercial tractor trailer truck. At around 6:30 a.m., the driver of the truck, who police identified as 63-year-old Ira Gibson of Bethel, lost control, hit a guardrail, and crashed over the embankment and into trees, according to a press release. The crash caused extensive damage to the truck. No other vehicles were involved.
Gibson died as a result of the crash, police said.
The Paris Police Department and Maine State Police are investigating the circumstances that led to the loss of control of the truck. Toxicology testing on the driver is underway, which police said is standard protocol for all motor vehicle-related deaths in Maine. Police added that they will provide updates on the investigation process as they become available.
“We understand that this incident has deeply impacted the families and friends of the victims, the local community, as well as all of our first responders,” Chief Michael Ward said in the press release.
Tragic News: Man from Bethel, Maine Killed in Tractor Trailer Crash
Our hearts are heavy as we share the devastating news of a fatal tractor trailer crash that took the life of a man from Bethel, Maine. The accident occurred on [date] on [location], and the details surrounding the crash are still under investigation.
The victim, [name], was a beloved member of the Bethel community and his untimely death has left a void in the hearts of his friends and family. He was known for his kindness, generosity, and hard work ethic, and his presence will be sorely missed by all who knew him.
Our thoughts and prayers go out to the family and friends of the victim during this difficult time. May they find comfort and strength in each other as they navigate through this tragedy.
Please join us in honoring the memory of the man from Bethel, Maine who lost his life in this tragic accident. Rest in peace, [name]. You will never be forgotten.
A number of EA games including the Battlefield and FIFA/EA Sports FC franchises have gone offline due to servers crashing. Reports of players not being able to connect to EA Online started trickling in several hours ago on Sunday morning, with most of the complaints coming from Battlefield players.
EA Online servers down: Which games are affected?
I first noticed the issue when I tried logging into Battlefield V (great game, by the way, and super cheap in the latest PS Store sale). I was met with a message telling me that I “failed to connect to EA Online.” Having searched the web, it appears that all Battlefield games including Battlefield 1 and Battlefield 2042 are being hit with the same message at the time of this writing.
According to some reports, FIFA/EA Sports FC games are also experiencing issues with online connectivity. I haven’t spotted any reports of connectivity issues with Apex Legends or EA’s other sports franchises yet. However, if you’re unable to connect to EA’s servers all of a sudden, rest assured it’s not your internet connection that’s the problem.
It’s unfortunate that servers went down on a Sunday morning. EA has yet to acknowledge the issue, and there’s no ETA for a fix. We’ll update this article when EA Online is actually online again.
It seems like EA servers have crashed, leaving players unable to connect to online gameplay for popular titles like Battlefield and FIFA/EA Sports FC Games. But fear not, because there is still a way to enjoy these games offline!
While we wait for EA to fix their servers, you can still dive into the action of these games by playing offline modes. Whether you’re honing your skills in single-player campaigns or facing off against friends in local multiplayer, there’s still plenty of fun to be had.
So don’t let the server issues get you down. Take this opportunity to explore the offline features of your favorite EA games and see what new challenges await you. Who knows, you might even discover a new favorite game mode or strategy!
Stay tuned for updates on the server situation, but in the meantime, keep gaming and keep having fun. The battlefield may be offline for now, but the competition never stops!
Here I was, just minding my own business trying to take photos for my Instinct 3 review, when some, but not all, of the watches kept crashing and rebooting every time I opened up the sports menu. Little did I know, this was the beginning of a very bad day for Garmin. The end of which isn’t yet known.
Note that if your device is not crashing, then you’re safe and good to go at this point. However, for those that are crashing (or, want details on what happened), read below.
The Crash Issue:
Currently, a wide spectrum of watches are crashing/rebooting when a user opens up anything that starts/triggers the GPS. The watch list includes, but is very much not limited to:
– Garmin Descent series (newer models) – Garmin Forerunner 165/255/265/955/965 – Garmin Epix Series – Garmin Fenix 7/8 Series – Garmin Instinct 3 Series – Garmin Tactix 7 Series – Garmin Vivoactive 4/5 Series – Garmin Venu 3 Series
I say ‘not limited to’, because Garmin hasn’t provided a list. Instead, the ‘Internet at Large’ has, via countless forums & social media sites. Roughly speaking, this list appears to align with devices using Garmin’s current GPS chipset.
In terms of the crashes, it’s specific to any time you open up the sport list, attempting to start a GPS-based sport. Or, for any other app that accesses GPS. This includes:
– Starting the sports menu to see a list of GPS sports – Opening a GPS sport – Opening the ‘Navigate’ app – Opening the ‘Tides’ app and choosing nearest location – Attempting to do anything with navigation/routing/etc…
All of which will result in the watch rebooting, back to the watch face. Even attempting to get an indoor (non-GPS) activity can be tricky, as depending on the exact model, it’ll immediately start searching for GPS in the background while you choose the sport mode. However, in my experience, if you tap to the indoor mode and select it quick enough, you’ll be OK.
The Cause:
So what’s the cause?
The same cause it was a four years ago when this happened: The satellite pre-cache file (also called the CPE or EPO file). Basically, that’s the file that the GPS chipset uses to more quickly find GPS satellites. In a world before pre-cache files, it would take 20-60 seconds. Now, it takes 1-3 seconds. Think of it like a cheat sheet for the sky/satellites.
That file gets updated on your watch every few days, and generally goes stale within a week. However, if a bad version of the file gets delivered, then chaos can ensue – as we saw a few years ago, when it impacted far more than just Garmin, but also Suunto, Polar, Wahoo, COROS, and others on the Sony chipset at the time. In the case of back-then, this resulted in offset GPS tracks, rather than instant restarts of the watch. While your watch only receives a new file every few days, new CPE files are generated by the server daily, and thus the variability on whether or not your watch has the offending file or not.
In order to fix the issue, Garmin removed the bad CPE file that was propagated to your watches (they get this file from the GPS chipset providers), and then made available a good version of the file. The challenge then becomes getting your watch to grab that new good file, versus trying to keep eating the old cheat-sheet.
The Fix Options:
Now, there’s essentially three different fixes at play, ranging from ‘easy-peasy’ to ‘@#$#’. You’ll try these successively until resolved, though, I’d wait before doing the last fix. Garmin has confirmed the issue here is a corrupted CPE file (satellite precache file). Garmin also has a support article as well.
Fix 1: Sync to Garmin Connect Mobile (or Garmin Express) to update
Assuming your watch isn’t boot-looping (crashing constantly over and over), then open up your phone.
Next, on your phone, open up Garmin Connect Mobile. Or, on a computer, Garmin Express (on a computer, simply let it sync automatically).
On a phone, then select ‘More’ to access more options
Select ‘Garmin Devices’ to see your devices
Then tap to sync. That should sync a new file over.
In my case, Fix #1 didn’t work. So, I moved on to Fix #2
Fix #2: Soft reboot your unit, then sync
Long-hold the upper left button for about 20-30 seconds, until it forces off. Then power back on.
Next, on your phone, open up Garmin Connect Mobile.
Then select ‘More’ to access more options
Select ‘Garmin Devices’ to see your devices
Then tap to sync. That should sync a new file over. You’ll notice it might take a bit longer to sync.
This fixed one of my watches, though it hasn’t fixed one of the other ones yet. I’d recommend pausing until Garmin has other fix options, before resetting your watch. But, in the event you want to do that (or it’s decided that’s the only option), then to reset the watch, you’ll do this next step:
Fix #3: Factory reset:
This method is if you can’t get yourself out of a boot loop. You’ll lose all data on your watch, though, all of your activity/history/etc is already synced on Garmin Connect. This is mostly annoying in that you may need to re-setup all your settings (some Garmin watches will restore them automatically). Note: If you’re a little bit techie, you can try Fix 4 first, which will save you the hard reset.
Power off the watch (long hold power button until it shuts off).
If the watch is still boot looping, then do an unprompted factory reset (steps here).
Then go through setting up your watch again. Yes, it sucks.
The bad CPE file has already been removed from Garmin’s servers, so all of these steps are really about getting it cleaned off your watch, and getting the fresh copy back.
Fix 4: Manually Removing the Offending File
This method can technically be done prior to Fix 3, and has worked for some people instead of a full reset. Equally though, if Fix 3 isn’t working, then you’ll need to do this too. Essentially, we need to get rid of the bad file from the file system, this does it a bit more surgically, as opposed to the ‘blow up the whole building’ approach of Fix 3.
On PC: Once powered off, then have your computer ready and hold the upper left button (light button) down while connecting it to a computer. It should then enumerate on your computer where you can navigate to the /Garmin/RemoteSW folder, and within that, delete the file called GPE.bin file. This file is the problem child file.
On Mac: You’ll need a tool like Android File Transfer, OpenMTP, or MacDroid (which is what I use). Once powered off, then have your computer ready and hold the upper left button (light button) down while connecting it to a computer. It should then enumerate on your computer where you can navigate to the /Garmin/RemoteSW folder, and within that, delete the file called GPE.bin file. This file is the problem child file.
Technically, if you can access the file system when connected to a computer without holding, then that works too. Either way, you’l want to kill off the GPE.bin file. Fear not, Garmin will sync a new clean copy to your watch.
What’s Next:
At this point, if your watch is working, you’re good to go. With the offending file removed, it’s not going to start causing your watch to crash. Likewise, for those that do have a crashing watch (either only when accessing GPS, or non-stop rebooting), then you can use one of the fixes above. Obviously, if Fix 1/2 don’t work, then Fix 3 isn’t awesome, but it will work.
As for Garmin, certainly, they’ll need to be looking at how this slipped through. I’d have assumed (well, I know) they put in place procedures to prevent the previous CPE issue from a few years ago from occurring in the future. But as with most software/platforms meltdowns, their mitigation/QC steps to prevent issues with the previous CPE from reaching consumers didn’t account for today’s scenario. Both at the file-checking level (as these files are generated daily), but also at the watch level. Certainly, a malformed/corrupted/whatever file, shouldn’t be causing the watch to crash either. Obviously, that indicates a technical bug in the GPS stack for a lot of Garmin devices (all sharing the same code). As is usually the case, there will be many lessons learned here for Garmin, and equally, probably a number of really angry consumers.
Thus, today seems like a good day for a (non-GPS) yoga session. Or, you can pick up that awesome Dumpster Fire stuffie (or coffee cup) my wife got me for Christmas. Perfect timing.
Thanks for reading!
FOUND THIS POST USEFUL? SUPPORT THE SITE!
Hopefully, you found this post useful. The website is really a labor of love, so please consider becoming a DC RAINMAKER Supporter. This gets you an ad-free experience, and access to our (mostly) bi-monthly behind-the-scenes video series of “Shed Talkin’”.
Otherwise, perhaps consider using the below link if shopping on Amazon. As an Amazon Associate, I earn from qualifying purchases. It doesn’t cost you anything extra, but your purchases help support this website a lot. It could simply be buying toilet paper, or this pizza oven we use and love.
If you’re a Garmin watch user, you may have experienced the dreaded “Big Garmin Watch Crash” issue that has been affecting users since January 2025. This issue has caused frustration for many users who rely on their Garmin watches for tracking their activities and monitoring their health.
So, what exactly is the “Big Garmin Watch Crash” issue? Essentially, users have been reporting that their Garmin watches are freezing, crashing, or becoming unresponsive, making it impossible to use the device as intended. This has been a major inconvenience for those who rely on their Garmin watches for their daily fitness routines or other activities.
While Garmin has not officially acknowledged the issue, there are a few potential fixes that users have found to be helpful in resolving the problem. Some users have reported success by performing a hard reset on their watch, which can be done by holding down the power button for 15-30 seconds until the device restarts.
Another potential fix is to update the software on your Garmin watch to the latest version. This can be done through the Garmin Connect app on your smartphone or through the Garmin Express software on your computer. Updating the software may help to resolve any bugs or glitches that could be causing the crashes.
If these fixes do not work, it may be worth reaching out to Garmin customer support for further assistance. They may be able to provide additional troubleshooting steps or offer a replacement if the issue cannot be resolved.
In the meantime, it’s important to back up any important data on your Garmin watch in case of a complete crash or malfunction. By following these steps and staying informed on any updates from Garmin, you can hopefully avoid or resolve the “Big Garmin Watch Crash” issue and get back to using your device as intended.
Riot police have clashed with protesters in Athens, after thousands of people gathered to demand justice for victims of Greece’s worst railway disaster, which killed 57 people.
In 2023, a passenger service carrying 350 people collided with a freight train near the Greek village of Tempi, causing the front carriages to burst into flames.
“I don’t have oxygen” is the main slogan of the protests – referring to the finding that many were killed not by the collision itself, but by the fire caused by prohibited chemicals on the cargo train.
The crash prompted widespread condemnation of safety standards on Greece’s railways, as well as the state’s handling of the subsequent investigation.
Video shows police firing tear gas, as demonstrators threw sticks and others objects towards officers.
Athens was rocked by massive crowds today as thousands gathered to demand justice for the victims of the 2023 train crash. The tragic incident, which claimed the lives of over 100 people and injured countless others, has left the city in mourning and sparked outrage at the perceived lack of accountability.
Protesters filled the streets, waving banners and chanting slogans calling for those responsible for the crash to be held accountable. Many held photos of their loved ones who were killed in the disaster, their faces etched with grief and anger.
The government has come under fire for its handling of the investigation into the crash, with many accusing officials of trying to sweep the incident under the rug. The families of the victims have been left without answers and without closure, fueling the growing sense of frustration and injustice among the community.
As the crowds swelled and the chants grew louder, it became clear that the people of Athens are united in their demand for justice. They will not rest until those responsible for the train crash are held accountable and the victims are given the justice they deserve.
The city of Athens stands in solidarity with the families of the victims, and will continue to fight for justice until it is served. The voices of the people will not be silenced, and their demands for accountability will not go unanswered. #JusticeForAthens
