XB-70A

It is, if I remember correctly the shot was taken in 1951, when a USMC Panther came back damaged by AA. The bad point about the story being... that two videos of Tomcat lost at sea (1981 and 1986) were available at the time the movie was realized, both being lost on the Constellation. The Alfa-class SSN (Project 705), with its Ramius' ex-disciple-mad-commander hunting the Red October is funny too, as this project was never intended to be used on patrol, but as fast SSBN interceptors, with only 32 men on board (all officers). But the presence of Connery (my favorite actor) made me like the movie, and McTiernan was good to make brain-dead but enjoyable action movies.

Hot fire for the Orion Jettison Motor:

LOL, D.D.O. just said "le pilotage est calme" (the control is calm). Looks like he was nominally nominal.

I know it's a dream, but could you imagine if tonight Arianespace was sharing a sight from a camera on board Vega? Finally.

T-48 minutes before the broadcast channels testing (goodbye headphones) https://www.youtube.com/watch?v=II9ULNvuD60

T-49 hours for Mohammed VI-B, the next (and final) Moroccan high-resolution optical reconnaissance satellite: Just like the first one, it is based on the "not-so-new" Pléiades models from Astrium. Five days ago: If everything is normal, the liftoff should occur at 01:42 UTC on Wednesday. It will be the 13th flight, and... the 10th happening at night.

How happy Lotarev Ivchenko would be with such a project!

Oh, this shot: I felt like being back in The Legend of Zelda Link's Awakening and Woodruff! EDIT: Okay... I did not resist... I took it... EDIT 2: Just in case, it seems like my computer is unable to display the game in full screen. The loading screen is available, however. Once restarted in a-kind-of-4:3 screen it worked perfectly. I just completed the introduction and the chats between characters is... pretty funny!

Thank you! I will try to make the next launch (CRS-16) even better if possible: a zoomed view of the 1st stage re-entry. Thanks! Not as good as some with their complex telemeter but hopefully better than the awful ones I was getting with my old Panasonic. The tracking is manual, but the camera is on a CH75 tripod. I wish it was, but that bird was a Cathartes aura (a.k.a the "Turkey vulture"). They are abounding in this coastal area, and I have rarely seen falcon in the park. However, ospreys are pretty easy to catch in the area of Port Canaveral: (Terrible lucky shot, it was in last December during CRS-13)

Hey everyone, For the first time since Dragon 13, in last December, I'm sharing a video of mine on the forum: It was the first occasion to me to film a launch with my new camera in the light of day, and I would be really interested to know what you think about it and how to improve it. I hope to reach 100 subscribers soon to be able to offer some live broadcast on the forum.

Bad screenshot: It doesn’t look really good for now, but let’s hope it will turn better.

Seems like it could be a funny ride: Anyway, we're still 30 hours away from the H-time, and as we know with meteorology: nothing is known in advance.

Personally, I loved the short (and rare) documentaries made some years ago in Samara, the home of the legendary Semiorka. It's pretty uncommon for them to share a lot about that site, however: There are some good sights in this one. Really good too, the best starting around 12:00. Others are also available... but not in English: That one is the best (to me), a lot to see there (and you can jump the interviews which, even if you could understand them, are not essentials). Good sights here too.

Yup! Virus from 1999 but in Space. With a slight pinch of The Thing.

I found Salyut 7 (2017) pretty nice. Somewhat a bit redundant on some points, but otherwise enjoyable. Otherwise, Tik Tik Tik (2018) was... laughable. I found it fun, really! Even if it was supposed to be a drama. On the other hand, I give the medal of the "disappointment known in advance" to Life (2017).

I don't know for you, but I got a beautiful and awesome day! At first, I ended my work earlier and decided to go to Playalinda to take some pictures of the F9 static fire. The weather was beautiful all along, or almost. Then, it happened (drum rolls)...

The hided population actually was far more advanced. Having been responsible for many wars they decided to become peaceful and to live in harmony. To ensure that they do not repeat their same mistakes, they prefer not to interfere with the primitive population of the neighboring planet... Then, against all odds they became the victims of a catastrophe of planetary magnitude, when a massive body came to impact with it. Not only did the impact destroy a part of the planet, and lifted so much ash and debris that it covered the entire surface, but it was so violent that it projected a part of it into another dimension, opening the way for vicious creatures. Defeated, and knowing that they could not fight any longer, the survivors decided to build an impregnable fortress, the Citadel, where, being cryogenized, they will wait until others come to liberate them. What happened when a vessel made an emergency landing on this somewhat known surface...

Reminds me the story of the Lt. Amjad Hussain... on 6 September 1965, he shot down an Indian Mystère IVA with an AIM-9B from his F-104. The next day, he and an ally were guided to catch up formation of Hunter and Mystère IVA coming back from a strike. He shot his second Mystère down, once again with an AIM-9B, but the second and last Sidewinder he fired was a "bidon", it never ignited. He decide to finish the last Mystère with his Vulcan and struck it but the aircraft was still airborne, and it's when he made his biggest mistake: entering in a turning fight against an aircraft far way more maneuverable. Progressively, the Mystère passed back to him and struck his Starfighter with some 30 mm rounds. He ejected a couple of seconds only before his aircraft blew off. Alas, his opponent, the Squadron Leader Devayya never came back home. Alas, the Pugachev's Maneuver is not really established as a useful one in operation (there is no record of it in action for now), it is more for demonstrations during air-shows. So much energy is loss during it that it could be a great maneuver... to be shot like a stationary pigeon. Without counting that it has to be executed in dry-mod (to make sure not to climb during the maneuver). A more standard and less aggressive "cobra" will be less energy hungry, but is still depending of a good equilibrium between the speed, the energy, and others conditions available at the time of the maneuver. In most of the cases, it's ending with an overload of the load factor, or in a stall. By the way, I'm not absolutely sure of it, but if I'm remembering well, when the InAF received its Su-30MKK in the 90's, they were equipped with a newer FBW control system preventing this maneuver to be realized (but which could be overridden).

Beautiful, simply beautiful!

Banned for having helped and saved Raiden. You should have let Solidus kill him.

Woooo, went to orbit on the first flight with a hideous flying stick: Most awful looking thing I built since KSP 0.90, but I just love the fact it contains procedural parts. Plus... There is a lot of thing to enhance (user interface at first), but I found it pretty fun and enjoyable for a beta release.

Airliners.net is from 1997 (and despite its booed 2016 update is still looking outdated (the forum design is awful))

Agree. However, Companies and manufacturers (in all departments) also tend to like when the whole reason can be imputed to ground and flight crew. From my point of view, the power of electronic systems and assistance is its almost "perfection". But, the number of flight crews complaining about having to reboot (literally) the electronics while flying is still alarming. Even worse is when a system is conceived improperly to human factors and is hard to detect: LOT 16... when a flight crew made a belly landing and were acclaimed as hero, until the inquiry clearly showed the lack of seriousness from the airline maintenance department, the failure of the same flight crew to detect a circuit breaker failure, and the lack of a redundant system. At the end, the flight crew could have used the alternate landing-gear extension system to lower the undercarriage () Even worse, PK-LQP was having problems during the last four flights: On Nov 5th 2018, following the KNKT release confirming airspeed indicator problems during the last 4 flights of the aircraft [...] On Nov 8th 2018 the KNKT reported an angle of attack sensor had been replaced on Oct 28th 2018 following the flight JT-775 from Manado to Denpasar (the aircraft completed the subsequent flight JT-43 to Jakarta and suffered the crash the next flight JT-610). The aircraft subsequently flew to Jakarta, the crew however reported there were still problems. --- For those of you (if any) who would be interested to read the recommendation published two days ago: On Nov 7th 2018 Boeing issued an Operations Manual Bulletin (OMB) to all Boeing 737 MAX Operators stating that the investigation into the crash of PK-LQP found one of the Angle of Attack Sensors had provided incorrect readings, which could cause the aircraft's trim system to uncommandedly trim nose down in order to avoid a stall during manual flight. The OMB directs "operators to existing flight crew procedures to address circumstances where there is erroneous input from an AOA sensor." The OMB reiterates the Stabilizer Runaway non-normal checklist. The flight Crew Operations Manual Bulletin TBC-19 reads: The Indonesian National Transportation Safety Committee has indicated that Lion Air flight 610 experienced erroneous AOA data. Boeing would like to call attention to an AOA failure condition that can occur during manual flight only. This bulletin directs flight crews to existing procedures to address this condition. In the event of erroneous AOA data, the pitch trim system can trim the stabilizer nose down in increments lasting up to 10 seconds. The nose down stabilizer trim movement can be stopped and reversed with the use of the electric stabilizer trim switches but may restart 5 seconds after the electric stabilizer trim switches are released. Repetitive cycles of uncommanded nose down stabilizer continue to occur unless the stabilizer trim system is deactivated through use of both STAB TRIM CUTOUT switches in accordance with the existing procedures in the Runaway Stabilizer NNC. It is possible for the stabilizer to reach the nose down limit unless the system inputs are counteracted completely by pilot trim inputs and both STAB TRIM CUTOUT switches are moved to CUTOUT. Additionally, pilots are reminded that an erroneous AOA can cause some or all of the following indications and effects: - Continuous or intermittent stick shaker on the affected side only. - Minimum speed bar (red and black) on the affected side only. - Increasing nose down control forces. - Inability to engage autopilot. - Automatic disengagement of autopilot. - IAS DISAGREE alert. - ALT DISAGREE alert. - AOA DISAGREE alert (if the AOA indicator option is installed) - FEEL DIFF PRESS light. In the event an uncommanded nose down stabilizer trim is experienced on the 737 - 8 / - 9, in conjunction with one or more of the above indications or effects, do the Runaway Stabilizer NNC ensuring that the STAB TRIM CUTOUT switches are set to CUTOUT and stay in the CUTOUT position for the remainder of the flight. Late Nov 7th 2018 the FAA released Emergency Airworthiness Directive (EAD) 2018-23-51 concerning all Boeing 737 Max aircraft reading: This emergency AD was prompted by analysis performed by the manufacturer showing that if an erroneously high single angle of attack (AOA) sensor input is received by the flight control system, there is a potential for repeated nose-down trim commands of the horizontal stabilizer. This condition, if not addressed, could cause the flight crew to have difficulty controlling the airplane, and lead to excessive nose-down attitude, significant altitude loss, and possible impact with terrain. The EAD requires operators to update the procedures in the Aircraft Flight Manuals within 3 days according to Boeing's Service Bulletin (see the text above), however, includes the possiblity the trim could move even after the cutout switches were set to cutout. The text of the proedure for a Runaway Stabilizer mandated reads: Disengage autopilot and control airplane pitch attitude with control column and main electric trim as required. If relaxing the column causes the trim to move, set stabilizer trim switches to CUTOUT. If runaway continues, hold the stabilizer trim wheel against rotation and trim the airplane manually. Note: The 737 - 8 /- 9 uses a Flight Control Computer command of pitch trim to improve longitudinal handling characteristics. In the event of erroneous Angle of Attack (AOA) input, the pitch trim system can trim the stabilizer nose down in increments lasting up to 10 seconds. In the event an uncommanded nose down stabilizer trim is experienced on the 737 - 8 / - 9, in conjunction with one or more of the indications or effects listed below, do the existing AFM Runaway Stabilizer procedure above, ensuring that the STAB TRIM CUTOUT switches are set to CUTOUT and stay in the CUTOUT position for the remainder of the flight. An erroneous AOA input can cause some or all of the following indications and effects: - Continuous or intermittent stick shaker on the affected side only. - Minimum speed bar (red and black) on the affected side only. - Increasing nose down control forces. - IAS DISAGREE alert. - ALT DISAGREE alert. - AOA DISAGREE alert (if the option is installed). - FEEL DIFF PRESS light. - Autopilot may disengage. - Inability to engage autopilot. Initially, higher control forces may be needed to overcome any stabilizer nose down trim already applied. Electric stabilizer trim can be used to neutralize control column pitch forces before moving the STAB TRIM CUTOUT switches to CUTOUT. Manual stabilizer trim can be used before and after the STAB TRIM CUTOUT switches are moved to CUTOUT. This is just a bad copy-pass. More can be followed on The Aviation Herald.

It reminds me this marvel from Rhode Island: