Newsroom Line
For urgent tips, embargoed releases, and live observing coordination. Voicemail is transcribed and routed overnight.
Whether you're a working astronomer, a curious observer, or a contributor with a story to tell — we read every message and reply within two business days.
Tell us what you're working on, what you'd like to see covered, or where we can sharpen our reporting. We treat every note as a coordinate worth plotting.
A few details help us route your note to the right editor faster. Nothing here is required to start a conversation — but the more context you share, the better we can help.
Four channels, all monitored by humans. Pick whichever suits the shape of your message.
For urgent tips, embargoed releases, and live observing coordination. Voicemail is transcribed and routed overnight.
General correspondence, pitches, observing reports, and corrections. Replies usually within two business days.
For physical mail, prints, and care packages. We open everything — though reply times are slower than email.
418 Syrtis Major
Cambridge, MA 02138
United States
The desk is staffed across time zones. Editorial coverage follows mission events; support is queued for the next window.
Mon–Fri · 09:00–18:00 ET
Weekend queue · 24h reply
Closed on US federal holidays
Our newsroom is tucked between the Charles River and the Harvard-Smithsonian CfA — a useful neighborhood for an astronomy publication.
The newsroom is open to contributors, sources, and visiting researchers by appointment. Drop us a line first so we can clear the schedule and put the kettle on.
We post observation alerts, mission milestones, and field photos across the platforms below. Pick the feed that fits the rhythm of your day.
Launch alerts, skywatch reminders, and the occasional argument about redshift conventions.
@acosmictrail · 84KField photography, telescope builds, and the long-exposure deep fields that started the whole project.
@acosmictrail · 52KLong-form interviews with mission scientists, observing tutorials, and full-night timelapses from dark sites.
@acosmictrail · 31KEvery Sunday: a single long essay, three skywatch targets, and a recommendation from the editor's desk.
Subscribe · WeeklyOpen-source data pipelines, the ephemeris tools we use for planning, and community observing scripts.
github.com/acosmictrailA quieter space for planning sessions, gear troubleshooting, and the long technical threads we love.
forum.acosmictrail.comA short brief for anyone pitching a piece, sending a correction, or wondering what happens after they hit send.
We publish long-form essays (1,500–3,000 words), mission explainers, observing field reports, and the occasional interview. We don't run press releases verbatim, and we don't syndicate. Original reporting and first-person observing accounts are the heart of the publication.
Yes. We pay on acceptance, rates starting at $0.40/word for essays and feature reporting, with a flat fee structure for shorter observing notes. Kill fees are 25% of the agreed rate. We pay via bank transfer or PayPal within 30 days of publication.
Initial review within five business days. If we're interested, you'll hear from a specific editor by name. We work through two rounds of edits, share a final proof for fact-check, and publish on a schedule we agree to upfront. Average lead time from pitch to publication is six to ten weeks.
Absolutely — observing reports are one of our most-read categories. Send us the date, location (general is fine), equipment, conditions, and what you saw. We love sketches, sketches-turned-photos, and unusual targets. Reports run 300–800 words and pay a flat $120.
Thank you — corrections matter. Email [email protected] with the article URL, the specific claim, and a source for the correct information. We verify, issue a dated correction note at the top of the article, and reply to the original reporter.
Every message gets a human reply within two business days. Pitches take longer (up to five days) because they go through an editorial meeting. If your message is time-sensitive, mention it in the subject line and we'll prioritize accordingly.