Home U.S. Coin Forum

Filled dies and VAMs

messydeskmessydesk Posts: 20,190 ✭✭✭✭✭
As has been mnentioned here before, Leroy Van Allen is no longer assigning VAM numbers to filled dies, since they are striking errors and not distinct die variations. While I agree with this, there is collector demand for filled die errors, especially those that are corroborated by multiple specimens, yet known to be rare.

In another thread, Leroy proposes that someone should come up with a cataloging system for these so that they could be tracked and collected as cataloged items. Filled dies clear up relatively quickly relative to the life of the die, and they can change dramatically from strike to strike. Somewhere I have a picture of a struck through grease progression on three 2000-S proof nickels, which I'll add later to illustrate this. When cataloging a die fill in ones collection, the degree to which a particular design element is filled needs to be cataloged, since demand for coins with completely missing features is going to be higher than demand for coins with partial fills. Some coins complicate this by having some elements filled completely, and some filled partially. I've seen a 1921-D VAM 1W that I've mentioned here before that has about half of the obverse stars missing completely, and most letters missing somewhat. Demand for this could should be pretty high given the size of the fill. As more with this fill are found, it can be determined what the "peak fill" was.

So how should they be cataloged? Start with the host die pairing name. In this case, VAM 1W. Call this die fill "Instance 1" and describe the appearance of the known peak fill. As lesser states of the fill are found, they can be compared with the peak and cataloged in a collection as, for example, "1921-D VAM 1W Filled Die Instance 1, 75% peak." Lots of words, but I can't think of a shorter description. If a more dramatic fill is found, the description of the peak can be changed, and then lesser fills would be adjusted downward. If another filled die of VAM 1W is found that cannot be a progression of Instance 1, it will be called Instance 2. It might even happen that a filled die remains filled while the opposite die is changed. In this case, the peak fill on the second pairing will be different than that on the first, but could still be cataloged accurately.

What should Leroy do? If he wants to start cataloging filled dies, he could use a system like this and keep VAM numbers for distinct die pairings or die states, as they were intended to be. If he doesn't want to catalog them but collector demand remains, someone else could start with the assigned VAM numbers and create a filled die catalog that references it. Writing ancilliary books to VAM has proven to be a worthwhile effort, as the author's collection gets a nice bump in value as collectors start demanding coins listed in the books.

What becomes of the filled dies currently assigned VAM numbers? Once a filled die cataloging system is established, the listings could be removed from the VAM catalog, but that could cause a certain amount of confusion, especially with something like the 1921-D VAM 1A2, which was formerly called VAM 1A until it was discovered it was a filled die instance of the VAM 1AB, which has since been removed and called VAM 1A1, and would logically be called VAM 1A if the filled die listing were removed. There is a limit to the tolerance collectors have for confusion, but it is probably far greater than that of grading services who may have to worry about attributions changing after holdering the coins. On the other hand, removing something from the VAM catalog may not be as traumatic to the value of the coins as one might think. The early die states of the 1882-O/S VAMs 3, 4 and 5 were removed after the 2nd edition of the VAM book was printed, but these somewhat anonymous varieties still enjoy hefty premiums over the later die states.

Whaddaya think?

Comments

Leave a Comment

BoldItalicStrikethroughOrdered listUnordered list
Emoji
Image
Align leftAlign centerAlign rightToggle HTML viewToggle full pageToggle lights
Drop image/file