Background and Context
The scene is a helicopter climbing out of the air it was designed for. Two men are aboard; one is flying and one is reading the altitude aloud as the numbers go past. There is no enemy, no cargo, and no one waiting at the top. The aircraft begins to lose its grip on the thin air, the pilot brings it back down into atmosphere thick enough to hold it, and only then does the other man ask what that was for.
The decade this belongs to had an appetite for the singular machine — one object, better than anything else of its kind, in the hands of a man who did not want to give it back. The series states its own version of the underlying problem in its premise, and states it more sharply than the genre usually manages: an intelligence agency builds the most capable aircraft anyone can build, and only afterward discovers that it has no way to control the man who designed it. Whether the thing could be made was settled a long way upstream of any question about what it was for. The climb in this episode is that premise performed small, by two men, for nobody, with the argument left out.
Interpretation
The sentence has no object in it. There is no summit, no altitude, no view, no record, and no adversary — nothing the speaker went and got. What the sentence describes is the closing of a question, and the question is named in the most reduced form available: whether it could be done. Not how well, not how often, not at what cost. A yes or a no.
That reduction is what makes the motive unusual, and two properties follow from it that do not follow from ordinary reasons for doing difficult things.
The first is that a feasibility motive is self-consuming. Most reasons survive being satisfied. A man who climbs for the view can climb again tomorrow and get the view again; a man who climbs to be good at climbing gets better each time and still wants the next one. But a man who climbs to find out whether the thing can be climbed has, on reaching the top, destroyed the only reason he had. The want is reported in the past tense here, and the tense is doing real work — wanted, not want. By the time the question is asked in the cockpit, the motive that produced the climb has already ceased to exist. It did not fade or get satisfied in the way appetites are satisfied. It was answered, which is a different and more final thing.
The second property is that the answer is non-transferable in one direction only. Once the question is closed, it is closed for everybody. The knowledge that the thing can be done is now loose, free, and available to people who did none of the work and took none of the risk; the second person to do it will not be finding anything out. This is the peculiar economics of a first. The doer keeps nothing that everyone else does not also receive, except the fact of having been the one — which is a claim about biography, not about the world, and is precisely the claim the sentence declines to make.
Put those two together and the escalation that tends to follow this kind of person stops looking like restlessness or vanity and starts looking like arithmetic. If the motive is destroyed by being satisfied, and the answer it produced is now common property, then the only way to have that motive again is to find a question that has not been answered — which means a harder one. Nothing about the person needs to be diagnosed to predict this. It is a consequence of the shape of the reason, and it would be true of a modest person and an arrogant one alike.
There is one more thing the sentence does, and it does it by omission. It offers no account of why the thing was worth finding out. It does not claim the answer will be useful, that anyone needed it, or that the world is better for having it. The whole justification is that a question was open and now is not. That is either the most honest thing a person in that seat can say or the most complete evasion available to them, and the sentence is built so that it cannot be told which.
Current Relevance
The demonstration has quietly become the dominant form of technical achievement. Not the product, not the deployment — the demonstration: the run that establishes the thing is possible, performed in advance of any decision about whether it ought to exist. A working proof of concept is now the standard opening move in software, in biology, in materials, in weapons, and the sequencing is nearly always the same. Feasibility is settled first, and the argument about desirability happens afterward, in a world where one side of it has already been conceded.
What makes this consequential is that a demonstration is irreversible in a way an artifact is not. A machine can be dismantled and a program can be deleted; the knowledge that the approach works cannot be withdrawn. Every subsequent attempt begins from a strictly better position than the first one did, because the hardest thing the first attempt supplied was not a technique but the confidence that the technique exists to be found. That is why the person who answers a feasibility question is doing something categorically different from the person who then exploits the answer, and why the first one is so often the one who feels least implicated.
The change since 1984 is in the length of the interval. A demonstration used to be private and slow: someone found out, and there was a stretch of time — sometimes years — in which a small number of people knew, and could argue about what to do with knowing. Publication was a decision, and it was separable from the discovery. That interval has now collapsed to roughly nothing. A result is a post; the finding out and the telling are one act, and whoever found out has published before deciding to. The consequence worth naming is not that things move fast. It is that the demonstrator has been relieved of a decision he used to be required to make — what to do with knowing — and the relief is invisible to him, because a decision nobody is asked to make does not feel like a decision that was taken away. Publication holds, staged disclosure, and review before release all try to hand it back by policy, and their proponents are routinely accused of obstructing science by people who are, quite genuinely, not aware there was ever a second step.
Impact and Legacy
The most legible thing this line did, it did to the series that contains it. Airwolf began as a dark, arc-driven Cold War drama in which the helicopter was genuinely frightening — a machine whose designer had turned out to be a murderer and whose recovery left it in the hands of a man who would not give it back. The aircraft's published ceiling in the first season was 89,000 feet pressurized. By the third season it was 100,000. The network had by then asked for something lighter and more family-shaped, and got it.
Having established at 86,000 feet that the thing could be done, the series could not go back to 86,000 feet for the same effect, so it went higher, and then higher, until the escalation stopped meaning anything. By the fourth season, moved to cable and rebuilt with a new cast on less than a third of the original budget, it no longer had access to the helicopter at all and was assembling its flight sequences out of footage shot years earlier. A show about a machine that could always do one more thing ended by replaying the things it had already shown, because there were no new ones to make.
The wider legacy belongs to the sentiment rather than to the line, and the sentiment's most famous statement is not Hawke's. It is Oppenheimer's, testifying in 1954: when you see something that is technically sweet, you go ahead and do it, and you argue about what to do about it only after you have had your technical success — that, he said, was the way it was with the atomic bomb. Same claim, made by a man who had watched the arguing-afterward actually take place and knew exactly what it had been worth. Hawke's version carries none of that, which is why it is the more commonly held of the two: it is the creed as it sounds before anything has gone wrong with it.
Contrasting Views or Controversies
A feasibility question can almost never actually be closed. "Could it be done" is not asked in the abstract; it is asked under conditions — this aircraft, this day, this crew, this much fuel — and the answer applies only to those. The question immediately afterward is whether it can be done twice, or reliably, or by somebody ordinary, or without the part that nearly went wrong. Airwolf itself went back to that regime in a later episode. On this account the escalation needs no arithmetic of exhausted motives at all: it is what refinement always looks like, the same question asked at a tighter tolerance, and it describes ordinary engineering rather than anything about the person doing it. What that account leaves unexplained is why the refinement so reliably has to be dramatic rather than incremental — why the next question is a harder one rather than a more careful one. Ordinary engineering tightens tolerances. It does not, as a rule, go looking for a bigger number.
A blunter objection is that the epistemic framing flatters what is really an appetite. Psychology has a well-measured trait for people who seek intense and novel physical sensation and tolerate risk to obtain it, and it predicts exactly this behavior without reference to questions, answers, or knowledge at all. On that account the man in the cockpit wanted the sensation of the climb, got it, and produced afterward the most creditable available account of why — one that recasts a physiological appetite as an intellectual project. This is a serious objection because it explains the same conduct more cheaply, and because the sentence's dignity is precisely what it predicts: nobody says I wanted the feeling of it, and everybody says they wanted to know. What it does not explain is the specificity of the reduction. An appetite for sensation is indifferent to whether the thing has been done before, and this motive is not — it is destroyed by the answer being already available, which no account of arousal-seeking predicts or needs.
The moral objection is the one most often made and the one that lands least cleanly. "I wanted to see if it could be done" is the standard alibi of consequence-free curiosity, offered by people who have made something that then went on to do harm, and its charm is a large part of why it works — it sounds artless, and artlessness reads as innocence. But the alternatives are worse. The person who answers this question with an invented mission rationale, a market, or a public good is not more accountable than the one who says plainly that he wanted to know; he has simply moved the same act behind a justification that can be argued with. What the sentence withholds is not honesty. It is any claim that the answer was worth having, and its refusal to make that claim is the most defensible thing about it.
Practical Application
- When your own reason for something is that you want to know whether it is possible: say so, at least to yourself, and expect the reason to be gone the moment you have the answer. What people usually experience at that point is a flatness they mistake for disappointment in the achievement. It is not that. It is the ordinary sensation of a motive having been spent, and it arrives on schedule whether the attempt succeeded or failed.
- When you are responsible for someone who runs on this motive: do not try to attach them to outcomes. The motive does not bind to outcomes and never has, and a person managed as though it does will read every conversation about impact as a request to become someone else. What holds them is being pointed at things nobody has settled yet, and an organization that has stopped generating those will lose the person long before it understands that it has done anything.
- When deciding whether to run a demonstration: treat the demonstration as the irreversible act, not the thing demonstrated. The decision that matters is the decision to find out, because it cannot be taken back, and it is routinely made at a level far below the one where the consequences will be handled. An organization that reviews deployments and not feasibility work is reviewing the second decision and has already lost the first.
- When you are the public a demonstration is aimed at: notice what is actually being asked of you. A capability demonstration is not evidence that the capability should exist; it is evidence that somebody already decided to find out, at a point long before the thing became visible enough for anyone outside to object. By the time a public gets a vote, it is voting on deployment, which is the second decision — and the interval in which the first one could have been contested has usually been closed by the same publication reflex that made the demonstration visible at all. The civic question worth pressing is not whether the demonstrated thing is good. It is who was positioned to say no while the question was still open, and whether that list has anybody on it who does not work for the people asking.
Background on the Author
Burton Armus spent twenty years in the New York City Police Department and began writing for television in the middle of them. He was with the 48th Squad in the Bronx when the producers of N.Y.P.D. hired him as a technical adviser in 1967 and he wrote an episode for them; Telly Savalas later picked him to advise on Kojak, work he was doing from inside the job. He retired from the department in 1976 and moved to Los Angeles to write full time, turning up across the mid-eighties machine shows — Airwolf, Knight Rider, Street Hawk — and later on Star Trek: The Next Generation and NYPD Blue. This episode comes eight years after the shield went into the drawer.
Twenty years on the job is twenty years of asking people why they did something and then living with the answer they actually give. The answers are usually short. They are frequently true. They almost never explain anything, because a real motive stated plainly tends to sound insufficient for what it produced, and the gap between the two is where the rest of the work happens. A line whose whole interest is that it answers the question completely and settles nothing is written by somebody with a great deal of practice in the difference.
The series around it belongs to Donald P. Bellisario, who created Airwolf and wrote and directed its pilot. He had served four years in the Marine Corps, leaving as a sergeant, before advertising and then television, and his body of work — Magnum, P.I., Quantum Leap, JAG, NCIS — returns steadily to competent men and the equipment they are trusted with. The premise he built supplies the line's frame: a machine constructed because it could be, by a designer who then could not be trusted with it, and inherited by a pilot who keeps it partly because he will not hand it over.