Sunday, January 1, 2012
Why are there not more mass produced houses?
http://articles.sfgate.com/2008-04-26/home-and-garden/17144890_1_affordable-housing-complete-houses-precut
Absolutely Prefabulous An all-metal mass-produced house just may be America's architectural ideal. Luston mass produced house
Absolutely Prefabulous An all-metal mass-produced house just may be America's architectural ideal.
(MONEY Magazine)
By Paul Lukas
April 1, 1999
(MONEY Magazine) – My friend Jennifer lives in Oak Park, Ill., a town that happens to have a lot of Frank Lloyd Wright houses. So every time I visit, she sticks me in the car and takes me on a little tour, saying, "Look, there's a Frank Lloyd Wright house.... And there, that's another one.... Ooh, and over there, Frank Lloyd Wright designed that one, and that one.... And hey, did you see that Frank Lloyd Wright special on PBS?"
All of which is to say: I am so sick of Frank Lloyd Wright. Yes, the guy was a genius, a visionary, blah-blah-blah, and most of his architecture is undeniably lovely. But that's sort of the problem: I've always found his work to be a bit, well, tasteful for a proudly middlebrow nation like America. His houses look like they attended a finishing school--or, worse, make me feel like I should have attended one. I'm not suggesting that we suddenly adopt the trailer park as our national housing ideal. But I do believe there can be a happy medium that would uphold a laudable structural aesthetic and simultaneously honor America's fast-food, mass-production ethos--a non-Wright option for architecture-minded travelers to look for when they're on the road. And I'm happy to report that this ideal can be summed up in one word: Lustron.
More from Money Magazine
Get more from your donations
Retirement in 2012: Don't panic
12 money moves -- in 3 hours or less
Best Places to Live
Current Issue
Subscribe to Money
Lustron homes are among the more overlooked and underrated architectural developments to emerge in the wake of World War II. With countless G.I.s returning home, an enamel-products executive named Carl Strandlund saw the need for inexpensive, mass-produced housing. Using $37.5 million in federal loans, he formed the Lustron Corp., whose signature product was a prefab, $7,000, two-bedroom house made entirely of porcelain-enameled steel, inside and out--an all-metal home. Lustrons featured an ingenious radiant heating system, a combination dishwasher/ laundry washer and lots of built-in shelving. Each home was made of about 3,000 separate pieces, all of which were manufactured in Strandlund's Ohio factory, trucked to housing sites and assembled atop a concrete slab foundation. Although production and cash-flow problems put the company out of business within a few years, nearly 2,500 Lustrons were erected between 1948 and 1950. There's no comprehensive registry, but the majority of them appear to have survived, providing an enduring legacy of Strandlund's vision.
So how do you spot a Lustron? Primarily by its characteristic exterior. Instead of shingles, Lustrons feature two-foot-by-two-foot panels of enameled steel, the same stuff that stovetops are made of. Available in pink, tan, yellow, aqua, blue, green or gray, the panels were arranged in rows like giant tiles, screwed into wall studs and sealed with plastic gaskets. Viewed from the street, they give the houses a sort of quilted look. A Lustron is also distinguished by its porcelain-enameled steel roof, which, like the rest of the house, is rust-, termite- and fireproof. Throw in the fact that Lustrons are largely maintenance-free--no need to ever repaint, reshingle or reroof--and it all adds up to what Strandlund called, in the futurist parlance of the day, "a new standard for living."
For the past several years, the best place to see a Lustron was at 411 Bowser Ave. in Chesterton, Ind., where Jim Morrow, a retired building-supply retailer and real estate broker, had turned his Lustron into a public museum. "I felt that the house was so unique that there was no sense keeping it a secret," he says. Although Morrow tired of the museum biz and recently sold the house, the new owner, Brian Coudriet, says he welcomes drive-by Lustron hunters and even the occasional knock on the door from those curious about the interior. (The Chesterton area has another attraction for fans of modernist housing: The nearby community of Beverly Shores features five futuristic homes originally displayed at the 1933-34 Chicago World's Fair, including George Fred Keck's 12-sided "House of Tomorrow.")
Des Moines is another good place to look for Lustrons. More than a dozen are scattered about the city, including the fourth one ever assembled (originally as a demo model) at 4343 Chamberlain Ave. I got to see that Lustron and most of the others in Des Moines during a recent driving tour with Michael and Stephanie O'Neal, who have their own Lustron at 1136 Polk Blvd. and like to keep tabs on the others in the area. "Ooh, that one looks like it's in perfect shape," said Stephanie as we passed a particularly well-preserved Lustron. "And this one has a two-car garage," said Michael, his voice a mixture of admiration and envy. If the O'Neals seem a bit Lustron-obsessed, it's hard to blame them--the mass-produced houses, with their pastel exteriors, fit so neatly into the realm of pop culture that it's tempting to collect them all.
It's worth noting that Wright once designed a simple, affordable house called the Usonian, but only about 25 were ever built. There are more Lustrons than that in Wright's home state of Wisconsin alone, including one at 717 Porlier St. in Green Bay, which was recently purchased by the music and art luminary known as the Rev. Norb. "I'd driven by this house, and it always looked so cool," he says. "Then I went to an open house. And I said, 'This is great! This is the place for me!'" As for Wisconsin's most famous architect, Norb is unimpressed. "Frank Lloyd Wright?" he sniffs derisively. "What did he ever make that was mass-produced?"
Plenty of other areas offer good Lustron hunting--the houses were built in 35 states, all east of the Rockies, and a simple Yahoo! search usually turns up a few of them in real estate listings. I've also learned that clusters of Lustrons were built in several towns, including the Chicago suburbs of Lombard, Brookfield and Lincolnshire, all of which are just a few miles from the Frank Lloyd Wright houses of Oak Park. Guess where I'm taking Jennifer next time I visit?
Paul Lukas, winner of a Lowell Thomas Award from the Society of American Travel Writers, hopes to have a Lustron of his own one of these days.
the c programming language The Tools We Work With varnish guy
https://www.varnish-cache.org/docs/trunk/phk/thetoolsweworkwith.html
The Tools We Work With¶
"Only amateurs were limited by their tools" is an old wisdom, and the world is littered with art and architecture that very much proves this point.
But as amazing as the Aquaeduct of Segovia is, tools are the reason why it looks nowhere near as fantastic as the Sydney Opera House.
Concrete has been known since antiquity, but steel-reinforced concrete and massive numerical calculations of stress-distribution, is the tools that makes the difference between using concrete as a filler material between stones, and as gravity-defying curved but perfectly safe load-bearing wall.
My tool for writing Varnish is the C-language which in many ways is unique amongst all of the computer programming languages for having no ambitions.
The C language was invented as a portable assembler language, it doesn't do objects and garbage-collection, it does numbers and pointers, just like your CPU.
Compared to the high ambitions, then as now, of new programming languages, that was almost ridiculous unambitious. Other people were trying to make their programming languages provably correct, or safe for multiprogramming and quite an effort went into using natural languages as programming languages.
But C was written to write programs, not to research computer science and that's exactly what made it useful and popular.
Unfortunately C fell in bad company over the years, and the reason for this outburst is that I just browsed the latest draft from the ISO-C standardisation working-group 14.
I won't claim that it is enough to make grown men cry, but it certainly was enough to make me angry.
Let me give you an example of their utter sillyness:
The book which defined the C langauge had a list af reserved identifiers, all of them lower-case words. The UNIX libraries defined a lot of functions, all of them lower-case words.
When compiled, the assembler saw all of these words prefixed with an underscore, which made it easy to mix assembler and C code.
All the macros for the C-preprocessor on the other hand, were UPPERCASE, making them easy to spot.
Which meant that if you mixed upper and lower case, in your identifiers, you were safe: That wouldn't collide with anything.
First the ISO-C standards people got confused about the leading underscore, and I'll leave you guessing as to what the current text actually means:
All identifiers that begin with an underscore and either an uppercase letter or another underscore are always reserved for any use.
Feel free to guess, there's more such on pdf page 200 of the draft.
Next, they broke the upper/lower rule, by adding special keywords in mixed case, probably because they thought it looked nicer:
_Atomic, _Bool, _Noreturn &c
Then, presumably, somebody pointed out that this looked ugly:
void _Noreturn foo(int bar);
So they have come up with a #include file called so that instead you can write:
#include
void noreturn foo(int bar);
The file according to the standard shall have exactly this content:
#define noreturn _Noreturn
Are you crying or laughing yet ? You should be.
Another thing brought by the new draft is an entirely new thread API, which is incompatible with the POSIX 'pthread' API which have been used for about 20 years now.
If they had improved on the shortcomings of the pthreads, I would have cheered them on, because there are some very annoying mistakes in pthreads.
But they didn't, in fact, as far as I can tell, the C1X draft's threads are worse than the 20 years older pthreads in all relevant aspects.
For instance, neither pthreads nor C1X-threads offer a "assert I'm holding this mutex locked" facility. I will posit that you cannot successfully develop real-world threaded programs and APIs without that, or without wasting a lot of time debugging silly mistakes.
If you look in the Varnish source code, which uses pthreads, you will see that I have wrapped pthread mutexes in my own little datastructure, to be able to do those asserts, and to get some usable statistics on lock-contention.
Another example where C1X did not improve on pthreads at all, was in timed sleeps, where you say "get me this lock, but give up if it takes longer than X time".
The way both pthreads and C1X threads do this, is you specify a UTC wall clock time you want to sleep until.
The only problem with that is that UTC wall clock time is not continuous when implemented on a computer, and it may not even be monotonously increasing, since NTPD or other timesync facilites may step the clock backwards, particularly in the first minutes after boot.
If the practice of saying "get me this lock before 16:00Z" was widespread, I could see the point, but I have actually never seen that in any source code. What I have seen are wrappers that take the general shape of:
int
get_lock_timed(lock, timeout)
{
while (timeout > 0) {
t0 = time();
i = get_lock_before(lock, t + timeout));
if (i == WASLOCKED)
return (i);
t1 = time();
timeout -= (t1 - t0);
}
return (TIMEDOUT);
}
Because it's not like the call is actually guaranteed to return at 16:00Z if you ask it to, you are only promised it will not return later than that, so you have to wrap the call in a loop.
Whoever defined the select(2) and poll(2) systemcalls knew better than the POSIX and ISO-C group-think: They specifed a maximum duration for the call, because then it doesn't matter what time it is, only how long time has transpired.
Ohh, and setting the stack-size for a new thread ? That is appearantly "too dangerous" so there is no argument in the C1X API for doing so, a clear step backwards from pthreads.
But guess what: Thread stacks are like T-shirts: There is no "one size fits all."
I have no idea what the "danger" they perceived were, my best guess is that feared it might make the API useful ?
This single idiocy will single-handedly doom the C1X thread API to uselessness.
Now, don't get me wrong: There are lot of ways to improve the C language that would make sense: Bitmaps, defined structure packing (think: communication protocol packets), big/little endian variables (data sharing), sensible handling of linked lists etc.
As ugly as it is, even the printf()/scanf() format strings could be improved, by offering a sensible plugin mechanism, which the compiler can understand and use to issue warnings.
Heck, even a simple basic object facility would be good addition, now that C++ have become this huge bloated monster language.
But none of that is appearantly as important as and a new, crippled and therefore useless thread API.
The neat thing about the C language, and the one feature that made it so popular, is that not even an ISO-C working group can prevent you from implementing all these things using macros and other tricks.
But it would be better to have them in the language, so the compiler could issue sensible warnings and programmers won't have to write monsters like:
#define VTAILQ_INSERT_BEFORE(listelm, elm, field) do { \
(elm)->field.vtqe_prev = (listelm)->field.vtqe_prev; \
VTAILQ_NEXT((elm), field) = (listelm); \
*(listelm)->field.vtqe_prev = (elm); \
(listelm)->field.vtqe_prev = &VTAILQ_NEXT((elm), field); \
} while (0)
To put an element on a linked list.
I could go on like this, but it would rapidly become boring for both you and me, because the current C1X draft is 701 pages, and it contains not a single explanatory example if how to use any of the verbiage in practice.
Compare this with The C Programming Language, a book of 274 pages which in addition to define the C language, taught people how to program through well-thought-out examples.
From where I sit, ISO WG14 are destroying the C language I use and love.
Poul-Henning, 2011-12-20
Dymaxion car chronology
http://www.washedashore.com/projects/dymax/chronology.html
Dymaxion car chronology
< back up to dymaxion car notes
1927
late in 1927, Bucky turns his attention to the transport phase of his comprehensive plan
he invents, at least on paper, his "4D twin, angularly-orientable, individually throtleable, jet-stilt, controlled-plummeting transport"
1933
given as main date for the car
January 1933, a friend gives "a few thousand dollars" for Bucky to test some of his Dymaxion ideas
due to the Depression at the time, this money has very large buying power
Bucky knows the Dymaxion house was not yet affordable to develop, and that jets weren't yet feasible, so he decides to focus on a ground vehicle
March 1933, rents a disused factory in Bridgeport, Conn.
screens 1,000 job applicants, hires crew of 27 to work under the engineering direction of Starling Burgess
July 12, 1933, demonstrated to the public
front-wheel drive, rear engine and rear-wheel steering
aluminum body, chrome-molybdenum aircraft steel chassis
1/8th inch shatterproof glass
19.5 feet long
about a half-ton
a great deal of suspension: The first frame, hinge-supported by the front wheels, carried the engine and drive shaft. Frame No. 2 was hinge-and-spring connected to Frame No. 1, but was supported by the steerable tail wheel. The body, in turn, had its own independent frame which was sprung directly from the front axle, with a balancing spring connected back, abreast the engine, to Frame No. 1. The consequence [...] was that the car could zoom across open fields with the agility of a light plane, yet provide a ride as smooth as any cruise on a highway.
Car #1car 1
color: white, with dark belly
sold to Captain "Al" (Alford F.) Williams, then holder of the world's speed record for seaplanes
Col. William Francis Forbes-Sempill, an English aviation expert, commissioned to come to the US and test the performance of car No. 1
car is involved in fatal accident (what date?)
both Williams and Fuller, after carefully inspecting the car's functioning parts and reconstructing the sequence of events, were convinced that the Dymaxion car itself had no design or structural fault which had a bearing on the accident
car is repaired
Williams sells it to the director of the automotive division of the U.S. Bureau of Standards
another source [3] says it was sold to Gulf Oil
was very lightwight, weighing about as much as a VW beetle [3]
October 18, 1933: US Patent application is submitted
1934
Car #2car 2
second car built on order from a group of English automobile enthusiasts
completed in January 1934
flat window panels on the front, instead of the rounded glass on Car #1
improved, lighter frame structure
color: entirely dark, and shiny
they no longer wanted it due to the bad publicity of Car #1's crash
some time later, Fuller sells it to a group of his Bridgeport mechanics
years later, it ended up USED AS A CHICKEN COOP [3]
also fairly light, but a little heavier than the first one [3]
Car #3car 3
Fuller spends his "entire family inheritance" to built car #3
color: emerald green, with white top and a blue Formica interior. [3]
according to J. Baldwin, it was really heavy, "built like a tank"
completed in 1934, makes it to the Chicago World's Fair
sold to Leopold Stokowski and his wife, who sold it a few months later
during the next nine years the car is resold many times, and for a long span disappears from sight
Peter Viemeister relates a story of going for a ride in the car in 1934, when he was not yet 6 years old.
1937
December 7 1937: US Patent Office grants the car patent #2,101,057
1943
Car #1 is destroyed in a fire in the U.S. Bureau of Standards' Washington garage
at the request of Henry Kaiser, Bucky redesigns the car, making use of newer automotive technology
the new design which was never built:
Powered by three separate air-cooled "outboard" type (opposed cylinder) engines, each coupled to its own wheel by a variable fluid drive. Each of the engine-drivewheel assemblies was detachable. The engines themselves were run always at the same speed; the speed of the car was controlled by varying the quantity of fluid in the coupling.
Low-horsepower engines - 15 to 25 hp, cut down to one engine at cruising speed, for 40-50 mpg
Steered at cruising speeds by the front wheels, rear-wheel steering was used only as an auxiliary for tight turns, or to move sideways
Tail mounted on extensible boom
summarized by J. Baldwin: "Ten years later, Bucky put what he'd learned to work in a much handier five-seater with a tiny engine at each wheel. This time, the front wheels steered, but all three could be steered for tight city turns and crabbing sideways into parking spaces. High speed stability was enhanced by extending the rear wheel on a boom to lengthen the wheelbase."
1944
Car#3 is discovered in Brooklyn, and repurchased for Fuller by his friend, J. Arch Butts, Jr. of Wichita, Kansas
1945
Car#3 shown at Wichita airport
estimated to have been driven 300,000 miles
Fuller restores it to prime condition
1950s
Car#3 disappears. J. Baldwin says he finally tracked down a junkyard owner in Wichita who says he cut it up for scrap during the Korean war. [3]
1960s
Reportedly, the magazine "Car and Driver" did some articles on the Dymaxion car in the late 60s.
Reportedly: "I remember the car being on display in the basement of the Museum of Science and Industry in Chicago in the mid 60's. I was frustrated because the windows had been painted and I couldn't see inside."
1970
December 1970 article in Special-Interest Autos, describes the Dymaxion. It appears online in 2007 on the Hemmings Auto Blog, SIA Flashback – Teardroppers powered by Ford
1970s
Reportedly, a wealthy patron from Beatrice, NE puts up the money to build three Dymaxion cars. This results in 3 chasses and 2 fiberglass bodies, but no finished vehicle.
Some people recall seeing a Dymaxion (presumably Car #2) listed for sale in Hemming Motor News in the mid-to-late 70s, with "the owner not asking a lot of money for it (under ten grand) ... the ad was in the front of the magazine in the special auto section"
Ted Staub reports "My Dad owned one of the Dymaxion cars ... 1978-1980 time frame.. in Kettering, OH"
1981
Bucky and his car pose with his 26' Fly's Eye dome during his 85th birthday party at the Windstar Foundation in Snowmass, Colorado
1995
July 1995, GENI sponsors and organizes the Buckminster Fuller Symposium and Centennial Celebration for 600 participants. Activities included a multi-media Opening Ceremony, several World Games, Symposia by 15 colleagues and students of Bucky, a Film Festival, display of the only remaining Dymaxion Car, and a Bucky for Kids Festival."
1998
Artist Steven Brower populates a diorama with a whole bunch of Dymaxion vehicles and fly's eye domes, in his work U-Town
2009
Crosthwaite and Gardiner, one of England’s most renowned restoration houses, is entrusted with the restoration of Cat #2, and the re-creation of Car #3, as reported on the Hemmings Auto Blog, Dymaxion No. 2 restoration underway; your help needed
Some resources used for this chronology:
[1] Dymaxion Transport page by J. Baldwin
[2] The Dymaxion World of Buckminster Fuller, Robert W. Marks (1960, 1973)
[3] correspondence between Wallace Johnston and Ann Willmott Andersson at WNET, which has some known inaccuracies in it
dymaxion car
http://www.washedashore.com/projects/dymax/
For those that haven't heard of it, the Dymaxion Car was a teardrop-shaped (least air resistance), 3-wheeled, rear-wheel (single) steering, 20 foot long, Aluminum bodied auto, designed by Buckminster Fuller in 1933 to achieve maximum output and service with minimum material input. It was about 6 feet tall (kinda like a big van), seated the driver and 10 passengers, weighed around 1600 lbs., went 120 miles/hr on a 90 horsepower engine, and got as much as 30 miles to the gallon of gas. Fuller referred to it as the "Dymaxion Car", "Dymaxion Vehicle", and "Omni-Medium Transport" since it was ultimately intended to go by land, water, or sky. Only three were ever built.
Since i will probably never be inside one in real life, and certainly never drive one, i would really like to do the next best thing: model it in 3D and simulate driving it. There are scattered bits of information about the car, in print and on the web, but i haven't found a complete history, so i attempt to compile one below.
patent drawingA biographer said "Bucky [...] took the idea of demonstrating what you are talking about very seriously. He said if you can't make a model of it, don't talk about it."
I have a printed copy of the original patent for the car, which has diagrams like the one to the right, from the out-of-print book "Inventions: The Patented Works of Buckminster Fuller". It includes top, side and front views, so there should be enough information to model at least the external body.
I haven't found anyone who's ever attempted this, which means i'll probably have to do it myself. Do you have any information that would help?
Notes
Chronology of the car
Pictures of the car
Print references to the car
Other notes on the car:
dymaxion Car #2 is at the National Automobile Museum in Reno, NV
however, they don't let you see the interior, claiming "it was never finished"
according to J. Baldwin, Car#2 was at one point: "Used as a chicken coop somewhere in the Midwest. This completely rotten the wood, vinyl, and formica interior. This, as you may have guessed, explains why the interior of the car is not viewable at the museum! No pictures were ever found showing the interior of the car, so the museum had no guide by which to reconstruct it. (looked through thousands of pictures in Fuller's archive looking for a shot of the interior, but couldn't find one.) Eventually it was found and sold to Harrah's for $90,000."
A quicktime movie (2.3 MB) of the car driving and unloading passengers.
The Buckminster Fuller Institute (BFI) website now has the text (and very rough figures) of the car patent. I scanned some higher-resolution patent figures.
Joe Moore's Buckminster Fuller Virtual Institute has a link page for the vehicle.
Some info is in WoodenBoat Magazine (!) from a few years back, and the connection is that its a bio about W. Starling Burgess, the naval architect/genius who collaborated with Bucky on the Car.
Fuller tested 22 different kinds of steering posts. The car always had a problem with shuddering from side to side, especially in wind, and he had been working on different ways to fix the problem.
When Fuller had the car, he rolled it with his family in it. They were injured but recovered--the car had seatbelts. Because of this accident, it was modified, and there are pictures of it with different detailing. These are sometimes mistaken for pictures of different cars.
Dymaxion page at 3wheelers.com
Dymaxion passengers is a large site with lots of pictures, notes and chronology of the car, by Michael John Gorman.
2009-09-19: synchronofile reports The Dymaxion Car is being restored by the company Crosthwaite and Gardiner, which causes some discussion on Slashdot: Dymaxion Car Being Restored
Modelling the Car
"As for the patent drawings, there are several drawings, but none of them reflect the car as built. J. Baldwin says the same is true of the Dymaxion house (which he took apart to have it moved to a museum in Michigan) -- the patent drawings differed from the blueprints, and both of these differed from the actual construction."
3DSI looked at using programs for creating 3D models from photographs
I tried a demo of 3D Builder, and went through the tutorials.
It is a very slow, painstaking process, even when your model is constructed of straight lines.
It would almost certainly be easier to just model it "from scratch" in an actual 3D modelling package.
Feb. 1999 took a stab at modelling the tires and shell in 3D Studio MAX
used the patent drawings as a guide
you can download the result in MAX or 3DS format
also tried cutting the windows into the shell, but the result didn't look very good
would be far preferable to model the internal framework first, then add the shell, like how it was actually built
Related Cars
In the 1940's, a couple of guys in British Columbia made a car strongly similar to the Dymaxion, but with 4 wheels.
Notes from 1986 World's Fair (Expo '86) in Vancouver, B.C. :"Aerocar" - designed and built by H. B. Oldfield and J. H. Norton, Victoria, B.C., 1940 - 1942. aka Bazil (Barney) Oldfield. Loaned to Fair by Mr. Robert Oldfield. License plate on car: Vintage 2086, "Spirit of Tomorrow".
"It's a very beautiful job of a Dymaxion knock-off, but with four wheels. From the front it's very similar, and the back is surprisingly similar as well"jones
a similar 3-wheeled car was designed by J. R. Jones
patent filed November 21, 1934 which is one year later than Fuller
used a "leaning thru curves" concept in its chassis design
the patent is available
a 4-wheeled, teardrop-shaped car (patented 1934) by famous industrial designer Norman Bel Geddes
bel geddes
he also designed a series of other land and air vehicles, all described on the Norman Bel Geddes page on the Stanford Dymaxion site
as far i can tell, none were ever built
fascinationthe Fascination
in the early 1970s, the 'Highway Aircraft Corporation' of Sidney, Nebraska produced a few 3-wheeled cars which look a lot like the Dymaxion car, except that the single wheel is in front and the back is flared.
anecdotal sources say around 3 were built, and one of them was still around in Nebraska around as of 1998
the 1932 Hill Arrow Plane
the Starliner was made by Robert Gougeon of Bay City Michigan in 1935 (not to be confused with the unrelated Ford Starliner)
there are very few other cars that put the front seat before front wheels, such as the 1960 Fiat 600 Multipla
Thanks to help from many people, including these:
Wallace L. Johnson of Amarillo, Texas, is considering redesigning the car and even building one
"I realize that the Dymaxion was very revolutionary for its time, but, is now 60 years old. Much change in engines, suspension and materials technology."
On this subject: Wallace Johnson's three-wheeled car material.
Bob Basques, a GIS / CAD fellow, may attempt to model the chassis with AutoCAD
Greg Trayling, a Canadian physicist, pointed me to more pictures, and info about the Aerocar
Joe S. Moore gave helpful references to the car
Mitch Casto told me about the J. R. Jones car and sent me the patent
Jeffrey McCabe sent me email about an attempt in the 1970s to build some Dymaxion car(s), although following correspondence indicates that these were most likely the Fascination.
Shawn Stanford provides a family history of Car #2
Jay Baldwin sent in corrections for some statistics in the car description, along with other details.
up to main site
Subscribe to:
Posts (Atom)