Skip to content
MobileVideo

Drone SD Card Shows Footage in Aircraft but Computer Sees Empty Folder

Aircraft gallery lists flights but the card appears empty on a computer. Diagnose files stored in internal memory, hidden alternate directory and unsupported card reader file system with targeted checks.

Quick Answer

Identify actual storage location and copy from aircraft using supported export. Verify by checking that original clips are located and copied with matching sizes.

Symptoms

Aircraft gallery lists flights but the card appears empty on a computer. This guide addresses that particular contrast, not every fault that can occur with the product or service.

  • Observable failure: Aircraft gallery lists flights but the card appears empty on a computer.
  • Control test: Compare device gallery path and computer-mounted partition without modifying the card.
  • A confirmed correction must meet this outcome: Original clips are located and copied with matching sizes.

A "connected" indicator usually reports one portion of the process, not end-to-end success. Keep the service, device and user-visible outcome separate in your observations.

Why It Happens

Camera originals, live previews and low-resolution caches are different files. Flight safety and recording integrity should not be put at risk merely to correct a transfer or playback issue.

Treat the problem as three testable possibilities rather than assuming the product is broken: files stored in internal memory, hidden alternate directory, or unsupported card reader file system. The order matters because the least disruptive test should come first.

Three competing explanations

  1. Files stored in internal memory.
  2. Hidden alternate directory.
  3. Unsupported card reader file system.

These are hypotheses. Do not infer a hardware defect, account restriction or network outage from one status indicator alone. A result that supports files stored in internal memory does not automatically exclude hidden alternate directory; the comparison needs to separate them.

Before Making Changes

Do not alter flight-critical controls for a media problem and preserve the original card or flight log until the copy is verified. Do not initialize or repair the only media card.

Preserve the current state: note the affected product or account, current mode and time of the failed attempt. If settings will be changed, photograph or write down their original values. Keep copies of any unique files or evidence before overwriting anything.

Use a non-sensitive sample whenever possible. If the issue involves a shared device, building system, workplace account or regulated equipment, obtain the appropriate owner or administrator permission first. Stop if the test would compromise security, electrical protection, access or an animal's welfare.

Problem-Specific Diagnosis

Run this discriminating test before restarting or resetting the entire system: Compare device gallery path and computer-mounted partition without modifying the card. Compare the observed result against the three paths below.

Observation or suspected layer Interpretation Next controlled check
Files stored in internal memory If the failing state changes under the comparison, files stored in internal memory is plausible. This is not yet proof. Repeat with that one factor changed, then return to baseline.
Hidden alternate directory If the first change has no effect but a supported configuration differs, hidden alternate directory moves higher on the list. Inspect the relevant option or documented behavior without clearing unrelated settings.
Unsupported card reader file system If both earlier paths are contradicted, investigate whether unsupported card reader file system accounts for the timing or device-specific result. Collect an event timestamp or status report for qualified support.

Now apply the least-disruptive change that corresponds to the evidence: Identify actual storage location and copy from aircraft using supported export. Avoid treating all three hypotheses at once; simultaneous changes erase the diagnostic value of the test.

Step-by-Step Troubleshooting

Begin with reversible comparisons. Use Advanced only if the evidence points to a deeper problem.

Capture the current behavior

Aircraft gallery lists flights but the card appears empty on a computer. Write down where it happens, its most recent time and the state displayed by the product. Do not treat a nearby working feature as proof the whole path is healthy.

Run the safe comparison

Compare device gallery path and computer-mounted partition without modifying the card. Use the same device, account and operating conditions where practical. Note what remains unchanged so the comparison is meaningful.

Correct the supported setting

Identify actual storage location and copy from aircraft using supported export. Make one adjustment at a time and preserve the previous value so it can be restored if the result becomes worse.

Confirm the real outcome

Original clips are located and copied with matching sizes. Repeat the complete user-facing operation and then make sure unrelated protections and functions still work. If the result is inconsistent, restore the previous setting and continue diagnosis.

Solution Checklist

Solution Checklist

0/12 completed

Common Mistakes to Avoid

  • Assuming files stored in internal memory is proven simply because the visible symptom matches this page.
  • Changing multiple accounts, rules, connections or device settings before running the control: Compare device gallery path and computer-mounted partition without modifying the card.
  • Skipping this safety boundary: Do not initialize or repair the only media card.
  • Resetting, formatting, deleting credentials or replacing hardware without a confirmed backup, a supported recovery path and evidence that the step is necessary.

A setting that makes one symptom disappear is not always the correct permanent configuration. If it disables another essential function, revert it and investigate the underlying dependency rather than leaving an unsafe workaround in place.

How to Verify the Fix

The primary pass condition is specific: Original clips are located and copied with matching sizes. Repeat the original workflow, not a loosely related shortcut, and confirm both the previously failing behavior and an unaffected comparison still work.

  • Record the before-and-after state in the same location, account and operating mode.
  • Repeat the original comparison: Compare device gallery path and computer-mounted partition without modifying the card.
  • Check the stated pass result: Original clips are located and copied with matching sizes.
  • Confirm that normal security, notification, storage or physical safety protections remain enabled.

If the result works only once or disappears after reopening the app, reconnecting the accessory or waiting for the next scheduled event, treat the issue as intermittent instead of fixed. Keep the event time and what changed between attempts.

If the Problem Continues

If the safe correction does not work, move to a focused deeper investigation: Inspect partition and file layout read-only with another compatible card reader. This is a different path from the first settings check; use it only if the device or service supports the required diagnostics.

When escalating to the aircraft or action-camera manufacturer, provide the exact symptom, result of the control test, changes already tried, time of occurrence and any non-sensitive error or status data. Explain whether files stored in internal memory, hidden alternate directory and unsupported card reader file system were supported or contradicted by evidence.

Do not share account recovery codes, private documents, live access tokens, sensitive location histories or full recordings merely to prove the problem. Redact or summarize identifiers before opening a public support request.

Prevent Recurrence

Keep a short reference note with the working configuration and the successful check: Original clips are located and copied with matching sizes. After an app update, firmware change, network migration or scheduled clock change, run the same short test before depending on the function again.

Watch for the condition that originally made the failure visible: Aircraft gallery lists flights but the card appears empty on a computer. Where practical, retain an alternative approved way to perform the essential task so that one device, cloud service or interface does not become a single point of failure.

FAQ

How can I tell whether files stored in internal memory is responsible?

Run the controlled comparison: Compare device gallery path and computer-mounted partition without modifying the card. A change that specifically affects the failing layer supports this hypothesis, but repeat it before changing permanent settings.

What if the real cause is hidden alternate directory rather than files stored in internal memory?

Do not repeat the initial correction blindly. Check the supported diagnostic path: Inspect partition and file layout read-only with another compatible card reader. Keep the earlier working configuration recorded so you can reverse the test.

When is this particular issue resolved?

The decisive result is: Original clips are located and copied with matching sizes. If it fails after the normal workflow is repeated, document whether unsupported card reader file system still explains the remaining behavior and escalate with non-sensitive observations.

Did this solution fix your problem?

Optional feedback helps us improve this guide. Never send private data.

Can't find your answer?

Tell our editors which problem needs a guide. Do not include passwords, API keys, email addresses, private URLs, or full error logs.

Analyze Error

Paste an error message to identify its likely category. Analysis takes place in your browser; only a short error category will be used if you choose to search.

Do not paste passwords, tokens, private URLs or full logs.