Sunday, April 25, 2010
The Tale of P-38 #44-23914
My friend, Mr. Gould, obtained the accident report for #44-23914 and furnished me with a copy. I now present the small amount of information contained therein along with some other components that will fill out the story. Unfortunately, the report leaves more questions than it answers.
The day was September 30, 1944. A few days earlier and about 20 miles to the south, the super-secret Uranium pile of the B-Reactor, part of the Manhattan Project, had gone critical for the first time. Further away, men of the US and its allies in Europe had just taken part in in the ill-fated Operation Market Garden and were withdrawing to lick their wounds. The situation in the Pacific was looking up, soon our forces would be gathering for another invasion, this time on the Philippine Islands. The small town of Othello a few miles away was quiet, except for the freight trains bearing war materials every now and then. The wind was moving at a leisurely 9 miles per hour. There were a few clouds above the valley floor. The farm land did not show the scars of war, yet. That would change this afternoon.
There were several Army Air Fields near by. Moses Lake Army Air Field was the closest. The fighters from that base would be training throughout the day over the farmland of Eastern Washington. The fast Lockheed fighter was the one that was seen most. It could be seen in flights of four, most days. The pilots would be going through the various training missions. From navigation, to bombing, to dogfights and low level flight.
The P-38 Lightning was recognizable because of its unique shape. Instead of the normal cross shape of most aircraft, the P-38 looked a lot like two T's written close together and attached at the bottom. It had two engines and was a great fighter as long as the pilot did not mistreat it. A training film of the era cautioned against inverted flight for any length of time, as the oil pressure would drop dramatically and ruin the bearings in the engines. It also stated that if you needed to recover the aircraft in a downward maneuver, you needed to have at least 10,000 feet altitude.
On this particular day, at 12:55PM, yet another flight of P-38s had left Moses Lake Army Air Field. These four proceeded to a local gunnery range for a sighter burst and then climbed to 12,000ft. for a syllabus of "supervised acrobatics" and individual combat. (the number three man, 2nd Lt. James B. Keller, and number four man,2nd Lt. John W, Eveland, both stated that they were actually at 7000-8000, this difference in stated altitudes is interesting. The leader, 1st Lt. Charles N. Fagan, stated that the cloud bases were at 7000-8000 feet and the cloud tops at 11,000. Could this be a mix up?)
The leader strung his formation out in "String Formation." and began to "rat race" around the cloud tops. This would appear to be simply a game of follow the leader. At one point, about 1:30PM, according to all flight members, the formation passed into the top of a cloud or through a wisp cloud (again, they differ). The flight members all stated that they were only in the cloud for one to two seconds at most. They did not even switch to instruments. When they entered the cloud, the number two man was there where he belonged. When they came out he was gone.
The number two man was Flying Officer Gene L. Dyer, apparently of Australia. He was flying P-38L #44-23914. There were no problems listed concerning the aircraft, save for the left oil shutter which was left in automatic. Dyer simply disappeared from the flight. A BT-13 pilot, 2nd Lt. Morris D. English, flying in the general area witnessed a P-38 in a spin at about 1:20PM, it came out of the bottom of a cloud at about 6500 feet and at about 5000 momentarily recovered in a nose down position. The BT-13 pilot did not see more because a cloud obscured his vision.
When he was noted as missing, his flight made radio calls to him and to Moses Lake tower. They flew around looking for the crash site. Then they headed back to the field to see what the tower knew. Lt. Fagan took another plane out and searched for Dyer. He located the wreck and guided the crash truck and ambulance to the site.
The majority of the aircraft was recovered. What remains today are just small pieces. Some of the cylinder housings from the engines, various hydraulic fittings and hoses, and even the side of a Browning Mk. 2 .50 caliber machine gun. There is just a crater or impact scar that marks the place where Gene L. Dyer died. There is no other marker.
What happened? Is it possible for things to go so completely wrong in 1-2 seconds that you cannot even call for help in your plummet to the ground? Given the characteristics of the P-38, and the eye-witness report from the BT-13 pilot, it seems that Dyer somehow got himself into a spin and may have been recovering. The ground level at the crash site is about 1000 feet above sea level. If the flight was at 12,000 feet, it seems completely possible that Dyer had plenty of room to recover. However, if the two other members of the flight were indeed correct when they stated that the flight was at 7000 to 8000 feet, it seems Dyer was just too low to recover completely from the spin.
Is it possible that the three members of his flight were covering for each other when perhaps they had been doing maneuvers that were not permitted? I do not know. I only bring it up because of the amazingly short amount of time that he was out of sight and the conflicting reports, which do not seem to have been questioned by anyone. Even though I am aware that accidents can happen very fast, the report just seems to be missing something. I suppose we will never know for sure.
Sources:
USAF accident report for #44-23914
Personal observations of wreck site, March 14, 2009.
http://www.othellowashington.us/
YouTube, WWII era training film.
http://www.youtube.com/watch?v=pDmIB7u18_0
Saturday, February 6, 2010
C-141A 65-281 Burns on Ramp At McChord AFB.
Sources:
Accident report for #65-281, USAF.
C-141 Heaven, http://www.c141heaven.com/
Wikipedia.
Friday, December 11, 2009
F-106 #59-022, Raymond, Washington, October 3, 1967

Sunday, November 29, 2009
P-38H #42-66767, Ellensburg AAF AND Paine AAF. December 1943
Some people have bad luck; we called them unlucky. Some vehicles have bad luck; we call them lemons, especially when dealing with cars. What do you call an aircraft with bad luck, though? P-38H #42-66767 might fall into the category of an unlucky airplane. What about a group of machines built at about the same time? #42-66767’s siblings might also fall into this category, but more on them later. Aircraft #42-66767 was a P-38H-5 LO.
First, a little information about military aircraft designations. When a company gets approved to produce a new aircraft, that company produces a first example. In some cases, two or three. These are usually given designations beginning with X, basically indicating the aircraft was experimental. So the first P-38 would have been the XP-38. During that era, the first few production/service examples were given a designation beginning with Y, meaning these were prototypes. So the first few P-38s were YP-38s. The first model of an aircraft to see service, that is full service, is usually followed by A, so there was a P-38A. When the designers make improvements that are major, the aircraft undergoes a model change. The P-38H was a result of many improvements on the original P-38A. Sometimes, during a production run, minor changes or improvements are implemented. If they do not entail a model change, these improvements are marked by block numbers. Block numbers are a way to keep track of minor improvements since the first new model. Usually they jump by five, so the second block would be -5, then -10, then -15, however, that was not always the case. Sometimes these block numbers were followed by letters designating the factory at which the aircraft was constructed. A B-29A -10 BW would have been the third block built at the Boeing Witchita plant. So, P-38H-5 LO #42-66767 had minor differences from the earlier P-38H blocks. LO stood for the Lockheed plant.
P-38H-5 LO #42-66767 was assigned to Ellensburg Army Air Field. At the time, the field was used for training. On the first day of December, 1943, 66767 had already been up twice with two different pilots when Flight Officer Russell W. Senger got into her for a local gunnery mission at a little after 4pm local time. He went through his check lists and then taxied out to the active runway and took off as part of a four ship flight. The aircraft had been checked out and was considered airworthy, which she was. At about 5:30, Senger landed safely on Runway 29. His flight was cleared to taxi. It was 1734 hours, or 5:34pm. At that time of year in Central Washington it begins to get dark at about 4:30pm (in fact as this is being written, November 29, 2009, it is now 5:22pm and I consider it to be completely dark outside). It was well into dusk then, when Senger began taxiing back to the parking area. He had only go about 600 feet when the right main gear left the taxiway and entered a drainage ditch, which was about 4 ½ feet deep. The pilot could not right the situation once it had happened, and momentum carried it another 100 feet where it stopped at a right angle to the taxiway. A P-38 pilot taxiing behind him notified the tower of the accident. The accident board attributed it as 75% pilot error (carelessness) and 25% taxiway construction. They recommended painting marker lines on the taxiway.
Normally, that would be the end of an article like this. The aircraft would have been repaired and sent back to service. However, 66767 was an unfortunate aircraft. 66767’s nosewheel had been damaged in the December 1st accident. A group of workmen from the 32nd sub-depot at Paine Field replaced the entire assembly. However, they were unable to repair the nosewheel door because there was no sheet metal shop facilities at Ellensburg AAF. The Engineering officer decided to have her flown the short distance to the 32nd sub-depot at Paine Field with her wheels locked down.
The gear handle was placed in down and safetied (Captain Laven’s account says it was safetied with wire). The main landing gear shut-off valve was closed to prevent an inadvertant gear-raising. Captain George Laven, Jr. was chosen to fly the aircraft to Paine Field on December 29, 1943. He took off at 3:48pm and encountered no trouble during the flight, except that the propeller on the left engine went out and he had to set to the manual position (What he meant by that was probably the variable pitch propeller was not operating automatically, so he had to operate it manually). He entered the landing pattern at Paine Field at about 4:30pm. Everything was normal until about 200 yards into the landing roll when he felt the ship turning right. He applied left brake, but the ship continued to pull right. He looked over and noticed that the right wing was lowering and felt the ship settle in that direction. He knew then that the right gear was collapsing and so as much left brake as he could to ease the turn. As soon as it left the runway he shut off the booster pumps, batteries, and mixture controls. When the ship stopped he exited the aircraft, no doubt, with alacrity.
First Lieutenant Robert W. Campbell, assistant operations officer at Paine Field, witnessed Laven enter the pattern and land. He watched as the right gear began to collapse and the plane veared off the runway. He jumped in a vehicle and headed for the scene of the accident. When he arrived the pilot was out of the aircraft.
The accident board discovered that the “right landing gear locking pin had been screwed down too far.” This prevented the gear from completely locking. The shut-off valve had also been shut in cold weather on the eastern side of the state while cold oil was still in the line bewteen the main gear and the actuating cylinder. The oil became heated due to engine temperatures and the warmer external air temperatures of the coastal climate over Everett, Washington. The heat expanded the oil sufficiently to partially move the actuating cylinder enough to dislodge the locking pin. The shock of landing and Laven’s application of brakes put enough force on the gear to retract.
As a result of this accident both engines were damaged by sudden stoppage. Three propeller blades were bent. The lower stabilizer and rudder were bent and crushed. Relatively minor dame considering.
I do not have information concerning what happened to 66767 after this. Given the amount of damage described in the report, it seems she was probably repaired and went on to lead a productive life, perhaps eventually becoming a part of the soda can we drink from, or perhaps she eventually made her way overseas and saw a different end. We may never know.
That 66767 was unlucky, may remain to be seen, since the damage she sustained was minimal and she could be returned to flying status. That her sisters were unlucky is no joke. #42-66775, #42-66768, and #42-66778 all met similar fates. I will write of them at a later date, though.
Sources:
Accident reports for #42-66767, dates: 12-1-1943 and 12-28-1943.
Fighter Planes, http://www.fighter-planes.com/info/p38_lightning.htm
Friday, November 13, 2009
P-38L #44-24350
Thank You, 2nd Lieutenant Ingersoll for your sacrifice.
Thursday, November 5, 2009
Wilbur B-29 #44-69989
In the aftermath of WWII, Americans wanted their troops home. NOW. Once hot to fight and win a war on two fronts, public fervor cooled significantly once the cries for peace arose in the West and the East. Gone was the cool, level-headed father-figure of Roosevelt, here was the country-bumpkin dropped-into-the-frying-pan Harry S. Truman.
Sunday, October 4, 2009
F-106A #59-142
Monday, August 3, 2009
Welcome Home Mr. Speicher, Still Looking For #41-38253!
NOTE:
February 6, 2010: I recently got an e-mail that indicates that this aircraft has indeed been located. One assumes Lt. Russel eventually found his way home. It appears it was located as early as 1957.
Sunday, May 10, 2009
F-104C #57-912, May 10, 1963

(the F-104D at McClellan Aviation Museum, now Aerospace Museum of California)

Saturday, May 2, 2009
Pasco F-106 #57-2489 *update #2*
On Tuesday, March 19, 1963, (at about 1712Z or zulu, which would be 9:12am local, because PST is Zulu -8) an F-106 on a local training mission came down about 5 miles south of Pasco, Washington. Its pilot had reported control problems.
Earlier that morning, Captain William F. Tesmer and Lieutenant Donld L. Hatcher briefed for a local training mission. Expected takeoff time was 1615Z, however, their flight was scrambled early at 1557Z(7:57am local). Tesmer's callsign for the mission was AH06 and Hatcher's was AH05. At this time, AH06 reported "dolly in valid." This phrase is not familiar, so could be reference to some ground control point with that call sign, or perhaps he was reporting that his automated guidance/data link was faulty. The latter seems to be supported, though: Three voice intercepts were completed against SAC target Y209 (Again, probably a B-52 from a local base). The results were three "MA's" (Mission Accomplished?) for three attempts. AH05 then completed two data link passes. The first pairing for AH06 was at 1612Z and the last was at 1647Z. The last intercept was completed about 200NM southwest of Geiger Field.
At this time AH05 had 4800 pounds of fuel and AH06 had 6400. AH05 had gone supersonic, which acounted for the difference. Both were returning to base (RTB) at Geiger. AH06 was 12 miles in trail of AH05 at 40,000 feet. AH06 called tallyho on AH05 (meaning he had picked him up visually) and said he would make a pass on AH05 on the way back to Geiger. At 1657Z AH06 transmitted MAYDAY at GEORFF position DRQA5049. (I would sure love to know how this navigation system works)
AH05 stated that, to his knowledge, AH06's intercepts had been completely normal until his breakaway maneuver had begun. AH06 overtook AH06 on the starboard side "began a medium back turn to the left, passing directly overhead." Ah06 transmitted that his "flight controls are frozen" and requested that AH05 follow him. At this time AH05 estimated AH06's mach to be 1.3 or 1.4. AH06 suggested that his "vari-ramps have possibly not returned to their normal position" and "'there is no light on' (vari-ramp), indicating that he was at a supersonic speed sufficient to actuate the vari-ramps." (the vari-ramps would appear to be the F-106 version of a variable inlet. As airspeed increases, engineers have found that it is desirable to alter the flow of air into a jet engine to keep the incoming air subsonic, despite the speed of the aircraft. This is usually done by changing the inlet shape or placing baffles in the inlet. Different designers found different ways of doing the same thing, for example, on the SR-71, there was a movable cone that went forward or aft in front of the engine, according to the airspeed. for more information see this NASA site.)
AH05 observed AH06 perform two tight barrel rolls to the left and then stabilize into a shallow left turn. AH05 joined AH06 for the completion of a 360 degree turn. AH06 had descended from 40,000 feet to about 33,000 feet. At 29,000 feet AH05 lost visual contact with AH06 in the clouds. During the 360 degree turn, AH06 reported that "it fees as though it's stuck in flight mode; the trim button has no effect; I can only maintain 160-170 knots." After he entered the cloud deck, there is no more transcripts of the pilot's transmissions on this report, though, apparently, the "Tab U transcript" has more.
Captain Tesmer reported that he was ejecting at 1712Z. The crash occured sometime between 1712Z and 1719Z. Eye witnesses stated that the aircraft passed the east edge of Pasco on a SSE heading at about 1000 feet altitude. They observed the aircraft pull up as it approached rising terrain south of Kennewick, Washington. As it pulled up, an object, probably the canopy, came off the aircraft. "A few seconds later they observed a bright flash, smoke, dust, and heard a loud muffled explosion."
The accident was fatal for Captain Tesmer, though there are no details explaining how. It does not say where the body/ejection seat was found, nor does it offer any other details tht would flesh out this story.
The map appears to show the impact somewhere near Jump Off Joe, a peak of 2200 feet. Not too far from the Nine Canyon Wind Project. The photo shows the crash to be on plowed land. It seems unlikely, however, that there would be any remnants after 45 years of tillings.
The flight path shows the two aircraft came from the west over the Horse Heaen Hills, about half way between the Yakima Valley and the Columbia River. Tesmer is shown as descending to 28,000 feet above Badger, Washington. A few miles later, almost over the impact area, contact was lost with him at 16,000 feet. From here it seems he made a wide descending turn to the left to end up where he did. It would seem to me that Captain Tesmer could have jumped out earlier, but he chose to ride his mount and keep it under control as best he could. Was this to find a spot to land this high speed aircraft with a high landing speed(unlikely)? Or was this to make sure his aircraft did not come down on a populated area? It seems doubtful we will ever know for sure.
Additionally, it is interesting that F-106 #57-2489 is shown in at least one source as going down some 30 miles further to the south near Hermiston, Oregon instead of its official USAF position on the same date.
*UPDATES* (Many thanks to Gene Gould for his time in the local library) Here is some added information.
1. The crater left by the aircraft was about 20X30 feet and 6 feet deep.
2. The pilot, Tesmer, was a graduate of Ohio University.
3. He served 3 1/2 years in Japan before transfer to Geiger.
4. He was survived by his wife and two children(ages 1 and 4). His parents, too lost a son, they lived in Shaker Heights, Ohio.
5. Tesmer, according to the paper, did NOT eject. While the report did not say that he did, it did not say he did NOT eject. The popping of the canopy seemed to indicate he had, though, and given early F-106 dificulties with the ejection seat, I had wrongly assumed it was to be blamed.
6. The paper confirmed the assumption that Tesmer had likely stayed with the aircraft to avoid populated areas.
*UPDATE # 2*
After some emails and a little patience, a fuller story has come to be revealed. these are the additional details:
1. The aircraft appeared to strike the ground nearly vertically.
2. Despite the fact that the canopy was found about 2 1/2 miles NNW of the crash site, the pilot's "body had remained with the aircraft upon impact." The report blamed a malfunction of the seat as most likely. The F-106 had ejection seat difficulties early on.
3. Preliminary results indicated the there had been a loss of control or near loss of control.
4. The aircraft struck at a high speed or a high thrust, given the depth of the hole.
5. The remains of the aircraft were sifted through a screen and layed out in a hangar at Spokane Airport. the report basically suggests that all remnants were removed.
6. The report further suggests that maintenance forms and records were not kept.
7. The committee suggested that a steering/control problem had occured.
While this does not say much more than the library article and the original accident report, it does add a little to what we know. Hopefully this is the last update necessary, however, if you have any personal relation to the airplane, please leave a comment or drop me an email.


