Skip to main content
v2026.11,986 entries · CC-BY 4.0

Minor Planet Center (MPC): the IAU Archive for Asteroid and Comet Observations

How the IAU Minor Planet Center archives asteroid and comet astrometry: submission, designations, WAMO, Observations API and replicated data.

Written and maintained by CASRAI Editorial Board

Published

On this page

The Minor Planet Center (MPC) is the single worldwide location for receipt and distribution of positional measurements of minor planets, comets and outer irregular natural satellites of the major planets. It operates at the Smithsonian Astrophysical Observatory under the auspices of Division F of the International Astronomical Union (IAU), and it keeps the master files of observations and orbits that the rest of solar-system astronomy builds on. For a researcher it is best understood as a data archive with a submission pipeline: you send it astrometry, it validates and publishes it, and you retrieve the result through documented web services and APIs.

What the Minor Planet Center is

According to the MPC’s own About page (read 2026-11-19), the center is responsible for the identification, designation and orbit computation of minor planets, comets and outer irregular natural satellites. In practice that covers four jobs: maintaining the master files of observations and orbits, keeping track of the discoverer of each object, assigning designations, and announcing discoveries through electronic circulars and its website.

The distinction matters for research practice. The MPC is not a telescope, a survey or a modelling group. It is the place where measured positions (astrometry) are collected, checked and made public, and where an object’s identity is settled. Other orbit and hazard services use those published observations as input. NASA’s Jet Propulsion Laboratory states, for example, that the orbits in its Small-Body Database are computed from the observational data published by the MPC, with radar astrometry added when available. Related CASRAI pages on archives for other planetary and astronomical data include the NASA Planetary Data System, the CDS services (VizieR, SIMBAD, Aladin) and the NASA Exoplanet Archive.

Who runs it and what it covers

The MPC’s About page says it operates at the Smithsonian Astrophysical Observatory under the auspices of IAU Division F, that all of its operating funds come from a NASA Near-Earth Object Observations program grant, and that much of its computer equipment was provided by the Tamkin Foundation. Its FAQ adds that data from the MPC database is made freely available to the public, and gives the funding acknowledgement to use when crediting the MPC in a publication: a NASA PDCO grant (80NSSC22M0024), administered through a University of Maryland to Smithsonian Astrophysical Observatory subaward (106075-Z6415201).

Scope is defined by object type: minor planets (asteroids), comets and outer irregular natural satellites. Two scope limits appear in the FAQ. The MPC does not track artificial satellites, and it does not handle names: naming and the associated citations for all minor planets and comets are handled by the IAU Working Group on Small Body Nomenclature (WGSBN). The MPC site also links to services for near-Earth object follow-up (the NEO Confirmation Page), orbital element files, an ephemeris service, observatory codes and the Minor Planet Electronic Circulars (MPECs).

How an observation travels through the MPC

The MPC’s public documentation describes a clear path from a telescope image to a citable record. Following it step by step also shows where researchers most often lose time.

  1. Get an observatory code. The reporting guidance says that a site without an observatory code should ask for one, and the FAQ points to the Guide to Minor Body Astrometry sections on beginning and on obtaining a code.
  2. Measure and format the astrometry. The MPC strongly prefers the Astrometric Data Exchange Standard (ADES); the older 80-character MPC1992 format may also be submitted. Use of ADES is not mandatory at the moment.
  3. Submit. ADES goes through the web forms submit_xml (XML) or submit_psv (pipe-separated values), which also show cURL examples for automation. A separate page checks whether an XML or PSV file is valid before submitting.
  4. Validation. The MPC validates all submissions against a W3C schema, submit.xsd, converting PSV to XML first, and runs additional checks. Data can be valid ADES and still not be valid for submission.
  5. Check status. After submitting, confirm receipt with WAMO (Where Are My Observations). If nothing is returned, the FAQ says the observations may have been rejected for formatting reasons.
  6. Publication. Per the MPC Processing page, NEO observations are published daily in the Daily Orbit Update, other observations appear in the monthly Minor Planet Circulars or Supplements, and new NEOs, TNOs and natural satellites receive MPECs.

Reporting rules that decide whether a batch is accepted

The Reporting Observations page lists several rules. Report at least three observations of each object from each night, because batches that contain single positions are generally returned in their entirety. Magnitudes are optional but highly desirable, especially for archival astrometry. New observers are expected to gain experience on routine objects and show good astrometry of known objects before attempting unusual ones or discoveries. Subject-line keywords route a batch to the right queue: batches with new NEO candidates must have NEO CANDIDATE in the subject line, objects already on the NEOCP need NEOCP, new comet candidates need NEW COMET and new TNO candidates need NEW TNO. Without the correct keyword, tracklets can end up in a wrong or slower queue.

The Getting Started page for astrometry adds measurement expectations: a pixel scale no greater than 2 arcseconds per pixel is preferred (3 at worst), at least three comparison stars should be used, positions come from a least-squares plate-constants solution rather than by eye, and the clock must keep accurate UTC. The FAQ explains the most likely reason for rejection: large orbital-fit residuals, including residuals larger than the uncertainty you reported. You can test for this yourself by fitting an orbit to the archival astrometry plus your own.

Processing order

Batches are processed in the order received, but with priorities. The Processing page lists the order as: potential new NEOs, unusual objects and comets suitable for the NEO Confirmation Page; follow-up of NEOCP objects; other NEO observations; survey observations from last night and recent non-survey material; older non-survey material; and finally survey observations from before last night. Observations not submitted in the proper format are subject to delay. Objects posted on the NEOCP are those that appear to be NEOs by motion or orbit and have a digest2 score larger than 65, along with suspected comets.

How to read a provisional designation

A provisional designation is the first label the MPC gives a new object. The MPC assigns one when an object cannot be identified immediately with an already designated object and its orbit is good enough not to need immediate follow-up. The documentation says the standard format has a 4-digit year, a space, a letter for the half-month of discovery, a second letter for the order within that half-month, and an optional number for how many times the second letter has been repeated.

Half-month letter Dates of discovery
A Jan. 1-15
B Jan. 16-31
C Feb. 1-15
D Feb. 16-29
E Mar. 1-15
F Mar. 16-31
G Apr. 1-15
H Apr. 16-30
J May 1-15
K May 16-31
L June 1-15
M June 16-30
N July 1-15
O July 16-31
P Aug. 1-15
Q Aug. 16-31
R Sept. 1-15
S Sept. 16-30
T Oct. 1-15
U Oct. 16-31
V Nov. 1-15
W Nov. 16-30
X Dec. 1-15
Y Dec. 16-31

The letter I is omitted and Z is unused for the half-month. The second letter runs A to Z with I omitted, so A is the 1st discovery, B the 2nd and Z the 25th. When a half-month has more than 25 discoveries, the second letter recycles and a numeral is appended: the documented order in one half-month is 1995 SA, 1995 SB, up to 1995 SZ, then 1995 SA1 onwards.

Worked decode. The MPC’s own Observations API example uses the designation 2023 AB. Read it with the rules above: the year is 2023, the half-month letter A means discovery between January 1 and 15, and the order letter B marks the 2nd designation of that half-month. Pre-1925 discoveries replace the first digit of the year with the letter A, so A904 OA is the first object designated from the second half of July 1904. Four special surveys (Palomar-Leiden, and the first, second and third Trojan surveys) use a different number-plus-identifier form, such as 2040 P-L.

The documentation also describes packed designations, the compact forms used inside MPC data files, and states that new designations are not assigned to objects observed on only one night, although a single-night object may receive a designation if it can be identified with an already known object.

How to search and retrieve MPC data

The MPC’s data services live at data.minorplanetcenter.net, which hosts newer web applications and APIs including MPC Explorer, an interactive search of the orbit and observation database. Which tool to use depends on the task. The data table below maps common research tasks to the MPC service documented for them, with the inputs and behaviour taken from the MPC’s public documentation.

Pull observations for one object with the Observations API

The get-obs endpoint (https://data.minorplanetcenter.net/api/get-obs, method GET) takes a required desigs parameter, a list holding one string: a name, permanent designation or provisional designation. The optional output_format accepts XML, OBS80, ADES_DF and OBS_DF, and several can be requested together. The optional ades_version is 2017 or 2022, with 2022 the default. The documentation notes that the API is limited to single-object queries. Its examples return ADES XML for 2023 AB and 80-column text for Bennu, and show a pandas data-frame route for analysis.

Check the fate of a submission with WAMO

The WAMO API (https://data.minorplanetcenter.net/api/wamo, GET) accepts up to about 50,000 identifiers per query. Accepted forms are a tracklet submission ID with the station code (the trksub and stn pair, for ADES submitters), an observation ID, an exact 80- or 160-column observation string, or a submission block ID. Astrometry is suppressed for unpublished observations. Adding the item ‘string’ to the list returns the same text as the original WAMO tool.

Identify a moving object in an image

The FAQ answers this directly: supply the RA, Dec and time to MPChecker, which returns a list of minor planets near that location at that time. If there is no good match, the FAQ says the object is most likely an artificial satellite, which the MPC does not track. A researcher convinced the object is unknown is pointed to the route of obtaining an observatory code, measuring accurately and submitting the astrometry.

Replicate the database

For bulk work, the MPC makes its PostgreSQL database of observations and orbits available for replication through the Small Bodies Node (SBN); the FAQ says to contact the SBN to subscribe. The replicated-tables documentation warns that each extra index slows writes on large tables such as obs_sbn, and suggests comparing the row count and latest updated_at value of your copy with the status shown on the SBN database status page.

Cite MPC records

The Processing page states that as of MPEC 2023-D40 (February 21, 2023) DataCite DOIs are available for all new MPECs, so those circulars can be cited in articles and proposals. The MPC says it is creating DOIs for earlier MPECs as well. For general crediting, use the funding acknowledgement given in the FAQ.

Strengths and limits

  • Strength: one authoritative record. Observations, orbits, discoverer credit and designations are kept in one master archive, and downstream services such as JPL’s Small-Body Database state that they use MPC-published observations.
  • Strength: open and scriptable. Data is freely public, documented APIs exist for observations, WAMO, designation identification and more, and submissions can be automated with cURL.
  • Limit: strict submission rules. Single-position nightly batches are generally returned, and observations that fail format validation or orbit-fit checks are rejected.
  • Limit: observations, not interpretation. The MPC is the archive for astrometry and orbit computation; impact-risk assessment and physical data are handled by other services (see below).
  • Limit: scope. No artificial satellites, no naming (WGSBN), and the documented Observations API handles one object per call.

Alternatives and complements

Service What its own documentation says How it relates to the MPC
JPL Small-Body Database (SBDB) API Provides machine-readable identification, orbital and selected physical data for all known asteroids and comets; orbits are computed by JPL’s Solar System Dynamics group. Uses the observational data published by the MPC as its input, so it is a downstream orbit and physical-data source rather than a replacement archive.
ESA Near-Earth Objects Coordination Centre (NEOCC) Describes itself as ESA’s centre for observing and computing asteroid orbits and assessing their impact risk, with risk lists and close-approach lists. A parallel European NEO service; use it for risk and close-approach views, not as the submission point for new astrometry.

For survey-scale detections feeding the MPC, see the Vera C. Rubin Observatory guide, and for the wider field see what planetary science is.

Sources

Data: MPC services mapped to research tasks

Compares the Minor Planet Center services documented for common research tasks: what you give each one, what it returns or enforces, and the public documentation page it comes from. Compiled from the MPC Public Documentation Hub and FAQ, read 2026-11-19.

Period covered: 2026.

MPC services mapped to research tasks
TaskMPC serviceInputOutput or rule
Submit new astrometry (ADES)submit_xml or submit_psv web forms, or cURLADES XML or pipe-separated valuesValidated against W3C schema submit.xsd; PSV is converted to XML first; valid ADES is not always valid for submission
Check status of a submissionWAMO tool and WAMO APItrksub plus station code, observation ID, 80/160-column string or submission block ID; up to about 50,000 identifiersStatus of the observations; astrometry suppressed for unpublished observations
Retrieve observations for one objectObservations API (get-obs)desigs: one name, permanent or provisional designation; output_format; ades_version (2017 or 2022, default 2022)Observations as XML, OBS80, ADES_DF or OBS_DF; single-object queries only
Identify a moving object in an imageMPCheckerRA, Dec and timeList of minor planets near that location at that time; no match suggests an artificial satellite, which the MPC does not track
Obtain a bulk copy of the databaseReplicated PostgreSQL tables via the Small Bodies NodeSubscription request to the SBNReplicated observation and orbit tables such as obs_sbn; subscribers manage their own indexes
Follow up a possible new NEONEO Confirmation Page (NEOCP)Observations with NEO CANDIDATE or NEOCP in the subject lineObjects with a digest2 score larger than 65, plus suspected comets, are posted

Sources

Compiled by CASRAI from the sources above. Free to reuse under CC BY 4.0 with attribution.

Follow CASRAI

Research-administration guidance, standards updates and independent tool reviews.

Ask CASRAI · full access

Ask about Minor Planet Center (MPC): the IAU Archive for Asteroid and Comet Observations

Full access: large monthly usage, up to 10 source passages behind each answer, and MCP and API access for Claude Code, Codex and other CLIs. Cancel any time.

An AI assistant for research: funder rules, compliance, methods and publishing. It links the sources behind its answers and labels answers that come from a web search.

Answers draw on CASRAI's guides and dictionary plus the federal and funder documents we index: Federal Register, Grants.gov, Regulations.gov and UKRI.

Works on this site and inside Claude, Cursor and the AI tools you already use.

Everything CASRAI publishes — this page, the dictionary, the guides and the news — stays open to read, with no account and no card.

Referenced across the research world

University of Cambridge logoColumbia University logoCrossref logoUniversity of Edinburgh logoHarvard University logoUniversity of Oxford logoPrinceton University logoStanford School of Medicine logoUniversity College London logoORCID logoUniversity of Cambridge logoColumbia University logoCrossref logoUniversity of Edinburgh logoHarvard University logoUniversity of Oxford logoPrinceton University logoStanford School of Medicine logoUniversity College London logoORCID logo
  • University of Cambridge logo
  • Columbia University logo
  • Crossref logo
  • University of Edinburgh logo
  • Harvard University logo
  • University of Oxford logo
  • Princeton University logo
  • Stanford School of Medicine logo
  • University College London logo
  • ORCID logo

View CASRAI adoption →