![]() |
33 build date How would I find the build date of my 33 and 34, both New Zealand new cars.
the 33 is C18NF 627, the 34 is C18MF 94 thanks Lawrie |
Re: 33 build date Lawrie, As you know, British Commonwealth countries recieved their Fords from Canada, which had their own engine assembly numbering system. I wish some industrious Kanuk would put together a code translation for our use, but I've never seen one. in comparing your numbers, it would seem that you've listed them backwards if the M & N are alphabetical codes for '33 & '34?
Kanuks, what say you? |
Re: 33 build date Alan, the N and M are the right way,I see by the list that was posted earlier that they are correct but there seems no month by month info.
Canadian Huh/ Lawrie |
Re: 33 build date Lawrie,
The best that is available is that the C18N prefix was the second of three prefixes used in the '33 model year. The first was C18H and it ran from 1 to 5,000. Theoretically, your '33 had the 5,627th '33 V-8 engine built by Ford of Canada which puts at least the engine more or less in the middle of the model year's production. Ford of Canada deliberately did not follow alphabetical order in choosing its second prefix letter for its engine number groups. For example, C18D was the prefix used for the first group of V-8 engines produced in April, 1932. C18A was the first prefix group used for '34 model V-8 engine production. Your '34's engine was produced early in the second '34 model prefix group (C18M) which suggests that your car would be a fairly early '34 model. The F is always present at the end of the prefix when the engine was destined to be installed in a RHD chassis and that applies to both Canadian and U.S. engine production. |
Re: 33 build date Thanks for that info, I thought that my chassis had been changed or something ,BUT I have the original ownership papers for them both and the numbers are on them as well as the chassis of both.Lawrie
|
All times are GMT -5. The time now is 05:26 AM. |
Powered by vBulletin® Version 3.8.11
Copyright ©2000 - 2025, vBulletin Solutions Inc.