Showing posts with label asteroid. Show all posts
Showing posts with label asteroid. Show all posts

Sunday, 12 September 2021

An Asteroid for Alice

 

Image

 

As long-time readers of this blog know, I have been active in searching for Near Earth Asteroids (discovering two: 2005 GG81 and 2015 CA40). As part of that search, I also discovered a number of new Main Belt asteroids

A batch of these, that where discovered by Krisztian Sárneczky and me with the 60-cm Schmidt of MPC 461 Piszkéstető in Hungary in the period 2012-2016, are now well observed enough that they are getting permanent numbers issued by the MPC. Which means that we have the opportunity to suggest names for these asteroids to the IAU.

The first name we proposed was accepted and published by the Work Group on Small Body Nomenclature (WGSBN) of the International Astronomical Union (IAU) last week. 

It is with much pleasure that I can announce that asteroid (551014) = 2012 UU185 will henceforth be called:

 

(551014) Gorman

 

...after Dr Alice Gorman, a pioneer "Space Archaeologist" and senior Lecturer at Flinders University in Australia.

 

Image
Dr Alice Gorman
 

Dr Alice Gorman is a pioneer in the field of Space Archaeology: the study of human material culture in space, and Space-Age related human material culture on earth (e.g. old launch or tracking sites). Some of you may know here from her book "Dr Space Junk vs the Universe" (if you don't know the book, I can warmly recommend it).

 The naming citation for the asteroid was published on 3 September 2021 in WSGBN-bulletin vol 1. nr 7 and reads:

(551014) Gorman = 2012 UU185 

Discovery: 2012-10-18 / K. Sárneczky, M. Langbroek * / Piszkéstető / 461 

Alice Gorman (b. 1964) is an Australian archaeologist and an expert in lithic analysis and Heritage management. She is one of the pioneers in the field of space archaeology, the study of human material culture in space and related material culture on Earth.


Asteroid (551014) Gorman was discovered on 18 October 2012 as a magnitude +19.2 object by Krisztian Sárneczky and me with the 60-cm Schmidt of MPC 461 Piszkéstető Observatory in the Matra mountains of Hungary. The animated GIF in the top of this post shows a 'blink' of a small part of the three discovery images (taken about 15 minutes apart). The asteroid can be seen as a faint moving dot in the center.

Our initial internal reference for the objects given on the night of discovery was object SaLa016. After submission to the MPC, it got the temporary designation 2012 UU185. In June this year, it was issued the permanent number (551014).

(551014) Gorman is an approximately 2 km wide asteroid (H = 15.9) that moves in the asteroid belt between Mars and Jupiter. It is a Main Belt IIIb type asteroid with perigee at 2.97 AU and an orbital inclination of 14 degrees. It takes the asteroid 5.8 years to complete one orbit around the sun.

 

Image


It makes me very happy to have been able to name this asteroid after Alice!

Friday, 31 January 2020

California 30 January 12:30 UT: the "space debris" reentry that wasn't




On 30 January 2020 near 12:30 UT (10:30 pm PST), a bright, slow, spectacularly fragmenting fireball swooped over southern California. It was seen and reported by many in the San Diego-Los Angeles area. The video above was obtained by a dedicated fireball all-sky camera operated by Bob Lunsford. The fireball duration approached 20 seconds.

In the hours after the fireball, the American Meteor Society (AMS) initially suggested that this was a Space Debris reentry, i.e. the reentry of something artificial from earth orbit.

But it wasn't.

Immediately upon seeing the video, I had my doubts. Upon a further look at the video, those doubt grew. To me, the evidence pointed to a meteoritic fireball, a slow fragmenting fireball caused by a small chunk of asteroid entering our atmosphere.

A discussion ensued on Twitter, until NASA's Bill Cooke settled the issue with multistation camera triangulation data, which showed that this was an object from an Apollo/Jupiter Family comet type heliocentric orbit with a speed of 15.5 km/s. In other words: my doubts were legitimite. This was not a space debris reentry but indeed a chunk of asteroid or comet.

I've already set out my argumentation about my doubts on Twitter yesterday, but will reitterate them again below for the benefit of the readers of this blog.

My doubts started because while watching the video I felt that the fireball, while slow and of exceptionally long duration, was still a tad too fast in angular velocity in the sky, and too short in duration, for this to be space debris. In the video, it can be seen to move over a considerable part of the sky in just seconds time.

The image below shows two stills from the video 6 seconds apart in time. The fireball passes two stars, alpha Ceti and beta Orionis, that are 35 degrees apart in the sky, and it takes the fireball a time span of about 6 seconds to do this, yielding an apparent angular velocity in the sky of about 5-6 degrees per second. That is an angular velocity that is a factor two too fast for reentering space debris at this sky elevation, as I will show below.

Image
stills from the fireball video, 6 seconds apart, with two stars indicated

Orbital speed of a satellite is determined by orbital altitude. Reentering space debris, at less than 100 km altitude, has a very well defined entry speed of 7.9 km/s. This gives a maximum angular speed in the sky of about 5 degrees/second would it pass right above you in the zenith (and only then): but gives a (much) slower speed (2-3 degrees/second) when the reentry is visible lower in the sky, such as in the fireball video.

To gain some insight in the angular velocity a reentering piece of space debris would have at the elevation of the California fireball, I created an artificial 70 x 110 km reentry orbit over southern California that would pass the same two stars as seen from San Diego.

The map below shows that simulated track, with the object (marked by the green rectangular box) at 70 km altitude and positioned 6 seconds after passing alpha Ceti (marked by the green circle):


Image
Simulated reentry track. click to enlarge
The angular velocity in the sky for a reentering object at this sky elevation suggested by this simulation is barely half that of the fireball. During the 6 seconds it took the fireball to move over 35 degrees of sky passing alpha Ceti and beta Orionis, the simulated reentering object would have moved over only 15 degrees, i.e with an angular velocity of 2.5 degrees/second rather than the 5-6 degrees/second of the fireball.

So this suggested that the fireball was moving at a speed a factor two too high for space debris. This therefore pointed to a meteoritic fireball, not a space debris reentry.

There were other reasons to doubt a reentry too. There were no matching TIP messages on Space-Track, the web-portal of CSpOC, the US military satellite tracking network. A reentering object as bright as the fireball in the video would have to be a large piece of space debris: this bright is clearly not the "nuts and bolts" category but suggests a large object like a satellite or rocket stage. It is unlikely that CSpOC would have missed a reentry of this size.

To be certain I ran a decay prediction on the full CSpOC catalogue with SatEvo myself: no object popped up that was expected to reenter near this date either, based on fresh orbital elements.

The fragmentation in itself, one of the arguments in the AMS' initial but mistaken conclusion of a "space debris reentry", is not unique to space debris reentries. It is also a common occurence with slow, meteorite dropping asteroidal fireballs, especially when they enter on a grazing trajectory. Take the Peekskill meteorite fall from October 1992 for example:




Likewise, while a 20-second meteor is not everyday, it is not a duration that is impossible for a meteor. Such durations (and even longer ones) have been observed before. Such long durations are especially the case with meteors that enter in a grazing way, under a shallow angle.

At the same time, a 20 seconds duration would be unusually short for a satellite or rocket stage reentry. Such reentries are usually visible for minutes, not a few seconds or a few tens of seconds.

So, to summarize:

1) the angular velocity in the sky appeared to be too large for space debris;
2) the fireball duration would be unusually brief for space debris;
3) and there were no obvious reentry candidates.

On the other hand:

a) the angular velocity would match those of slow ~15 km/s meteors;
b) the 20 second duration, while long, is certainly not impossible for a meteor;
c) the fragmentation observed occurs with slow asteroidal origin meteors as well.

Combining all these arguments,  my conclusion was that this was not a space debris reentry, but an asteroidal origin, slow meteoritic fireball. This was vindicated shortly later by the multistation camera results of Bill Cooke and his group, which yielded an unambiguous speed of 15.5 km/s and as a result a heliocentric orbit, showing that this was not space debris but a slow chunk of asteroid or Jupiter Family comet.

In defense of the American Meteor Society (who do great work on fireballs): it is not easy to characterize objects this slow, certainly not from single camera images and visual eyewitness reports. Given the slow character and profuse fragmentation, it is not that strange that the AMS initially (but incorrectly) thought it concerned a space debris reentry. It does go to show that you have to be extremely careful in drawing conclusions about slow moving fireballs: not every very long duration fragmenting fireball is space debris.

Monday, 4 September 2017

OT: imaging the close flyby of Amor asteroid (3122) Florence



On 1 September 2017 near 12:06 UT the Amor class Near Earth Asteroid (3122) Florence made a relatively close approach to Earth. The nominal pass distance, 0.047 AU or about 18 Lunar distances, was a safe distance. It does not often come this close: the asteroid had last been about similarly close in 1930, and will not be really close again until 2057.

(3122) Florence is one of the more rare larger NEA's. It is about 5 km in diameter and currently has a theoretical MOID (Minimum Orbit Intersection Distance) of 0.044 AU, only slightly less than the pass this year.

While this is a safe distance for now, orbital disturbances in the (distant) future could bring it closer, and the size of the object is such that it would be of future impact concern. It is therefore on the PHA list, where PHA stand for "Potentially Hazardous Asteroid" (for some reason, I always make "Potentially Hostile Asteroid" of this in my mind, probably because of the similar "Potentially Hostile Aircraft").

(3122) Florence became quite bright during this close pass, and was visible in binoculars at a maximum brightness of about magnitude +8.7 just before the moment of closest approach.

About 1.5 days after the moment of closest approach, near local midnight of September 2-3, I imaged the fast moving asteroid from Leiden with my Celestron C6 telescope. It was about mag +9.1 at that time. The movie above, and the stacked image below, was made from 87 images (each an exposure of 10 seconds with a 5 second interval) taken over a 17-minute period between 22:31:32 - 22:48:47 UT (Sep 2).

The asteroid was at a distance of 0.048 AU at that time and moving fast through Delphinus, at an angular speed of about 22".5 per minute.

The equipment used was a Celestron C6 (15 cm) Schmidt Cassegrain telescope with F6.3 focal reducer, and a Canon EOS 60D DSLR at ISO 3200 in the prime focus of the telescope.

(the satellite that can also be seen zipping past in the movie, is a Russian GLONASS, Kosmos 2425)

Image
stack of 87 images taken over a 17-minute time interval
(click image to enlarge)

Thursday, 8 December 2016

OT: the slow, 13.8 second duration earthgrazing fireball over the Netherlands of 28 Nov 2016, 04:40 UT

Image
the long duration (13.8 s) fireball of 28 Nov 2016, 4:40 UT 
image (c) Jos Nijland, Benningbroek, NL - click to enlarge


In the early morning of 28 November 2016, near 04:40 UT (05:40 am local time), a bright, slow fireball with an extremely long duration occurred over the Netherlands.

The image above was captured by the all sky meteor camera of Jos Nijland in Benningbroek and shows how the fireball trajectory spanned much of the sky. This camera was  equipped with a rotating shutter, and the number of breaks visible in the trail amount to at least 13.8 seconds visibility. That is very long for a fireball.

With such slow, long duration fireballs, one of the first questions asked usually is: is it a meteor, or is it the re-entry of artificial space debris? In this case, the analytical results clearly show it was not an artificial object, but a meteoric fireball of asteroidal origin - i.e. a small chunk of asteroid entering the atmosphere.

A total of 7 all sky photographic cameras captured the fireball: apart from Benningbroek (Jos Nijland) shown above,  it was also captured by stations Ermelo (Koen Miskotte), Oostkapelle (Klaas Jobse), Utrecht (Felix Bettonvil), Bussloo (Jaap van 't Leven), Borne (Peter van Leuteren) and Twisk (Marco Verstraaten). Benningbroek also captured the last few seconds of the fireball on video with a CAMS camera. Koen Miskotte in Ermelo in the center of the Netherlands also observed the fireball visually, estimating it magnitude -5. He reported fragmentation.

Image
Click to enlarge

The photographs allow to reconstruct the atmospheric trajectory, speed, radiant point and heliocentric orbit of this fireball, and whether something survived at the end or not.

The fireball appeared between 04:40:26 and 04:40:40 UT. It entered the atmosphere on a grazing shallow angle of only 11.2 degrees. The trajectory was over 180 km long - the average trajectory for all stations combined is 183 km long, but some stations captured an even longer part, with Benningbroek topping all with 212 km trajectory length! The fireball started over the North Sea at an altitude of 77 km near 53.0 N, 3.1 E (average of all stations), and moved on an almost due West-East trajectory, over the tip of North Holland province and Lake IJssel, ending at 42 km altitude over the northern part of the Noordoost Polder near 52.8 N, 5.7 E.

Four of the 7 stations were equipped with a rotating shutter in front of the lens, allowing speed reconstructions. Combined with the radiant point determination, this yields the orbit in the solar system.

The fireball entered the atmosphere with an initial atmospheric speed of 15.45 km/s. At the end of the trajectory, at 42.3 km altitude, it had slowed down to a terminal speed of 9.3 km/s. At that point, nothing was left of the original meteoroid: no meteorites reached the ground, it had completely ablated away. The deceleration curve obtained is actually quite nice:


Image
Click diagram to enlarge


The apparent radiant of the fireball was low in the western sky, at RA 53.2 degrees, DEC +13.0 degrees in Taurus. The geocentric radiant (the radiant point corrected for amongst others gravitational influence) was at RA 43.8 degrees, DEC +0.4 degrees. The geocentric speed was 11.1 km/s.

Image
Click star map to enlarge

The resulting heliocentric orbit is that of an Apollo asteroid, with perihelion at 0.874 AU, aphelion squarely in the asteroid belt at 2.76 AU, an orbital eccentricity of 0.518 and an orbital inclination of  4.9 degrees.

Image
Click to enlarge


 

Thursday, 14 May 2015

[UPDATED] Why the Emergency Asteroid Defense Project (EADP) will not fly, imho

[editted and expanded May 15, 2015, to reflect on the content of the legal report commissioned by EADP. Edits and expansions are in italics between square parenthesis, to differentiate them from the original first version published]

The danger of an Asteroid impact is a real threat. To that, everybody agrees. It is however also (and I am not alone in stating this) a threat that has been, and is, overhyped by some.

Lately, a number of publicly very vocal groups have jumped on the bandwagon of  'asteroid defense'. Within the community of asteroid researchers (of which I am very modestly a member -  I search for and have actually discovered Near Earth Asteroids), some of these groups raise eyebrows and generate a somewhat uneasy feeling. Several people in our small community feel that some of these groups, often consisting of people considered outsiders, hijack the issue and overhype a threat in a way that is detrimental to the real issues and complexities involved.

One of the newest initiatives in this game is the Emergency Asteroid Defense Project (EADP). EADP wants to rescue us from a potential asteroid on a collision course with Earth. Note: there isn't such an asteroid in the picture yet.

On their website, EADP presents itself as a Denmark-based NGO that wants to develop and build an asteroid defense system for this purpose. The defense system EADP wants to build consists of two parts:

(1) a kinetic impactor, that will create an impact crater on the target asteroid;

(2) a small nuclear bomb that will next be steered into this crater and detonated, shattering the asteroid into smaller pieces.

Sounds feasible right?

EADP has just created a lot of publicity by starting a crowd funding initiative on Indie-gogo to jump-start their plans. They aim to raise money for a feasibility study and then launch their first test mission as early as 2017.

Mind you: to succinctly make clear what they propose, they propose to launch a nuclear bomb and detonate it on another celestial body. Or at least: develop the technology for it.

Now, IANASL (I Am Not A Space Lawyer). But apart from the worry that it is a private enterprise rather than a (consortium of) Nation States or the UN undertaking this: in my humble opinion, this plan runs foul of at least two international treaties, in a way that will not be easy to resolve and should not be glossed over.

EADP so far appears to do however . You should realize this before you toss your money to EADP.

[note added 15 May 2015: there is actual a legal report on their website - not their Indiegogo page - which is a bit buried, addressing these issues. From the contents of this report and its major recommendations - especially the first one -, it is clear that the issues raised should not be neglected. This is important for a crowd funding campaign, as this is information about the feasibility of the project and attached problems that potential backers need to know in order to decide whether to back the initiative. This report should have been a primary part of their Indiegogo appeal page]

For the plans of EADP to become reality, they need to:

(1) have c.q. develop a nuclear explosion device (i.e. a nuclear weapon);

(2) develop a kinetic impact weapon;

(3) find someone willing to launch these.

With regard to point (3), on their website EADP mentions the US commercial launch corporation SpaceX as an option. I have my doubts about their time-plan however: 2017 seems very soon to commission a launch. Building and launching rockets takes time [let alone tackling the political and licensing issues]. There are moreover other problems to employing SpaceX, discussed below.

Kinetic impact missions are not new. The technology for this already exists. Witness for example NASA's Deep Impact mission and LCROSS mission.

The problematic aspect is the nuclear payload that is employed next. And again, the technology is not what is most problematic here. The real problems are geopolitical.

EADP is Denmark-based, and they are an NGO (Non-Governmental Organization, i.e. a private enterprise of citizens). Denmark as a country itself has no nuclear weapon capability - and it is very doubtful that a sane government would put that capability at the hands of an NGO anyway, would they have it. Denmark also currently doesn't have their own space launch capability (but they do take part in ESA, which has). So they would be dependent on foreign countries for a launch capability (e.g. the US SpaceX, or ESA as a European organization, or Roskosmos in Russia, JAXA in Japan or perhaps the Chinese), and EADP would either have to develop/build the nuclear device themselves (but: see below), or obtain it from a country that does have a nuclear capability.

Here, they face their first problem: the Treaty on the Non-Proliferation of Nuclear Weapons (NPT). The nuclear powers US, UK, France, Russia and China all signed this treaty. They would violate this treaty would they help EADP to a nuclear explosive device. They would also violate it by simply providing the technological aid for it (i.e. helping to develop it).

Likewise, given that Denmark - although not possessing a nuclear capability on its own -  is a signatory to the treaty as well, the Danish government can not allow EADP to develop a nuclear explosive device themselves, as that again would breach the treaty they signed. 

[note added 15 May 2015: while the legal report commissioned by EADP discusses the Partial Nuclear Test Ban Treaty (NTB), not a word is being said about the NPT).

Israel, Pakistan, India and North Korea also possess The Bomb and did not sign the treaty. Yet, it is highly doubtful they will openly share their technology with EADP. And if they would, they would get in severe trouble with the other nuclear powers. Handing your nuclear technology to private organizations in another country is the kind of thing that starts a war, as it might lead to nuclear technology falling into the wrong hands. The USA has invaded and bombed countries for less.

Moreover, EADP would still get in trouble with the fact that Denmark, the country in which they are based, has signed the treaty. Note that EADP need not actually build the actual device, for this to be problematic.

So there you have one problem with the plans of EADP.

But as if that is not enough, there is a second problem: the Treaty on Principles Governing the Activities of States in the Exploration and Use of Outer Space, including the Moon and Other Celestial Bodies of the United Nations (also known as the 'Outer Space Treaty').

This treaty has been signed by many countries, including Denmark and the United States. It regulates what can and can't be done in Outer Space and on celestial bodies other than Earth.You can find the full text of this treaty here. Important to realize, given that Denmark signed the treaty and EADP is a Danish-based NGO, is that the treaty unequivocally states that:

"States bear international responsibility for national activities in outer space, whether carried on by governmental agencies or by non-governmental entities"

In other words: EADP, as a Denmark-based NGO, cannot do as they wish: they are bound by the treaty signed by the Danish government. Even if EADP would outsource the nuclear device and/or the launch to another country, Denmark (plus the other countries involved in the launch) is responsible. Basically, this means that under the Outer Space Treaty, they can't allow it (just like they can't allow it under the Nuclear Non-Proliferation Treaty).

Of relevance are also provisions 2 and 3 of article III of the Agreement Governing the Activities of States on the Moon and Other Celestial Bodies that is part of the Outer Space Treaty. These state that (and note that while the texts below talks about the Moon, the preamble to these clauses makes clear it concerns not only the Moon but all other celestial bodies other than Earth, i.e. including asteroids):

States Parties shall not place in orbit around or other trajectory to or around the Moon objects carrying nuclear weapons or any other kinds of weapons of mass destruction or place or use such weapons on or in the Moon.
and:
The establishment of military bases, installations and fortifications, the testing of any type of weapons and the conduct of military manoeuvres on the Moon shall be forbidden

In other words: launching, let alone detonating, a nuclear explosive device to and on another celestial body (like an asteroid) is simply forbidden. In fact, I think Space Lawyers could get into a real heated argument whether testing with a dummy payload already breaches this clause of the Outer Space Treaty, as a test with a dummy load is still a test, i.e. it relates to the 'testing of any type of weapon' in the clause above. [Von der Dunk, legal advisor to EADP, thinks it is not].

These are questions that, in an international diplomatic environment, therefore should not be taken lightly (and on which different countries and different lawyers might take different viewpoints).

[Von der Dunk basically says the same in his report: at various points in the report it is stressed that "in view of the geopolitical sensitivities" the EADP initiative requires a firm open discussion on these points from a  very early stage onwards. i.e.: that these geopolitical sensitivities should not be underestimated (which is exactly the main point which I argue here!). This is also the first of the main conclusions at the end of the report (p. 32): "It would be recommended for the EADP to:  * Address from an early stage onwards and in a continuing fashion the risk of ‘political fall-out’ outside the United States which EADP missions might give rise to"]

Point is: while it would be possible that countries united in the United Nations would, in the context of the United Nations Assembly, perhaps lift these provisions in the case of a real, imminent asteroid impact danger (but: don't put up your hopes high, folks!), there is imho no way a private enterprise like EADP would get this off without such a real, imminent danger. [again, Von der Dunk appears to actually  agree on this in his report: lifting of certain treaties is seen as feasible by him in case of an "emergency situation", i.e. a real imminent threath]. It is highly, highly unlikely that they would get any country to cooperate with a test mission for this purpose (which is what they are fundraising for) as, even with a dummy load, this basically still is a weapons test in Space (or at least could be seen as this by third parties) and hence diplomatically a very sensitive issue.

Now, if you pose this case to space lawyers, they will tell you that the wording of the Outer Space Treaty is ambiguous. There is also the question, whether a nuclear explosive device to blow up an asteroid should be regarded as a weapon. There is discussion possible about that [e.g. Von der Dunk thinks it isn't necessarily so. ]. But that is not the point. Or rather: it is.

Countries tend to be suspicious of each other's intentions when doing outlandish things like this. Some countries might see it as a covert military space weapons test. Remember, for example, how the shootdown of the USA 193 satellite (an imminent [artificial] impact threath from earth orbit according to the US government) was and is widely regarded and criticized as a covert ASAT test by other countries. The USA itself has expressed significant worries about recent Chinese activities in both near and deep space (including experiments the Chinese themselves present as being purely "scientific") which it considers as covert Space Weapon tests. The same is true for US and other countries' concerns about the true intentions behind the North Korean and Iranian space programs.

This gives you an idea about how sensitive this all is. Strapping a nuclear load (even if it is a dummy) onto a rocket capable of reaching and leaving Earth orbit, basically makes it an ICBM test. EADP is therefore seeking to develop technology that by all means could be considered ICBM technology by some countries. It is clear, that international arms treaties and the NPT get relevant here. Thinking they do not, is irrealistic.

EADP mentions SpaceX. Note that SpaceX, as a US company, is bound by the treaties the USA signed. They cannot launch a nuclear device (or even a dummy test load of such a device) for EADP without the US Government's approval, and the US Government in principle cannot do this without approval of the international community (represented by the United Nations) as they would otherwise breach the Outer Space Treaty. I also doubt that the US government would be okay with a private US company launching a technology test that ultimately includes a nuclear explosive device developed by a private entity in another country. This is stuff where ITAR (the International Traffic in Arms Regulations) is potentially relevant, and the US Government has been a pain in the neck with respect to ITAR issues even to organizations like NASA.

These are things that, in the face of international geopolitic realities, should not be glossed over lightly. You should not think you can just happily build and test technology for a kinetic and nuclear impact device, expect another country to launch it for you, and think other countries will be okay with that and believe Denmark is out to Save the World. It just doesn't work that way. Not even for Denmark, as much as I love that country myself.

Note that the point also isn't whether you actually build and design the nuclear device. EADP is now (on twitter, after critical questions) stressing that they don't want to test the nuclear device but leave that to "specialists"They emphasize that they "must stress that handling nukes is not our job but the government's" (they don't say which government, by the way). They also said that "we will not be the decision makers but merely the providers and the fundraisers for the technology".

But, besides that it is odd to simply waive away testing the most crucial part of the proposed mission and technology, it is besides the point that they say they only develop, not actually build a nuclear device. Developing the technology meant to bring a nuclear explosive device into space, already is something that is (or should be) reason for concern.

This brings us to the real issue at hand. This issue is not whether some treaties are outdated and are at odds with reality and a hindrance to legitimate activities in space (they are). This is not about whether we should or should not try to do something in case we detect an asteroid on a collision course, either.

The real issue is that EADP is fundraising for a project, without having done the necessary diplomatic groundwork.

And that is where the real issue is. This is not an issue of technology. It is not an issue of money. It is a diplomatic issue, and the EADP initiative currently does not solve this. Even though it is the first thing they have to overcome for their plans to become reality.

[added 15 May 2015: Indeed, this also seems to be the explicit view of Von der Dunk in his legal report for EADP. The very first point of his final recommendations (p 32) reads:


"Address from an early stage onwards and in a continuing fashion the risk of ‘political fall-out’ outside the United States which EADP missions might give riseto, in particular as regards the use of NEDs in actual threat mitigation missions, byway of information of and appropriate consultation with the other states of the world, the United Nations and the global scientific community and by stressing the clear benefits for and interests of all mankind and all states in the EADP mission"
He also clearly warns (top of page 32) that not everybody might share his assessment that the EADP plans are not necessarily running counter to treaties like the NTB and OST:

"This is not to say, however, that in the present geo-political reality such a legal analysis would be globally shared, and efforts should be undertaken at the international level to minimise the potential for any ‘political fall-out’ that might result from the intended use of NEDs in outer space in such emergency scenarios, preferably by way of open and transparent information of, and as necessary consultation with, the other states of the world, the United Nations and the global scientific community"

i.e., on these points, the EADP commissioned Von der Dunk report actually confirms what I argue here: that geopolitically, this is a very sensitive issue. He also specifically mentions that circumnavigating these sensitivities takes a lot of time and diplomatic effort. I observe that this in turn is something which is nowhere reflected in the time-line put forward by EADP in their Indie-gogo appeal]

Their crowd-funding initiative hence seems extremely premature, and their timeplan is overtly ambitious given the realities of the diplomatic (apart from the technological and logistic) trouble they'll have to face.

What worries me, is that in their crowd-funding pitch to the public, they nowhere mention these fundamental issues. There for example isn't any statement that the Danish government is positively supporting all this (I have put out this question to EADP by twitter but received no answer yet). Nor on how they see their plans in the context of the various international treaties. [a legal report is included on their company webpage, but nothing of this is raised in their Indie-gogo appeal]

One of the EADP partners, Remco Timmermans, in answer to my question, simply claims on twitter that "This is a private enterprise. No government approval needed to do a technical design study".

Again, IANAL, but I highly doubt this is true. Private enterprises are not exempt of complying to the international treaties which their Governments sign, and the ramifications of such treaties are usually signed into the law of the signing country.

[Von der Dunk in his report does not discuss how this pertains to a technical design study, but makes very clear that government oversight indeed pertains to an actual space mission: "First, states are going to be held internationally responsible for any potential violation of international law resulting from space activities also if conducted by private entities. Further to such international responsibility, the ‘appropriate state’ would then be actually required to ensure “authorisation and continuing supervision" of such activities"].

So yes: government approval will be needed, given that Denmark signed treaties that (a) stipulate that Denmark does not acquire nuclear weapons technology on its own, nor acquires it from other countries; and (b) stipulate not to test weapons in space.

As pointed out,  the Outer Space Treaty explicitly states that Governments are responsible for what non-governmental organisations based in their country do in Space. I also doubt the Nuclear Non Proliferation Treaty would allow loopholes of the kind expressed by Timmermans. Just have your nuclear weapons developed by a private enterprise rather than the State and all is okay? That Kim never thought of this!

So I would expect the Danish government to take a keen interest in this. Here is a group of private citizens developing technology for a nuclear space mission, and indicating they will hand this technology to a third, foreign party for the operational part. That should raise alarm bells.

In another twitter answer to me EADP does say that the "legal raport [sic] and groundwork has been done" but here is the point:

To their audience of potential crowdfunders they do not say a thing about all these international legal and diplomatic issues involved.

And with whatever they may say on Twitter, I see no indication that these issues have been solved yet [added May 15, 2015: also not after reading Von der Dunk's commissioned report, which makes very clear that these geopolitical sensitivities should not be underestimated and demand action and openness from a very early stage onwards].

Again: IANASL (and I would like to see some independent Space Lawyers chime in here!). But you don't have to be a Space Lawyer to see the trouble ahead.

The whole crazy idea has elements in common with the much discussed Mars One project: a bold, even downright crazy plan that however speaks to the imagination (the project had immediate staunch supporters), and which National governments so far didn't dare to tackle yet. Ad to this a lot of publicity, an easy glossing over very real political problems involved, and presenting an unlikely timetable. And of course, having it all in the end primarily revolve around solliciting money from the public.

If EADP doesn't want to become the next Mars One and wants to be taken serious, they will have to explicitly and honestly address these issues first: their plans in the context of national and international agreements, laws, and geopolitical reality.

And yes, it sucks that the survival of humanity is held in suspension by such geopolitical realities. But what is new under the sun here? Look at how we (not) handle global warming.

[final notes added May 15, 2015: 

- EADP on twitter berates me for focussing on the nuclear part of the project. That is their good right of course: but I find it disingenious how they try to separate the issues around a nuclear explosive device (NED) from the rest of their project, given that a NED is an integral part of the eventual deflection technology they want to develop and test. In my opinion, you can't seperate the issue of launching a NED from the current discussion.

- I want to stress again that my main point is the apparent easy way with which EADP, in their Indie-gogo appeal towards potential financial backers, glosses over the geopolitical realities pertinent to their plan. It is my firm position that this is not correct: in order to make a fair judgement on whether this plan is backable, potential donors need to be honestly provided with information on the potential difficulties to be encountered as part of the endeavour.]

(I thank Brian Weeden for some comments on a draft of this post. All opinions expressed are however solely mine)

Friday, 27 February 2015

OT: another update on NEA 2015 CA40

Image
 
Our Near Earth Asteroid discovery (see earlier post) 2015 CA40 is now past it's point of closest approach. It reached that point, at 6.3 lunar distances, on Feb 23 near 21:49 UT.

Image


The animated GIF above shows the asteroid early on Feb 24, about 12 hours after closest approach, imaged with the 0.61-m F/10 Cassegrain of MPC G68 Sierra Stars Observatory in California, USA. The animation is made from 6 images taken over a 10-minute timespan. Each image was 30 second exposure, and the images were separated by 2 minutes.

The observed orbital arc of the asteroid now extends from Feb 15.93 to  Feb 24.58, or 8.5 days. Updated orbital elements from the MPC (MPEC 2015-D86, 26 Feb 2015):

Epoch 2014 Dec. 9.0 TT = JDT 2457000.5
M 298.05944              (2000.0)
n   0.84818796     Peri.  176.19408    T = 2457073.52693 JDT
a   1.1052859      Node   334.93169    q =     1.0044127
e   0.0912644      Incl.   15.06659    Earth MOID = 0.01553 AU
P   1.16           H   24.6
From 147 observations 2015 Feb. 15-24, mean residual 0".74.

13 observatories have now contributed to the observations, including our own MPC 461 Piszkéstetö where we discovered the object, and two observatories I used myself for 'remote' observations: MPC G68 Sierra Stars Observatory in the US and Q65 Warrumbungle observatory in Australia. The full list of contributing observatories (up to 24 Feb 2015) is:

461   Piszkéstetö Stn. (Konkoly), Hungary
J95   Great Shefford, UK
246   Klet obs. KLENOT, Czechia
J69   North observatory, Clanfield, UK
703   Catalina Sky Survey, USA
F65   Haleakala-Faulkes Telescope North, Hawaii, USA
C47   Nonndorf, Austria
G68   Sierra Stars Observatory, Markleeville, USA
474   Mount John Observatory, New Zealand
A48   Povegliano Veronese, Italy
B18   Terskol, Russia
Q65   Warrumbungle, Australia
W87  Cerro Tololo-LCOGT C, Chile


The asteroid is currently only observable from the southern hemisphere.

Sunday, 22 February 2015

OT: An update on Near Earth Asteroid 2015 CA40

2015 CA40, the Amor Near Earth Asteroid discovered by Krisztián Sárneczky and me with the 0.60-m Schmidt telescope of MPC 461 Piszkéstetö (Konkoly) in Hungary on Feb 15, 2015 (see previous post) has now been observed for a week.

Image


The animated GIF above shows the asteroid zipping through the FOV of the 0.61-m Cassegrain telescope of MPC G68 Sierra Stars Observatory in Markleeville, USA, in the morning of Feb 21. It was made from 5 images of 30 seconds exposure each, separated by 5 minutes each. A single frame from this sequence (taken 21 Feb 2015 at 09:45 UT) is below. Even at a relatively short exposure of 30 seconds, the asteroid has trailed:

Image


With an observational arc of over 6 days, the orbital solution already is much better than it was when the discovery MPEC was issued. A number of observatories have now contributed to the observations. As of 22 February, these included, apart from our observatory MPC 461 Piszkéstetö (Konkoly):

246 Klet obs. KLENOT
703 Catalina Sky Survey
C47 Nonndorf
F65 Haleakala-Faulkes Telescope North
G68 Sierra Stars Observatory, Markleeville
J69 North observatory, Clanfield

J95 Great Shefford

The G68 observations are 'remote' observations by myself (see images above) on Feb 21.

Current orbital elements (source MPC, MPEC 2015-D57 of Feb 22):

Epoch 2014 Dec. 9.0      TT = JDT 2457000.5 
M 298.04783 (2000.0) 
n 0.84852056     Peri. 176.17901      T = 2457073.51198 JDT 
a 1.1049971      Node 334.93125       q = 1.0043903 
e 0.0910471      Incl. 15.04633  
P 1.16           H 24.5             Earth MOID = 0.01551 AU

From 104 observations 2015 Feb. 15-21, mean residual 0".54.

When we discovered 2015 CA40 on Feb 15 it was at 15.6 lunar distances. Tomorrow near 21:48 UT (Feb 23, 2015) it will have its closest approach, to 6.3 lunar distances. In the days following this it will move out of view of the Northern hemisphere, but I hope to be able to follow it a few days using the 50-cm telescope of MPC Q65 Warrumbungle Observatory in Australia.

NASA has placed 2015 CA40 on the NHATS page. This page lists objects in orbits suitable for potential future crewed space missions. NHATS stands for Near-Earth Object Human Space Flight Accessible Targets Study.

Last but not least, a picture of the 0.60-m Schmidt telescope at MPC 461 Piszkéstetö (Konkoly) in Hungary with which we discovered the asteroid (image Krisztián Sárneczky/Miclós Rácz):

Image

For those able to read Hungarian (or use Google Translate), a nice story about the discovery in Hungarian is here. Stories in Dutch are here, here and here (and of course my previous blogpost).

Tuesday, 17 February 2015

OT: the discovery of Near Earth Asteroid 2015 CA40 (updated)

Satellites is not the only thing I dabble with: as some long-time readers of this blog know, I am also involved in asteroid searches.

Since 2012 I am part of a small team that searches for asteroids with the 60-cm Schmidt telescope of Piszkéstető (MPC 461, Konkoly obs, Szeged university) in Hungary. The project is run by Dr Krisztián Sárneczky from the Szeged university.

My task in this project is to visually inspect the images for objects that have been missed by the automated (computerized) moving object detection routines. Typically, Krisztián sends the images to me via Dropbox within hours of the observing session. I then inspect them on my pc at home here in the Netherlands and measure any unidentified objects I encounter on the images. Over the years I have fished out a number of new main belt asteroids from our imagery.

This weekend, I found a Near Earth Asteroid in the imagery, my first NEA find in this project and my second in total (10 years ago I found NEA 2005 GG81 when I was a plate reviewer with the Spacewatch FMO project).

Image
Part of one of the discovery images from Feb 15. Note the faint trail.

We had a run of several nights with the Piszkéstető Schmidt telescope last week. On Monday around lunchtime I was inspecting images taken Sunday-on-Monday night by Krisztián at high declination (+56 degrees) in Ursa Major. Usually, images at this high a declination are devoid of asteroids. But this time I noted a small moving streak in the images near RA 14h 22m 32.6s, dec. +56 16' 37". See above for (a part of) one of the images, and the animation below. Each frame in the animation below is a 5-minute exposure.

Image
Animation of the discovery images.

Initially I was a bit cautious. As can be seen in the animation above, the object was very faint in the first two frames and brighter in the last two. This is a bit unusual (it can be due to rapid rotation of the object, or -most likely in this case- to changing sky conditions). My first thought therefore was a high altitude slowly flaring satellite: but checking the image times it was clear that this object moved much too slow for a satellite. So: a Near Earth Asteroid?!

I mailed Krisztián the positions noting that it looked like an FMO, a fast moving NEA. Krisztián remeasured the images (measuring is difficult with trailing objects, and certainly faint trails) and sent the observations to the Minor Planet Center (MPC) of the IAU in Harvard, under our temporary object designation "SaLa122".

It was then posted on the MPC's "NEOCP" page, a webpage that lists potential Near Earth Asteroid discoveries with a request to other observatories for confirmation. Due to a mistake it initially appeared as "SaLa123" there (see below) with only 50% of our data: this was however quickly corrected and soon it was on under the correct designation "SaLa122".


Image
SaLa122 (under the erroneous designation SaLa123) on the NEOCP

At that moment we had a 30-minute observational arc, which is very short. It was vital that the object should be recovered over the next day, otherwise the object would be regarded as "lost" and would not count as a discovery.

Luckily, that recovery happened! The next night (16-17 Feb) Krisztián managed to relocate the object with the 60-cm Schmidt (see image below) and could follow it for several hours. In addition, astronomers at the Czech Klét observatory and British amateur astronomer Peter Birtwhistle at his private Great Shefford Observatory in the UK looked for the object too and could confirm it. This expanded the observational arc to 29 hours, enough for a preliminary orbit determination.

Image
Stacked follow-up images from MPC 461 in the night of Feb 16-17

In the late afternoon of Feb 17 the MPC made the official discovery announcement in MPEC 2015-D10: the object now has the official designation 2015 CA40.

2015 CA40 is a borderline Amor/Apollo asteroid with [updated 22 Feb 2015] a semi-major axis of 1.1049538 AU, an eccentricity of 0.0910145 and an orbital inclination of 15.04 degrees. The perihelion is just outside the orbit of the earth at 1.004 AU. The aphelion is at 1.20 AU, well within the orbit of Mars. The orbital period of the asteroid is 1.16 years. With H=24.5 the asteroid is estimated to be about 45 meters in diameter.

Image
Orbit of 2015 CA40

[Updated] 2015 CA40 orbital elements (MPC, from MPEC 2015-D47)

Epoch 2014 Dec. 9.0   TT = JDT 2457000.5 
M 298.04901 (2000.0) 
n 0.84857047     Peri. 176.17310     T = 2457073.50630 JDT 
a 1.1049538      Node 334.93131      q = 1.0043870 
e 0.0910145      Incl. 15.04278      Earth MOID = 0.01551 AU
P 1.16           H 24.5 

From 98 observations 2015 Feb. 15-21, mean residual 0".51. 

The theoretical minimum distance (MOID) of the asteroid's orbit  to the orbit of the Earth is 0.0155 AU or about 6 times the Earth-Moon distance. Closest actual approach of the asteroid to Earth this year, to about 6.3 times the lunar distance, is in the night of Feb 23-24 when it might reach mag. +16.6 and will be moving at a speed of 42" per minute.

Objects in this kind of orbit with a semi-major axis of ~1.0 AU (similar to the orbit of the Earth) are objects that already must have had one or more close encounters with the Earth and/or Mars.

We plan to follow the object over the coming nights, to expand the observational arc as much as possible, in order to increase the chances of it being found back during the next similarly close approach, which will be on 23 February 2066. There are some earlier dates at which the asteroid comes near Earth too (indicated in the diagram below: e.g. 2022, 2029, 2037, 2044, 2051 and 2058), but at a clearly larger distance than in 2015 and 2066. It will be much fainter and hence harder (but not impossible, given a big enough telescope) to detect during those years.


Image
click diagram to enlarge: distance (in AU) of 2015 CA40 to earth over the coming century

Earlier close approaches to less than 0.1 AU over the past 200 years were in 1813 (0.0161 AU);  1849 (0.0429 AU); 1863 (0.0245 AU); 1899 (0.0773 AU); 1928 (0.0469 AU); 1950 (0.0503 AU); and 1979 (0.0665 AU).

2015 CA40 is  the 7th Near Earth Asteroid discovered by the Konkoly survey and my second NEA discovery (and my first in the Konkoly project).

More on my other asteroid discoveries here.

Update (21 Feb 2015): we are still following this object and the arc now includes observations from early Feb 21.


Acknowledgement: we thank Peter Birtwhistle and the people of Klet observatory for their follow-up observations.

Friday, 12 April 2013

The discovery of asteroid 2013 GM21

I am way behind with my reporting on this blog, for which I apologize. I still have satellite observations from early March to report, as well as (somewhat off-topic) observations of comet 2011 L4 PANSTARRS and spectacular Aurora borealis (Northern Lights) from Finland mid March. For various reasons, I did not come to that yet. Maybe coming weekend...

Meanwhile, a short report on my latest asteroid discovery: 2013 GM21, which was published in the DOU MPEC K13-G54 today (Apr 12, 2013: look for object K13G21M).

On  April 6th, I was on my own initiative (and successfully) trying to get follow-up observations on three objects (2013 EZ102, 2013 EB103 and 2013 EC103) which Krisztian Sarneczky and I discovered in the Konkoly survey from MPC 461 (the 60-cm Schmidt of Konkoly, HU) mid-March. I was "remotely" using the 81-cm Schulman telescope of the Mt. Lemon Sky Center (MPC G84) for that, one of the telescopes in the SSO Network.

In the images that should (and did) contain 2013 EZ102, I found two other moving objects. Both were unidentified - i.e., they were not in the MPCOrb asteroid database of the IAU Minor Planet Center and could be new discoveries! So they were submitted to the MPC with the temporary designations LaMa515 and LaMa516.

One of these (LaMa515) turned out to have been observed by another observatory just days before, so that one was not a new discovery: the other observatory alas beat me to it.


 photo 2013_GM21_LaMa516_6APR_G84_anim_zps6ec97a6c.gif
click image to enlarge


The second object however, a mag +19.5 to +20 object I temporarily designated LaMa516 moving quite close to 2013 EZ102 in the images, turned out to be truely new: my observations of April 6th were the first! It can be seen in the blink above, which shows you a small part of the April 6th discovery images. 2013 EZ102 is in the images too.

I next obtained new images, based on a very rough search orbit fit, on April 7th, 8th and on April 11th, again using the 81-cm telescope of MPC G84. As a result, it was formally MPEC-ed today by the MPC as 2013 GM21: my second asteroid discovery using a "remote" telescope! And my 69th asteroid discovery in total (and 5th in 2013, the other four being in the Konkoly survey. For a full list of my discoveries see here).

The asteroid is a borderline Maria family main belt asteroid. With H=16.8, it is an estimated 1.5 km large. It has the following orbital elements (source: MPC):

2013 GM21

Epoch 2013 Mar. 29.0 TT = JDT 2456380.5   MPC
M 351.06235              (2000.0) 
n   0.24233744     Peri.   39.90632             
a   2.5479390      Node   164.25356             
e   0.0734092      Incl.   17.12483
q   2.3608968      T       2456417.38101 JDT 
P   4.07           H   16.8 
From 13 observations 2013 Apr. 6-11.
 
 

Image

Image
click images to enlarge

As can be seen in the orbital plots, the orbit is well inclined to the ecliptic. I discovered it when it was in opposition and close to perihelion of its orbit, these two factors combining in a maximum brightness for the object. This is basically the same situation as with my earlier discovery 2012 SM58.

Sunday, 17 February 2013

Movie: Why the Russian Super Meteor was not related to asteroid 2012 DA14 - explained with the help of an orange

Dutch note: een Nederlandstalige versie van deze video is eerder hier gepost.



Added Note: the reality is slightly more complex than I present it in the video, as objects that graze just past the earth limb are slightly deflected by earth gravitation and can end up on (low) northern latitudes. Latitude 55 N is out of the question though, and as this added detail might make the story too complex I decided to leave it out.

Filmpje: waarom de supermeteoor boven Rusland niets te maken heeft met planetoide 2012 DA14 - uitgelegd met behulp van een sinaasappel

Note to English readers: an English version of the Dutch language video below is posted in a separate post here.




Toegevoegde noot: Het is in werkelijkheid iéts complexer dan ik hier doe voorkomen, omdat een langs de rand van de aarde scherend object door de aardse zwaartekracht iets wordt afgebogen en er zo dus wel fragmenten op (lage) noordelijke breedtegraden terecht kunnen komen. Maar 55 Noord is echt buiten de mogelijkheid, en ik heb dit er daarom maar uit gelaten omdat het anders misschien te complex werd.

Saturday, 16 February 2013

On national television about 2012 DA14 and the Russian super meteor

Yesterday was a crazy day, that started as soon as I woke up, opened my e-mail and saw the messages about the Russian super meteor event. Next, my telephone was red-hot from phone calls, and my e-mail and twitter flowed over from private messages by persons and news media seeking information.

I got two TV crews visiting me, plus a radio reporter, and I turned down a couple of other media requests.

At 22:00 (10 pm) Dutch time I was Live in the broadcast of 'Nieuwsuur', a prominent news program on Dutch national television channel Nederland 2. Through a satellite connection, I was interviewed by the news anchors in the studio, while I was standing next to my telescope in my courtyard. The topics were both the Russian event and the 2012 DA14 asteroid fly-by.

Image
 TV van in the street

Image

Image

screenshots from the live Nieuwsuur broadcast

The video (in Dutch) can be seen here. It starts directly with my item.

I was also interviewed by a regional TV and radio station, TV West. The video of that TV appearance (again in Dutch of course) can be viewed here [link fixed: it initially erroneously linked to the Nieuwsuur item]: my item starts at 3:40 in the video.



Image
TV West filming my explanation

Image

Image
Screenshots from the TV West broadcast

Image
Radio reporter interviewing me

Friday, 15 February 2013

[updated] HUGE fireball over Russia this morning! Not 2012 DA14 related.

A HUGE fireball has appeared over Chelyabinsk, Russia, this morning. And with HUGE I mean: HUGE. Apparent brightness rivalling the sun, and very strong sonic booms leading to glass damage and people being wounded by flying glass. This must have been a seizable object entering the atmosphere.

Phil Plait, the "Bad Astronomer" has very good coverage including some amazing videos here, so I will refer to him for imagery and the general story (apart from two I include below: one showing the meteor, the other one the arrival of the shock wave).





Below, I will briefly explain why this fireball cannot have been a fragment of 2012 DA14, the ~50 meter wide asteroid that will pass very close to earth coming evening (Feb 15, 2013).

First of all (and Phil Plait points this out as well), the fireball in Russia came from the wrong direction. Several of the videos show it appearing in the east near the rising sun, coming from a N-NE direction. That is the wrong direction: fragments of 2012 DA14 are on a south-north trajectory.

What is even more important: fragments of 2012 DA14 could never enter the atmosphere as far north as latitude 55 N (Chelyabinsk). Fragments in orbits similar to that of the asteroid, have a theoretical geocentric radiant at declination -81 degrees, i.e. almost at the southern celestial pole. They hence approach earth from due south. This means that the northern hemisphere is out of reach of these fragments: the northern hemisphere represents (as seen from these approaching fragments) the "far side" of the earth.

[video added 18/02/2013]


[added 18/02/2013] In the above video I explain this more visually, with the help of an orange. In reality, it is slightly more complicated than I present it in the video, as objects grazing the earth's limb are actually slightly attracted by earths gravity and can end up a little bit over the line between "front" and "far" side of the earth. Ending up at latitude 55 N is nevertheless out of the question.

The funny thing is that the latitude of Chelyabinsk and the approach direction of 2012 DA14 (and fragments in a swarm around it) are well established facts, even if the trajectory of the Russian fireball is less so at the moment. So it is quite nice that from the encounter geometry with the 2012 DA14 orbit and the latitude of the Russian meteor alone, we can actualy already exclude a connection between the two with a quite strong certainty.

Fragments in 2012 DA14-like orbits and the Russian fireball itself are also too fast to be temporarily captured in earth-orbit, so that is no explanation either.

This fireball was not man-made space junk either. Besides coming from an unlikely direction, it is too fast and much too bright for that.

These are amazing times: the reentry of a Russian rocket stage seen from NW Europe on the evening of the 13th, then this hughe meteoric fireball over Russia this morning, and a close pass of asteroid 2012 DA14 tonight. Wow!

Saturday, 6 October 2012

OT - My latest Asteroid Discovery, 2012 SM58

It has been a while, but I finally have bagged another asteroid discovery to ad to the ones I already discovered earlier.

The new discovery appeared in MPEC 2012-T11 today as 2012 SM58 (packed designation: K12S58M). It is a high-inclination main belt asteroid.

On September 21, I was using SSON's 61-cm Cassegrain in search of an object discovered by another observatory, when I noted a faint  mag. +19.5 object moving near the upper edge of the images.  It is indicated in the blink below (which shows only part of the original images):

click image to enlarge
Image

The images were made at a high declination (+35 degrees) well away from the ecliptic. A check showed that no known object was at this position. So, a new, high inclination asteroid? At first I was not entirely sure. The object came out of the glare of a bright star, so it was a possibility that it was a reflection in the telescope's optical system. In the first of the 4 images (taken 15 minutes apart) it was difficult to see, probably because it was closer to the glare of the star. After measuring it in Astrometrica, and trying an orbit fit with FindOrb, it did however seem to fit an asteroid orbit.

I decided to wait until I had been able to image it a second time before sending in the observations to the Minor Planet Center. Bad weather on the two telescopes I use (in Arizona and California) however meant it took six days before I could image it again, on September 27th. With a Vaïsälä orbit fit to the Sept 21 observations to go by only, 6 days is already enough to create clear positional uncertainties. I was lucky though: the object was visible (near the image edges) in the new images.

While I was quite sure it was the same object, FindOrb initially had some trouble linking the 21 Sep and 27 Sep data, so I decided to send in both sets under different temporary designations: LaMa 502 and LaMa 504. The MPC sent me back a message indicating they thought it concerned the same object:   " LaMa504 (LaMa502 "

More bad weather and the entry of a full moon next again prevented new observations, untill I was able to image it again on October 4 and 5. Below is the blink of the October 5 images:

click image to enlarge
Image


The new discovery appeared in MPEC 2012-T11 today as 2012 SM58 (packed designation: K12S58M). It is a MBIIb asteroid with an inclination of  21 degrees. Orbital elements (from the MPC):

Epoch 2012 Sept. 10.0 TT = JDT 2456180.5                MPC
M 344.68019              (2000.0)
n   0.21885053     Peri.  110.11057          T = 2456250.50125 JDT
a   2.7271204      Node   273.19478          q =     2.3235562
e   0.1479818      Incl.   21.08086
P   4.50           H   16.7           G   0.15


Assuming a typical albedo, the absolute brightness of H 16.7 suggests an object about 1.5 km large.

The orbit in our solar system:

(click images to enlarge)
Image

Image