RECORDED POSSIBLE-ECHO CANDIDATES
0 possible echoes flagged
The source reported zero since its run began at 5:54:12 PM EST, with 91.59 seconds of post-warmup observation. This is not zero meteors and not a rate estimate.
METEOR WATCH / EXPERIMENTAL RADIO SCATTER
Could that signal
be a meteor echo?
We are testing whether brief radio signals can reveal meteor trails overhead. For now, these are possible-echo candidates—not confirmed meteor detections.
Experimental · RF channel not validated. A possible-echo candidate is a radio signal flagged for review—not a confirmed meteor. This page must not be used as a meteor counter, storm forecast or safety alert.
One verified historical observation
November 7, 2026 · 5:56:45 PM ESTStale snapshot · not automatically refreshed. These are recorded values at the observation time, not current readings. They do not establish present receiver status.
HOST SAMPLE COVERAGE
98.93% nominal
151.104 processed sample-seconds over 152.73 seconds of reported uptime. This is host-side accounting, not proof of uninterrupted RF observation. Internal USB losses are not measurable.
RECORDED TUNING
97.3 MHz
Provisional and unvalidated. The source explicitly reports no identified transmitter and no validated channel.
RECORDED HOST HEALTH
0 queue drops
No acquisition errors were listed and the maximum clipped-component fraction was zero in this observation. Those checks do not validate meteor detection.
Current station status
Not connected to a live transportLAST VERIFIED OBSERVATION
Not available
No as-of time or freshness can be assigned without a verified source timestamp.
OBSERVING COVERAGE
Unknown
We need the actual listening period and gaps—not just how long a program was open.
TUNING FREQUENCY
Unverified
The listening channel and its suitability for this experiment still need confirmation.
CURRENT POSSIBLE-ECHO CANDIDATES
Not available
No current count is available. The recorded zero above is historical; missing updates must never become zero detections.
Radio waterfall
Waiting for genuine spectrum uploads. No simulated detections are displayed.
FIELD NOTES / LEARNING TO LISTEN
November 10: a full day of listening, and the possible echoes again kept to daylight hours
2026-11-10 · Saved daily recap — check coverage below
Completed November 10 Eastern calendar day with essentially full recording coverage. Saved status samples run from 12:00:02 AM to 11:59:57 PM EST. Adjacent observing records support about 23 hours 59 minutes of host sample time, 99.99% of the day, with no gaps longer than 15 seconds. That measures logger records, not proof the radio path was perfectly steady all day.
What did we learn?
On November 10 the detector listened all day and flagged 64 possible radio echoes (unverified), saving a trace for each. Every one arrived between 7:43 AM and 2:17 PM. The busiest hour was 1 to 2 PM, with 17. From midnight to 7:43 AM, and from about 2:18 PM to midnight, the detector was running but flagged none.
This is the third day in a row with the same shape. Meteor experts note that random meteors are usually most common before dawn, when our side of Earth faces forward in its orbit. Our candidates showed up only after sunrise and stopped by mid-afternoon. A repeating daytime-only pattern points more toward something on the radio channel, such as daytime interference or changing reception, than toward meteors. We have not found the cause, so these stay possible echoes. Quiet hours do not mean no meteors, only that nothing passed the detector's rule.
How strong and how long?
Strength is measured in decibels (dB) above the receiver's changing reference. Flagged signals peaked between +5.5 and +14.9 dB, averaging about +9.5 dB; every 10 dB is about ten times more power. The strongest came at 8:44 AM. Strength does not reveal a meteor's size, distance or brightness.
Durations ran from 0.06 seconds to one 121-second signal at 9:00 AM. 33 lasted under two seconds and nine lasted over ten. Many arrived as two to four pieces only seconds apart, which may be one longer signal split up. Frequency drift was not measured. Late in the evening the band was calm, within -0.63 to +0.31 dB of the reference.
Reading the waterfall
On the waterfall, left to right shows radio frequency and newer rows appear at the top. Brighter colors mean a stronger signal than the reference. It is a radio picture, not a meteor photo. Today's rolling strip is current data, not November 10's archive, and was not used here.
Why it matters for Space Coast readers
When the same pattern repeats on full days, it becomes a clue worth chasing, and that is how real science works. Our transmitter and listening path are still unvalidated, so the next step is learning what causes these daytime signals. This is an experiment, not a meteor count or safety alert.
Sources: Completed November 10 station database summary · International Meteor Organization: radio observations · American Meteor Society: visual observing and time of night
Saved explanation, not a live forecast. It stays fixed while the readings above refresh. New daily recaps look back at the previous Eastern calendar day.
THE IDEA, IN PLAIN ENGLISH
Why listen to radio
to study meteors?
As a meteoroid enters the atmosphere, it can leave a short-lived trail of electrically charged gas. That trail can scatter a distant transmitter's radio signal toward a receiver.
A brief reception change is only a clue. Whether it supports a meteor interpretation depends on the transmitter, frequency, geometry, signal shape and other evidence.
WHAT ELSE COULD IT BE?
A stronger signal
is not a verdict.
Aircraft can reflect radio signals. Local FM stations, unusual atmospheric propagation, electrical interference and receiver changes can also create bursts or changes in reception.
Until the RF channel is validated, even a clean-looking candidate may have another cause. More listening alone does not solve that uncertainty.
WHAT WE CAN SAY RIGHT NOW
No trend. No forecast.
Not enough evidence yet.
Automatically refreshed candidate counters alone cannot establish a meteor trend or near-term forecast. No validated candidate-event timeline is supplied here, and the radio channel remains scientifically unvalidated.
How to read future updates
- Possible-echo candidate: a signal flagged for review, not a confirmed meteor.
- Duration: how long the signal met the detector's rule—not necessarily a meteor's lifetime.
- Relative signal excess: a change above the detector's reference level—not an object's size, brightness or distance.
- Coverage gap: a period we cannot evaluate; it must stay visibly missing.
A few important distinctions
Does zero candidates mean zero meteors?
No. Even a verified zero applies only to a defined listening window and detector configuration. Meteors may occur outside the receiver's sensitivity or geometry. Without coverage information, a zero is especially uninformative.
What would stale or offline mean?
Stale means the last verified observation is older than an agreed freshness limit. Offline requires evidence from receiver status; an old or missing website update alone does not prove that the receiver stopped collecting.
Will explanations be generated on every update?
No. Explanations will use fixed rules tied to verified observations and their time window. They will describe uncertainty and missing coverage, not invent meteor identifications or predictions.
Experimental public station page. Verified automatic source status is shown above when available; otherwise the recorded snapshot remains historical. No precise receiver location or private network details are included.