More on the F-22 Problem in Hawaii
Aloha from the land of the “almost F22 deployment”. Keep an eye on your sources for the next couple of weeks to see if this makes the headlines.
You have probably heard that the USAF is deploying 12 F22 “Raptors” to Kadena for a 3-4 month rotation. They arrived at Hickam last Thursday from Langley enroute to Kadena. Launch on Saturday was uneventful (except they could only get 9 airborne). Problem came when they approached the International Date Line. As the first two flights crossed over, all of their computer driven systems went tango uniform. Essentially had a bunch of multi-multi-million dollar day VFR only jets loitering over where they knew not. Utilizing their trusty Hawaii ANG Tankers, they all made it back to Hickam for assisted approaches…on the wing of the two who did not cross over to the dark side and were unaffected. Hate to think of what it would have been like if we had the same weather we did a few weeks back. Will be very interesting to see how this comes across and what the fix is.
Aloha,
xxxxxxx
This was the small item in today’s Honolulu Advertiser, on page 3 of the main section:
ARRIVAL of F-22s in Japan Delayed
Kadena, Japan - The arrival in Japan of a detachment of the Unites States’ newest and most expensive fighter jet has been delayed, officials said yesterday.THE 12 F-22 stealth fighters were to arrive on Kadena Air Base on Saturday, but had to turn back after leaving
Hawaii. It is the aircraft’s firstoverseas deployment.Officials at Kadena and at Hickam Air Force Base were unable to immediately confirm why the arrival was delayed, or when they were rescheduled to reach Kadena.
The F-22s are scheduled to deploy to Japan for a three - to four – month training mission.
Did you enjoy this post? Why not leave a comment below and continue the conversation, or subscribe to my feed and get articles like this delivered automatically each day to your feed reader. If you don't have a feed reader, you can always have these articles delivered to your email inbox every day. Click here to sign up.
Trackbacks & Pingbacks
Comments
Leave a comment
Line and paragraph breaks automatic, e-mail address never displayed, HTML allowed: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <strike> <strong>
\"raptor squadron, squawk VFR, frequency change approved, suggest 121.50 for assistance, good day\"
“raptor squadron, squawk VFR, frequency change approved, suggest 121.50 for assistance, good day”
This is not a new problem. Here\'s an excerpt
from “>http://www.f20a.com/f20ins.htm
\"An example of an undetected software bug in the F-20 INS occurred during the two-aircraft world tour. After GG1001 crashed in Korea, GI1001 had to make the lonely trip home, alone, across the north Pacific from Hawaii to Alaska. The two aircraft had traveled around the world easterly, flying from California, to Farnborough in England, then across Europe, North Africa, and Asia. As the aircraft crossed the international date line for the first time, the inertial navigation system went haywire. The pilot had to use the compass, and once within range of Alaska, radio homing to navigate. After landing, shutdown, and restart in Alaska, the system worked fine. The problem was found to be a multiplier with the wrong sign deep in the software code. The problem would never emerge until the moment the aircraft first crossed the international dateline, going from west to east.\"
This is not a new problem. Here’s an excerpt
from http://www.f20a.com/f20ins.htm
“An example of an undetected software bug in the F-20 INS occurred during the two-aircraft world tour. After GG1001 crashed in Korea, GI1001 had to make the lonely trip home, alone, across the north Pacific from Hawaii to Alaska. The two aircraft had traveled around the world easterly, flying from California, to Farnborough in England, then across Europe, North Africa, and Asia. As the aircraft crossed the international date line for the first time, the inertial navigation system went haywire. The pilot had to use the compass, and once within range of Alaska, radio homing to navigate. After landing, shutdown, and restart in Alaska, the system worked fine. The problem was found to be a multiplier with the wrong sign deep in the software code. The problem would never emerge until the moment the aircraft first crossed the international dateline, going from west to east.”
Thanks for the link Wade. It looks like they just fixed the issue with the f-22\'s, however I don\'t think they should have missed a problem like this… Billions were spent on R&D for this fighter.
lol, thats why we have checklists. this sounds like a red item to me instead of the yellow ones my captain likes to call \"happy-no problem-feel good checklist\"
this is what happens when you fly planes, especially the ones built by the lowest bidder
Thanks for the link Wade. It looks like they just fixed the issue with the f-22’s, however I don’t think they should have missed a problem like this… Billions were spent on R&D for this fighter.
lol, thats why we have checklists. this sounds like a red item to me instead of the yellow ones my captain likes to call “happy-no problem-feel good checklist”
this is what happens when you fly planes, especially the ones built by the lowest bidder