Juliet Hotel
En-Route
- Joined
- Jul 21, 2018
- Messages
- 2,631
- Display Name
- Juliet Hotel
Possible? Sure. Likely? That's a tall order. Most likely? Pull the other one it plays jingle bells.Yes there is. The PF just drove it into the ground, most likely.
Possible? Sure. Likely? That's a tall order. Most likely? Pull the other one it plays jingle bells.Yes there is. The PF just drove it into the ground, most likely.
Thanks for the write up and detailed analysisIn short I'm skeptical weather caused a direct effect, but I do see enormous potential for a sudden, rough ride here, and that could have been the first event in a chain that led to something like a CG shift or loss of a control surface (from fatigue, improper maintenance, design issue, something like the 737 in Colorado Springs, etc).
Regarding the insinuation of suicide. Crazy conclusion to immediately jump to, especially considering
-weather in the area
-why wait until you are on approach
-no sign of a struggle or anything leading up to it
If you compare this to an ACTUAL attempted suicide mission like https://en.wikipedia.org/wiki/Federal_Express_Flight_705 or other ones there is usually quite a struggle on board and the radar track from this 767 would likely have revealed that.. not https://www.flightglobal.com/news/a...rew-appeared-to-be-trying-to-avoid-we-456051/ a crew working together trying to avoid weather
What sucks is that without CVR or black box data we're going to know very little. I shudder to think that the small (relatively) sized black box is sitting somewhere 5 feet deep in thick mud
PS - with our phones constantly connected to the internet, I can't figure out why black boxes and CVRs aren't in constant communication with a cloud based database system. Surely there are orders of magnitude more phones than their are commercial planes in the sky?
^ been wondering the same about cloud sync for years. guessing there are folks in the industry who can answer "why not".
Sent from my SM-G960U1 using Tapatalk
This part doesn't compute. The engines already send packets of data periodically back to RR, PW, etc. Every person sitting in their seats can watch Real-Housewives-of-Who-Gives-A-F#ck. You can surf the web in the middle of the Pacific on a 40 foot sail boat.. but an airliner can't send small packets periodically? $1,000 will buy you a phone that will push you Facebook notifications, Tweets, and Instaselfies, and other nonsense 24/7. A sat phone is a few hundred bucksBecause it costs money. Getting another box and antenna certified on a transport category aircraft isn't an inexpensive undertaking and nobody wants to pay the up-front costs or the ongoing costs of the monitoring service.
This part doesn't compute. The engines already send packets of data periodically back to RR, PW, etc. Every person sitting in their seats can watch Real-Housewives-of-Who-Gives-A-F#ck. You can surf the web in the middle of the Pacific on a 40 foot sail boat.. but an airliner can't send small packets periodically? $1,000 will buy you a phone that will push you Facebook notifications, Tweets, and Instaselfies, and other nonsense 24/7. A sat phone is a few hundred bucks
There must be other reasons this hasn't taken place.
The point is to negate the need for a black box. Just stream the data backThat would not help find the black box though

Honestly, all of this is easily solvable with adopting basic compression, buffering, token exchange, etc. Yes I get that everything in commercial aviation is some multiple more expensive than a consumer delivery. But there's not much technologically ground breaking here.Between them, the two black boxes on transport aircraft record almost 100 different inputs on a continuous basis. That's a lot of data to record and transmit. The only way to guarantee you'll get the important parts of the information is to have that data uploaded continuously. A gap of 30 seconds between packets might have resulted in the 767 in this thread going from "All is fine" to the crash in such a short time that no relevant data was sent. So, if you really want to transmit and record the same level of data you'd get from a flight recorder, that turns into a lot of data.
And, like I alluded to, getting any new piece of hardware approved and installed on an airliner is a big deal. Haven't I seen reports that ADS-B installs are $100k/airframe on the big iron? Even at half that amount, Delta, SW and all of the other carriers are going to balk because of initial and and ongoing expenses.
Honestly, all of this is easily solvable with adopting basic compression, buffering, token exchange, etc. Yes I get that everything in commercial aviation is some multiple more expensive than a consumer delivery. But there's not much technologically ground breaking here.
The ADSB upgrade is causing enough headaches, and is insanely expensive already, for commercial aircraft.Because it costs money. Getting another box and antenna certified on a transport category aircraft isn't an inexpensive undertaking and nobody wants to pay the up-front costs or the ongoing costs of the monitoring service.
You beat me to it.Nothing like advocating for the exorbitant costs of live streaming black box data for every airline or similar aircraft so that we can take up crap loads of “cloud” storage for 99.9% of uneventful flights. It would only come into use if you can’t locate the black box, which is fairly rare in terms of already-rare airline crashes. Smart financial move . . .
The point is to negate the need for a black box. Just stream the data back
How much does an airplane cost? How much do lawsuits from families cost? How much do increased regulations cost the industry? It can be done. The technology exists, and is literally already in use (engine data getting sent back, IFE, etc.) but as a society we're relatively short sighted
View attachment 72023
It does take place, but only when the end user wants to pay the uplink/data costs. The reason they knew how long MH370 flew was the engine OEM paid the engine uplink costs. In the AF447 accident, they knew 60% of the failure mode as it happened because AF paid to have select mx data uploaded to improve mx turnaround rates. So its all about the money.There must be other reasons this hasn't taken place.
We wouldn't have to limit this strictly for the event of when a black box or CVR can't be found.. if we think outside the box here then having all this data at the fingertips of the beancounters and data analysts at the airliners, manufacturers, etc., could help in many ways. Information is generally a good thing
If we always assumed we were already living in the best of worlds and other advancements are cost prohibitive or unnecessary than progress would never be ma
We wouldn't have to limit this strictly for the event of when a black box or CVR can't be found.. if we think outside the box here then having all this data at the fingertips of the beancounters and data analysts at the airliners, manufacturers, etc., could help in many ways. Information is generally a good thing
If we always assumed we were already living in the best of worlds and other advancements are cost prohibitive or unnecessary than progress would never be ma
Cargo coming loose normally causes issues on takeoff, so that is improbable. Typically it's either secured properly or it isn't.
I have no personal knowledge of this, but considering that Amazon cargo is relatively light and palletized, I would guess the cargo deck space was full from front to back. Volume, not weight in other words. It seems unlikely the cargo could shift.
...there was a case of that happening at least once before, National Airlines Flight 102, the 747 that crashed on departure, had an improperly secured vehicle roll back, hit and damage the bulkhead, which damaged hydraulics and made the airplane uncontrollable: https://en.wikipedia.org/wiki/National_Airlines_Flight_102
The MRAPs loaded on that aircraft weighed over 30,000 lbs each, so when the rearmost vehicle broke loose, the CG shifted in an immediate and fatal manner.
That's very unlikely to happen on an aircraft loaded with lightweight and locked down pallets, and as I said above, there probably wasn't any space in the fuselage for much movement.
That would not help find the black box though. Bury your phone underwater, under 5-10 ft of mud and see how well you can find it then... :/
That would not help find the black box though. Bury your phone underwater, under 5-10 ft of mud and see how well you can find it then... :/
Isn't some of the infrastructure in place with the WiFi so many planes have for passengers? That goes up to satellites and then to...wherever.It does take place, but only when the end user wants to pay the uplink/data costs. The reason they knew how long MH370 flew was the engine OEM paid the engine uplink costs. In the AF447 accident, they knew 60% of the failure mode as it happened because AF paid to have select mx data uploaded to improve mx turnaround rates. So its all about the money.
As to justifying the costs of uploading GBs of data vs aircraft cost or lawsuits that is what risk-management and insurance costs are for. Two separate topics. But there is only so much airborne bandwidth in the world. Even small upload systems like those used with helicopters in the GOM are rather expensive. And the first thing they do to mitigate cost is get the satelitte data down into ground based as soon as possible. The 1st Outerlink systems would download data from GOM aircraft to Maryland then use phonelines to send it to the com center on the beach.
As a piece of anecdotal evidence, one day we rolled into the gate and a mechanic asked us about a specific problem with the airplane. We had no idea what he was talking about so some sort of connection with our maintenance people was made automatically. I am sure a lot of information can be had automatically if a company has enough interest in making it happen.Isn't some of the infrastructure in place with the WiFi so many planes have for passengers? That goes up to satellites and then to...wherever.
While this is outside my skill set, the conversations I've been involved with from the provider/user side is that it's not an "infrastructure" problem. The architecture for this data movement has been available for years, especially as the digital/technical side reinvents itself every 6 months. The issue is market.Isn't some of the infrastructure in place with the WiFi so many planes have for passengers? That goes up to satellites and then to...wherever.
That was my thought.. why not plug *some* kind of system into existing infrastructure. On any given flight you have 200 clowns watching TV, surfing Facebook, doing email, etc. The G1000 stores loads of data on the tiny memory disk.. I doubt we'd need GB of data.. just send a small .txt or .csv every 5 seconds with a handful of core data pointsIsn't some of the infrastructure in place with the WiFi so many planes have for passengers? That goes up to satellites and then to...wherever.
All that was missing in MH370's could be lat/long data. At least they they'd know where it wasEvery modern airliner, basically a 777/330 forward (and some helicopters) has the ability to upload airframe and engine data in real time. As I mentioned above, in the AF447 crash off Brazil, they knew most of the failure sequence from real-time data uploads. However, this data was intended to give the mechanics back in Paris a heads up so they could prepare for the repair prior to the aircraft's arrival.
Exactly. But you'll have to ask Malaysia Airlines why they didn't want to spend the nickel on that. From what I've read, ICAO is looking into requiring operations over "remote" areas to have basic real-time info uplinked on a per-programed cadence.All that was missing in MH370's could be lat/long data.
As you mentioned, the cost is getting lower. Delta Airlines would charge me ~$500 for all the internet I want in a year, and I'm sure they are making a profit on that. I can be on one plane at a time, so let that be the price for one aircraft a year. I agree with you the operators won't pay this unless they had to. How to justify the expense? Same way the expense of the "black boxes" are justified. Either lower insurance rates, or mandated by law.While this is outside my skill set, the conversations I've been involved with from the provider/user side is that it's not an "infrastructure" problem. The architecture for this data movement has been available for years, especially as the digital/technical side reinvents itself every 6 months. The issue is market.
For example, 5 years ago you couldn't buy a 65" 4K flat screen for less than $10K. Now they're $675 at Walmart. In our connected world, WiFi on aircraft is no longer a luxury and the cost (market) is shared across provider, middleman, and user. With real-time aircraft operational data streaming via satellite where's the market?
Every modern airliner, basically a 777/330 forward (and some helicopters) has the ability to upload airframe and engine data in real time. As I mentioned above, in the AF447 crash off Brazil, they knew most of the failure sequence from real-time data uploads. However, this data was intended to give the mechanics back in Paris a heads up so they could prepare for the repair prior to the aircraft's arrival.
Bottomline, it's all about the operator paying for the bandwidth and how they can expense it out. But how to you justify the expense when you may only use that data once every 10 years, or in QUANTAS's case, never. It's a bigger discussion than just uploading a few 1s and 0s as I saw during the ADS-B trails and tests in the GOM.
Some years ago I jumpseated on a UPS 767 and they had a lav.Does the B767 cargo have lavatories in them.??
Does the B767 cargo have lavatories in them.??