Erik

Sad is the day the Mirror has more credibility than the BBC.

Hope you have a

In other words anyone who doesn't agree with your solution is immature and irrational. Nice backhanded bullshit directed poorly.

People snap, it happens. Who knows what will or does send someone over that cliff of no return but it happens. Whether he used a gun, his car, or an explosive someone was going to pay and they did. Gun's aren't the problem, people are the problem. How about we get more civilized people control laws and solve the real problem or maybe just maybe teach people some real life coping skills so their knee jerk reaction isn't shock and effin aw.

With so much media coverage of the ill fated Malaysia Airlines Flight MH370 you can't help but speculate what the cause may have been. I've tried watching some of the CNN coverage and while I applaud their attempt at trying to recreate the cockpit environment it's the furthest distraction from the truth I can imagine. I know some of our pilots here have some thoughts and I'd like to hear them. As for me I'll be happy to share mine. Some unknowns that I feel need answers but we haven't heard about. 1. The lithium ion batteries. Which container, which hold, and quantity. How and where was it loaded they must know for weights and measures. 2. The track of the flight. Radar signatures are not singular they must know or someone knows. 3. The altitude of the flight at any point after loss of communication. 4. The fuel load. How many pounds of fuel were requested and how many loaded and where. 9M-MRO Boeing 777-2H6ER (MSN 28420/404) of Malaysia Airlines, at Perth Airport – 1 October 2006. Landing on runway 21 as flight MH125 from Kuala Lumpur. This aircraft was declared missing on 8 March 2014, whilst operating flight MH370 from Kuala Lumpur to Beijing with 239 people aboard (227 passengers and 12 crew). Photo © Keith Anderson Here's the flight plan that was filed: Route DCT PIBOS R208 IKUKO M076F290 R208 IGARI M765 BITOD N0480F330 L637 TSN N0490F350 W1 BMT W12 PCA G221 BUNTA N0480F350 A1 IKELA N0480F350 P901 IDOSI N0480F390 DCT CH DCT BEKOL K0890S1160 A461 YIN K0890S1190 A461 The part of the flight we know about was up and to the hand off and transfer to Ho Chi Minh City FIR at the IGARI waypoint. It's here the track of this aircraft suddenly becomes unknown. I personally don't believe this for a minute, but I digress. I've seen reports of this flight turning left at IGARI but this is where it gets vague at best. How does this flight skirt the sovereign territories and radars from that point on and what happened? I would speculate that flight MH370 suffered from the batteries igniting and being loaded in the forward cargo hold just aft of the Electronic and Aviation Bay. The batteries may have had a failure, ignited in a runaway reaction, or vented caustic gasses into the cargo hold. If this was a fire could it have burned through any important wire harnesses affecting the radio, transponder, and other gear in the E&A bay? I think this is highly possible though I admit I don't know the physical construction of the aircraft. Here's where things get really fuzzy but lets assume a fire. The pilot then turns left to land at the nearest ILS runway in Penang and descends to 12,000 ft to vent the cabin air which is ironically just above the transition altitude into Penang. Assuming again he set up for an approach transitioning through LUNTU like the ISMAS 1A Arrival which has an outbound departure of 207 degrees to TAMIT which would account for the lateral navigation and heading of it's final presumed flight path. So he descends to altitude and presses altitude hold but he leaves the original flight level of 29,000 and climb rate programmed into the auto pilot. He then reaches to the FMC and programs a new route to Penang with the arrival he wanted. This would account for lateral navigation. The questions I have at this point would be lets say the FMC flew the new route to Penang, at what point would it have a disconnect and stop routing? I'm asking this because I believe the FMC will disconnect when there is a discrepancy (altitude) and then does it hand it back to the auto pilot which has their original altitude, climb, and now a new heading of 207 degrees magnetic from LUNTU? This is the only way I can support the ghost aircraft theory where the crew and passengers were disabled at some point just after the left turn and after the pilot could make some plans for landing. Some things I can't reconcile are: 1. The distance it traveled. If the flight didn't return to the original cruise altitude how did it make it down to the 40th parallel southwest of Australia. 2. How there is no radar reports of this flight. If it flew outbound LUNTU how did it not cross over Singapore airspace. 3. If this flight flew around Singapore to avoid detection how did it make it so far south. 4. If this or other explanations can't be found that don't assume a hijacking or pilot suicide what's left. 5. How does a fire, explosion, or decompression disable radio communications, ACARS reporting, transponder malfunction, crew incapacitation AND at last resort descending to a point they could use other communication devices like cell phones. I pray for the families affected by this and I wish them the strength to heal and recover from their loss.

Happy birthday buddy. So glad I've been able to share the years with you. Just me E

In his case all gloves fit so they must convict.

Your member status didn't allow you to edit it. That has been fixed. Your original post has been edited. I would also recommend uploading anything you want to share to the download manager > upload file. Once you do that you get your own support topic for the mod and a few other nifty tools. Enjoy your stay, bring your friends.

I think you are the only one who can see it. The United States was in that list provided earlier (no redacted).

So basically planet Earth.

I'd like to give a huge endorsement and personal "job well done" to the editors. Our articles and interest pieces have been terrific and I couldn't be prouder. For those of you who do not know, Skyviper took on the role of editor in chief a couple months ago and is working with a top notch group of guys. Together they've put together and amassed some great stuff for everyone to dig into. Please let them know they're doing a great job, offer suggestions on things you'd like covered, and stay tuned for what's next. It goes without saying the staff deserves some appreciation too. These guys tirelessly stay after things and do a great job at it. One of our newest additions to staff is Migbuster and I couldn't be happier. For all of you behind the scenes who don't think I notice, I do. Thank you all. From all of us here at CombatACE, great job guys!

Adger - The only winner was you. I thought that had been cleared up. I asked how I could transfer purchases internally for WOFF expansions like you asked have not heard anything back. I will send off another request, maybe I have an old email address. I'll get this sorted with you even if we just reimburse you for the purchase directly. I had hoped for a better answer and maybe have some consolation prizes but at this point I just don't know. I'll advise as soon as I have something for you or we can figure out a different solution if waiting isn't amenable. Let me know. Erik

I'll have an announcement for everyone soon. I have an email out to sort the details of delivering the prizes. Simplicity isn't always doing the math. I'll keep you all posted.

Definitely fell through the cracks, will have to find that thread, figure this out, and advise. Thanks.

Well your outbound to us is solid, 10 hops and 128ms from Germany to the US is great. You are resolving us correctly at 216.104.36.210. So the only thing I can see is that it's us returning anything to you. Known fixes might be call your ISP, reset your router and system, check any firewall or internet security suite you might have, unplug from any router and go straight to the internet modem. You can give the trace routes to and from us above to your ISP if needed. I would have more complaints about this if it were more widespread so I have to hope this is isolated. We are in a highly robust data center with a datacenter in copenhagen which they carry back from. Please keep me advised as to what you find out. As a precaution I have submitted this information to our upstream provider to see what they can sort out. Thanks and I apologize for the trouble you're having.

Ok, from our server to you. root@server2 [~]# traceroute 84.141.190.144 traceroute to 84.141.190.144 (84.141.190.144), 30 hops max, 40 byte packets 1 server2.combatace.com (216.104.36.209) 0.696 ms 1.026 ms 1.341 ms 2 dr6506b.ord02.singlehop.net (99.198.126.145) 0.450 ms 0.521 ms 0.595 ms 3 xe-1-2-0.er2.ord2.us.above.net (64.124.200.141) 0.377 ms 0.411 ms 0.403 ms 4 xe-0-1-0.cr2.ord2.us.above.net (64.125.25.109) 0.605 ms 0.600 ms 0.590 ms 5 ae5.cr1.ord2.us.above.net (64.125.28.233) 21.758 ms 21.752 ms 21.742 ms 6 ae5.er1.ord7.us.above.net (64.125.20.38) 0.502 ms 0.531 ms 1.483 ms 7 80.150.171.65 (80.150.171.65) 1.249 ms 1.289 ms 1.263 ms 8 ki-ea1-i.KI.DE.NET.DTAG.DE (62.154.100.58) 121.987 ms 122.784 ms 122.551 ms 9 (217.0.71.9) 118.572 ms 119.010 ms 118.064 ms 10 * * * 11 * * * I get a timeout which means our machine isn't able to reach your IP at #10 so the machine after 217.0.71.9 is the culprit. As you can see from the line above that's already in Germany at DTAG.DE. Now it's possible the machine at #10 is yours and you're running some type of filtering software which means nothing other than I can't see what's happening past that point. To run a trace route here's what you do. > OPEN A CMD PROMPT (start > run > CMD + [ENTER]) or (start > all programs > accessories > cmd prompt) > At the command line enter: tracert combatace.com [ENTER] Let the trace complete and then highlight and copy all the lines it returned. (right click in header of command window > choose mark > highlight text > [ENTER]) Then paste what you copied here. Thanks.

Go to whatismyip.org and tell me what your external IP is showing as.

The simple answer is. I don't know. Unless I can get more specific information it's impossible to figure out. There's no reason our inbound traffic would be blocked, that's like shooting ourselves in the foot. There are so many connection configurations the answer is too large to even guess at. I need point to point details.

There should never be that problem and this is the first I've heard of it. Networking wise you should be minimized in this day in age. Can you provide a traceroute to us when you're having this problem and one when you're not? I can give it to our upstream and see what they can get resolved for you. Thanks.

Just be sure you read this thread. LINK Thank you.

It's that time of year when we are tasked with paying the bills and we'd like your support. Please take a moment and renew older subscriptions or sign up for a new one today and of course donations are always appreciated. Your continued support for all we do is important to us and we are grateful for your help seeing us into 2015. Here's to another great year ahead. Subscribe or Donate From all of us at CombatACE, thank you for your support.

Just paste that URL you provided in the signature area when you're editing your profile. I've never used the share links for something like this, share links are for sharing content off site.

You can go back 3 years. Settings updated. Thanks.

Great review.