Skip to main content

Smoke doesn't always mean fire Part V

Lt Col Martin was released from the jury on the 22nd of April 2016. That evening he discussed why he was released with Chief Gleesing, another jury member.

Because of the delay due to Lt Col Martin's dismissal the judge elected to continue the trial the following day [Saturday the 23rd of April]

I'm not quite sure how, but somehow the judge learned that jury members had heard why Lt Col Martin was released. Unfortunately I don't have supporting evidence for this so at best it's hearsay and speculation but all of the evidence points to it as you will see below. The bolded section is the court recording from the day before.

**These are actual court documents from Lt Col Dominick Martin's Article 48 hearing. They were acquired by a Freedom of Information Act request submitted by me. Furthermore, FOIA was unwilling to meet their timeline required by law without a congressional inquiry, through Congresswoman Dorris Matsui at my request.**

What I do know is that Lt Col Martin was summoned to the courtroom that same day for an Article 48 [Contempt] hearing at 0930 [I received the following documents from a FOIA request in July 2016]:

Col Martin was summoned back to court on the 23rd to answer to the military judge (MJ) for violating his lawful order not to discuss the trial or his release with any other jury members.

The initial court appearance was procedural in nature and allowed Col Martin to understand the charge levied against him. It would be almost a month before Col Martin would return to the court room to answer that charge.

However, in the meantime there was much more going on.

I reached out to a few professional friends and mentors in key leadership positions throughout the group and 49th Fighter Wing to gauge the response of my recording.

I learned on the following Monday (April 25th, 2016) that everyone from SMSgt and above in the group knew of the recording, Col Martin's ouster, and his contempt charge.

I also learned that the 49th Fighter Wing commander was considering launching an investigation into the recording. You might be thinking 'good, someone should hold a squadron commander accountable for the maltreatment of the people entrusted to him.'

You would be wrong. Even though the recording exposed Col Martin's true opinion of suspicion, assumption of guilt and punishment [at complete odds with the notion of justice and due process]; the 49th Fighter Wing commander was not investigating Col Martin. He requested an investigation into the legality of the recording. I had already done my homework and knew recording the conversation was legal so I wasn't concerned for my career. Only I was a bit surprised how readily a commander will rally around another who was so flagrantly unfit to command [Saying he was unfit isn't rhetoric, I'll expand on that next episode].

That same day I had to brief the afternoon production meeting like I had in the past. Lt Col Martin was chairing the meeting.

It was a bit surreal. Col Martin had to pretend that he didn't know I recorded him. However, I knew that he knew I had recorded him. But I had to pretend that I didn't know, that he knew. He was barely able to keep his seething rage from spilling over into his tone and inflection. I, mostly emotionally detached from the encounter [the side effect of not being guilty I suppose], observed how ineffective Col Martin was at hiding his disdain for me.

He didn't refer to me by name, didn't speak to me at all. He made no attempts to ask follow-up questions from my briefing. At the conclusion of the meeting he skipped over my corner of the table completely when asking for final thoughts.

I've never had an easier time briefing in my life. I could've claimed Ewoks had sabotaged our base on
Endor, resulting in our low MC rate and he would've accepted it as an answer.

What made the exchange even more uncomfortable was the knowledge that everyone else in the room also knew what had happened and they had to all play along as well.

After a week or so of the silent treatment Lt Col Martin eased his anger some and eventually referred to us as 'the AMUs' at the conclusion of the meeting and even at times looked in my general direction when I was briefing him.

After two weeks he even called me by my official rank and last name; although you could hear it was forced.

I called the Holloman Area Defense Counsel and asked her opinion on whether I should schedule a sit-down meeting with Lt Col Martin to explain my motivations, reasons and moral perspective for my actions. As clearly he was cooling off and might be willing to hear me out.

She told me that would be an exceptionally bad idea because of the active investigation into a Privacy Act violation. Interesting thing about Command Directed Investigations [CDIs]: they don't actually tell you you're being investigated for awhile.

As for my work, my actual job? It was more miserable than normal. It was plainly obvious that Fraley was using all of his administrative tools at his disposal to ensure I was thoroughly miserable as a Lead Production Superintendent. He, much like Lt Col Martin, viewed me as a traitor among the ranks that deserved the worst possible treatment. I was a toxic cancer, tainting Airmen and NCOs alike. As such, he made a point to tighten the screws and micromanage me even more.

One of the few times I've felt guilt over this ordeal. My actions created an unbearable work environment for my superiors in the 314th. They were experiencing the same scrutiny and rage as I was, without ever doing anything to deserve it themselves.

I knew what would happen to me when I provided that recording to the court. The collateral of the 314th AMU OIC, NCOIC and ANCOIC was something I hadn't foreseen.

I learned that Lt Col Martin's hearing was on the 20th of May. I wanted to be there to gauge the scope of my exposure as the CDI against me gained steam. However, I didn't dare sit in the audience during the hearing, which could be seen as gloating or humiliating by Lt Col Martin. Life was miserable enough as it was, I certainly didn't need to stoke that fire.

Eventually, May 20th came and Lt Col Martin had to answer for his crime.


  1. Oh my god, I cant wait to hear the end of this.

    1. I’m working on it. Unfortunately I have 137 pages of court transcripts to capture and make all my annotations for the blog.

      I’ll try to have it published in the next two weeks!

  2. Scary how many common coworkers and duty stations we've had. Small Air Force

    1. Being we are both anonymous, is it possible we are the same person?

  3. I'm a retired MSgt, spent my youth in the fighter world, then most of the rest of my USAF sentence in Bombers. I thought wacky stuff happened in the bomber world, but this entire chain of events is unconscionable. I wish more leadership had the giant steel balls that you have sir.

    1. New article is published if you want to check it out!


Post a Comment

Popular posts from this blog

Smoke doesn't always mean fire Part I

This is the first post in the long final story that I will tell from my career in the Air Force. All the other stories up to this point were told so you, the reader, could understand how I was guided in my career to be prepared for the moment in this story. The main character in this story has had his name changed to protect his identity as he is still active duty. He has given me permission [read: excitedly asked when I will write this] to tell this story. In the summer of 2015 I was the specialist section chief in the 311th AMU at Holloman AFB. We had a few new arrivals to the section. Most of them were new avionics airmen, which we desperately needed. However, we did have an E&E SrA arrive who had a line number for Staff Sergeant. His name was SrA Tyler Perkie. He was respectful, polite and hard working. It was rare to not see him covered in aircraft filth, which is quite the compliment for the working sector of the Air Force. He was tireless at the job and his positive at

An opaque response to a request for transparency

  This article will be published at the same time as a podcast addressing the exchange on the CMSAF's Facebook page. For a complete analysis I encourage you to continue reading then listen to Episode 17 of the 20 Years Done Podcast. The podcast can be found on typical podcast mediums as well as the RSS feed in the top right of this website. On October 17th at 6:32 PM the  Facebook page for the CMSAF posted a photo of a few deployed Airmen that she had a video conference with. Then one person made a comment. This blog isn't going to analyze that exchange, that's what the podcast episode is for. However, in the course of preparing and recording the podcast I heard rumors that the CMSAF herself didn't actually make that post. So, I did what anyone would do. I tracked down contact information for her Public Affairs team and asked them some questions. But before we get to those questions, I think it's important to first provide some context. First, the CMSAF's Faceb

So what's with the 7 levels?

I recently asked in a  Facebook post what are some subjects you the readers wanted me to write about. I received quite a few great suggestions, but one stood out as a topic that I haven't quite addressed and I believe its time is due: inexperienced 7 levels. [I will apologize in advance, this one has quite a bit of acronyms.] Before I dive into the topic I think it's important to explain my own journey to a 7 level, and it goes all the way back to MEPS. You see, like many aspiring Airmen I didn't know what job I would get when I joined the Air Force; I came in open mechanical. Which to me seemed strange, because mechanical was my lowest ASVAB score. My recruiter assured me that my score would allow me many mechanical jobs to pick from. I tried to explain that the ASVAB was an aptitude test, and I should be selected for a job that matched my highest category. He seemed apathetic, obviously meeting his quota was his motivator, not me aligning my career to my aptitude.