Fighter File
F-401 “Slicer”
The current line of Federation naval fighters, and the first aircraft in service able to fight in vacuum and atmosphere without compromise. Designed by Johnathan E. Henderson as an academy class project.
Registry Summary
Design Lineage
The Navy operated two fighters, each excellent in one environment and useless in the other. The F-401 was Henderson’s answer to both.
F-201
An excellent aerial fighter. Performed poorly in space.
F-301
The opposite. An excellent space superiority fighter that could not maneuver in an atmosphere.
F-401
Both. The Navy no longer has to choose which fighter to embark. She is also, by every pilot account, hard to adapt to.
Note on the designer. The Slicer and the WarpStar were both academy work by the same man. Only one of them went into mass production, and it was not the starship.
Airframe
The Slicer is named for her shape, and for her ability to slice her way through an atmosphere. Three major sections, all shaped aerodynamically so the airframe works in air and in vacuum.
Cockpit
The F-401 was the first fighter ever produced without a viewport.
An artificial view is superimposed on the HUD in front of the pilot, reproducing what a pilot would otherwise see through glass. The reason is structural. A canopy is weaker material, and the Slicer does not carry any.
This is the hardest thing about the aircraft. The 401 is a technological marvel and it is difficult to adapt to, and the missing window is most of why.
Pilot Load
Warning. Federation fighters carry no inertial compensation of any kind. High-G maneuvering has direct physiological consequences, and a braking burn is survivable only within limits set by the pilot’s body, not the airframe’s. A flight plan the fighter can survive is not necessarily one the pilot can.
Combat Doctrine
The manned fighter is not the Navy’s primary strike element, and the reason is worth stating plainly.
Coordination limit
Fighters can only coordinate effectively within a few light-seconds of their carrier. Most fighting happens further out than that.
No fire-control brain
Fighters lack the combat computers larger ships carry. Calculating a target’s trajectory, speed, and distance is near impossible from the cockpit.
Verdict
For general space use, fighters by themselves are near useless.
The answer is the assault Corvette. Corvettes are the control point for the modern fighter arm, deployed from Capital ships down to Battleships.
Destroyers carry no Corvettes. A destroyer is maneuverable enough to serve as the control point herself, so the Corvette layer is skipped entirely.
Why the Manned Fighter Still Exists
Drones cannot enter planetary atmospheres.
That single limitation is why the F-401 is aboard every starship fitted with a fighter bay. When the fight goes into air, the drones stop being an option and a human has to fly.
The Slicer is the only Federation fighter that can do both, which is precisely why she is the one they keep.
X-401 — Experimental Variant
Betsy. A prototype artificial intelligence unit installed in a modified 401 airframe. Henderson wrote the software governing her. Charlene Carr programmed the combat maneuvers, tactics, and behavioral traits, with the stated intent that Betsy would learn and become a better pilot.
Betsy is identified on sensors by her own EM signature and returns to the ship under her own control. She is also recorded under the name Betsy Ross.
Archive Assessment
The F-401 is the rarest thing in the Federation inventory: a piece of Henderson engineering that actually got built in numbers.
She solved a problem the Navy had accepted as permanent, that a fighter is either an aircraft or a spacecraft and cannot be both. She did it by giving up the one thing every pilot expected to have, which was a window.
Her real significance is doctrinal. In a fleet that fights with drone swarms directed from corvettes, the Slicer is the exception that puts a person back in the cockpit. She exists for exactly one reason. There is still air on some worlds, and drones cannot fly in it.
Return to Archive
Continue through the Fleet Registry or return to the wider Codex archive.