- Communications satellite
- Military
- OPS 6392 (FLTSATCOM 2)
- NORAD 11353
- 1979-038A
- Inclined geosynchronous
Current orbit
View on live mapOrbit began over the Pacific Ocean
Orbit ends over the Pacific Ocean
In view from you
Nobody watches FLTSATCOM F2 go over, but a receiver still asks whether it is above the horizon. Say where you are and this card answers.
Your position is rounded to about a kilometre and sent only to the Orbinauts API, to find the pass.
No brightness has been published for FLTSATCOM F2, so it is not a naked-eye satellite and no city page carries pass times for it. Nothing here estimates one.
Seeing it
There is nothing to go outside for: it is too faint for the naked eye. What reaches you from it reaches a dish or an antenna, not an eye.
Timeline
- Launch
Launched, on the day GCAT records. Source
Summary
Over the Pacific Ocean LIVE
Where is FLTSATCOM F2?
At 6:21:06 PM UTC FLTSATCOM F2 was over the Pacific Ocean (6.8° S, 88.2° W), 36,328 km up, moving at 3.05 km/s and in sunlight.
What is FLTSATCOM F2?
A communications satellite in an inclined geosynchronous orbit, in space since May 4, 1979.
Can I see FLTSATCOM F2?
No, not with the naked eye: no brightness has been published for FLTSATCOM F2, and nothing here estimates one; the dishes and receivers on the ground use its signals instead.
General
- Operator
- Navy Electronic Systems Command
- State
- United States of America
- Built by
- TRW Inc.
- What it is
- Communications satellite
- Military
- Yes: a defence organisation flies it
- Launched
- Mass
- 942 kg
- Operating
- Orbit class
- Inclined geosynchronous
From GCAT, Jonathan McDowell’s general catalogue, licensed CC BY 4.0: the operator, the state, the manufacturer, what it is for, that a defence organisation flies it, the launch day, the mass, and whether it is operating. The orbit class is read from its current elements.
Latest orbital data
- Position received
- 6:21 PM UTC
- Station time (UTC)
- 6:21 PM UTC
- Latitude / longitude
- 6.8° S, 88.2° W
- Altitude
- 36,328 km
- Speed
- 3.05 km/s (10,991 km/h)
- Course
- north
- Light
- In sunlight
- Inclination
- 7.4°
- Orbital period
- 1,461.3 minutes
- Orbits per day
- 0.99
- This orbit
- 36,221 to 36,337 km
- In shadow
- None of this orbit
- In view from
- Within 7,960 km of the point below it
- Elements epoch
- Nov 8, 2026, 12:17 AM, 18 hours old
- Source
- Position from Space-Track orbital elements of Nov 8, 2026, 12:17 AM, 18 hours old.
No operator publishes an ephemeris for FLTSATCOM F2, so every position here comes from its orbital elements.
In orbit
- Close approaches
- No close approach to FLTSATCOM F2 has been reported publicly in the past thirty days.
From Space-Track’s public conjunction messages; the latest report was issued Nov 8, 2026, 1:11 PM, 3 hours old. Only approaches serious enough to be reported publicly are listed: within three days and, for two bodies near the Earth, closer than a kilometre with a chance of a collision above 1 in 10,000, the level at which NASA moves the ISS.
Beside the others
| Satellite | Typical altitude | Orbital period | Mass | In space since |
|---|---|---|---|---|
| FLTSATCOM F2 | 36,221 to 36,337 km | 1,461 minutes | 942 kg | 1979 |
| Hispasat 30W-6 | 35,786 to 35,786 km | 1,436 minutes | about 6.1 t | 2018 |
| Amazonas Nexus | 35,786 to 35,786 km | 1,436 minutes | about 4.1 t | 2023 |
| ARSAT-1 | 35,786 to 35,786 km | 1,436 minutes | about 3 t | 2014 |
| Astra 1N | 35,786 to 35,786 km | 1,436 minutes | about 5.3 t | 2011 |
| Hotbird 13F | 35,786 to 35,786 km | 1,436 minutes | about 4.5 t | 2022 |
Data and API
The current elements from Space-Track as an OMM object, epoch Nov 8, 2026, 12:17 AM, 18 hours old.
{
"OBJECT_NAME": "OPS 6392 (FLTSATCOM 2)",
"OBJECT_ID": "1979-038A",
"EPOCH": "2026-11-08T00:17:58.945920",
"MEAN_MOTION": 0.98542773,
"ECCENTRICITY": 0.00136173,
"INCLINATION": 7.412,
"RA_OF_ASC_NODE": 301.6968,
"ARG_OF_PERICENTER": 79.3447,
"MEAN_ANOMALY": 307.1085,
"EPHEMERIS_TYPE": 0,
"CLASSIFICATION_TYPE": "U",
"NORAD_CAT_ID": 11353,
"ELEMENT_SET_NO": 999,
"REV_AT_EPOCH": 17180,
"BSTAR": 0,
"MEAN_MOTION_DOT": -4e-7,
"MEAN_MOTION_DDOT": 0
}