I build the connective tissue between engineering, manufacturing, suppliers, facilities, maintenance, customers, and leadership so advanced hardware can move from development into first-asset execution and repeatable field operations.
My career began at the wrench-turning and operator level, where consequences were immediate and systems knowledge was earned in the aircraft. I spent 22 years in naval aviation as a mechanic, Flight Engineer, instructor, and operational leader, logging more than 6,000 flight hours on P-3 Orion and C-130 aircraft.
I later moved into flight test, maintenance leadership, technical data, fleet support, and program readiness on major aerospace programs. The altitude changed, but the operating problem stayed remarkably consistent: capable but siloed functions often execute well individually while the enterprise struggles to integrate them around one executable readiness plan. This is the white space I operate in.
That is the work I do now. I expose dependencies early, clarify ownership, create operating models, establish readiness criteria, and build the procedures and feedback loops that make the next deployment more repeatable than the first. I am also applying that same systems mindset to software and product development focused on field operations intelligence.
I am applying three decades of operator, maintainer, flight-test, and program leadership experience to a simple problem: how do we capture what field teams know, connect it to what systems are doing, and turn that knowledge into better operational decisions?
If you are moving complex hardware from development into field execution, standing up a new operating function, or trying to make cross-functional readiness visible and accountable, that is a conversation I am always interested in having.