> if you plan to go for 973B138 on the NEOCP, please wait until you see
> its status as "updated".

With KNOBS at the ready, that's unnecessary.

973B138 C2009 07 05.48744700 36 41.550+23 53 46.99 18.8 R 568
973B138 C2009 07 05.48816700 36 41.616+23 53 47.90 18.8 R 568
973B138 C2009 07 05.48884400 36 41.682+23 53 48.79 18.7 R 568

> We found this object two nights ago but didn't submit it because
> we were not sure if it is real. Last night we confirmed it on a second
> night, but both nights do not match perfectly.

We see what you mean.

973B138
Epoch 2009 Jun 18.0 TT = JDT 2455000.5 Tholen
M 356.36945 (2000.0) P Q
n 0.15802218 Peri. 64.29333 +0.93384019 +0.18438388
a 3.3883689 Node 283.82348 -0.31215325 +0.83849666
e 0.4393682 Incl. 18.39987 +0.17465063 +0.51276304
P 6.24 H 15.4 G 0.15
Residuals in seconds of arc
090704 J75 (1.62- 1.17+) 090705 J75 0.23- 0.15- 090705 568 0.02- 0.01-
090704 J75 0.03+ 0.02- 090705 J75 0.14+ 0.25+ 090705 568 0.00 0.01+
090704 J75 (1.48+ 1.22+) 090705 568 0.02+ 0.00

I was guessing that it might be a Phocaea, but there isn't a local minimum
into which that type of orbit can settle, so it migrated to more of a
Griqua-type orbit. But there are still all sorts of possibilities,
including NEO orbits. There is a local minimum near a Hungaria-type orbit:

973B138
Epoch 2009 Jun 18.0 TT = JDT 2455000.5 Tholen
M 1.58374 (2000.0) P Q
n 0.34056277 Peri. 55.14293 +0.84354489 +0.44945294
a 2.0308192 Node 276.50558 -0.53609189 +0.73750373
e 0.1457744 Incl. 17.21061 +0.03221030 +0.50406379
P 2.89 H 15.7 G 0.15
Residuals in seconds of arc
090704 J75 (1.62- 1.15+) 090705 J75 0.31- 0.09- 090705 568 0.02- 0.01-
090704 J75 0.06+ 0.05- 090705 J75 0.11+ 0.30+ 090705 568 0.00 0.01+
090704 J75 (1.53+ 1.18+) 090705 568 0.02+ 0.00