In late August 2026, some Honda and Acura vehicles began showing a navigation clock stuck at 0:00. It is probably not your antenna, and it is not worth paying anyone to fix it yet.
Last updated October 5, 2026. I added owner reports and an image of what appears to be an Acura ServiceNews article, both from Reddit, and corrected the battery and fuse reset advice and my claim that nobody had written this up. This is a developing situation, and I will post updates here as they come in.
This is well outside our usual subject matter. A note at the bottom explains why it is here anyway.
AI tools were used in the research, drafting, and editing of this article. Every claim traces to a document listed under Sources, rests on the author’s own readings of one vehicle, or is marked as inference.
The short version
If your Honda or Acura has the factory navigation system, and the clock on the navigation screen now reads 0:00 (or 12:00 AM, if your display is set to twelve-hour time) and will not change, while the smaller clock on the audio display keeps perfect time:
- If the diagnostic screen described below shows your correct position and time of day next to a date in early 2007, you have the problem this article describes. The same menu runs hardware tests on the antenna, receiver, and hard drive. If those pass too, as they did on our van, nothing in your vehicle is broken. Check before you conclude it: a frozen clock has other possible causes, and this article covers only that one signature.
- In that case, the GPS chip inside the navigation unit has lost track of what year it is: it believes the date is in January 2007.
- Do not let anyone sell you a new GPS antenna, a new navigation hard drive, or a replacement head unit for this. The first two are not the problem, and a head unit of the same design carries the same chip.
- Do not buy a map update disc hoping it will fix this. No update we can confirm addresses it, and in 2017, the update available at the time was what kept some clocks from coming back on their own.
- There is no known fix for the date right now. An image posted on Reddit of what appears to be an Acura ServiceNews article from September 2026 says American Honda is investigating a solution [14]. We have not obtained an official copy of it or of any Honda bulletin. Furuno’s own documentation lists the chips whose rollover date can be changed by command, and the GN-84 family, which these vehicles appear to use, is not among them [1].
The rest explains how we worked that out, what happened the last two times this occurred, and what might happen next.
What a navigation clock stuck at 0:00 looks like
The vehicle in question is our own 2012 Honda Odyssey with the factory hard-drive navigation system. The upper navigation display shows 0:00 and stays there through every drive and every restart. The blue audio and climate display below it shows the correct local time, all day, every day.
Everything else works. The map is right. The van drives normally. Just the one clock, frozen.
That combination usually points to a dead GPS antenna. It is not.
Two things this is probably not. If your clock is off by exactly one hour, that is usually a daylight saving or time zone setting, and a separate issue. On the Acuras in the ServiceNews image described below, it can be part of this problem: a 2012 MDX owner reports a clock an hour off that the daylight saving setting will not fix [13]. Check the GPS Information date before you decide. If your map puts you in the wrong place, or the system cannot find satellites at all, you may genuinely have an antenna or receiver fault, and this article does not apply to you.
What the car told us
Rather than guess, we went into the factory navigation diagnostic menus and read the GPS receiver directly. On September 3, 2026, it reported:
- Latitude and longitude: correct, to the arcsecond.
- Elevation: correct.
- Satellites: 8 in use, with a 9th still being acquired.
- Time: 23:42:55. That is UTC, which the receiver reports directly rather than converting. Subtract five hours for Central Daylight Time, and it is exactly right for 6:42 in the evening. Expect the same on your own screen: the time there will look wrong by your clock and be correct by Greenwich.
- Date: January 18, 2007.
The system’s own hardware tests were all green. Antenna: OK. Receiver: OK. Hard drive: OK. Vehicle network: no errors.
So the receiver can see the satellites, knows exactly where it is, and knows what time it is. It just does not know what year it is.
The number
From January 18, 2007 to September 3, 2026 is 7,168 days.
Divide by seven, and you get 1,024. Exactly. Not approximately.
That number is the heart of it, and here is why.
What a GPS receiver has to guess
GPS satellites do not broadcast a calendar date. They broadcast a week number and a time within that week, and your receiver does the arithmetic to turn that into a date.
The catch is that the original GPS design only allotted ten binary digits to the week number. Ten digits can count from 0 to 1,023, and then it starts over at zero [1]. That happens every 1,024 weeks, which is 7,168 days, or a bit over 19 years and 7 months.
So when the satellites say “week 385,” the receiver has to decide on its own whether that means 2007 or 2026. It is the same problem as a two-digit year on an old form. The information is not there, so the device has to make an assumption.
Different manufacturers handle that assumption differently. Furuno gives each family of chips a fixed window exactly 1,024 weeks wide [1]. Inside its window, the chip gets the date right, including through the industry-wide rollovers. Once the calendar walks past the end of that window, the chip can start assigning the incoming week number to the previous era instead. When that shows up varies. In 2022, Honda said owners met it at the next power-on [4]. Acura said its owners noticed it only after a battery disconnect or the next daylight saving change [9].
Furuno publishes the dates. For the chip family that appears to be in these vehicles, the window closed on August 23, 2026, and after that the chip reports the date as January 7, 2007 [1].
The window closed on August 23, and we read the screen on September 3, eleven days later. January 7, 2007 plus the same eleven days is January 18, 2007, which is precisely what the Odyssey showed.
That date proves one thing and not another. Every Furuno family whose window has closed reports the same wrong date on any given day, because each one is exactly 1,024 weeks behind. So January 18, 2007 tells you the frozen clock comes from the rollover, not a broken part. It does not tell you which family the chip belongs to.
What points to the GN-84 family is elimination. A chip from any family whose window closed earlier would have failed when it closed: January or September 2022, March 2024, or February 2025 [1]. This van’s clock kept correct time through every one of those dates. The only family in Furuno’s table whose window has closed since is GN-84.
We should be plain about the one soft spot. We did not note the day the clock stopped, only that we noticed it a couple of weeks before reading the screen on September 3. That could fall a few days either side of August 23. Other owners were more exact: one wrote on August 24 that the navigation clock had shown 0:00 “since yesterday” [15], and the Acura ServiceNews image described below gives August 23 as the start [14]. The argument does not rest on the exact day. It rests on the clock surviving every earlier window, and it did.
There is one piece of paper underneath the recollection. The unit’s own error log still holds entries stamped December 3, 2025. If those timestamps come from the same GPS-fed date, and we have not established that they do, the unit was recording a correct year that December, which is after every earlier window in the table had closed.
This is not “the” GPS rollover
You may have read about the GPS week rollover as a global event. Those happened in August 1999 and April 2019, and the next one is in November 2038 [1]. August 2026 is not one of them, and the satellites are working perfectly.
This is a private expiration date built into one manufacturer’s chips. It is why your phone, your handheld GPS, and your neighbor’s newer car are all completely unaffected while your minivan thinks it is 2007.
Why 0:00 and not just the wrong time
This is the part that confused us longest. The chip is handing up a perfectly good time of day. So why does the display show zero rather than the correct time with a wrong date next to it?
Honda’s bulletins from the last round describe what happens without saying why: the date resets to a fixed default, and the time to a fixed default hour, on every restart [4]. Honda never gives the reason. Our reading is that the navigation software checks the date it receives, decides a date from twenty years ago cannot be real, and throws out the whole package rather than salvaging the time from it. It then falls back on built-in placeholder values. On the vehicles affected in 2022, that placeholder was January 1, 2002, and a time of 1:00 Pacific. Honda listed a different default hour for each zone: 2:00 Mountain, 3:00 Central, 4:00 Eastern [4]. On this Odyssey, the calendar app sits on January 2009, and the clock reads 0:00. Both look very much like this generation’s placeholders [10].
The smaller audio clock on this van kept correct time throughout, which suggests it keeps its own time rather than taking it from the GPS chip.
What else stops working
The clock is the obvious symptom, but it is not the only one. When Honda documented the 2022 round, it listed three other functions that a wrong internal date affects [3], and Acura’s bulletin adds a fourth [9]:
- Stored navigation history, including saved locations and previous destinations, stops sorting correctly. New entries land at the bottom of the list instead of the top.
- Detour and route guidance may not work properly.
- Live traffic information may fail to display.
- On Acura models, AcuraLink cannot connect, and server-based routing fails [9].
Honda’s list does not include basic point-to-point navigation, and on this van it still worked. If you have noticed your saved destinations in a strange order, this is why. The Acura image described below lists the same functions and adds the clock adjustment setting, automatic daylight saving, the calendar, and reminders [14].
Which vehicles
This is the question everyone wants answered, and the honest answer is that we have confirmed exactly one vehicle in detail. But there is a strong pattern to work from.
When the previous generation of these chips expired on January 2, 2022, Honda published bulletins covering [3][4]:
- 2006 to 2012 Accord, 2010 to 2012 Accord Crosstour, 2006 to 2007 Accord Hybrid
- 2005 to 2010 Odyssey
- 2006 to 2011 Pilot
- 2006 to 2014 Ridgeline
- 2006 to 2011 Civic and Civic Hybrid, 2007 to 2011 CR-V, 2011 to 2012 CR-Z, 2009 to 2010 Element, 2009 to 2011 Fit, 2010 to 2011 Insight
- On the Acura side: 2005 to 2012 RL, 2007 to 2008 TL, 2005 to 2009 MDX, 2007 to 2012 RDX, 2006 to 2010 TSX [9]
All with factory navigation only. Honda split its own bulletins by map disc: [3] covers the Accord, Odyssey, Pilot, Ridgeline and Crosstour; [4] the Civic, CR-V, CR-Z, Element, Fit and Insight. The Acura list comes from Acura’s own bulletins [9].
Notice where those lists stop. The 2022 event covered the Odyssey through 2010 and the Pilot through 2011. Those vehicles failed on the day the older chip family’s window closed. Our working assumption is that the model years right after each cutoff moved to a newer chip. It is an assumption, and some cutoffs have plainer explanations. The Accord Hybrid, for one, stops at 2007 because Honda stopped making it. Nor does “the next chip” name any particular one: Furuno’s table has three families that expired between the 2022 event and this one [1]. A teardown of a 2012 Pilot navigation unit identified its GPS module as a Furuno GN-8407B [2]. Furuno’s rollover table does not list that exact part number, so placing it on the GN-84 row is an inference from the part number rather than something Furuno documents. The elimination above points to the same row.
As a rough guide, check the vehicles that came right after the 2022 lists ended, such as the 2011 and newer Odyssey and the 2012 and newer Pilot. For every other line, check the screen rather than guessing from the model year. Nobody has established how far forward it extends. At some point, Honda moved to newer hardware that is not affected.
Other people’s evidence now fills in part of that guide. On September 2, a Reddit user whose flair reads Acura Master Technician posted an image of what appears to be an Acura ServiceNews article dated September 2026 and titled “Incorrect Date and Time on Navigation Display” [14]. It applies to the 2010 to 2013 MDX and ZDX and the 2012 to 2014 TSX, all with navigation. It says that on August 23, 2026, owners may see a wrong date and time that “cannot be manually adjusted,” blames the GPS receiver’s internal memory “reaching the end of its service life,” and says American Honda “is currently investigating a solution.” It also says every clock in the vehicle will be wrong. Our audio clock kept good time, and so did a 2013 Pilot’s [16], so Hondas and Acuras may differ. The image shows no article number, and we have not seen an original, so we cannot authenticate it. August 23 is the date Furuno’s table gives, and the MDX years start right where the 2022 list ended. The 2011 TSX is on neither list, so check the screen if you have one.
Owners report the same 0:00 on Hondas. Posts on r/HondaOdyssey and r/hondapilot describe it on a 2012 and a 2013 Odyssey and on a 2012 and a 2013 Pilot [15][16][17][18]. One commenter quotes a reply from Honda that names the 2011 to 2013 Odyssey and the 2012 to 2014 Pilot [15]. We could not verify that reply, and none of these is a Honda bulletin, so the advice stands: check the screen, not the model year.
If your vehicle was on the 2022 list and is misbehaving now, that is a different and older issue.
This is the third time
Honda has been here twice before, and the history tells you two things: an update can change the outcome, and a clock can come back on its own once the wrong date reaches something the software accepts.
2017. Honda and Acura issued bulletins titled, word for word, “Navigation Screen Clock Reads 00:00,” covering the 2001-03 CL, 2001-02 MDX, 2000-03 RL and 2000-03 TL [5][6], and the 2000-04 Odyssey and 2003-05 Pilot [7]. Identical symptom. Here is the part every owner should read twice, in Honda’s own words:
For models that didn’t have the navigation maps updated with software Version 2.1x to 2.Ax, this issue self-corrected on September 17, 2017, and the clock reads normally. For models that did have the navigation maps updated with that software version, this issue remains and the clock reads 00:00.
The problem cleared itself for cars that had not received the update, and stayed stuck at 00:00 for cars that had. The newer software made it worse. That wording appears verbatim in a September 2017 Tech Line article [5] and again in two January 2018 ServiceNews articles [6][7].
One correction to how that is usually retold: “stuck” did not mean stuck forever. Honda said in the same bulletins that it was “currently working on a software patch to fix this,” and its owner-facing page now says an update disc can correct the condition [8]. The lesson is narrower than “never update.” It is that the update available at the time converted a problem that would have expired on its own into one that needed a fix.
2022. The previous chip generation expired on January 2, 2022, and vehicles began reporting May 19, 2002 [1][4]. This one made the news. Honda’s bulletins described the problem and said plainly there was no way to correct the date [4]. Then Honda waited it out: the clocks began working again on August 17, 2022 [3][4]. The calendar and the automatic daylight saving handling stayed broken, and Honda’s eventual answer for those was to point customers at a paid map update disc [3][4].
Two notes on those dates, because they look wrong next to Honda’s own account. Honda put the rollover at midnight local time on January 1, then answered its own question: “When will customers first notice the incorrect time and date? Starting on January 2, 2022 at each vehicle power on” [4]. The chip turns over at midnight; the driver meets it the next time the van starts. And May 19, 2002 is the date the chip reported. Honda’s bulletin says so outright: “when the system internal calendar is reset to May 19, 2002” [4]. January 1, 2002 is the placeholder the navigation software substituted once it rejected that date. Two numbers, two layers: the same split described above.
2026. Here we are again, with the next chip generation.
Will it fix itself?
Maybe, and there is an interesting clue.
Nobody, Honda included, ever explained why August 17, 2022 was the magic date. Run the arithmetic, and it becomes clear: on that day, the wrong date the chip was reporting had finally advanced to exactly January 1, 2003. The navigation software appears to have started accepting the time again once the bad date crossed into a new year.
There are two ways to read that, and they give answers two years apart. We’ll show both, because the difference matters and we can’t settle it.
The first reading says what matters is the chip’s wrong date crossing into any new year. In 2022 the chip reported May 19, 2002. It reached January 1, 2003 after 227 days, which landed on August 17, 2022. Apply the same rule now. The chip reports January 7, 2007, and reaches January 1, 2008 after 359 days. That lands on August 17, 2027.
The second reading says what matters is the chip’s date catching up to the placeholder year the software falls back on, plus one. In 2022, the placeholder was January 1, 2002, and recovery came when the chip reached 2003, which is the placeholder year plus one. This Odyssey’s calendar sits in January 2009, and the receiver firmware in this van, version 7.110-090703, appears to carry a 2009 build date, which is the same year as that placeholder. Placeholder plus one is 2010, and the chip’s wrong date reaches January 1, 2010 on August 17, 2029.
Both readings fit the single 2022 data point exactly, because in 2022 the two rules happened to give the same answer. They come apart now only because this generation’s placeholder year (2009) is further from its reported year (2007) than the 2022 generation’s was. We do not know which rule the software actually implements, and we are not going to pretend otherwise by naming one date.
Both readings also assume our explanation of the 0:00 is right: that the software rejects an implausible date and accepts one again once it crosses some threshold. This is a hypothesis built on one previous event, not something anyone has confirmed. The 2017 event does not help arbitrate: it self-corrected on a date Honda documented but never explained, and the arithmetic above does not obviously generate it. Do not make plans around either date.
Some owners say theirs already has. Two TSX owners on Reddit say their clocks came back on their own, one in mid-September and one on September 23 [19][20]. One says the date still looks wrong, and the other that the time still cannot be adjusted. Neither names a model year or the display, and neither says they checked the GPS Information screen. If the navigation clock is what came back, a clock can recover without the wrong date crossing into a new year, which neither reading above predicts. Then the two dates describe this Odyssey and not every vehicle. The Honda owner reports in [15] to [18] describe no recovery.
What not to do
This is the part worth reading twice, because almost every way of losing money on this involves fixing something that is not broken.
Do not replace the GPS antenna, the navigation hard drive, or the head unit. On a unit showing this signature, none of them is the problem. A shop that has not seen this before will work down the usual list and may well sell you one anyway. A replacement head unit is an expensive answer to a problem it does not fix.
Do not buy a used replacement unit from the same era. This is the expensive mistake nobody sees coming. A used head unit pulled from another van of the same model years will almost certainly carry the same GPS chip with the same expiry date, so it will arrive already broken in exactly the same way. One from a year or two earlier may carry the older chip, whose calendar broke in 2022. A remanufactured or superseded service part might differ. If you are offered one, get the part number and check it before you pay.
Do not buy a map or software update disc expecting it to fix the clock. In 2017, the update available at the time kept the failure from clearing, while unpatched cars recovered on their own. In 2022 an update did eventually correct the calendar, but only after the clocks had already come back by themselves [3][4]. We have found no update that addresses this, and we have not examined a vehicle with one installed. One Reddit commenter says Honda released a dealer update in September for about $175 [15]. They give no model year or bulletin number, and we found no one who confirms it. A Pilot owner who installed a software update from the diagnostic screen says the clock still would not adjust [16]. Ask the dealer for the bulletin number before you pay for anything.
Do not spend an evening in the settings menu. Turning off automatic time, turning off automatic daylight saving, and setting the clock by hand were all tried extensively in 2022, and none of it held. Honda’s own bulletin said plainly that the date could not be corrected manually [4]. The value reverts on the next power cycle.
Do not reset the system, pull fuses, or ask for a cold start to get the date back. Once its window has closed, the chip reports the earlier era every time it reads the satellites [1]. The UK’s Maritime and Coastguard Agency, warning ship operators about Furuno receivers with the same kind of rollover, put it plainly: “although you should reacquire the GPS position, date information cannot be restored by cold-starting” [11]. If yours still shows the right date, leave it alone. In 2022, Honda said owners met the problem at the next power-on [4], and Acura said its owners first noticed it after a battery disconnect or the next daylight saving change [9]. Owners report the same pattern now: a 2013 Odyssey owner [17] and a 2013 Pilot owner [18] each say the clock on the audio display went wrong after a battery replacement.
Do not count on a timed battery or fuse reset to fix the navigation clock. In 2022, Acura’s bulletin gave a timed battery disconnect for what it calls the digital radio and LCD clock: off at exactly 12:40, back on at exactly 1:00, then the radio and navigation codes. It applied only from January 1 to August 16, 2022, and the same bulletin said the date had no solution [9]. A Honda dealer’s page dated January 26, 2022 gave the same steps for Honda models including the Odyssey and Pilot [12]. Owners are trying it again, and the reports that say which clock they mean agree: the radio or audio clock restarts, and the navigation clock stays at 0:00. One owner who pulled fuse 23 on a 2012 reports the radio clock running again from 1:00 while the navigation screen stayed at 00:00 [16], and another commenter says the navigation clock “is going to say 0:00 no matter what” [17]. The Reddit user who posted the ServiceNews image says an MDX restarts its clock at 1 AM after a battery disconnect, so the AM and PM may be wrong [14]. Others say the reset did nothing [15][18]. We have not tried any of this. If you try it, have your navigation and radio security codes ready first, or you will lock yourself out of both.
Do not pay for a diagnosis of this. You can read the same screen the technician would, in about a minute, for free. Instructions are below. If your screen does not show the early-2007 signature, that is when a paid diagnosis earns its fee.
Do not wait for a recall. Recalls exist for safety defects, and a frozen navigation clock is not an obvious one. In 2022, Honda handled the same problem with service bulletins and a paid map update [3][4], and we found no recall for it. Nothing rules out a different response this time, but nothing so far points to one. Plan as if there will not be one.
What you can do
Check it yourself. It takes a minute and changes nothing.
- Turn the ignition to ON and let the navigation screen come up.
- Press and hold three buttons together for about five seconds [10]. On the 2012 Odyssey we checked, the combination was MAP/GUIDE, DEST/ROUTE, and CANCEL. On older Honda and Acura navigation systems, it is MENU, MAP/GUIDE, and CANCEL. If one does not work, try the other.
- The screen should jump to Select Diagnosis Items.
- Choose Detail Information & Setting, then GPS Information.
- Read the date. On an affected unit, it is exactly 7,168 days behind today: January 18, 2007 on September 3, 2026, and one day later for each day after that.
The same diagnostic menu runs the hardware tests. Back out to Detail Information and Setting, choose Unit Check, then GPS for the antenna and receiver, and HDD for the drive. On our van, all three passed, and B-CAN, one level up on the same screen, reported no error. If your date is exactly 7,168 days behind, your position and time of day are right, and those tests pass, that is it. Back out without changing anything. There are settings in these menus that can cause real problems, so look but do not touch.
Name the problem at the dealer. “GPS week number rollover in the navigation receiver” will get you considerably further than “the clock is broken,” and it makes it harder for the conversation to drift toward a parts sale.
Use your phone for the time. Unsatisfying, but for a navigation clock stuck at 0:00 it is the honest answer for now.
What we have not proven
In fairness to anyone checking our work:
- We have not physically opened this vehicle’s navigation unit to read the chip’s part number. The identification comes from a teardown of a comparable unit from the same era, plus elimination: the clock survived every earlier Furuno window.
- That teardown reports a Furuno GN-8407B, and Furuno’s rollover table does not list that part number in any row. It does spell out four-digit variants elsewhere in the table, so its absence is worth stating plainly: assigning the GN-8407B to the GN-84 row is our inference from the part number, not Furuno’s published mapping.
- The chip change this article describes would have happened partway through a vehicle generation. The torn-down unit’s part number, 39100-SZA-A710-M2 [2], uses the SZA code that Honda’s parts catalogs apply across the whole 2009-2015 Pilot generation, yet Honda’s 2022 list has the older chip in Pilots through 2011. So the evidence for a switch between 2011 and 2012 was one bulletin list on one side and one teardown on the other. Owners reporting 2012 and 2013 Pilots failing in late August [16] add a third leg, though they say nothing about the chip.
- We do not have the navigation system’s source code, so the explanation of why it displays 0:00 rather than the correct time is well supported by Honda’s own descriptions of the previous event, but it is not proof.
- The self-recovery prediction is arithmetic plus a single precedent.
- We have not obtained an official copy of any Honda or Acura bulletin covering this specific event, and we have not contacted Honda, Acura, or Furuno.
- We could not authenticate the ServiceNews image [14], and every Reddit report in this article is a stranger’s account of a vehicle we have not seen.
- We have not tried a timed battery or fuse reset on our van, so we cannot say whether it would bring back the navigation clock.
- We did not note the day the clock stopped. The identification rests on elimination, not on an exact onset date. Other owners’ posts and the ServiceNews image put the start on August 23 [14][15].
The full list of dates
For anyone who wants to check other equipment, this is Furuno’s published list of when each chip family’s window closes and what date it reports afterward [1]. These chips went into far more than cars: the UK’s Maritime and Coastguard Agency issued its own warning about Furuno receivers on ships [11].
| Chip family | Window closes | Reports instead |
|---|---|---|
| GN-72 | 2010-12-12 | 1991-04-28 |
| GN-74 / GT-74 | 2013-08-11 | 1993-12-26 |
| GN-77 / GF-7712 / GF-7715 | 2017-09-17 | 1998-02-01 |
| GN-77C1 / GN-77R1-01 | 2018-08-19 | 1999-01-03 |
| GT-77 / GT-7731 | 2018-09-16 | 1999-01-31 |
| GN-78 / GN-79 | 2019-03-17 | 1999-08-01 |
| GN-79N5A-N / GN-79L5A-N | 2020-12-20 | 2001-05-06 |
| GN-8091 / GN-8092 | 2021-06-20 | 2001-11-04 |
| GN-80 / GH-80 / GH-8299 / GN-8093 / GN-8096 / GN-8097 / GN-8098 / GS-8094 | 2022-01-02 | 2002-05-19 |
| GT-80 / GO-80 / GT-8031 / GT-8036 / GT-8037 / GF-8043 / GF-8048 | 2022-09-18 | 2003-02-02 |
| GH-81 / GH-82 | 2024-03-24 | 2004-08-08 |
| GF-8044 / GF-8045 / GF-8046 / GF-180 | 2025-02-02 | 2005-06-19 |
| GN-84 / GV-84H / GH-84 | 2026-08-23 | 2007-01-07 |
| GT-84 | 2027-08-22 | 2008-01-06 |
| GF-8051 / GF-8052 | 2028-04-23 | 2008-09-07 |
| GF-8055 / GF-7712A / GF-7715A | 2030-02-17 | 2010-07-04 |
| GN-85F / GV-85 / GH-85 / GT-85 / GT-8536 / GF-8557 | 2030-08-25 | 2011-01-09 |
| GN-86F / GN-87F / GV-86 / GV-87 / GT-86 / GT-87 / GT-8736 / GT-8777 and related | 2032-08-15 | 2012-12-30 |
| GN-8620 / GN-8720 / GV-8620 / GV-8720 | 2034-08-20 | 2015-01-04 |
| GT-88 / GF-8801 through GF-8805 | 2037-10-11 | 2018-02-25 |
The row in bold is the one we believe is affecting Honda and Acura owners right now. The rows below it are the ones that have not happened yet, and the 2027 date is only a year away.
If you are seeing this
The most useful thing anyone can contribute is a record of what an affected vehicle shows. A photo of the GPS Information screen is the core of it, but a photo alone cannot tell us whether newer software changes the outcome. Please send:
- The model year and trim.
- Whether the navigation unit is original or a replacement, and whether its software or map disc has ever been updated.
- The date you looked at the screen.
- The GPS Information photo, with the latitude, longitude, and elevation values covered, since they show where you are.
- Any version numbers the diagnostic menus show, including the receiver firmware under Unit Check, then GPS.
- Which clock is wrong, the one on the navigation screen or the one on the audio display, and what it shows.
A 2013 Odyssey or newer, or one that has had a navigation software update installed, would help most. That would tell us whether the newer software behaves differently, which is the one question with real money attached to it. You can send any of it to me on LinkedIn.
Why this is on this site
This is not what we normally publish, and if you came here for the usual subject matter, fair enough.
It ran for two reasons. It is time-sensitive: people are dealing with this right now, and the useful window for a plain explanation is measured in weeks, not years. And as far as I could tell in early September 2026, there was no plain explanation. Searching this problem then turned up forum threads full of guesses and very little else. Others were ahead of me. One AcuraZine reply blamed a GPS rollover bug on August 24 [13], a Reddit post of September 2 carried what appears to be an Acura ServiceNews article [14], and on September 17 a TSX owner there wrote that the date reverts to 2007 [19].
We tried to hold it to the same standard as everywhere else on this site. Every claim traces to a document listed below, rests on our own reading of one vehicle, or is marked as our inference. The documents are linked so you can check them instead of taking our word for it. Where we could not prove something, we said so in its own section. And we wrote it so someone who has never heard of a GPS week number can walk out to the driveway and check their own vehicle.
That is the job this site does with networks and power grids: find out what the primary documents actually say, and explain it to the people who have to live with the result. Different subject, same work.
Sources
[1] Furuno, GPS/GNSS Receiver GPS Week Number Rollover, document SE18-100-034-02. https://www.furuno.com/files/document/GNSS_Receiver_WeekNumberRollover_SE18-100-034-02_en.pdf. Archived copy: https://web.archive.org/web/20260927203901/https://www.furuno.com/files/document/GNSS_Receiver_WeekNumberRollover_SE18-100-034-02_en.pdf. Chapter 5 is the date table reproduced above. Chapter 6 lists the chips whose rollover date can be changed by command, and the GN-84 family is not on it.
[2] Electronics360, teardown of Honda part 39100-SZA-A710-M2, the 2012 Pilot head unit. https://electronics360.globalspec.com/article/3652/honda-39100-sza-a710-m2-head-end-unit-teardown. The site refuses some readers. Archived copy: https://web.archive.org/web/20250429050643/https://electronics360.globalspec.com/article/3652/honda-39100-sza-a710-m2-head-end-unit-teardown
[3] Honda ServiceNews A21120A, Version 2, published June 2023, via NHTSA. https://static.nhtsa.gov/odi/tsbs/2023/MC-10237953-0001.pdf. Archived copy: https://web.archive.org/web/20260927202856/https://static.nhtsa.gov/odi/tsbs/2023/MC-10237953-0001.pdf
[4] Honda ServiceNews A21120B, via NHTSA. Version 2, published January 2022, answers the owner questions quoted in this article: https://static.nhtsa.gov/odi/tsbs/2022/MC-10206994-0001.pdf (archived: https://web.archive.org/web/20260909013306/https://static.nhtsa.gov/odi/tsbs/2022/MC-10206994-0001.pdf). Version 3, published June 2023, adds the workaround and the paid map update: https://static.nhtsa.gov/odi/tsbs/2023/MC-10237952-0001.pdf (archived: https://web.archive.org/web/20260917174423/https://static.nhtsa.gov/odi/tsbs/2023/MC-10237952-0001.pdf)
[5] Honda Tech Line BTS 170801, September 2017, via NHTSA. https://static.nhtsa.gov/odi/tsbs/2017/MC-10118544-9999.pdf. Archived copy: https://web.archive.org/web/20260927203927/https://static.nhtsa.gov/odi/tsbs/2017/MC-10118544-9999.pdf
[6] Honda ServiceNews B18010I, January 2018, via NHTSA. https://static.nhtsa.gov/odi/tsbs/2018/MC-10130044-9999.pdf. Archived copy: https://web.archive.org/web/20260927204201/https://static.nhtsa.gov/odi/tsbs/2018/MC-10130044-9999.pdf
[7] Honda ServiceNews A18010J, January 2018, via NHTSA. https://static.nhtsa.gov/odi/tsbs/2018/MC-10130038-9999.pdf. Archived copy: https://web.archive.org/web/20260927204044/https://static.nhtsa.gov/odi/tsbs/2018/MC-10130038-9999.pdf
[8] Honda owner support, “Why is my navigation screen clock reading 00:00?” https://crmshonda.my.salesforce-sites.com/hondaknowledge/articles/Knowledge/Why-is-my-navigation-screen-clock-reading-00-00. Archived copy: https://web.archive.org/web/20260927204156/https://crmshonda.my.salesforce-sites.com/hondaknowledge/articles/Knowledge/Why-is-my-navigation-screen-clock-reading-00-00
[9] Acura ServiceNews B21120A, January 2022, via NHTSA. https://static.nhtsa.gov/odi/tsbs/2022/MC-10207004-0001.pdf (archived: https://web.archive.org/web/20260927203910/https://static.nhtsa.gov/odi/tsbs/2022/MC-10207004-0001.pdf). And B23040A, April 2023: https://static.nhtsa.gov/odi/tsbs/2023/MC-10237044-0001.pdf (archived: https://web.archive.org/web/20260927204213/https://static.nhtsa.gov/odi/tsbs/2023/MC-10237044-0001.pdf)
[10] The vehicle’s own diagnostic screens, read on September 3, 2026. Not a published document, and the one source here that nobody else can check, which is why the numbers it produced are stated alongside the published dates they match.
[11] UK Maritime and Coastguard Agency, Safety Bulletin 25, “Furuno navigation & communication equipment (incl GMDSS) – GPS week number rollover,” 14 December 2021. https://www.gov.uk/government/publications/safety-bulletin-25-furuno-navigation-communication-equipment-gps-week-number-rollover/safety-bulletin-25-furuno-navigation-communication-equipment-incl-gmdss-gps-week-number-rollover. Archived copy: https://web.archive.org/web/20260927204224/https://www.gov.uk/government/publications/safety-bulletin-25-furuno-navigation-communication-equipment-gps-week-number-rollover/safety-bulletin-25-furuno-navigation-communication-equipment-incl-gmdss-gps-week-number-rollover
[12] Bianchi Honda (Erie, PA), “Change Clock on Accord, Odyssey, or Pilot with Navigation – Repair,” January 26, 2022. https://www.bianchihonda.com/change-clock-on-accord-odyssey-or-pilot-with-navigation-repair/. Archived copy: https://web.archive.org/web/20240725150453/https://www.bianchihonda.com/change-clock-on-accord-odyssey-or-pilot-with-navigation-repair/
[13] AcuraZine, forum thread “2012 mdx nav clock stuck,” August 24, 2026: one question and one reply, no later posts as of October 5, 2026. https://acurazine.com/forums/1-2g-mdx-2001-2013-166/2012-mdx-nav-clock-stuck-1013284/. Archived copy: https://web.archive.org/web/20261005143843/https://acurazine.com/forums/1-2g-mdx-2001-2013-166/2012-mdx-nav-clock-stuck-1013284/
[14] Reddit, r/Acura, “The clock issues are back! 10-13 MDX, ZDX, and 12-14 TSX,” posted September 2, 2026, with an image of what appears to be an Acura ServiceNews article, “Incorrect Date and Time on Navigation Display,” September 2026, Version 1. https://www.reddit.com/r/Acura/comments/1w5qwmu/the_clock_issues_are_back_1013_mdx_zdx_and_1214/.
[15] Reddit, r/HondaOdyssey, a thread posted August 24, 2026 by owners whose navigation clocks stopped the day before. https://www.reddit.com/r/HondaOdyssey/comments/1vx18m3/clock_stopped_working/.
[16] Reddit, r/hondapilot, a thread posted August 23, 2026 by the owner of a 2013 Pilot Touring whose navigation clock reads zero, with replies to September 3. https://www.reddit.com/r/hondapilot/comments/1vw7kri/clock_at_zero/.
[17] Reddit, r/HondaOdyssey, a thread posted September 25, 2026 by the owner of a 2013 Odyssey whose radio time went wrong after a battery replacement. https://www.reddit.com/r/HondaOdyssey/comments/1wq6n3s/2013_cant_set_radio_time_after_replacing_battery/.
[18] Reddit, r/hondapilot, a thread posted September 18, 2026 by the owner of a 2013 Pilot Touring whose dash clock went wrong after a battery replacement. https://www.reddit.com/r/hondapilot/comments/1wjwi8i/anyone_know_how_to_fix_the_dash_clock_not_the_000/.
[19] Reddit, r/AcuraTSX, a thread posted September 17, 2026 by the owner of a 2014 TSX whose clock will not adjust. https://www.reddit.com/r/AcuraTSX/comments/1wie71f/acura_tsx_clock_will_not_change/.
[20] Reddit, r/AcuraTSX, “Tech Package gang: are your clocks working again?” posted September 23, 2026. https://www.reddit.com/r/AcuraTSX/comments/1wohgoq/tech_package_gang_are_your_clocks_working_again/.
The Reddit entries, [14] through [20], were read on October 5, 2026. They are other people’s accounts, and we could not check any of them. Reddit gave our own script a bot check instead of each page, and the one archive.org copy of a cited thread that we could open was an empty page, so these seven have no archived copy.
Honda’s technician site hosts these bulletins too, at techinfo.honda.com, but it is subscription-only and will turn you away. The NHTSA copies above are the same documents, free to anyone.