Showing default

OTV 5 (USA 277), 42932

Orbit data source: Public

OTV 5 (USA 277), 42932 is a payload satellite owned by AF RCO (US) that was launched on Thu, 07 Sep 2017 UTC via an FALCON 9 launch vehicle from the Air Force Eastern Test Range (AFETR). Payload-class satellites include a variety of spacecraft equipped with specific instruments for various scientific and technological missions. These include communications satellites like Starlink; space stations such as the ISS; scientific satellites like the Hubble; Earth observation satellites from companies like Planet Labs, Umbra, and HawkEye 360; GPS; miniature CubeSats for education and research; and military/defense satellites.

Not visible in the next 10 days

Iframe embed code

<iframe src="https://www.satcat.com/sats-embedded/42932?theme=dark&initialShowStats=false" width="600" height="400" frameborder="0" title="Kayhan Space Satcat Satellite Viewer"></iframe>

Iframe URL

https://www.satcat.com/sats-embedded/42932?theme=dark&initialShowStats=false

Optional Secondary NORAD IDs

Max 10 NORAD IDs; Separated by commas

Initial load time (optional)

ISO8601 Format

TLE date request (optional)

ISO8601 Format

Identifier

42932, 2017-052A

Orbit

Unknown

Last TLE update

Unknown

Origin

United States Air Force (US)

Manufacturer

Boeing/HB

Mission

Decayed Defense Classified

Bus & Motor

X-37, AOCS

Mass

~5,000 kg wet, ~5,000 kg dry

Launch date (UTC)

2017-09-07 (8 years ago)

Launch vehicle

FALCON 9

Launch site

Air Force Eastern Test Range (AFETR)

Object type

Payload

Rocket body

Debris

Shape & HBR

Half Cyl + 2 Wing, 8.92 m

Radar Cross Section

18.277 m²

Expand to show TLE details & history

Historical TLE search

Format must be ISO8601 or YYYY-MM-DD

Definitive object data

Latitude

Unknown

Longitude

Unknown

Altitude

Unknown

Speed

Unknown

True Right ascension

Unknown

True Declination

Unknown

Sunlit

N/A

Visualization observer readout

Observer readout values are unavailable because the object's trajectory could not be propagated. This is usually caused when the trajectory data is faulty or the object's orbit has decayed.

Visualization observer readout

Observer readout values are unavailable because the object's trajectory could not be propagated. This is usually caused when the trajectory data is faulty or the object's orbit has decayed.