Why did the 2014 MBH 5000K NAV glitch feel like a missed short on MTD SPY?

Anyone else still haunted by that March 2014 glitch on the MBH‑5000K NAV where the fund's price dipped 6% for a split‑second before snapping back? I swear it was the most convincing fake‑flash crash I'd seen since the 2010 "Flash” that ate a million‑plus orders on Nasdaq.

Back then I was just a kid with a $7k Roth IRA and a habit of flipping between the S&P 500 (ticker: SPY) and the old “MTU ETF” on the advice of some 20‑year‑old analyst on the message board. I loaded 12 % of my portfolio into MBH while keeping a 75/25 split‑equity‑bond and set the limit to 0.5 % max draw‑down.

The glitch was a nightmare:

• NAV reported at 98.23 instead of 105.12 – instantly triggering my DTC auto‑sell.
• My broker (then WFS) filled the stop‑limit at $98.26, wiping $450 from my account.
• The NAV corrected within seconds, the fund closed the day at $105.25 – a 7% gain that never hit my account.

Fast forward to now, with algorithmic bots and Dark‑pool data streaming nonstop, I still hear whispers about that incident when someone drops “#NAVglitch2014” in a thread.

So I'm asking: did any of you actually survive that dip long enough to capture the bounce? Or were we all forced into the inevitable 0‑beta cash‑drag? I’d love to hear those war stories and any takeaways on how to rig your order‑routing settings to avoid phantom stops in today’s hyper‑high‑frequency world.

(P.S. The irony isn’t lost on me that I used a “static limit” rule while the market was anything but static.)