9th Circuit rejects Stancil appeal

I thought that announcing my “medical leave of absence” would allow me to step away from this blog and from posts on Facebook.

But that has proved to be difficult.

It’s been frustrating to watch developments related to the ongoing Miske-related proceedings that have gone unreported.

Today I finally broke, and sought out the aid of Google’s Gemini AI assistant to help report on the 9th Circuit’s dismissal of John Stancil’s appeal of his 20-year sentence. The court’s decision was handed down over a month ago, and hasn’t been reported on.

I asked Gemini’s help in summarizing the arguments. Although I tried to tweak Gemini’s tone, I just didn’t have the time or energy to get control of it through detailed instructions.

I did, however, go through and edit the text to remove errors and ambituity. I hope that I was successful.

So, here’s my disclosure: I co-authored this blog post with Gemini, but I have to take responsiblity for any remaining errors.

The 9th Circuit Court dismisses Stancil’s appeal of his 20-year sentence

A three-judge panel of the Ninth Circuit Court of Appeals completely shut the door on John B. Stancil’s appeal of his 20-year sentence, the maximum for the crime of racketeering conspiracy. The court’s decision granting a government motion to dismiss was posted in late February.
The court ruled Stancil’s plea agreement included valid waiver of his right to appeal his case or sentence except under very limited circumstances.

Stancil’s attorney, Boise-based William Miles Pope, argued that comments by Federal Judge Derrick K. Watson during Stancil’s plea hearing opened the door to on of those limited exceptions, but the Ninth Circuit wasn’t buying it. The court concluded Watson’s choice of words simply “did not negate the written waiver of the right to appeal.”

Although rejecting Stancil’s appeal, the court also provided additional time to allow Pope to file a motion for reconsideration. The deadline for filing the motion has been extended to May 11.

Stancil’s appeal goes back to his guilty plea to a racketeering conspiracy charge tied to the violent “Miske Enterprise” in Hawaii. To dodge a trial, Stancil made a deal with the government. He agreed to plead guilty to the one racketeering conspriacy charge, and in return, prosecutors would drop twelve other serious counts and cap his maximum prison time at 20 years instead of a potential life sentence.

Part of this bargain meant signing a broad appeal waiver, standard in such plea agreements. Stancil agreed to give up his right to appeal his conviction and any sentence that fell “within the Guidelines range as determined by the Court at the time of sentencing”. At his sentencing, the district court crunched the numbers, figured his guideline range was 210 to 262 months, capped it at the 240-month statutory maximum, and gave him exactly 240 months behind bars. Since 240 months was right in that court-determined range, the government argued his appeal was totally blocked.

But Stancil claimed a “Get Out of Jail Free” Loophole. Even with that signed contract, Stancil appealed anyway. His entire argument hinged on whether comments by Judge Watson during his change-of-plea hearing opened the door to his appeal.

Stancil’s defense argued that the judge clearly and unambiguously told him he’d keep his right to appeal if his sentence was “something above the applicable sentencing guideline range”. Under Ninth Circuit precedent, if a judge gives you an unambiguous free pass to appeal, that spoken word overrides whatever you signed in the plea agreement.

Stancil also argued that the phrase “applicable guidelines range” legally means the correctly calculated range. In his appeal, Stancil argued that he deserved a lesser sentence because, in his view, he played only a minor role, rather than a central role, in murder-for-hire plot. If the court had agreed with him, his true guidelines range would have dropped to 188-235 months.

He argued that his 240-month sentence was technically “above” what he argued was the true applicable range, meaning the judge’s oral exception should let his appeal move forward.

Prosecutors responded with a motion to dismiss the appeal, insisting that Stancil’s written waiver was absolutely binding. They pushed back on Stancil’s narrative by adding some much-needed context from the hearing transcript.

They pointed out that right before the judge spoke, the prosecutor had detailed the waiver and specifically noted the exception only applied if the sentence went beyond the range “that the Court finds is applicable”. The judge then agreed with the prosecutor’s summary and warned Stancil that he was signing a “very broad, general waiver” of his rights.

The government argued that, at worst, the judge’s slight change in phrasing was just ambiguous—and precedent says that ambiguous statements from a judge aren’t enough to blow up an otherwise valid appeal waiver. Plus, they reminded the court that Stancil got a massive sweetheart deal, dodging a life sentence and getting a dozen charges dropped. They argued he shouldn’t be allowed to back out of his end of the bargain after reaping all those benefits.

It’s worth looking at Judge Watson’s review of Stancil’s criminal history to understand the gravity of this case.

Technically, Stancil stood before the court as a first-time felon with a low Criminal History Category of I. But Chief District Judge Derrick K. Watson made it very clear at sentencing that Stancil’s actual track record was incredibly violent and spanned years.

This wasn’t just a brief lapse in judgment. Judge Watson and the prosecution detailed a long list of crimes Stancil actively committed for the racketeering organization controlled by his half-brother, crime boss Michael J. Miske, Jr..

This included:

Murder-for-Hire: Stancil’s active role in a plot to assassinate a man named Joe Boy Tavares.

Chemical Attacks: Providing the toxic fumigant chloropicrin to a co-conspirator, which was then released into two crowded rival nightclubs (the Ginza and The District) on consecutive nights.

Armed Robberies: Participating in a clothing store robbery where he and his crew wore masks and used zip ties, a handgun, and a baton. He was also involved in robbing a methamphetamine dealer where they impersonated law enforcement officers.

A Deadly Ambush: A masked ambush at Aloha Tattoo that Stancil actually filmed on his phone, which ultimately ended with a co-conspirator getting stabbed to death.

Vicious Assaults: A string of brutal beatings targeting Miske’s business rivals. Victims were violently attacked and hospitalized for “crimes” as minor as handing out party invitations or bidding against Miske at local car auctions.

Speaking directly to Stancil, Judge Watson summed him up as a “key player in terrorizing the citizenry of this city and this county for years, doing the bidding of Mr. Miske any time he asked”.

In the end, the Ninth Circuit completely sided with the government. By granting the motion to dismiss, the court confirmed that Stancil’s written plea agreement holds up. The district court’s conversational summary at the hearing just wasn’t enough to rewrite the contract he had signed.

Our affair with Apple Computer

Apple will be celebrating its 50th birthday in April. Fifty years since the company was formed to sell simple computer kits designed by Steve Wozniak to local computer hobbyists in and around Palo Alto.

Meda and I jumped on the Apple bandwagon not long after the introduction of the Apple II in 1977, probably late that same year.

I knew nothing about computers. When we were in college, “computer” meant the room of electronic equipment in the administration building where an anointed few had access. The rest of us used fancy addling machines. Even handheld calculators were still in the future.

But I had been reading that these new “personal” computers would be fundamental “game changers” and wanted to learn more. I finally convinced Meda that we should just buy one and see what it could do, and we did.

That was the year we turned 30, and over the next nearly 50 years we have remained firmly in the Apple camp.

The original Apple II introduced what became the familiar beige case with an apple in rainbow colors. It had very limited memory, no disk storage and no built in software. The few programs that were available for purchase came on standard audio tape cassettes. You would plug your cassette player into a port on the computer and manually download each program. I remember the thrill of playing “Little Brick Out” at the Apple II’s slow speed after loading it from a cassette. It was like magic!

I can date our first Apple purchase by the use of cassette tapes. A year late, in mid-1978, Apple introduced a floppy disk drive priced at $600. It stored what was then a dramatic amount of data–113K, that is, kilobytes. It seemed to open up whole new worlds.

The following year, Apple introduced the Apple II+. We quickly got on that bandwagon via a Bell & Howell black Apple II+ manufactured under license for the education market. One day we walked into a small Honolulu computer hobbyist store and saw a stack of black Apples, and took one home.

That same year, 1979, saw the introduction of Apple Writer and VisiCalc, which turned the hobbyist-oriented Apple II into something that could do real work!

A few years later, Apple added the Apple IIe, with more memory and other features.

By that time, we had yielded to the “need” for his and her Apples at home, along with Apple’s for our office desktops as well.

Apple added Macintosh in 1984, but we didn’t invest in the new computer until the Macintosh Plus was introduced two years later. Unfortunately, the mists of time have erased any memory of which exact models followed as the first Mac Plus was replaced with newer iterations.

We invested thousands of dollars in new Macs over the years, more than I can recall at this point. Each made us more productive, or perhaps simply more efficient.

But it’s fair to say that our affair with Apple changed our lives for the better.

So I’ll simply say, Happy Anniversary, Apple!

An automated collision avoidance system warned of a close call

A reader writing as Pete808 left the following comment, which appears to provide additional details showing why our United flight to SFO on March 21 abandoned it’s initial landing attempt and powered up, went around, and made another landing attempt (this second one was successful).

Pete808’s findings show how much information can eventually be gleaned from existing public data.

Here are his findings, which initially appeared in a comment but are being elevated here because of their importance.

Here’s what I found by doing some additional internet research. By the way, I have no training or experience as a pilot or air traffic controller, although I’ve flown to SFO quite a few times.

In any event, one can go to LiveATC.net and listen to or download the archived air traffic control recordings for SFO for March 21, 2026. The archives are in half hour segments. After what seems to be a routine clearance to land, the archive for “SFO Tower” has a very cryptic communication from UA 373 a little more than halfway through the recording covering the time period beginning at 2200Z (Zulu or UTC time which is 3 pm SFO time). UA373 indicates that he’s going around although I couldn’t really tell what was being said by listening. In response, the tower controller tells UA373 to fly the runway heading and eventually to contact NorCal Approach.

If you review the archive for NorCal Approach for the period starting again at 2200Z, at around 23:45 into the recording the controller asks UA373 to say the reason for the go around and UA373 replies that they were responding to an RA. An RA is apparently a Resolution Advisory from the ACAS system (Airborne Collision Avoidance System), which is an onboard aviation safety system designed to prevent mid-air collisions by independently detecting nearby aircraft and advising pilots on avoidance maneuvers.

Although two planes landing on parallel runways is pretty routine at SFO with the aircraft required to maintain visual separation, the instructions with respect to ACAS Resolution Advisories is to do what the RA says. So even though UA373 was supposed to maintain visual separation from the other aircraft and even if that visual separation was still being maintained by UA373, when the RA was given by ACAS, the crew of UA373 was obliged to follow it.

Hope your health issues get resolved favorably.

A nocturnal adventure

Some of you might find this of interest.

I found myself in a very immersive dream, probably somewhere around 2 or 3 a.m. on a night not long ago.

The dream was very much like a movie in which I was a first-person narrator.

As I recall, I had infiltrated a strange religious cult along with one other reporter. I remember walking through a group of flower-child types who were off in their own worlds, with an occasional hard character with a predator’s gaze, probably the flock’s keepers.

I have no recollection of why we were involved in an undercover investigation of this cult, but I felt vulnerable and a bit worried as we collected observations.

At some point, I was talking to a couple of cult members, and one showed me a flyer challenging some of the cult’s primary beliefs. I pretended to be shocked, but it was something we had written and dropped around in an attempt to cause some disruption of internal discipline.

Seeing the flyer made me realize that they were looking for the source, and decided it was time to get out.

I recall strolling over to the back exit, where it was necessary to go through a small obstacle course before leaving. I managed that task and tried to look casual as I walked away from the property, but within a minute or so I started running to get as far away as possible.

I found myself running parallel to a low berm to my left, away from that exit.

Then I noticed one of those predator-types running off to my right, cutting across the field that separated us as he tried to intercept me. He soon caught up and to evade him I threw my body to the side, over that berm.

And BAM.

It was a rude, startling, and somewhat painful awakening as I found myself stretched full length on the hard wood floor on the side of our bed where I had fallen.

I landed along my right side, right arm, elbow, and shoulder, and right knee, but then rolled over flat on my back as my brain caught up with my situation. A few deep breaths and I began a quick assessment. Lots of parts were sore, but nothing seemed broken. Meda was now awake and also assessing my situation.

Luckily, after a minute or two of self-assessment, I was able to sit up, get up on one knee, and then stand, before getting back into bed and going back to sleep.

Part of this is our own fault. During our entire marriage 55+ years of marriage, we have shared a double bed. Right. Not King, not Queen. A plain old double bed, usually shared with a cat or two, pushing the two of us to the sides.

Is that what they term “living on the edge”?

I’m not sure what psychological term applies to this crossover between dream and reality, where parts of the dream “break out” into real world movements.

Yes, I searched online. Most descriptions say there is usually no memory of the content of the dream. In my case, the opposite. A clear memory.

As far as I know, this was the first time I entered this particular space.

Now when I feel myself entering a similar deep sleep dream state, I try to escape toward the surface of consciousness, just in case.