The day my new boss walked into our quarterly review and called our entire compliance infrastructure a bureaucratic relic holding the company back, I knew exactly what was coming. I didn’t say anything. I just wrote down the date in my notebook and kept listening. For 11 years, I had been the senior director of regulatory affairs at Meridian Aerospace Solutions, a mid-size defense and aviation contractor outside Huntsville, Alabama.
We built guidance systems. We held FAA production approvals, DoD contracts, and three active DER designations that were tied, by name, directly to me. Those authorizations didn’t belong to the company. They belonged to me, granted by the FAA after years of demonstrated technical competence.
When I left the room, those authorizations left with me. But my new boss didn’t know that. And honestly, I don’t think he would have cared even if someone had explained it slowly, with pictures. He came in as our new CEO six months after our founder retired.
His name was Greg. He was 41, had an MBA from a school he mentioned in the first three minutes of every conversation, and had spent the previous decade in commercial real estate—not aerospace, not defense, not anything remotely adjacent to what we did. He had been brought in by two board members who wanted to modernize the leadership profile of the company, which I eventually understood to mean they wanted someone who wore slim-fit suits and used the word leverage as a verb. Greg’s first move was to bring in his own people.
That’s normal. CEOs do that. I expected it and didn’t begrudge him one bit. His second move was to reorganize the entire senior leadership structure, which was less normal but still within his authority.
His third move was to tell me, in a one-on-one meeting in February, that he was evaluating the regulatory function and wanted to bring in someone with a more dynamic, growth-oriented approach to compliance. I asked him what that meant in practical terms. He said he was looking at a candidate his brother-in-law had recommended—someone who had recently completed a regulatory affairs certification program and had three years of experience in medical devices, not aviation, not defense. Medical devices.
I looked at him across the conference table and chose my words carefully. I said our regulatory structure was built around specific FAA authorizations and DoD compliance frameworks that required years of institutional relationship building, and that any transition would need to be handled with considerable care given our contractual obligations. He told me he appreciated my perspective and that change was sometimes uncomfortable for people who had been in a role for a long time. I wrote that down, too.
Over the next eight weeks, I watched Greg’s brother-in-law’s recommendation—a man named Tyler—get introduced to the team as my strategic successor. Tyler was pleasant enough. He was organized, eager, and knew medical device FDA submissions reasonably well. He knew absolutely nothing about FAA Part 21 production approval, nothing about DER authorization scope, and nothing about the DCSA compliance requirements attached to two of our active defense contracts.
When I walked him through our quality management system during his onboarding, he nodded at everything I said with the confidence of someone who understood none of it. I didn’t try to sabotage him. I want to be clear about that. I answered every question he asked.
I documented everything. I spent three weekends writing transition binders that were more thorough than anything the company had ever had. I did that not for Greg and not for Tyler, but because the work mattered and the people who would inherit it deserved accurate information. What I did not do was hide the truth about what my departure would actually mean.
In March, I submitted a formal memorandum to our general counsel, a woman named Patricia, who had been with the company for 14 years and understood our regulatory architecture the way a surgeon understands anatomy. The memo was eight pages long. It documented, in precise detail, the following facts. First, I was listed by name as the responsible DER on three active FAA-approved design projects.
FAA Order 8000. 15 is specific about what happens when a DER leaves an organization. The authorizations terminate. They don’t transfer.
They don’t temporarily pause. They terminate, and the projects tied to those authorizations end in a compliance gap that must be reported to the agency. Second, I was listed as named key management personnel on two DoD contracts under our facility security agreement. The National Industrial Security Program Operating Manual is also specific about this.
Changes to key management personnel require advance notification to the Defense Counterintelligence and Security Agency, and depending on the contract, that notification window can be 60 to 90 days minimum. Tyler did not have a security clearance. Obtaining one, on the timeline Greg was proposing, was not realistic. The DCSA does not expedite clearances because a CEO has a reorganization schedule.
Third, our largest active contract—a $34 million guidance system production agreement with an Army Program Office at Redstone Arsenal—had a specific clause requiring that any change in named technical personnel be approved in writing by the contracting officer before the change took effect. Not after. Before. Patricia read the memo.
She went very quiet. She asked me if I had shared it with anyone else. I said not yet. She asked me to give her 48 hours.
48 hours later, she came to my office and told me she had presented the memo to the board’s outside legal counsel, and that there were, in her words, significant concerns about the transition timeline Greg had outlined. She asked if I would be willing to stay through an extended transition period to avoid triggering compliance events. I told her I would think about it. That same afternoon, Greg called me into his office and told me he had heard I had been creating obstacles to the transition and that he wanted me to understand this was not a negotiation.
He said Tyler would be assuming full responsibility for the regulatory function at the end of Q2, which was ten weeks away, and that if I was not prepared to support that transition professionally, we could discuss accelerating my departure. I looked at him. I thought about 11 years. I thought about the three FAA authorizations with my name on them.
I thought about the $34 million contract and the Army Program Office at Redstone and the contracting officer who had personally called me twice in the last year because he trusted my judgment. I thought about the DCSA and what a security gap notification would do to our facility clearance. Then I thought about what Greg had just said—that this was not a negotiation. He was right.
It wasn’t. I submitted my resignation the following Monday. Two weeks notice, professional and clean. I gave Tyler every document I had ever created.
I answered every question during the notice period. On my last day, I shook hands with the people I had worked alongside for over a decade and drove home. Then I did what Patricia had quietly, carefully, not quite explicitly suggested I make sure to do. I contacted the FAA directly to formally notify them that I was no longer employed with Meridian and that my DER authorizations should be reviewed accordingly.
This is not vindictive. This is required. The FAA expects DERs to self-report changes in organizational affiliation. I was complying with a regulatory obligation.
I also sent a brief, factual, unemotional email to the contracting officer at Redstone—not to complain, not to warn, simply to let him know, as a professional courtesy, that I had left the company and that he might want to verify the current status of the named technical personnel on our contract. He and I had worked together for six years. He deserved to know. I went home.
I took two weeks off. I started some consulting conversations with two other firms in the aerospace sector who had reached out over the years. I did not call anyone at Meridian. I did not post anything.
I did not talk to the press or to former colleagues or to anyone connected to the company. I didn’t need to. Six weeks after I left, the Army Program Office at Redstone issued a formal cure notice to Meridian. A cure notice is the contractual equivalent of a defibrillator going off in a quiet room.
It means the government has identified a material contract compliance failure and is formally notifying the contractor that they have a specific window—usually 10 to 30 days—to fix it or face termination for default. The failure identified in Meridian’s cure notice was the unauthorized change in named key technical personnel without contracting officer approval, in direct violation of contract Section H. Tyler had been introduced to the Army Program Office as the new regulatory director without anyone having obtained the required written approval. Greg had apparently assumed that was a formality.
The program office did not agree. At roughly the same time, the FAA opened a compliance review of the three design projects attached to my former DER authorizations. Without an active DER designation, those projects could not continue. Two of them were paused.
One—a modification package that had been six weeks from final approval—was suspended entirely pending reassignment to a new DER, which would require the entire technical data package to be reviewed by someone who had not been involved in the original design. That process, I was told later by someone still at the company, took four months. And then the DCSA notification issue surfaced. When the agency conducted a routine review and discovered that the named personnel on the facility security agreement had changed without proper prior notification, they opened a formal review of Meridian’s security posture.
That review placed the company’s facility clearance in a conditional status for the duration of the investigation. A company in the defense sector cannot effectively bid on new classified contracts while its facility clearance is conditional. The business development pipeline, which Greg had been telling the board was about to generate significant new revenue, went silent. I learned all of this through Patricia, who called me on a Saturday morning about two months after I left.
She didn’t editorialize. She just told me the facts in the same quiet, precise way she did everything. She said the board was asking hard questions. She said Greg had retained outside counsel to review whether the regulatory transition had been handled properly.
She said the Army had not yet decided whether to cure or terminate, but that the legal exposure was significant. Then she asked if I would be willing to come back in a consulting capacity to help stabilize the situation. I told her I appreciated the call and that I would think about it. I did think about it.
For several days, honestly. 11 years is a long time. I knew those contracts. I knew the program offices.
I knew exactly what it would take to get the FAA reviews resolved and the DCSA situation stabilized. I could have walked back in and had meaningful progress within 60 days, probably. The work itself was never the problem. The work I genuinely loved.
But I thought about Greg sitting across that conference table telling me this was not a negotiation. I thought about Tyler being introduced to the Redstone program office as if the last 11 years of relationship building could be handed off like a key fob. I thought about the word relic. I called Patricia back and told her I was honored by the confidence, but that I had accepted a senior position with another firm and was not available for consulting engagements with Meridian at this time.
I thanked her for the years of working together. I meant it. The offer from the other firm was real. They had been calling for 18 months.
The title was VP of regulatory and government affairs. The salary was 31% higher than what I had been making at Meridian. I started four weeks later. From what I heard through the industry—and aerospace in Huntsville is a small world—Meridian ultimately survived.
They hired a regulatory director with actual aviation experience, which took four months to find because competent people in that specialty are not waiting by the phone. They resolved the DCSA situation after a nine-month review. The Redstone contract was cured, not terminated, but only after significant concessions to the program office and a six-month schedule delay on deliverables. The two paused FAA projects were eventually restarted under a new DER.
The suspended modification package was approved, finally, about eight months after it had originally been on track for closure. The new business pipeline Greg had promised the board—from what I understand, two of the three major opportunities they were pursuing during that period were lost to competitors while the facility clearance was conditional. One of those opportunities was a program worth approximately $28 million over five years. Greg left the company 14 months after joining.
The board accepted his resignation, which is the polite way of saying what actually happened. The press release thanked him for his company’s strategic evolution. I keep that phrase in mind sometimes. Strategic evolution.
It’s a useful phrase. It doesn’t mean anything specific, which is exactly why people reach for it. What I know about this industry—what 11 years and three DER authorizations and dozens of government contract audits taught me—is that the infrastructure you can’t see is the most important infrastructure there is. The clearances, the authorizations, the named personnel clauses, the agency relationships built over years of showing up and doing the work correctly, even when no one is watching.
None of that shows up on a reorganization chart. None of it fits neatly into a slide deck for a board meeting. But it is the architecture that everything else rests on. And when someone who doesn’t understand it decides to renovate without reading the load-bearing walls, the building doesn’t care about their MBA.
The contracting officer at Redstone sent me an email about a year after I started at my new firm. He said he was glad I had landed well. He said his program office was about to release a new competitive solicitation and he hoped the firm I had joined would be submitting a proposal. He said—and I’m recalling his exact words here because I saved the email—that they were looking forward to working with people who understood the mission.
I forwarded the solicitation to our business development team that afternoon. We won the contract six months later. It was worth $41 million over four years. The award notification came on a Tuesday.
I was in a staff meeting when the email arrived. I stepped out into the hallway to read it, and I stood there for a moment by myself, and I felt something that was not quite triumph and not quite relief, but somewhere in between. Something quiet and solid. Then I went back into the meeting because there was work to do.
There is always work to do when you’re someone who actually knows how to do it.