US20120068002A1

US20120068002A1 - Guided missile

Info

Publication number: US20120068002A1
Application number: US12/781,868
Authority: US
Inventors: Michael P. Unger; Stephen D. Witherspoon; James T. Schleining
Original assignee: Raytheon Co
Current assignee: Raytheon Co
Priority date: 2009-05-19
Filing date: 2010-05-18
Publication date: 2012-03-22
Also published as: WO2011019424A2; EP2433084A2; WO2011019424A3; EP2433084B1

Abstract

A missile (10) comprising a projectile body (20), a payload (60) contained within the nose portion (30), wings (70) stowed within the mid portion (40), and fins (80) stored within the tail portion (50). The wings (70) can be deployed during intermediate stages of the flight path when lift is advantageous, and re-stowed during terminal stages when an almost vertical angle-of-attack is desired. The fins (80) function as stabilizing components during the early ballistic stage of the flight path and function as guiding components thereafter.

Description

This application claims the benefit under 35 USC 119 to U.S. Provisional Application No. 61/179,391, filed May 19, 2009, which is incorporated by reference in its entirety.

FIELD

A guided missile having a projectile body and aerodynamic surfaces that stabilize, guide, and/or lift the projectile body during various stages of a flight path.

BACKGROUND Range (e.g., 25 nautical miles), accuracy (e.g., within 10 meters of identified target), and effectiveness (e.g., greater than 99% lethality), are usually considered key performance parameters when designing a guided missile. In other words, these parameters cannot be compromised in the interest of reduced costs, manufacturing reliability, and/or simplified structure. Moreover, these key factors need to be balanced within a missile design to insure that all three are optimized. For example, while range can be prolonged by faster muzzle velocity, the resulting increased setback acceleration can negatively impact crucial instrumentation and thereby shortchange accuracy and/or effectiveness.

A missile also often inherits other variables that afford little or no liberties during design development. For example, the projectile body usually must have a size/shape to accommodate an intended artillery platform and/or gun barrel (e.g., 155 mm diameter and 1 m length). And if a missile includes a payload (e.g., a warhead), its size, shape, and/or weight are almost always dictated primarily by mission objectives.

SUMMARY

A missile design is provided that reduces costs, increases reliability, and/or simplifies structure without compromising key performance parameters. Range performance is achieved by enhanced acceleration capability and improved lift-to-drag ratio, not faster muzzle velocities and/or greater launch charges. In this manner, setback acceleration is decreased, whereby the missile's instrumentation can reside in a less reliability-threatening environment. And, thanks to lower launch loads, the missile's structural-strength requirements can be relaxed.
The missile achieves its enhanced-acceleration feature by combining the functionality of certain aerodynamic surfaces. Specifically, the missile comprises tail fins that perform a stabilizing function during the just-launched stage of the flight path and perform a guiding function during post-ballistic stages of the flight path. And the missile achieves its improved-lift feature by a pair of wings that are deployed from a mid portion of the projectile body. By controlled maneuvering of the wings and the fins, the missile can cruise during an apogee stage, precisely adjust direction during a midcourse trajectory stage, and/or situate itself for a near vertical angle-of-attack during terminal trajectory.
The missile can be constructed to have a conventional projectile-body shape) and to carry a payload adequate for most mission objectives. For example, the projectile body can have a diameter (e.g., 155 mm) and length (e.g., 1 m) compatible with current and future artillery platforms and/or howitzers. And the missile can provide accurate, first round fire-for-effect capacity.
According to an aspect of the invention, a missile includes: a projectile body having a fore-aft axis and comprising a nose portion, and a mid portion aft of the nose portion, and a tail portion aft of the mid portion; a bearing coupler within the projectile body allowing at least a part of the tail portion to rotate freely relative to the mid portion about the fore-aft axis; a clutch within the projectile body that engages/disengages to selectively allow/prevent tail rotation; wings, stowed within pockets in the mid portion, each having an airfoil and a leading edge; a deployer, within the mid portion, that selectively deploys the wings from the pockets to deployed positions whereat their leading edges extend radially outward from the aft-fore axis in lift-imparting orientations; fins stored within slots the tail portion and biased to extend radially outward from the aft-fore axis with their leading edges in roll-stabilizing orientations; an obturator maintaining the fins within the slots; and a deflector that deflects the fins from their roll-stabilizing orientations to angularly align their leading edges relative to the aft-fore axis in direction-controlling orientations.
According to another aspect of the invention, a missile includes: a projectile body having a fore-aft axis and comprising a nose portion, and a mid portion aft of the nose portion, and a tail portion aft of the mid portion; a bearing coupler within the projectile body allowing at least a part of the tail portion to rotate freely relative to the mid portion about the fore-aft axis; a clutch within the projectile body that engages/disengages to selectively allow/prevent rotation of the at least part of the tail portion; wings, stowed within pockets in the mid portion, that extend to deployed positions outside of the projectile body; and fins stored within slots in the at least part of the tail portion, wherein the fins are biased to extend radially outward in roll-stabilizing orientations.
According to still another aspect of the invention, a method of missile flight includes the steps of: launching a missile from a launch unit; deploying fins of the missile; during an initial roll-stabilized flight regime, allowing free rotation of a tail of the missile that includes the fins; and after the roll-stabilized flight regime, engaging a clutch of the missile to prevent tail rotation.
These and other features of the missile are fully described and particularly pointed out in the claims. The following description and annexed drawings set forth in detail certain illustrative embodiments, these embodiments being indicative of but a few of the various ways in which the principles may be employed.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is schematic diagram of a mission wherein a missile is launched and then guided to encounter a target.

FIGS. 2A-2C are side, top, and aft schematic views of a missile having wings deployed in an aft direction.

FIGS. 3A-3C are side, top, and aft schematic views of a missile having wings deployed in a fore direction.

FIG. 4 is a schematic diagram of a controller of the missile.

DETAILED DESCRIPTION

Referring now to the drawings, and initially to FIG. 1, a missile 10 is shown in a military setting as it follows a flight path from a launch unit 11 to a target 12. The launch unit 11 can comprise a howitzer 13, or other gun or cannon, having conventional specifications and/or capabilities. For example, muzzle velocity can be 700-1000 m/s and the launch acceleration can be 8-15K.
The illustrated flight path includes a just-launched stage (immediately after exit from the howitzer 13) and post-launch stages thereafter. The post-launch stages include a ballistic stage (determined primarily by muzzle velocity and launch angle), an apogee stage (upon reaching a cruise elevation), a mid-course trajectory stage (optimized for target range/arrival), and a terminal trajectory stage (optimized for target impact). Other flight paths are possible and contemplated. For example, if the missile 10 was on a battle-damage-assessment or other information-collecting mission, the flight path may not includes the latter trajectory stages.
The missile's pursuit of the target 12 can be collaborated by other manned and unmanned units, such as a remote command unit 15, a field intelligence unit 16, and/or a global-positioning-system unit 17.
Referring now to FIGS. 2A-2C and/or FIGS. 3A-3C, the missile 10 is shown in more detail. The missile 10 comprises a projectile body 20 having a generally cylindrical shape with a fore-aft axis 21. The projectile body 20 can be shaped/sized to accommodate a conventional launch unit (e.g., launch unit 11). For example, the projectile body 20 can have a diameter of 155 mm and a length of 1-3 meters (e.g., 1 m, 1.55 m, 2.25 mm, etc.).
The projectile body 20 comprises a nose portion 30, a mid portion 40 aft of the nose portion 30, and a tail portion 50 aft of the mid portion 40. The nose portion 30 can comprise a payload chamber 31 occupying most of its interior space. The mid-portion 40 comprises diametric wing slots 41 and can comprise instrument bays 42 occupying the space around the slots 41.
The tail portion 50 can comprise a base part 51, a retainer part 52, a bearing coupler 53, and a clutch 54. The base part 51 can be fixedly mounted to the mid portion 40 and the retainer part 52 attached to the base part 51 by the bearing coupler 53. The retainer part 52 includes radial slots 55 (e.g., four) spaced circumferentially around its outer surface.
The bearing coupler 53 allows the retainer part 52 to rotate freely relatively to the base 51 (and/or the mid portion 40) about the fore-aft axis 21. The clutch 54 can be engaged-disengaged to allow-prevent tail rotation. In an alternative design, the entire tail portion 50 could be coupled to the mid portion 40 by the bearing coupler 53, whereby it would constitute the retainer part 52. In either event, at least part of the tail portion 50 can rotate freely relative to the mid portion 40. The retainer part 52 includes (has in it) the slots 55.
The missile 10 can comprise a payload 60, contained within the chamber 31 in the nose portion 30. In a military setting, such as illustrated, the payload 60 could comprise a warhead (e.g., destructive munitions). The nose portion 30 and/or the chamber 31 can include other objects or devices, such as communication/guidance gear for actively or passively interacting with remote units 11, 15, 16, and/or 17.
The missile 10 further comprises wings 70 and fins 80. In FIG. 2A and FIG. 3A, the wings 70 are shown stowed within the pockets 41 in the mid portion 40 and the fins 80 are shown stored within the slots 55 in the tail portion 50. In FIGS. 2B-2C and FIGS. 3B-3C, the wings 70 are shown in deployed positions and the fins 80 are shown in released conditions.
The wings 70 each comprise an airfoil 71 having a leading edge 72. A wing deployer 73 within the mid portion 40 is operative to deploy the wings 70 from their stowed positions (FIG. 2A and FIG. 3A) to their deployed positions (FIGS. 2B-2C and FIGS. 3B-3C.) In the stowed position, the wings' leading edges 72 are aligned substantially parallel with the fore-aft axis 21. In the deployed positions, the wings' leading edges 72 extend radially outward from the fore-aft axis 21 in lift-imparting orientations.
The wings 70 can comprise arms 74 connected to their inboard edges and the wing deployer can comprise a rod 75 to which the distal ends of the arms 74 are pivotally attached. As shown in FIGS. 2A-2C, the rod 75 can be located in an aft region of the mid portion 40, and the wings 70 can symmetrically move in the aft direction to deploy from the pockets 71. Alternatively, as shown in FIGS. 3A-3C, the rod 75 can be located in a fore region of the mid portion 40, and the wings 70 can symmetrically move in the fore direction to deploy from the pockets 71. In either or any event, the deployed position of the wings 70 can be rigid whereby their leading edges 72 remain at a constant deflection angle relative to the fore-aft axis 21.
The fins 80 each comprise an airfoil 81 having a leading edge 82. An obturator 83 maintains the fins in their stored condition (FIG. 2A and FIG. 3A) until muzzle exit and releases them upon muzzle exit for movement to their released conditions (FIGS. 2B-2C and FIGS. 3B-3C.) The obturator 83 is designed to break, fracture, or otherwise destruct to release the fins 80 during the just-launched stage of the flight path. Preferably, the obturator 83 is located towards the aft end of the tail portion 50, to protect the fins 80 during firing and/or reduce pressure on protective covers (not shown).
When the fins 80 are in released conditions, their leading edges 82 extend radially outward from the aft-fore axis 21 in roll-stabilizing orientations. A fin deflector 84, within the tail portion 50, is operative to deflect the fins 80 from their roll-stabilizing orientations to angularly align their leading edges 82 relative to the aft-fore axis 81 in direction-controlling orientations.
The missile 10 can further comprise a controller 90, such as schematically shown in FIG. 4. The controller 90 can comprise, for example, an output panel 91 that conveys control signals to the clutch 54, the wing deployer 73, and the fin deflector 84. The illustrated controller 90 also comprises an input panel 92 that receives information from onboard sensors, a GPS receiver 93, a collector 94, a command-unit receiver 95, a command-unit transmitter 96, a processor 97, and memory/storage 98. The controller 90 can be housed within the instrument bay 42 in the mid portion 40 and/or it can be powered by a battery 99 also housed within the instrument bay 42.
Prior to launch of the missile 10, the wings 70 would be stowed within the mid portion 40, the fins 80 would be stored within the tail portion 50, and the obturator 83 would be intact. As the missile 10 exits the gun muzzle, the obturator 83 would release the fins 80 and they would move to released conditions whereat their leading edges 82 are in roll-stabilizing orientations. The clutch 54 would be disengaged, thereby allowing tail rotation during the ballistic stage of the path flight. The clutch 54 would remain disengaged, the wings 70 would stay in stowed positions, and the fins 80 would maintain roll-stabilizing orientations until the missile 10 reached the apogee stage of the flight path.
Upon reaching the apogee of the ballistic stage of the flight path, the controller 90 can begin its contribution to the flight path. Specifically, the controller 90 can be programmed to send control signals (via its output panel 91) to the deployer 73 to deploy the wings 70. The wings 70 can be adapted to impart substantial lift to the projectile body 20, with little or no steering or guiding responsibilities. To this end, the tip-to-tip span of the wings 70 can be greater (e.g., 50% greater, 75% greater, 100% greater, 150% greater, and/or 200% greater) than the tail span of the fins 80. And, as indicated above, the wings' leading edge 72 can rigidly remain at a constant angle relative to the fore-aft axis 21.
During the apogee stage of the flight path, the clutch 54 can be engaged to prevent tail rotation. And the controller 90 can signal the fin deflector 84 to deflect the fins' leading edges 82 in particular direction-determining orientations. Preferably, the fins 80 and/or the deflector 84 are designed to deflect in a multitude of orientations (about a plurality of axes) for optimum guidance of the missile 10.
As the missile 10 approaches the target 12, and begins the midcourse trajectory stage of the flight path, the wings 70 can remain deployed or be returned to stowage (depending upon descent angle). And the fins 80 can continue to be maneuvered to direct the missile 10 towards the target 12. The wings 80 can be returned to stowed positions (if not already there) during the terminal trajectory stage, to allow a near vertical angle of attack.
The controller 90 can ascertain the missile's stage in the flight path in a variety of ways. For example, the controller 90 can continuously obtain the missile's current global position (via its GPS receiver 93) and compare this to previously input positions (e.g., input prior to launch). Flight path stages can be ascertained by the altitude of the missile 10 and/or predetermined period of times. If the missile 10 and/or the controller 90 are equipped with target-seeking instrumentation (e.g., the collector 94), visual data concerning the target 12 can be used for this purpose. And/or a remote unit, such as the command unit 15, can receive data from and/or convey instructions to the controller 90 (e.g., via receiver 95 and transmitter 96).
One may now appreciate that the missile 10 has design that reduces costs, increases reliability, and/or simplifies structure without compromising key performance parameters. With particular reference to the fins 80, they function both as stabilizing components during the ballistic stage of the flight path and later as guiding components during post-ballistic stages of the flight path. This combined functionality removes the need for canards or other separate guiding components. Such a canard-less design, especially with a fore-stored payload, frees up space in the mid portion 40 for the relatively large wings 70 which provide additional lift/acceleration capability and an improved lift-to-drag ratio.
Although the missile 10 has been shown and described with respect to a certain embodiment or embodiments, it is obvious that equivalent alterations and modifications will occur to others skilled in the art upon the reading and understanding of this specification and the annexed drawings. In regard to the various functions performed by the above described elements (e.g., components, assemblies, systems, devices, compositions, etc.), the terms (including a reference to a “means”) used to describe such elements are intended to correspond, unless otherwise indicated, to any element which performs the specified function of the described element (i.e., that is functionally equivalent), even though not structurally equivalent to the disclosed structure which performs the function. In addition, while a particular feature of the invention may have been described above with respect to only one or more of several illustrated embodiments, such feature may be combined with one or more other features of the other embodiments, as may be desired and advantageous for any given or particular application.

Claims

What is claimed is:

1. A missile comprising:

a projectile body having a fore-aft axis and comprising a nose portion, and a mid portion aft of the nose portion, and a tail portion aft of the mid portion;

a bearing coupler within the projectile body allowing at least a part of the tail portion to rotate freely relative to the mid portion about the fore-aft axis;

a clutch within the projectile body that engages/disengages to selectively allow/prevent rotation of the at least part of the tail portion;

wings, stowed within pockets in the mid portion, that extend to deployed positions outside of the projectile body; and

fins stored within slots in the at least part of the tail portion, wherein the fins are biased to extend radially outward in roll-stabilizing orientations.

2. A missile as set forth in claim 1,

further comprising a controller;

wherein the controller is programmed to control the clutch to prevent tail rotation upon reaching a fin-guiding stage of the flight path.

3. A missile as set forth in claim 1,

further comprising a controller;

wherein the controller is programmed to control a deployer to deploy the wings upon reaching a wing-deploying stage of the flight path.

4. A missile as set forth in claim 3, wherein the controller is programmed to control the deployer to return the wings to the pockets upon reaching a large angle-of-attack stage of the flight path.

5. A missile as set forth in claim 2, wherein the controller is programmed to control a deflector to deflect the fins in different angular alignments whereat their leading edges are in direction-controlling orientations.

6. A missile as set forth in claim 1, wherein the tip-to-tip span of the wings is greater than the tail span of the fins.

7. A missile as set forth in claim 1, wherein the tip-to-tip span of the wings is at least 50% greater than the tail span of the fins.

8. A missile as set forth in claim 1, wherein the projectile body has a diameter of less than 160 mm and a length less than 3 m.

9. A missile as set forth in claim 1,

further comprising an obturator on an aft end of the fuselage;

wherein the obturator protects the fins during launch of the missile.

10. A missile as set forth in claim 1,

further comprising a deployer, within the mid portion, that selectively deploys the wings from the pockets to deployed positions.

11. A missile as set forth in claim 10,

wherein the deployer includes a rod;

wherein the wings each include an arm having one end connected to the airfoil and another end pivotally connected to the rod; and

wherein the wings pivot in an aft direction when moving from the pockets to their deployed positions.

12. A missile as set forth in claim 10,

wherein the deployer includes a rod;

wherein the wings pivot in a fore direction when moving from the pockets to their deployed positions.

13. A missile as set forth in claim 1, further comprising a deflector that deflects the fins from their roll-stabilizing orientations to angularly align their leading edges relative to the aft-fore axis in direction-controlling orientations.

14. A method of missile flight, the method comprising:

launching a missile from a launch unit;

deploying fins of the missile;

during an initial roll-stabilized flight regime, allowing free rotation of a tail of the missile that includes the fins; and

after the roll-stabilized flight regime, engaging a clutch of the missile to prevent tail rotation.

15. A method as set forth in claim 14, further comprising deploying wings of the missile during flight.

16. A method as set forth in claim 15, wherein the deploying the wings occurs after the beginning of the roll-stabilized flight regime, and before the conclusion of the roll-stabilized flight regime.

17. A method as set forth in claim 15, further comprising, after the deploying the wings, stowing the wings while the missile is still in flight.

18. A method as set forth in claim 14, further comprising deflecting leading edges of the fins using a deflector of the missile.

19. A method as set forth in claim 18, wherein the deflecting includes deflecting the leading edges in order to change course of the missile.

20. A missile comprising:

a clutch within the projectile body that engages/disengages to selectively allow/prevent tail rotation; wings, stowed within pockets in the mid portion, each having an airfoil and a leading edge;

a deployer, within the mid portion, that selectively deploys the wings from the pockets to deployed positions whereat their leading edges extend radially outward from the aft-fore axis in lift-imparting orientations;

fins stored within slots the tail portion and biased to extend radially outward from the aft-fore axis with their leading edges in roll-stabilizing orientations; an obturator maintaining the fins within the slots; and

a deflector that deflects the fins from their roll-stabilizing orientations to angularly align their leading edges relative to the aft-fore axis in direction-controlling orientations.