Skip to content
View in the app

A better way to browse. Learn more.

iniBuilds Forum

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

schizzel

Member

Everything posted by schizzel

  1. Recently I observed the gradual improvements of additional ECAMs especially for flaps and l/g, therefore showing potential into system depth with an already deep ECAM simulation. However, I think other failures might need attention here as behavior is different in real world documentation. For example: Bird strike situation should also affect outside TAT probes and windshield These probes such as AoA, airspeed, ice detection and static are located below the windshield and should have a random chance of failing due to bird strike to the cockpit since they could be located near the impact point. Interestingly, according to the virgin atlantic FCOM below, bird strike can affect the data that feeds to the ADRs and the current way of failing it other than turning those off is not available in the EFB, nor the bird strike situation. Another thing is window strike damage which will need the ABN COCKPIT WINDOW CRACKED checklist. Another situation n/a in the bird strike simulation. Some engine systems such as engine relight simulation, EGT and vibration need work Bird ingestion doesnt necessarilly cause the engine to fail, but, when they do, its ingestion to the compressor might cause turbulent airflow leading to a compressor stall. This should show the telltale signs such as high fluctuating egt, n1, fuel flow and abnormal vibration while the engine bangs occur. However, this does not reflect to your external engine failure animation due to bird strike. It could be recoverable provided that the compressor returns to its normal airflow config that escapes the imbalance vs combustor. I also noticed that your engine failure in the efb induces it in such a way that it still windmills and has no abnormal vibration, which can consider a relight in flight. However, recovery cannot be done for some reason? Because, in that case, I would love an option for a recoverable (and unrecoverable) engine failure option in the efb, while showing the nuances in it. In some FCOM documentation, unrecoverable ones could show a reason: The oil low pressure should gradually trigger high vibration and abnormal egt first before engine seizure, which should give off a more authentic engine simulation, as well as FADEC shaft failure trigger, any of these in order. You also forgot about the situation for lithium batteries too. This is also from real world operations: I look forward to the update of the a350v2, but please do a C check of your failure and system depth.

Account

Navigation

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.