Category Archives: Avionics

How do you retrieve the BIT Fault codes from a LaserRef1?

How do you retrieve the BIT Fault codes from a LaserRef1?

“BIT” button leads to 3 pages :
Bit 2- Current Status
Bit 3 – Last Flight
Bit 4 – All History

Now: lets look at the 270 word

One example is 0082 2800

Note the first two digits are 00 and the last two are 00.  they are unused digits in this scheme.

This Work sheet might help with the decode.

And the 270 Word definition, or the 350 word definition might help.

My notes from N850BA EGPWS squawk.

What are the EASA requirements for DFDR and CVR installations?

Here is my analysis of the specific requirements for DFDR Channel count requirements for

F900B S/N 051, Type certA46EU, originally issued March 7, 1979:

ICAO Annex 5 Part I, chapter 6

After reviewing every exciting paragraph carefully, we are NOT required to have a Type I, Type IA, Type II, OR a TYPE IIA recorder. These types of recorders have concisely defined lists of required parameters.

The paragraph that we are forced to comply is 6.3.1.2.9, and 6.3.1.2.10, including a), and b).

These requirements are VERY VAGUE and obviously meant to be looser requirements than the Type 1and type 2 recorder installations.

ICAO_DFDR_CVR

 

How do we comply?

 

DFDR P/N 980-4700-25 in BMB and BZZ:

 

We can now use the HHDLU owned by Duncan BTL.  Contact Scott Davis at FTW to rent it.

 

Send the results of the download to

 

http://www.aeroinst.com/

 

Also send this list:

 

FalconAMM_Ch31_Appendix A

 

then fight through the results to see if anything is REALLY missing?  File the results.

 

++++++++++++++++++++++++++++++++++++++++++++++++++++

some old notes

 

OTAR 91.140 (a) (1) (ii) 

 

_________________

 


Now then…. here is the history that was set in motion by the insistence of Dan Staina.

The items that we have been complying with up to this point are:
ICAO Annex 6 , Appendix 8, Section 7.
7.1 is complied by the Pilot’s Taxi Checklist.
         we got that sorted out 2 years ago with a Notice To Staff.
7.2 a), and b)  is complied by pulling the DFDR and sending it to Honeywell…..GIGANTIC pain in the behind.  Honeywell provides a letter that states the DFDR is correctly recording the parameters that the Falcon work card calls for. (32 parameter list)
c) is complied by having the pilots pull the C/B on the Taxi In prior to the removal.. That way we capture a full flight for Honeywell Analysis.
d) Honeywell.
e) The Falcon work cards fully test the CVR operation in the airplane.
f) “where practical” The CVR’s are removed  and read out every year. The CVR from BZZ goes to Duncan for readout. Honeywell for the other CVR’s.  We retain a voice CD of the recordings.  I was been verifying the “Intelligibility” myself by listening to the .WAV file.
I say that is SUPREMELY  UNPRACTICAL. I would like to suggest that you quit doing this and change the CAMP code to AS REQUIRED
g) N/A , none of the aircraft are fit with AIR (Video Recording)
7.4 we comply with this by filing the Honeywell and Duncan results right in the work order binder.
7.5 a) this is due on BMB.  It is not due on BZZ because it has been installed less than 5 years.  Best I can tell, this is ONLY the calibration of the 3 resistors that report the control column position.
This is the best summary of where we stood 6 months or so ago.
Portion of the ICAO ANNEX attached.

 

 

 

 

 

 

 

 

What are the Standard Data Interfaces for a DFDR?

ARINC Report 657 Airborne Recorder File Format

This document defines the characteristics necessary to standardize the airborne recorder download file format in order to facilitate data import, transcription, and exchange. A standardized data format will reduce the variety of readout equipment required for airborne recorder data transcription. This document defines the detailed architecture of the Recorder Standard Output (RSO) file. The architecture is a tagged file structure within which many different files and their formats can be supported. The structure is necessary to support newer recording requirements for flight data, data link, audio, and image recording. This structure is intended for use with all civil recorders and should support use with military recorders.

Last Print: 02/2009
Price (PAPER): $196.00
Price (PDF): $98.00

Godd reegulatory discussion

FrenchBEAonFDRs

This AIRINC overview includes a detail of Airinc 573, for flight data recorders

ARINCTutorial

What are the Common Extractor Part Numbers, terminal block part numbers, crimper part numbers?

Here is a quick guide that actually makes sense…… remember to use Connector Micro Tooling Systems in Arlington,,,,,, super nice

 

PlasticToolRferenceSheet

and here is the same sheet, reduced to the most common falcon extractor

 

PlasticToolRferenceSheetReduced

 

Red and White Metal

Red and White Plastic

 

__________________________

Here is the last order:

Syringe style:

2 each 455822-2,  ALTPN 206388-1 – $14.95, ALTPN R-5926(Jonard), . Cheap Amp white

2 each 305183  – $12.25,  M style , Type 1, 2 or 6 Extractor for Tyco/amp CPC round connecor, 18-20. metal tube,plastic body
1 each Red Daniels canon Syringe, Daniels MS24256R200 each Red Daniels canon Syringe
 
Plastic wrap around style:

15 each Red/Wht  plastic pn M81969/14-02 

15 each Red/Wht Metal M81969/1-02 

0 each Grn/Red plastic

0 each Blu/Wht plastic

0 each Blu/Wht metal

10 each Grn/Wht plastic M81969/14-01

15 each Grn/Wht Metal M81969/1-01

5 each Red/Orn plastic M81969/14-10

5 each Yel/Wht plastic  P/N M15570-22-1 

 

Tweezer style:

2 each Red  astro M81969/8-06

0 each Green

Forked Devil style:

0 each Collins P/N 359-0697-020, made by daniels
___________________________________________

 

 

red terminal blocks in Falcon 50

 

Contacts small  pn 1841-1-5622 or alternate 100060-56 deusch

 

Strippers for tefzel wire

Home

Dakota electronics San antonio.

 

Small and large green