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.

Deep ECAM & System Logic vs. Limited EFB Failure Triggers

Featured Replies

The Inibuilds A350 has quite alright system airbus depth and exceeded my inital expectation, however, after spending significant time digging into emergency procedures and non-normal scenarios, there is a clear disconnect between the underlying depth of the aircraft's ECAM logic and our ability to actually utilize it via the EFB Failure Manager:

1. Advanced ECAM Logic with Limited Failure Access

The issue that the a350 has is that the A350 features rich, highly accurate ECAM procedures and conditional logic for complex system failures. Yet, the current EFB failure menu only offers a very basic, high-level subset of failure toggles (e.g., basic engine failures, basic A-Ice valves, and simple TCAS/XPDR faults).

This is quite a missed potentional, because the EFB lacks toggles for core system nodes (like individual ADRs, IRs,), a huge portion of the complex ECAM logic and procedural depth you built cannot be intentionally simulated or trained for.

2. Example: Air Data & Unreliable Speed Indication

As a clear example, the ECAM contains full interactive checklists and switching logic for NAV UNRELIABLE AIRSPEED and NAV ADR 1+2+3 FAULT (complete with flight control law degradations, Backup Speed Scale options, and pitch/thrust memory item steps).

However,s a resul looking under ATA-34 Navigation in the EFB, there are zero options to induce pitot/static blockages or individual ADR faults. At, one of the most vital non-normal training scenarios in modern Airbus flying can't actually be triggered by the user.

  • I would hope Inibuilds will expand the EFB Failure Manager across the ATA chapters to allow triggering granular failures that feed directly into these built-in ECAM states such as in this example:

    • ATA-34: Pitot/Static probe blockages, individual ADR/IR faults, Air Data switching failures.

      But this isnt specific for the UNRELIABLE SPEED, more overall. Because the ecam pages exist but cant be used realisticly. The system have so much potentionalScreenshot (522).pngScreenshot (521).png

Create an account or sign in to comment

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.