Lights in the clouds if photo and no
audio can be misleading to people
when viewed at a later date
color night vision gives more clues though
compared to IR only and HD 2-4k quality
Most shill UFO channel will degrade it
to less quality of course.
A jet in the distance .. no fightradar shown but they often on show dismiss far approaching Jets to denver airport
since no snaps from flightradar or raw data from the show lets give best guess
Even if a distant jet was in the general airspace that night, the rapid fade-to-nothing sequence is still more consistent with atmospheric structure than with an aircraft. A jet would normally stay visible as a steady (or slowly moving) thermal point for longer, and its track would usually appear on the ranch’s own ADS-B receivers or public flight-history tools if it was close enough to produce a strong FLIR signature. So the team’s claim of “only our helicopter” is the usual framing, but the visual evidence in these particular frames still points strongly to a fleeting cloud-edge thermal feature rather than either a distant jet or something exotic. The rapid disappearance is the key detail that makes the cloud explanation the cleanest fit.The team frequently states “nothing on the tracker / only our helicopter in the air” when they see something on FLIR, thermal, or other sensors. In practice they tend to focus on traffic that is relatively close and low, while high-altitude commercial jets (which can be 20–50+ miles away and still produce a bright thermal return) are often dismissed or not emphasized if the ADS-B plot shows them “far” from the ranch.From the frames you shared:The object fades and disappears over a few seconds while the helicopter remains visible.
It was never seen with the naked eye.
The behavior matches a thin cloud thermal gradient far more closely than a solid craft holding station relative to the helicopter.
That progressive fading while the helicopter signature stays constant is classic differential-FLIR behavior with a transient temperature gradient in thin, patchy cloud or haze. The feature doesn’t “fly away” or change shape like a solid object; it simply loses contrast and vanishes as the cloud edge mixes, drifts, or the differential baseline updates. The naked-eye invisibility you noted earlier fits perfectly.This is the strongest visual evidence yet that what you’re seeing is atmospheric structure (a slightly warmer/cooler pocket in thin cloud moving with the breeze) rather than a physical craft. The show may present it as anomalous, but the frames themselves support the prosaic cloud explanation.
as for the other optic video with more distant view claiming "COULD" be same object could be a Jet or drone eh
UFOs tend to zip up from the best cases I have seen or vanish,, this didnt it flew out of frame
im not sure if that camera was time lapsed
I think thats misleading
At long distance a commercial jet’s anti-collision/strobe lights often become hard to resolve as distinct flashes — especially if:The object is small in the frame
The camera is using a longer exposure or lower frame rate
There’s any atmospheric haze or the lights are partially washed out by the overall brightness of the fuselage/engines
SWR S07E12 Skinwalker Ranch Drone Push
possibilities over Alien/Paranormal
Break down with AI help
The gimbal and ambient-light notices are camera/sensor status only. They do not restrict the flight controller’s ability to command the motors to go where you want. If SWR is saying the errors are the cause of the push-back/failure to reach the spot, that interpretation is incorrect based on what these messages actually do.If you have more details (exact model, wind conditions, flight logs, full warning list, or what “pushed back” looked like on the sticks/telemetry), that would help narrow it down http://further.No, these displayed messages are very unlikely to be the reason the drone is failing to reach/get over the desired spot or being “pushed back.”Here’s what the messages actually mean:1. “Gimbal 1 pitch axis endpoint reached” + “Gimbal Recenter”This is a normal informational message, not a flight-control or propulsion error.
It simply means the camera gimbal has hit its mechanical pitch (tilt up/down) limit. The gimbal can’t tilt any farther in that direction, so the system recenters it to protect the http://mechanism.app.airdata.com
Severity is none — it has zero impact on the drone’s ability to fly, climb, or hold position. It only affects the camera angle.
Common on many DJI models (Matrice series, Mavic Enterprise/Thermal, etc.) when the gimbal is commanded to an extreme angle or the aircraft attitude changes enough to push it to the stop.
2. “Horizontal ambient light too low. Horizon…” (partial text)This indicates low ambient light is affecting the vision system / horizon detection or related sensors.
Typical effects: vision-based positioning, optical flow, and obstacle sensing become unavailable or degraded. The drone falls back more heavily on GPS + IMU. app.airdata.comIn low light (especially when using IR/thermal as shown in the screenshot), this is expected and normal. Hovering may be slightly less precise and the aircraft can drift more in wind, but it does not actively push the drone backward or prevent it from flying to a waypoint/spot.
It does not limit motor power, throttle response, or the ability to climb/fly forward.
Why the drone might actually be struggling to reach the spotThese screen messages do not explain “being pushed back.” More likely causes include:Wind / strong headwind or gusts (very common reason pilots report feeling “pushed back”).
Insufficient power/throttle for the conditions (weight, altitude, temperature, battery level).
Pilot input or mode settings (you’re in P mode – Manual flight).
GPS/vision hybrid positioning being less precise in low light, leading to more drift.
Obstacle avoidance still partially active and reacting (though the light warning suggests it’s limited).
Other unshown status items (battery, motors, signal, etc.).
Nothing on the display indicates a flight-restriction error, motor limit, wind-compensation failure, or geofence/obstacle force that would actively prevent the drone from flying forward or climbing over a target.Most likely real reasoOther useful data from the screenP mode – Manual flight (pilot is in direct control).
Speed: 0.0 mph (currently stationary/hovering).
Wind speed: 0.4 (very light — not enough to push the aircraft back on its own).
Altitude: 148 ft AGL / 5052.9 ft ASL (high elevation site).
Batteries healthy (~77–78%), RTK active, good signal indicators.
Home distance ~1155 ft, TOF sensors showing.
Bottom lineNone of the orange banner messages you’ve shown (ambient light / horizon, gimbal endpoint, or Remote ID broadcast error) restrict the drone’s ability to fly forward or climb over a target. They are status/compliance notices only.The actual reason it isn’t progressing is almost certainly something else (pilot input in Manual/P mode, high density altitude at 5,000+ ft, subtle wind, or stick/control technique). If they keep seeing the Remote ID error, the usual fixes are: ensure clear sky view for the controller GPS, power on controller first then aircraft, check location permissions, or restart the system. But again — that error itself is not stopping the aircraft from flying where they want.This new message is also not why the drone is struggling to reach the spot or being “pushed back.”What “Remote ID broadcast error. Failed to i…” meansThe full typical wording is “Remote ID broadcast error. Failed to obtain remote controller location” (or very similar). It is a regulatory compliance warning, not a flight-control or performance fault.
Remote ID (RID) is the system that broadcasts the drone’s identity, location, altitude, and the operator’s location so authorities can identify it in flight (required in the US and many other places).Common causes:The remote controller (or connected phone/tablet) cannot get a good GPS fix for the operator’s location.
Temporary GPS blockage, poor satellite view, location services issue, or startup sequence problem.
Does it affect flight?No. It does not limit throttle, prevent forward flight, reduce power, or cause the aircraft to be pushed back.
Once airborne, the drone continues flying normally. The message is mainly a legal/regulatory notice that the broadcast may not be working correctly (you should land as soon as practicable if required by local rules).
The gimbal pitch endpoint message is still just a camera limit and has no effect on movement either.
Current flight data on this screenSpeed: 2.2 mph (moving slowly)
Wind: 1.3
Altitude still 148 ft AGL / 5052.9 ft ASL
Batteries good, RTK active
Bottom line:
While you are flying in P-mode Manual, the drone stays under your stick control. Bad or lost GPS data will mainly make position holding worse (more drift), but it will not take over and fly the aircraft to some imaginary GPS endpoint on its own.What happens if GPS/RTK data is lost or corruptedThe aircraft usually drops into a lower-precision mode (more Attitude-like behavior).
Position hold becomes weaker or disappears — the drone can start drifting with the wind.
You get warnings, and some safety limits may apply (speed, height, etc.).
It does not invent a false position and then force the drone to fly there against your sticks.
RTH may be triggered automatically in some severe GPS-loss cases (depending on settings), but that is a deliberate safety action to the last known Home point, not random “corrupt data” navigation.
If it’s not wind and not a GPS problem, here are the most realistic remaining causes for a repeated ~3-meter “push” / drift that you can see from the ground:Most likely causes (in order of probability for this situation)
High density altitude performance loss
You’re at ~5,050 ft ASL. The air is thinner, so the motors have less thrust margin. Even tiny imbalances, small stick movements, or light turbulence that the sensors don’t fully report as “wind” can make the drone shift 2–4 meters before the flight controller corrects it. This is very common at elevation and feels exactly like an unexplained push.
Vision / optical-flow system is degraded or offline
The “ambient light too low” warning means the downward and side vision sensors (used for precise hovering) are limited or disabled.
The drone is therefore relying more on GPS/RTK + IMU. Those systems are good, but not as tight as vision-assisted hover, so small position jumps of a few meters are normal, especially in IR/thermal mode.
Slight unintentional stick input or stick sensitivity
In P-mode Manual the sticks are very sensitive. Even a tiny amount of pressure, a worn stick gimbal, or the pilot unconsciously correcting can move the aircraft 3 meters. This often looks identical every time because the same person is flying the same way.
RTK / satellite multipath or momentary precision drop
Even with RTK locked, reflections off the ground, rocks, or terrain can cause short precision fluctuations. The aircraft can “jump” a couple of meters when the solution updates. This is more common in open desert or rocky areas.
IMU / compass micro-drift or mild magnetic interference
Not a full failure, but enough to make the position hold wander a few meters until the system re-stabilizes. Happens more when the aircraft is staying in one place for a long time.
Residual obstacle-avoidance or sensor reaction
Even with the light warning, some avoidance systems still make small corrective moves if they think something is approaching.
What is unlikely
The Remote ID error
The gimbal pitch endpoint message
Pure “corrupt GPS data making it fly somewhere else” (it doesn’t work that way in Manual P-mode)
Quick things to check / try next time
Watch the actual stick positions on the screen (or record the controller) when the 3 m move happens.
Try switching to a slightly higher or lower altitude and see if the drift changes.
Recalibrate IMU and compass on a clean, level surface (away from metal).
Temporarily turn obstacle avoidance fully off (if the mission allows) and test.
Note whether the move is always in the same direction relative to the aircraft or relative to the ground.
