01.12.2014 Views

November 2012 - Indian Airforce

November 2012 - Indian Airforce

November 2012 - Indian Airforce

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

AEROSP CE<br />

Safety<br />

FOCUS: AIR TRAFFIC CONTROL<br />

<strong>November</strong> <strong>2012</strong><br />

inside<br />

History Repeats Itself<br />

I am a Good Supervisor<br />

T-20 in a Controller’s Life<br />

Oops! They Forgot the Toggle Pin<br />

An Air Incident<br />

Aur Kitna Time Lagega?<br />

ATS Crossword<br />

Where Eagles Dare


Vol 202<br />

Director General (Inspection & Safety)<br />

Air Mshl AP Garud VM<br />

Principal Director Aerospace Safety<br />

Air Cmde R Marwaha VSM<br />

Chief Editor<br />

Gp Capt S Shrinivas<br />

Editors<br />

Wg Cdr MK Srivastava<br />

Wg Cdr GS Bishen<br />

Wg Cdr Nishant Dhar<br />

Sqn Ldr Shashank Sharma<br />

Editorial Assistants<br />

Mr Niraj Kumar<br />

Mrs S Sangeetha<br />

Mr Rakesh Kumar Singh<br />

Graphic Design<br />

JWO G Ramesh<br />

Sgt DK Chatterjee<br />

Cpl RS Thokchom<br />

Mr Rajib Paul<br />

<strong>November</strong> <strong>2012</strong><br />

AEROSP CE<br />

Safety<br />

'Aerospace Safety' magazine can be<br />

viewed through http://www.airhq.iaf.in/<br />

(links : DG (I&S) % DAS % FS Magazine)<br />

and on the internet at<br />

http://www.indianairforce.nic.in<br />

Articles/Suggestions may be sent to:<br />

Editor, Aerospace Safety<br />

Institute of Flight Safety<br />

Air Force Palam, New Delhi-110 010<br />

Tele : 011-25672871, 23247789(AFNET)<br />

Fax: 011-25675059<br />

e-mail: editorfsmiaf@yahoo.com<br />

Round-the-clock contact of Principal<br />

Director Aerospace Safety:<br />

Tele:<br />

011-26172738 (Off)<br />

21125130, 21125131 (AFNET)<br />

91-9717095606 (Mob)<br />

e-mail: pdfs_iaf_in@indiatimes.com<br />

Every article must be accompanied by a<br />

brief bio-data and passport size<br />

photograph of the author.<br />

The opinions expressed in the ‘Aerospace<br />

Safety’ magazine are the personal views of<br />

the authors and do not reflect the official<br />

policies of Air HQ. Contributions are<br />

welcome, as are comments and criticism.<br />

The Editorial Board reserves the right to<br />

make any improvements/changes in the<br />

manuscripts.<br />

2<br />

inside<br />

History Repeats Itself<br />

Wg Cdr PC Kalia<br />

4 Avian Activity Risk Assessment and Prioritisation<br />

Wg Cdr Anuj Pathak<br />

8 T-20 in a Controller ’s Life<br />

Wg Cdr Rajesh Sharma<br />

12 An Air Incident that ‘Kick-Star ted’ Us<br />

Gp Capt KVS Nair<br />

14 Oops! They Forgot the Toggle Pin<br />

Wg Cdr R Vijay<br />

18 ATS Crossword Puzzle<br />

WO PM Jangid<br />

20 Aur Kitna Time Lagega?<br />

Wg Cdr B Anandhan<br />

22 Billion Hearts Beating and Flight Safety<br />

Gp Capt Narinder Taneja<br />

24 I am a Good Supervisor<br />

Sqn Ldr Vijaya Kumar<br />

26 Do You Know?<br />

WO PK Swain<br />

28 Where Eagles Dare<br />

Wg Cdr N Dhar<br />

32 Good Show<br />

14 20<br />

36 From The Desk of Ornithologist<br />

24<br />

The Aerospace Safety Magazine is a monthly publication to promote safety<br />

consciousness and prevent aircraft accidents. <strong>Indian</strong> Air Force units may reprint articles<br />

from the magazine without further authorisation. However, no part of this magazine can be<br />

used or reproduced in any form by any means or translated in any other language without<br />

the explicit permission in writing by the Chief Editor.


Editorial<br />

he onset of winter is a welcome time, as one gladly trades the swelter for the sweater! However,<br />

winter also brings with it its associated weather phenomena that are so very important for<br />

Taircrew to watch out for, be it poor visibility or Western Disturbances. But there is another<br />

group of professionals who need to maintain an equally vigilant eye for safety in the skies. And so we<br />

focus on the vital bonding between aviators and air traffic controllers, highlighting several cases<br />

where prompt action saved the day.<br />

'History Repeats Itself ' is an account of mistaken identity of airfields in close proximity. Such<br />

errors of judgement have been made by both, service as well as civil aircraft, despite a plethora of<br />

sophisticated navigation equipment on board. This is not the first such example and may not be the<br />

last. Aircrew and controllers both need to be extra cautious when operating in such conditions. 'T-20<br />

in a Controller's Life' is another collection of anecdotes which prove that the alertness and quick<br />

response required of an air traffic controller are as demanding and dynamic as a player in a T-20<br />

thriller! 'An Air Incident that Kick-Started Us' is a wonderful account that stresses the intense coordination<br />

required between different agencies involved in the launch and recovery of aircraft,<br />

particularly when today's profiles and area of operations span large durations and distances from<br />

base.<br />

'Avian Activity Risk Assessment and Prioritisation' emphasises the need to be specific to the<br />

peculiarities of each base when planning for effective bird control and avoidance. 'Where Eagles<br />

Dare' is a bird's perspective of its struggle for existence in its natural domain due to the intrusion of<br />

humans; a reminder that it is us who have to learn to co-exist!<br />

'Aur Kitna Time Lagega?' is a situation perhaps encountered many a time when impatience<br />

and interference actually end up delaying task accomplishment. 'Oops They Forgot the Toggle Pin' is<br />

a reminder for being forthright to ensure correct and timely analysis of any unusual occurrence, while<br />

'I am a Good Supervisor' succinctly spells out what a supervisor should do to ensure safe and efficient<br />

operations.<br />

The importance of tool discipline and a comprehensive quiz on ‘matters aviation’ are good<br />

fillers for all of us to test our knowledge at leisure.<br />

Happy Landings.<br />

(S Shrinivas)<br />

Group Captain


Wg Cdr PC Kalia<br />

HISTORY<br />

REPEATS ITSELF<br />

The old adage, ‘Accidents happen when you<br />

expect them the least’ has a special bonding<br />

with IAF, perhaps because of the kind of business<br />

we are in. At times it seems as if Mr Murphy is always<br />

on the lookout for you to commit a mistake so that he<br />

can play his part.<br />

These incidents although more than a decade<br />

old, never fade from my memory. Instead the lessons<br />

learnt from these incidents have helped me in averting<br />

a major mishap in the recent past.<br />

On a beautiful Sunday morning, when the visibility<br />

was in excess of 10 Km (CAVOK in aviation lexicon),<br />

a young Pilot Officer was relaxing in the ATC tower<br />

because no one apart from birds was flying in the<br />

area. He was jolted out of the comfort of a full back<br />

Godrej chair by a call from an Air India Flt from Delhi<br />

to Chandigarh. He rattled out the weather report and<br />

asked the ac to “report for descent”. Over ONOGI (121<br />

deg 21.5 NM from VICG) the pilot requested “a left<br />

hand orbit to lose altitude” and “permission to report<br />

direct finals for runway 29”. The same was granted by<br />

the controller in a near mechanical response. While<br />

in orbit, the pilot reported “runway in-sight”; he was<br />

“cleared descent to circuit altitude” and asked to<br />

“report finals for runway 29”. After a while, the pilot<br />

reported “finals for runway 29” and sought “permission<br />

to land”. As per the drill, the controller looked at the<br />

Airman On Look-Out (AOLO) (fondly called ‘The Third<br />

Eye’ of the controller) who indicated ‘ac not in sight’ by<br />

vigorously waving his hand. The controller couldn’t<br />

believe this and asked him to use the binoculars to<br />

spot the ac (Boeing class in CAVOK conditions). In a<br />

state of disbelief himself, the controller once again<br />

asked the ac to “report position”, to which the pilot<br />

angrily replied, “finals, request permission to land.”<br />

You could call it ‘sixth sense awakening’ or the<br />

result of meticulous training at ATCOTE, where past<br />

experiences shared by the DS had left a lasting<br />

impression in the minds of the budding ATCOs,<br />

much more than the writings in text books. The<br />

controller looked at the DRDF (now replaced by<br />

CADF) and to his utter shock saw that the homing<br />

indicated was Northerly instead of 290 or so. He<br />

literally jumped out of the chair and shouted in a<br />

single breath, words rarely heard in ATC, “(call Sign),<br />

Homing indicated is ______, wherever you are,<br />

climb to 6200 feet (initial approach altitude) and<br />

report steady.” Getting no response from the pilot,<br />

he repeated (rather shouted) the call, possibly in<br />

the same breath. Now, he heard the pilot meekly<br />

saying “Roger”. Complete silence in the tower<br />

was disturbed only by the heavy breathing of<br />

the DATCO. After a while, the AOLO indicated the<br />

“aircraft in sight” and pointed towards the South<br />

of runway. Rest everything was what they call<br />

‘history’.<br />

On another occasion at the same base, the<br />

same youngster was on duty (operating from the<br />

alternate semi-underground ATC) and giving him<br />

company was the COO of the base. A transport ac<br />

(AN-32) was carrying out an air test overhead at an<br />

altitude of 27000 feet. As this was the only ac flying<br />

at the time, on “request for rejoin”, he was “cleared<br />

descend to Initial Approach Altitude (6200 feet)<br />

and report runway in sight”. On receiving the call<br />

of “visual with runway”, he was cleared to report<br />

downwind, followed by “call finals for runway 29”.<br />

2<br />

Aerospace Safety N o v e m b e r 2 0 1 2<br />

INDIAN AIR FORCE


Expecting the ac to report finals at any time, the<br />

controller was busy looking for the ac through the<br />

limited space available to look out from the semiunderground<br />

ATC, when he was jolted by a call<br />

from the pilot, “Going around, why did you fire a red<br />

cartridge.” The controller spontaneously replied<br />

in the negative and said, “Will check with Runway<br />

Controller.” On hearing this RT conversation, the<br />

COO said, “He might have got confused by some<br />

cracker on approach (civil population and Diwali<br />

days), ask him to report downwind again.” Still<br />

confused the controller hesitantly asked the pilot<br />

to report downwind again and re-iterated,<br />

“no one from ATC fired<br />

any cartridge; runway i s<br />

clear and available for landing.”<br />

Everyone was speechless<br />

and looking at each other in<br />

shock and awe. The silence<br />

was broken by the ringing<br />

of the direct line from our<br />

Southern diversion. The Cpl<br />

on other side of the line was<br />

shouting, “What is this AN-32<br />

doing over our base without<br />

any clearance or notification?” The<br />

DATCO, wiser by his past experience,<br />

immediately asked the ac to climb to the<br />

Initial Approach Altitude and report steady. The red<br />

cartridge was fired by an alert Runway Controller at<br />

our Southern diversion because when the ac was<br />

spotted on finals, a working party was deployed on<br />

the runway for maintenance work. Rest all is again<br />

‘history’.<br />

The then budding ATCO has now grown into<br />

a full fledged professional and has a reasonable<br />

working experience in the Tower as well as on<br />

Radar. If nothing else, these experiences added<br />

to his wisdom kitty and engrained a unique habit<br />

of establishing contact with ac reporting finals<br />

notwithstanding the pilots’ report. This habit<br />

proved handy recently, thus averting a total disaster.<br />

At a Western base, on a bright sunny day, when<br />

fighter flying was in full swing and the time was<br />

the peak arrival time for civil scheduled flights, the<br />

duty Radar controller vectored a non-scheduled<br />

civil ac for a visual approach on runway 10 (noninstrument<br />

runway). Approximately at 9-8 miles<br />

from touchdown at a height of a little more than<br />

1500 feet, the pilot reported runway in sight and was<br />

asked to contact tower. The fully occupied Tower<br />

Controller, mechanically responded by asking the<br />

ac to “report short finals”. Though not demanded<br />

out of him as a Radar Controller but out of sheer<br />

habit, the duty Radar Controller was following the<br />

ac on visual approach. He observed that the ac<br />

had altered its heading to 080-085, as against<br />

the expected heading of 095-097 and<br />

the height indicated on radar<br />

was just 400-450 ft while still<br />

5-4 NM from touchdown.<br />

On sensing something<br />

amiss, without wasting a<br />

moment he changed over<br />

to the Tower frequency<br />

and nearly screamed, “(call<br />

sign), STOP DESCENT CLIMB<br />

IMMEDIATELY (repeated<br />

twice).” The pilot diligently<br />

complied acknowledging the<br />

same and was re-vectored for another<br />

approach. Post flight discussion with the pilot<br />

revealed that he had mistaken the rowing channel<br />

on approach (almost the same length as the runway<br />

and of similar orientation) for the runway and<br />

had made an approach for the same. Had it gone<br />

unnoticed, the result could have been anything but<br />

pleasant.<br />

Notwithstanding the fact that ATCs in IAF<br />

lack the crew room culture of flying squadrons,<br />

wherein aircrew learn from each other’s mistakes,<br />

experiences need to be shared for a safer tomorrow.<br />

In this era of technology too, despite the most<br />

advanced avionics being available on board, if all<br />

this happened; chances of history repeating itself<br />

can’t be ruled out.<br />

- Wg Cdr PC Kalia<br />

INDIAN AIR FORCE 2 0 1 2 N o v e m b e r Aerospace Safety 3


Wg Cdr Anuj Pathak<br />

A<br />

large part of any SASIO’s task and time<br />

is taken up in trying to manage the bird<br />

activity at an airfield, so as to permit<br />

operations to continue. Being an integral part of<br />

the flying profession, no SASIO would like to hold/<br />

restrict/stop flying due to birds. But at times, that<br />

is the only solution, albeit a temporary one. Apart<br />

from managing the bird activity on a day-to day<br />

basis or planning for short term measures, the<br />

SASIO needs to put his mind in identifying the<br />

risk species/periods with respect to birds, their<br />

habitat, food cycle, travel routes etc and prioritise<br />

the avian hazards so as to be able to effectively<br />

tackle this impediment. Presently, a generalised<br />

approach for control of all species on an airfield<br />

is resorted to. Despite some periodic species<br />

specific modules devised by the Ornithology<br />

Cell, the system lacks a procedure of any risk<br />

assessment and prioritisation of the avian hazards.<br />

It is a known fact that threats posed by all species<br />

are not the same and therefore concentrating on<br />

a particular population or species of birds may be<br />

ultimately more productive than a generalised<br />

control of all available species.<br />

A need therefore exists to carry out a risk<br />

assessment of avian species affecting operations<br />

and to prioritise the risk to plan for effective<br />

control measures.<br />

Why Assess Risk?<br />

How does a SASIO focus his control measures<br />

against general avian activity? Will the same<br />

methods work against all types of birds? Is<br />

‘spiking’ R/W/ taxy track markers to deny perch<br />

area to birds effective for all types of birds?<br />

Are specific forms of control measures such as<br />

food chain denial, roost harassment or habitat<br />

management going to work across the board<br />

for all species of avian activity? Are the modules<br />

season specific? Do some modules work more<br />

effectively in the mating season or the roosting<br />

season? A risk assessment of avian activity would<br />

bring out such answers. This would go a long<br />

way in determining long term policies of avian<br />

control. Also, expenditure planning in terms of<br />

whether or not to implement a particular control<br />

procedure and whether or not to purchase<br />

equipment for the same, can be prioritised. Avian<br />

4<br />

Aerospace Safety N o v e m b e r 2 0 1 2<br />

INDIAN AIR FORCE


species posing the greatest risk to aviation can be<br />

identified and a control programme by which they<br />

could be addressed, created.<br />

How to Assess Risk and Prioritise it?<br />

To combat avian hazards, assessing, identifying<br />

and prioritising risks posed by different species<br />

present in their environment is an important facet<br />

of the SASIO’s job profile. Expert assistance from<br />

the Ornithology Cell is available and should be<br />

sought. The proposed steps permit risk assessment<br />

of avian hazards on airfields and subsequently,<br />

aid in developing a control protocol for dealing<br />

with these risks. Evaluation of all species affecting<br />

operations will result in relative risk evaluation<br />

for various species. After this is determined, an<br />

effective control measure can be developed to<br />

address those risks. As not all species are equally<br />

hazardous to flight operations, this assessment<br />

allows us to acquire a list of species that pose the<br />

greatest risk to aviation and the order in which they<br />

should be addressed in any control programme.<br />

Significant criteria need to be taken into account<br />

when determining the order that the species fall<br />

into and exactly how they might affect overall<br />

operations. Based on survey reports, a ‘Final Risk<br />

Value’ could be worked out which would tabulate<br />

the bird hazards and permit prioritising the risk.<br />

The following factors need to be considered<br />

when carrying out risk assessment and prioritising<br />

control measures:-<br />

Species Population. Greater the numbers,<br />

greater would be the impact on operations.<br />

Obviously, greater the number of birds present in<br />

the environment, greater the likelihood of striking<br />

an aircraft. For example at an airfield if there are<br />

almost 1000 pigeons crossing over a particular<br />

area in a given time frame, the chances of them<br />

hitting an ac are far greater than a bunch of cattle<br />

egret.<br />

in overlooking a serious risk factor. Accurate<br />

determination of species population becomes<br />

important in assigning relative risk status to that<br />

species and prioritising its control. Therefore,<br />

the species that have the highest number of<br />

birds found within an airfield’s environment are<br />

assigned higher risk factor in the relative risk<br />

hazard compilation.<br />

Bird Size. The impact force generated by<br />

a bird strike depends on the ac velocity and the<br />

mass of the bird. The larger an animal’s body mass,<br />

the more significant the damage it could cause to<br />

an aircraft. A single bird strike involving a large<br />

vulture could wreak havoc on even the largest<br />

of planes while impact of smaller birds may not<br />

cause significant damage. Therefore efforts need<br />

to be concentrated on eliminating the presence<br />

of larger sized birds first.<br />

Large Flock Movement. Birds that travel<br />

in flocks are potentially more of a hazard to<br />

aircraft operations than those that move about in<br />

small groups or individually. Ingesting a bunch<br />

Quantifiable surveys are needed to be<br />

conducted to determine the absolute number<br />

of birds involved. Care should be taken to avoid<br />

assumptions during the survey as this may result<br />

INDIAN AIR FORCE 2 0 1 2 N o v e m b e r Aerospace Safety 5


of sparrows or larks into an engine can be as<br />

damaging as ingesting a much larger vulture.<br />

This is especially true for bird groups like the<br />

short toed lark, wagtails, ashy crow sparrow lark<br />

etc.<br />

Time Spent in Airfield Environment. A bird<br />

that passes through the area and may only be<br />

spotted near the aerodrome once, obviously<br />

poses much less of a risk than one that spends<br />

the whole year in the local environment. A case<br />

in point is the migratory bird ‘in transit stopovers’<br />

like that of the greater/lesser flamingo etc.<br />

Activity Cycle of the Bird. All bird species<br />

have a distinct feeding, sporting and resting<br />

cycle. Identifying this cycle of intense activity<br />

be permitted only above stipulated heights at<br />

certain airfields.<br />

Species Location wrt Operations. Those<br />

species that may be located farther from the<br />

airfield area, but could fly to great heights may<br />

pose more of a threat than species that spend<br />

their time within the airfield but do not fly very<br />

far from the group, for example all raptors like<br />

kites/eagles etc. The score for kites in this factor<br />

can be much higher since they fly at considerable<br />

heights. Also, a bird located 100 m off to the side<br />

of a runway poses a very different threat than<br />

one situated 100 m on the approach of the same<br />

in a 24 hr period will allow time specific control<br />

measures. For eg. if resting time is denied by<br />

creating constant disruption in their resting<br />

place, the birds would tend to find an alternate<br />

resting place outside the airfield. Additionally<br />

certain operations may / may not be permitted<br />

during specific periods of the day. For example<br />

despite green period timings, overshoots may<br />

runway. For example, the green bee eater may be<br />

abundantly available at a base, but rarely found<br />

on the R/W shoulders.<br />

Time Spent in Air. Those species of birds<br />

that spend a great deal of their time foraging<br />

on the ground or rarely change locations do not<br />

pose as great a threat as those species that fly<br />

about the airfield frequently.<br />

6<br />

Aerospace Safety N o v e m b e r 2 0 1 2<br />

INDIAN AIR FORCE


Number of Reported Strikes. Knowing what<br />

bird or wildlife species have caused greater<br />

number of strikes at the airfield is generally quite<br />

predictive of future problems. This however<br />

takes time as the normal gestation period for the<br />

swab analysis results, is a few months. Therefore,<br />

for accurate prediction a larger database of a few<br />

years bird strike cases needs to be catered to.<br />

Ability to Actively Avoid Ac Collisions. Not all<br />

species are equally capable of actively avoiding a<br />

collision with an incoming aircraft. Crows, Kestrels<br />

etc. are quite adept at avoiding ac while a vulture<br />

Conclusion<br />

A risk assessment rating system is applied to<br />

each species at an airfield in order to determine<br />

a risk ‘rating’. This list should be used to prioritise<br />

wildlife control efforts and can be used as an<br />

index to help determine the overall effort and<br />

money that should be spent on preventing a<br />

strike of that particular species. Though only<br />

a guideline, this methodology can serve as an<br />

effective method of setting bird control priorities<br />

and may, in the long run, help SASIOs improve the<br />

effectiveness of bird control measures on their<br />

airfields.<br />

- Wg Cdr Anuj Pathak<br />

is notoriously unskilled at avoiding impacts with<br />

faster aircraft.<br />

Bird Response to Control Measures. Different<br />

birds need different approaches to control their<br />

activity. Certain birds would not respond to a<br />

particular control measure. Different measures<br />

would be required to tackle various bird species.<br />

For example spraying of insecticides, drum<br />

beating module, thumping parade etc, must<br />

be aimed specifically at different bird groups/<br />

species.<br />

INDIAN AIR FORCE 2 0 1 2 N o v e m b e r Aerospace Safety 7


Wg Cdr Rajesh Sharma<br />

It’s been more than 15 years since I resigned from my previous job as an Inspector in the Customs<br />

and Central Excise Department and joined the fourth largest Air Force of the world. Pride in uniform,<br />

discipline, security in all aspects and flying were the things which attracted me then and continue to<br />

attract me till date. All this while, for the last one and a half decades, like in T-20 matches, I too have had<br />

my share of good and bad days on the field. Not many are aware of the these moments or nail biting<br />

finishes, therefore it is my endeavour to share these with all of you so as to help others derive lessons<br />

and to perform better each day. As lessons are more important than the names, I do not mention any<br />

names. Being positive in life is ‘THE MANTRA’ of life so I too shall start with days when I performed well<br />

in the T-20 match.<br />

Scoring a Quick Fifty. One day I was on duty as a GCA Radar Controller and fighter flying was in progress.<br />

Three Bisons were carrying out an exercise SE of base. One member rejoined early and informed us that<br />

he was coming for a landing off a descending circuit. Being new to Radar, I wanted to practise vectoring<br />

8<br />

Aerospace Safety N o v e m b e r 2 0 1 2<br />

INDIAN AIR FORCE


of ac and requested the pilot, who was the Flight<br />

Commander of the fighter Sqn, for vectoring<br />

the ac for JLD. This was negated by the pilot. I<br />

could see two ac still operating in sector and one<br />

leaving the sector. The ac which was leaving the<br />

sector was on a North Easterly course, instead of<br />

a North Westerly course as required for overhead.<br />

On the pretext of passing Runway and QNH, I<br />

cross checked the position of ac with homer.<br />

As no other flying was on, I was certain that the<br />

pilot was going in the wrong direction. I had not<br />

identified the ac on Radar. As the ac was going<br />

away from base and getting closer to the ATS<br />

route, I mustered my guts and asked the Flt Cdr if<br />

he would like to be Radar Vectored for JLD. This<br />

time he reluctantly agreed. As ours was a Primary<br />

Radar, I asked for the heading of the aircraft and<br />

gave a left turn by 70 degrees for identification.<br />

The pilot was surprised and reconfirmed if it was<br />

a left turn and that too by 70 degrees. The same<br />

was confirmed by me. Thereafter he did not<br />

speak much on R/T. After landing I got a call from<br />

the Flight Commander. He first thanked me and<br />

said that he had selected an incorrect waypoint<br />

in his navigation system and hence was actually<br />

setting course for a different base. In addition<br />

he said that he was slightly low on fuel as well.<br />

So, that day with this quick fifty, I contributed<br />

significantly towards our team and it was a winwin<br />

situation for all. This episode taught me to<br />

monitor ac regularly even when they were not<br />

being Radar Vectored.<br />

Yet Another Useful Knock. This time, the<br />

venue was the same but the type of ac was<br />

Jaguar. Two ac had gone to sector and changed<br />

over to SU. Within no time both changed over<br />

back to Radar and I was informed by No 1 that<br />

No 2 had an emergency. They were coming in<br />

for a priority rejoin off a descending circuit. After<br />

informing the tower to initiate primary alarm,<br />

I continued monitoring the R/T calls of No 1<br />

who was asking the No 2 for his ac parameters.<br />

I asked the formation leader if he would like to<br />

be vectored for a JLD. This was overruled by the<br />

leader. Meanwhile the SFS in tower told me to<br />

be more careful with respect to No 2 as he had<br />

just become ‘Operational’ on Jaguars and that he<br />

should be made to land ASAP. During our training<br />

on Radar it was grilled into us that emergency ac<br />

must land ASAP unless the pilot had an intention<br />

of holding due to some reason. But in this case the<br />

leader had resorted to a mode of recovery which<br />

was longer. Though I was a little apprehensive, I<br />

gathered the courage and piped up on R/T “.........<br />

(Name) from present position Radar letdown will<br />

be a shorter vector than descending circuit.” I do<br />

not normally use a pilot’s name on R/T or question<br />

the pilot’s decision in an emergency as he/she<br />

may be preoccupied with taking quick decisions,<br />

but this day I did it anyway. The leader agreed<br />

and after identification I vectored No 2 followed<br />

by No 1. Run to touchdown was reduced by<br />

approx 25 miles in this mode of recovery. After<br />

landing the leader informed me that due to No<br />

2’s problem it did not strike him that JLD would<br />

have been a better option. So yet again I was<br />

satisfied with my contribution to the safety of our<br />

ac.<br />

Hat Trick. Another location, dark night,<br />

single engine ac and night flying was in<br />

progress. Fighters were airborne for 1 vs 1 and<br />

maintaining with SU. SU had changed them<br />

over to the training frequency for the exercise.<br />

As other ac had become U/S before departure<br />

and the workload in Radar was less, I decided to<br />

monitor the frequency of SU, though I had no<br />

obligation to do so. I was trying to make sense<br />

INDIAN AIR FORCE 2 0 1 2 N o v e m b e r Aerospace Safety 9


of the position of aircraft engaged in PI, when<br />

all of a sudden I heard a call, “RPM dropping,<br />

attempting relight.” I immediately informed<br />

the Tower that the SFS should change to the<br />

training frequency on the LUP Set and listen<br />

to the calls of the pilot. Meanwhile the pilot<br />

who had successfully relit the engine of the<br />

Bison ac was heading for base. He informed<br />

the SU controller, “Tell SRE to come up on this<br />

channel. I cannot change frequency.” The ac<br />

was nearly 20-22 miles from touchdown and<br />

I had not identified the ac as yet since both<br />

ac were nearly together, though separated<br />

vertically. Now, had the SU controller told<br />

the ADSO to inform Tower, then Radar and<br />

considering the time required for me to<br />

tune the required channel on the LUP set, it<br />

would have been too late to give any Radar<br />

assistance for the landing/approach. Lady<br />

luck was with us that day and on listening to<br />

the last call about SRE, I instructed the pilot to<br />

turn left onto 170 degree for identification. As<br />

there was no reply I repeated my call. My mind<br />

had started working faster as ac was coming<br />

closer. I called up SU on R/T to transmit to<br />

the ac to turn left for identification. I had<br />

given discretionary descend as well. Range<br />

of my R/T on the Training freq was very less.<br />

So whatever I transmitted on R/T, the same<br />

was repeated by the SU controller and the ac<br />

responded. By the time he turned left, he was<br />

just 11 miles from touchdown. By this time<br />

he started getting my calls. I carried out an<br />

emergency approach and the ac landed with<br />

nearly 3000 L of fuel. It was a heavy landing<br />

and it was indeed commendable on the<br />

pilot’s part to have successfully relit the Bison<br />

engine and landing within no time. The No 2<br />

ac of the formation diverted. That day after I<br />

came home I prayed to God in silence for some<br />

time and thanked him for everything. A COI<br />

was convened and subsequently the pilot was<br />

awarded a well deserved SC. To my surprise, this<br />

was one COI wherein the ATC officer was not<br />

asked any questions. Whatever help I could offer<br />

in the emergency approach was very satisfying<br />

and till date I do not know as to why I had that<br />

urge to change channels and listen to the PI that<br />

day. That helped in saving valuable time, when<br />

time was very critical. May be God had his plans<br />

for me. I may hardly ever get such a close call<br />

again for assisting in an emergency approach in<br />

my life.<br />

There is hardly any cricketer who hasn’t had<br />

his share of a lean patch in his career. I too had my<br />

lean patch a couple of times wherein my timing<br />

wasn’t good and I couldn’t contribute much<br />

with the bat or ball. It was due to Situational<br />

Awareness of the pilot and my luck, that we did<br />

mange a safe recovery.<br />

Missed Being Run Out by a Whisker. The<br />

source of electro-magnetic waves is the radar<br />

and if we vector the ac towards this, then the<br />

ac will head towards the radar and not towards<br />

the touchdown point. There exists a procedure<br />

wherein a Radar Controller offsets the centre to<br />

the touchdown point (thankfully, in present day<br />

radars this off-centering is done at the click of<br />

a button, unlike earlier when it had to be done<br />

manually). Once I was vectoring an ac for JLD<br />

10<br />

Aerospace Safety N o v e m b e r 2 0 1 2<br />

INDIAN AIR FORCE


and I forgot to off centre. Now I was vectoring the<br />

ac to the radar and not towards the touchdown<br />

point. I was blissfully unaware and continued<br />

vectoring. At around 1NM from touchdown the<br />

ac went around and positioned for a descending<br />

circuit. It was my good luck that the weather was<br />

good, the pilot senior and very sure of his position.<br />

When the pilot went around, I was informed by<br />

the Tower Controller that the ac was well right of<br />

track and heading towards the radar. I realised my<br />

mistake straight away and thereafter just could<br />

not wait to say sorry. It was good understanding<br />

and a timely “NO” call by the pilot, which saved<br />

me from being run out that day.<br />

Overconfident and First Ball Duck. As I<br />

was gaining experience, I was becoming more<br />

confident in Radar controlling. Little did I realise<br />

that I was becoming overconfident. Once, during<br />

full fledged flying, a five ac formation asked for<br />

a tactical QGH followed by a precision approach<br />

on inbound. I was too greedy to give this QGH<br />

to the Tower Controller and started the QGH<br />

myself. On outbound the ac were to enter sector<br />

SE and a two ac formation was doing a low level<br />

exercise in that sector with the formations being<br />

separated vertically. I was not looking at the<br />

Radar and continued with QGH looking at the<br />

homer. The low level formation after finishing<br />

the exercise gave a call “climbing to 7000 feet,<br />

request precision approach”. It was time to give<br />

a correction to the QGH ac and I responded to<br />

the call with “Roger” and gave a correction to the<br />

formation doing QGH. Within no time I heard the<br />

call “too close” from one of the members of the<br />

formation doing QGH. I looked at the display and<br />

realised that the two formations had come close<br />

to each other. I should not have been doing QGH<br />

and the pilot should have asked permission to<br />

climb instead of giving me information. It was a<br />

bad day but luck favoured all of us. However this<br />

first ball duck did not result in our team losing<br />

advantage.<br />

Caught but Outside the Boundary Line.<br />

Once I was on night flying duty in the tower for<br />

base night flying. My course mate was waiting<br />

for me and as soon as I reached the tower, she<br />

handed over the traffic to me. The first detail was<br />

airborne and as I sat on my seat, I got a call on<br />

EPABX from one end of the runway where the<br />

CFT was parked. The AFSO informed me that the<br />

arrester barrier was still down. I looked at the<br />

light indication and looked at my course mate.<br />

We did not say anything and I quickly raised the<br />

arrester barrier. We were lucky that no aircraft<br />

had required to engage arrester barrier that day<br />

till it was raised by me.<br />

Ups and downs keep taking place in<br />

life including the work place, but better<br />

understanding, confidence in each other and<br />

professionalism go a long way in success of a<br />

mission. Aviation is a team game and everyone<br />

needs to contribute. But in all this one must<br />

remember to enjoy the T20 game we play daily.<br />

After all, in the end it is the team ‘INDIAN AIR<br />

FORCE’ which should be winning all the time. Our<br />

ranking at the top is assured by our efforts alone.<br />

Happy flying and happy controlling.<br />

- Wg Cdr Rajesh Sharma<br />

INDIAN AIR FORCE 2 0 1 2 N o v e m b e r Aerospace Safety 11


Gp Capt KVS Nair<br />

One comes across incidents / events in<br />

one’s life and profession, which spur him<br />

/ her in a particular direction, often called<br />

‘turning points’. Cricket commentators scramble<br />

to identify the ‘turning point(s)’ in IPL matches.<br />

We as a unit also came across one such incident<br />

(on the first working day after assuming a new<br />

role) which ‘kick started’ us and got us going in<br />

the right direction.<br />

The Incident<br />

On a busy Monday morning, a Gulfstream<br />

corporate jet ac at approx. 8000 ft goes through a<br />

formation of fighter ac. During descent on its ATS<br />

route towards its destination (an IAF airfield also<br />

used by civil flights), the corporate jet comes on<br />

a collision path with the trail pair of a 4 ac mixed<br />

fighter formation. The Resolution Advisory (RA)<br />

of the civil passenger ac cuts in, prompting the<br />

pilot “climb; climb now” from the first fighter<br />

and approaching the second, prompts “descend;<br />

descend now”, to avoid a collision.<br />

The very experienced SATCO thereafter is<br />

obliged to exercise all his superior PR (Personal<br />

Relations) skills to convince the civil pilot not to<br />

report the incident. Incident report or not, there<br />

are lessons to be learnt by all the operators and<br />

associated elements. The following paragraphs<br />

analyse the incident and attempt to bring out<br />

some of those lessons.<br />

What Happened?<br />

On that day, the 4 ac formation of a<br />

detachment was planned for a live Low Level<br />

strike mission. The navigation route passed<br />

through all sectors of the base, crossed an ATS<br />

route at 20° angle (approx) and culminated at<br />

the pull up point for live weapon delivery. Due to<br />

inclement weather during the earlier part of the<br />

day, the sortie launch was postponed repeatedly.<br />

Sure enough, as the weather cleared, there was a<br />

mad rush by all the locally based squadrons and<br />

the one on detachment, to launch sorties in order<br />

to achieve the day’s planned task.<br />

The lead pair of the formation got airborne<br />

at 1118h and contacted the SU to level out at<br />

6000’ for the navigation (instead of low levels)<br />

as it was now ‘Red Period’. Number 3 and 4 got<br />

12<br />

Aerospace Safety N o v e m b e r 2 0 1 2<br />

INDIAN AIR FORCE


airborne six minutes later as planned, to execute<br />

a planned rendezvous (RV) as a part of the sortie<br />

profile. They too contacted the SU, seeking to<br />

maintain 7000’ and 8000’ respectively to maintain<br />

safe height separation for the RV. Having levelled<br />

out at the allotted heights, the formation<br />

was permitted to change over to the training<br />

frequency by the Recovery Director (RD), who is<br />

the FC controlling local flying in the sectors, with<br />

an instruction to give ‘Ops normal’ call every ten<br />

minutes. It was only after about 7-8 min that the<br />

RD started getting perturbed when the formation<br />

started deviating from the track passed by the<br />

Base Ops Room. The RD could not check with the<br />

formation as they were on a different frequency<br />

and so asked the Recovery Assistant (air warrior<br />

detailed to assist the RD) to call up Base Ops<br />

Room and check the route.<br />

The fighter formation meanwhile had<br />

completed three legs of the route but had not<br />

effected the RV. The trail pair was together,<br />

trailing the lead pair by about 15 Km. As per<br />

the sortie profile, a bogie was simulated by the<br />

supervisor and the trail pair took tactical action.<br />

In the process, the Air Interception Radar of one<br />

of the ac picked up a track approaching from the<br />

right and after resuming course, the left member<br />

reported the civil airliner, after making visual<br />

contact. The right member ‘ducked down’ to<br />

create separation and the left member ‘pulled up’.<br />

The Gulfstream civil aircraft passed between the<br />

two ac with RA cutting in, asking the pilot to first<br />

pull up and then push down. Neither the civil ac<br />

nor the fighter formation was informed of each<br />

other’s presence.<br />

The RA is an audio warning, notifying<br />

imminent danger of collision, given by Traffic<br />

Collision Avoidance System on transponder<br />

equipped ac. When an RA is issued, the pilot is<br />

expected to respond immediately. He is allowed<br />

(at that time) to violate the ATS instructions given<br />

to him till the danger is over.<br />

The Mistakes Made / Questions to be Asked.<br />

In retrospect it is clear that mistakes were<br />

committed by many operators/functionaries in<br />

the chain for the situation to reach such unsafe<br />

levels. There are also some questions that arise.<br />

Some of them are listed below.<br />

Should the formation have stuck to its profile,<br />

now that it had got airborne during red period,<br />

given that at the newly decided heights, they<br />

were going to transgress into the airspace of ac<br />

operating in the sectors? It should also have been<br />

expected that the traffic in sectors would have<br />

been heavier as everyone had launched nearly<br />

together with the weather suddenly clearing up.<br />

While planning, ATS route crossing should<br />

have been as close to perpendicular as possible.<br />

Positive RT contact / clearance should have been<br />

taken from SU before crossing/approaching<br />

ATS route. Should the formation have been<br />

Continued on page 17<br />

INDIAN AIR FORCE 2 0 1 2 N o v e m b e r Aerospace Safety 13


Wg Cdr R Vijay<br />

14<br />

Aerospace Safety N o v e m b e r 2 0 1 2<br />

INDIAN AIR FORCE


The time was 2100h and I had just finished my<br />

dinner when my mobile rang. It was Gp Capt<br />

xx C Eng B from the Command Headquarters.<br />

He said that the VIP Avro ac of Command<br />

Communication Flight had made an emergency<br />

landing at Mumbai International Airport at 2030<br />

h due to nose undercarriage red light remaining<br />

‘ON’. Luckily there was no VIP on board and the ac<br />

was returning to base. The ac had landed safely but<br />

had been switched off on the taxi link due to nose<br />

wheel steering failure and was being towed back to<br />

the parking. The STO of the unit was on leave and<br />

since I was the STO of the neighbouring AVRO unit,<br />

I was asked to speak to the aircrew to ascertain the<br />

complete snag and keep a rectification party ready<br />

to go to Mumbai at first light.<br />

I called the senior most aircrew who was a Sqn Ldr<br />

with sufficient experience on type. He said that for<br />

this sortie he was the co pilot and the captain was a Fg<br />

Offr with about one year’s experience. He explained<br />

that they had taxied out normally and after takeoff<br />

when the undercarriage had been selected up, the<br />

nose undercarriage light had changed from green<br />

to red and remained ‘ON’, indicating that the nose<br />

wheel had not locked up. They tried one cycling of<br />

undercarriage and when the red light persisted, they<br />

declared the emergency and carried out a priority<br />

landing back at Mumbai. During the landing roll,<br />

while turning onto the link, he (the Sqn Ldr) realised<br />

that the nose wheel steering was ineffective and<br />

therefore had switched off the ac after clearing the<br />

runway. I spoke to one of my clueful Airframe Fitter<br />

JWO and we suspected that the snag might have<br />

been due to a bird hit during takeoff, which might<br />

have damaged the nose undercarriage door linkage<br />

and also severed the nose wheel steering cable.<br />

However, it was reported by the crew that they could<br />

not find any avian remains or damage, other than<br />

two large dents on the right undercarriage door of<br />

the nose wheel.<br />

A rectification team with I as the team leader<br />

(also the technical member of the Court of Inquiry)<br />

was airlifted to Mumbai to ascertain the cause of<br />

malfunction of the undercarriage and to undertake<br />

rectification on site. Since Mumbai did not have the<br />

requisite equipment, it was decided to carry even<br />

the 10 ton jack along with other requisite tools.<br />

Draining out of hydraulic fluid due to pipeline<br />

rupture was initially suspected, however, it was seen<br />

that the reservoir was still full and no abnormality<br />

in the nose undercarriage system was found<br />

during visual inspection. However two major dents<br />

wherein one of them had torn the aluminium skin<br />

were seen on the right front undercarriage door.<br />

We decided to jack up the front wheel and do a<br />

retraction test with pins on the two main wheels in<br />

place. The system was energised and pressure built<br />

up using the hand pump and the front wheel was<br />

retracted. No fouling was observed and the nose<br />

wheel undercarriage light changed from green to<br />

red and upon getting locked up, the red light went<br />

off. This confirmed that the system was working<br />

perfectly well. The nose wheel steering was also<br />

checked and tested thoroughly and was found to<br />

be serviceable.<br />

The team thereon proceeded to find the<br />

cause of the dent on the undercarriage door.<br />

The nose wheel toggle pin was removed and on<br />

closer examination it was seen that the dent was<br />

commensurate to the shape of the toggle pin<br />

head and there were even traces of red paint near<br />

the dent. The undercarriage was again retracted<br />

this time with the toggle disconnected and the<br />

pin fixed in the upper toggle. It was seen that the<br />

undercarriage door got obstructed by the upper<br />

toggle link at exactly the same place where it was<br />

dented. It was therefore deduced that the ac had<br />

taken off with the nose wheel toggle disconnected<br />

and this had caused the nose undercarriage not<br />

getting locked up and the red light remaining ‘ON’,<br />

creating an emergency in air.<br />

Exact Cause of Failure<br />

Parking for AF aircraft in Mumbai is such, that it<br />

requires being towed out of the slot during refuelling<br />

or just before starting. In this case the ac was towed<br />

out twice for refuelling and also just before departure<br />

at around 1915h. During towing the nose wheel<br />

toggle link is disconnected from the nose wheel<br />

steering jack. However, in this case the ground crew<br />

INDIAN AIR FORCE 2 0 1 2 N o v e m b e r Aerospace Safety 15


forgot<br />

to reconnect<br />

the nose wheel toggle link<br />

after positioning the ac for startup. This<br />

check is also part of the aircrew preflight checks<br />

and was missed by all the three aircrew. The crew,<br />

oblivious of the fact that the toggle link was not<br />

attached, started taxiing out. Transport crew familiar<br />

with Mumbai will appreciate that the ac has to take<br />

a series of almost 90 deg turns during taxiing so as<br />

to reach the runway. During taxiing, the Captain felt<br />

that the nose wheel steering was sluggish during the<br />

turns and resorted to the non standard procedure<br />

of differential braking to negotiate turns. This fact<br />

was also corroborated by the CVR recordings. The<br />

tradesman responsible for reconnecting the toggle<br />

link was a Propulsion Fitter tradesman with barely<br />

one year of service and this was his first outstation<br />

duty. He realized his mistake immediately after<br />

landing back at Mumbai, however, due to fear, he<br />

reconnected the toggle link before others alighted<br />

from the ac and did not inform anyone.<br />

Why it Happened?<br />

Major international airports like Mumbai<br />

and Delhi have strict time slots, considering their<br />

perpetually busy traffic. In Delhi, the visiting ac is<br />

handled and received in AF dispersal, which is not<br />

the case in Mumbai. In this case, the navigator was<br />

already in the ac during towing, busy coordinating on<br />

RT with Mumbai ground for startup and hence could<br />

not check the toggle link position. The Captain and<br />

the co-pilot also could not ascertain the fitment of<br />

toggle link during their externals as the ground/duty<br />

crew were in the process of disconnecting the tractor.<br />

Hence, the complete onus of ensuring the toggle<br />

link fitment was on the ground crew, who was a Prop<br />

Fit on his first outstation trip. In the urge to avoid<br />

missing the critical time slot, all the crew missed out<br />

o n<br />

the small<br />

toggle link which later<br />

became the weakest link in Flight<br />

Safety. Even during the taxy out when the Captain<br />

experienced sluggishness of the nose wheel<br />

steering, the more experienced co-pilot interpreted<br />

it wrongly and suggested using differential braking<br />

to negotiate turns. Though an incorrect procedure,<br />

aircrew of Avro fleet had expressed that they had<br />

had to resort to this procedure to negotiate turns<br />

at Mumbai and a few other such typical airbases,<br />

while parking. Hence, pointing a finger at the<br />

more experienced co-pilot too was not correct.<br />

Moreover, the decision of the crew to re-cycle the<br />

undercarriage once could also not be questioned<br />

as they thought that it was only an indication<br />

problem.<br />

The Court of Inquiry, after carefully deliberating<br />

over the entire chain of events, was of the opinion<br />

not to blame the tradesman or the aircrew for<br />

this emergency as it was due to the peculiar<br />

circumstances of Mumbai airport. The COI also<br />

recommended the following.<br />

<br />

Carry out pre flight externals<br />

meticulously.<br />

<br />

Detail suitable senior ground crew<br />

whenever flying into international airports<br />

where there is heavy traffic.<br />

<br />

Conduct regular OJT classes for ac<br />

towing for the benefit of FLM tradesmen.<br />

<br />

Educate duty crew personnel at<br />

Mumbai regarding towing procedures of all<br />

transport ac in the IAF.<br />

<br />

In the end one thought remains in my<br />

mind: what if the nose undercarriage had not<br />

come down after recycling?????<br />

- Wg Cdr R Vijay<br />

16<br />

Aerospace Safety N o v e m b e r 2 0 1 2<br />

INDIAN AIR FORCE


Continued from page 13<br />

maintaining training frequency at that time?<br />

The Recovery Director who cleared the<br />

different heights, started losing SA when the<br />

formation changed over to training frequency<br />

and it emerged that the route being followed by<br />

the formation varied from the flight plan available<br />

with the SU.<br />

The RD did not inform GCA that the formation<br />

was maintaining higher height and was on the<br />

training frequency (not in contact with SU).<br />

The RD did not react despite convergence<br />

of the 5 tracks (four military & one civil) which<br />

could be seen on the scope. At least at this stage<br />

the GCA controller should have been cautioned<br />

about the heights being maintained by the<br />

formation. She had got engrossed in handling<br />

other local flying.<br />

The GCA controller also had the five tracks<br />

converging on his scope. The civil ac was in RT<br />

contact with him. He too did not react.<br />

The formation did not give ‘Ops Normal’ call<br />

at the stipulated intervals (which could have<br />

brought them in contact with the RD) and instead<br />

continued maintaining training frequency.<br />

Lessons Learnt<br />

There are valuable lessons to be learnt by all<br />

involved to prevent a similar incident in future.<br />

Some of these are:<br />

Training. All mistakes committed in the<br />

incident are old and relate to training of all<br />

functionaries in the chain. Everybody’s training<br />

failed and the day was saved by technology -<br />

the Al Radar and TCAS worked. Things might<br />

have been different if the fighters were without<br />

transponder equipment or Al radar.<br />

Aircrew. Sortie planning, profile changes<br />

related to environment changes, SOP (ATS<br />

crossing), avionics exploitation (one RT set on<br />

listening watch, the other for training) etc - in the<br />

hurry to get airborne; much was left unattended.<br />

Launch Base. Training of ADSOs at Base<br />

Ops Room, briefing of outstation crew, GCA<br />

involvement, detailed scrutiny of detachment<br />

flying programme etc; launch bases need to be<br />

serious about these, for these are known areas<br />

where communication ‘gaps’ take place - and<br />

here too they did.<br />

SU. Training of RD and ADSOs, how to<br />

maintain SA being the agency equipped with the<br />

largest picture, how/when to raise alarm and ask<br />

for more help etc.<br />

Policy. Is there a requirement for a separate<br />

control (of civil traffic) with the SU, like the ‘alpha’<br />

control in some sectors, now that the civil traffic<br />

has increased, sortie profiles of fighter ac have<br />

become complicated and cover larger areas?<br />

Unified control will also help M&l functions at the<br />

SU.<br />

Conclusion<br />

The incident, without causing anybody any<br />

harm, brought out many lessons for all agencies<br />

conducting/supporting flying operations.<br />

Providence brought these lessons to this unit<br />

on its first working day (probably the first detail)<br />

and set us off in the right direction. Care needs<br />

to be taken to ensure that the lessons are revised<br />

periodically and our guard remains up, to prevent<br />

any such incident in future.<br />

- Gp Capt KVS Nair<br />

INDIAN AIR FORCE 2 0 1 2 N o v e m b e r Aerospace Safety 17


WO PM Jangid<br />

18<br />

Aerospace Safety N o v e m b e r 2 0 1 2<br />

INDIAN AIR FORCE


CROSSWORD CLUES (ACROSS)<br />

1. Pilots aim to touch down at this marking on<br />

the runway while landing.(6)<br />

3. As a runway is for aeroplanes, a................is for<br />

helicopters. (7)<br />

9. Message type designator for alerting ATS<br />

messages. (3)<br />

10. Rectangular paved surface used for an aeroplane’s<br />

take off and landing. (6)<br />

12. An act of aircraft proceeding to alternate<br />

aerodrome. (6)<br />

13. Services on an aerodrome available at night<br />

only. (2)<br />

14. Essential notices distributed by means of<br />

telecommunication to flight associated personnel.<br />

(5)<br />

15. An ATC vehicle meant to lead RT failure or<br />

unfamiliar aircraft. (6,2)<br />

18. Beginning of a runway. (9)<br />

20. ‘A’ in ATD and ATA (6)<br />

21. Cross bar. (4)<br />

22. A unit of speed generally used in aviation. (4)<br />

24. A meridian adopted for calculation of International<br />

Time. (5)<br />

26. Speak out this to indicate that the exchange<br />

of transmissions has ended and no response is<br />

expected. (3)<br />

28. Special series of NOTAM for snow affected<br />

aerodromes. (7)<br />

30. ‘V’ in VFR or VUABC is pronounced this way<br />

when spelt out. (6)<br />

32. Insert this word in flight plan for persons on<br />

board if their numbers are not known. (3)<br />

33. Colour of FOD lanes. (6)<br />

34. Abbreviation for Passengers. (3)<br />

35. Transmitter which helps in locating aircraft in<br />

emergency. (3)<br />

37. Generally known as arrival routes. (4)<br />

39. Meaning of affirm or affirmative. (3)<br />

40. A flight plan which is filed in flight. (4)<br />

41. A type of controlled descent. (3)<br />

45. First known Air Traffic Controller. (1,1,6)<br />

47. A service which provides aerodrome information<br />

automatically to arriving and departing<br />

flights. (4)<br />

48. A critical segment of instrument approach<br />

procedures. (5)<br />

49. ‘S’ in FDPS, RDPS, ILS etc. (6)<br />

50. ICAO type designator for Jaguar aircraft. (4)<br />

CROSSWORD CLUES (DOWN)<br />

1. An area of aerodrome used for accommodating<br />

aircraft for loading/unloading of passengers/<br />

cargo, refueling, parking or maintenance. (5)<br />

2. Listen out on frequency/channel. (7)<br />

3. Be cautious. This may happen to your aircraft<br />

on landing if a thin layer of water is present on<br />

the runway. (12)<br />

4. One of the sub-items of item-15 of flight plan<br />

form. (5)<br />

5. ATC radar meant to provide precision approaches<br />

to flights. (3)<br />

6. An instrument in aircraft that indicates its<br />

vertical position. (9)<br />

7. One of the methods of air navigation. (2)<br />

8. As a guide is to a tourist, a ........... is to a pilot.<br />

(10)<br />

11. Abeam in abbreviated form. (3)<br />

16. Shape of tactical circuit pattern. (4)<br />

17. All radio frequencies from 30 MHz to 300<br />

MHz. (3)<br />

18. Surface movement of an aircraft. (4)<br />

19. On the route. (2,5)<br />

23. An ATS unit designated to provide Aerodrome<br />

Control Service. (5)<br />

24. The title of FLIP Part-I. (8)<br />

25. Rating of a pilot for operating under adverse<br />

weather conditions. (2)<br />

27. Second general rule of the air for avoidance<br />

of collision. (5,2,3)<br />

29. A dangerous cloud for aviators. (2)<br />

31. The direction of fore and aft axis of a moving<br />

aircraft. (7)<br />

32. A letter displayed in the signal square. (3)<br />

33. Frequencies/channels not confidential. (4)<br />

36. Head lights in vehicles but.....lights in the<br />

aircraft. (7)<br />

38. Meteorological personnel use this code for<br />

‘Rain’. (3)<br />

42. A unit for atmospheric pressure. (3)<br />

43. Red navigational light is displayed on this<br />

side of an aircraft. (4)<br />

44. One of the essential factors that governs<br />

runway-in-use. (4)<br />

46. Time estimated by an aircraft to cover the<br />

distance between two points. (3)<br />

- WO PM Jangid<br />

INDIAN AIR FORCE 2 0 1 2 N o v e m b e r Aerospace Safety 19


Wg Cdr B Anandhan<br />

It was a cold winter morning. The Detachment<br />

should have gone by now but it hadn’t because of<br />

a snag.<br />

The snag was another ‘puzzling snag’. After some<br />

brain storming, it was zeroed down to a component<br />

malfunction.<br />

The Supervisor (Warrant Rank) and the<br />

Engineering Officer were on either side of the ladder,<br />

nearly at its top, reaching the roof of the aircraft inside<br />

the fuselage. Their hands were inside the panel to<br />

remove the faulty component. It was an intricate job!<br />

Nobody had removed this particular component in<br />

the Fleet ever before. Concentration was intense, not<br />

a word was spoken.<br />

The team did not notice the Flt Cdr who had come<br />

near the ladder and was watching them for a while.<br />

The silence was broken by the shrill voice of the Flt<br />

Cdr shattering the concentration of the team.<br />

“Aur kitna time lagega”?<br />

And something fell from inside the panel. The Flt<br />

Cdr searched for that ‘something’ for some time. He<br />

could not find it. He left the place. He realised what<br />

he had done.<br />

After securing the component the WO and the<br />

EO climbed down the ladder and searched for that<br />

‘something’. They could not find it. It had rolled away<br />

after bouncing on the floor.<br />

A Corporal was told to hold the commando torch<br />

to light up the space inside the panel.<br />

One side of the component was released from the<br />

linkage and was held by hand; another 10 minutes<br />

and the faulty component would be in their hands.<br />

WO:<br />

EO:<br />

WO:<br />

EO:<br />

Sir, who asked him to come here?<br />

Nobody. Vo apne aap aa gaye!<br />

First let us remove the component.<br />

Okay, but let us put some boys to<br />

20<br />

Aerospace Safety N o v e m b e r 2 0 1 2<br />

INDIAN AIR FORCE


search for the missing thing. We don’t even know<br />

what it looks like.<br />

A team of five was deployed to search for that<br />

‘something’ which had rolled away. The morning<br />

fog meanwhile reduced the visibility. The EO & WO<br />

removed the component, checked it, rectified it<br />

and serviced it. Now it was ready to be fitted back.<br />

EO: Let us reflect it as a snag in the Form 700<br />

and in the snag register.<br />

WO: Nahi sir, then people will come to know<br />

that we removed the component.<br />

EO: Let’s tell him to buy more time for us to offer the<br />

aircraft.<br />

WO: Sahab, galti unki hai, kyon beech me aaya, let him<br />

only buy more time.<br />

EO calls up Flt Cdr.<br />

EO to Flt Cdr: Sir, the snag is rectified, but we need more<br />

time.<br />

(On Phone)<br />

Flt Cdr: I will get back to you.<br />

EO:<br />

So what?<br />

After sometime:<br />

WO: Part to mila nahi na. (The part was never<br />

found, isn’t it?)<br />

EO:<br />

We will get it.<br />

WO: Time nahi hai sir. Tab se log uchchal rahe<br />

hain. Bina ye chhota part bhi kam chal jayega.<br />

EO: WO Sahab! Agar us part ka koi purpose nahi<br />

to wo part hota kyon?<br />

WO: Theek hai sahab, aap jaise kahenge hum<br />

vaise karenge.<br />

EO: Theek hai, abhi pehle fit karke dekhte hain ki<br />

theek ho gaya ya nahin.<br />

Component was fitted, checked and found ‘S’<br />

on ground.<br />

WO:<br />

Sir, Kaam to ho gaya na?<br />

EO: Yeah! Snag is solved, but let’s find the<br />

missing part. Get the exploded view of the<br />

assembly, then we can find out what the missing<br />

part looks like.<br />

WO: Sir, let’s tell the Flt Cdr that the snag is<br />

rectified. Mere hisab se kaam khatam ho gaya hai.<br />

Flt Cdr to EO:<br />

(On Phone)<br />

CO pooch rahe hain: Aur kitna time lagega?<br />

EO: Sir, Jab missing item mil jayega tab bata sakte hain ki<br />

kitna time lagega. I will keep you informed (On Phone).<br />

EO to WO: Phir poochch rahe hain, ‘aur kitna time<br />

lagega’! **+&$*#@%&>


Gp Capt Narinder Taneja<br />

Billion Hearts Beating is an example of<br />

a successful professionally designed<br />

preventive health campaign against heart<br />

disease in our country. I use it as a template<br />

to demonstrate that if we have to succeed in<br />

preventive efforts- health or flight safety, we<br />

need to engage in professionally designed,<br />

sustained and focused campaigns to achieve<br />

the desired objectives.<br />

Have you heard about ‘Billion Hearts<br />

Beating’ and taken the pledge? Some of you<br />

would have done that. For those who have not<br />

heard about it let me describe what the ‘Billion<br />

Hearts Beating’ is. The vision of ‘Billion Hearts<br />

Beating’ is a long-term sustained movement<br />

towards a heart-healthy India and the mission<br />

is to actively promote heart health across the<br />

country by creating awareness about heart<br />

disease and providing workable solutions to<br />

help overcome it. At the time of writing this<br />

article 353815 people had taken the pledge.<br />

The slogan is extremely catchy; the website is<br />

equally attractive and well designed.<br />

What about focus on prevention of any<br />

similar disease in the IAF. Sadly, none. We have<br />

generic advisories on obesity and lifestyle<br />

diseases. But neither do we have a sustained,<br />

focused, or professionally designed and driven<br />

campaign, nor do we have measures to assess<br />

the outcomes. It is important that we identify<br />

the disease that is most prevalent among our<br />

serving personnel and their families (let us say it<br />

is hypertension). It is a concern because it affects<br />

our personnel, their families, affects longevity,<br />

quality of life and places a yet uncalculated<br />

financial burden on healthcare services. We<br />

need to focus our effort towards combating this<br />

disease problem.<br />

Let us now consider Flight Safety. We have<br />

interesting slogans on each page of the Flight<br />

Safety calendar. There are even more interesting<br />

slogans and themes in the Flight Safety magazine.<br />

Yet if we were to ask anyone how they identify with<br />

Flight Safety issues, we may not get a concrete<br />

reply. This probably is due to lack of a focussed,<br />

sustained and professionally run campaign.<br />

What could be the issues in Flight Safety that<br />

could benefit from campaigns such as ‘Billion<br />

Hearts Beating?’ FOD, human error servicing,<br />

22<br />

Aerospace Safety N o v e m b e r 2 0 1 2<br />

INDIAN AIR FORCE


human error aircrew and bird hits prevention are<br />

some issues that would benefit from campaigns<br />

like that being talked about. We need a focus that<br />

is apparent, all pervasive across the organisation<br />

and sustained for a tangible period of time.<br />

You may at this stage be wondering what<br />

a ‘Billion Hearts Beating’ campaign has got to<br />

do with flight safety and how there are beating<br />

hearts in the IAF. You are right to some extent but<br />

there are deeper and complex implications of the<br />

‘Billion Hearts Beating’ campaign that I want to<br />

put into the perspective of good health and flight<br />

safety.<br />

The whole aim of a preventive program in the<br />

form of a campaign is to overwhelm the target<br />

clientele in a way that he/she literally cannot<br />

avoid the print or electronic message looking at<br />

him/her wherever he/she is. This should be done<br />

to the extent that if he/she opens his/her AFNET<br />

computer, that should be the first message for<br />

him/her e.g. a Flight Safety or health message.<br />

In my view, for a campaign to be effective and<br />

successful, it should be:-<br />

<br />

Relevant to the clientele and be<br />

genuine.<br />

<br />

Topical.<br />

<br />

Practical and easily understood.<br />

<br />

Such that people can identify with it.<br />

<br />

It must have a face to it.<br />

How Could We Run a Successful Campaign for<br />

Flight Safety?<br />

Media. The Air Force has a wide array of media<br />

which it can utilise effectively for mass reach in<br />

any program. Print, web, cable TV, offices and<br />

housing areas, shopping complexes, display<br />

electronic boards, you name a medium and we<br />

possibly have it. When the campaign focusses<br />

on the role each support personnel can play in<br />

enhancing Flight Safety e.g. timely PORs, on time<br />

sick report and availability of medicines, quick<br />

and user friendly issue of clothing, it will appeal<br />

to each individual and give him ownership in the<br />

cause of flight safety.<br />

Brand Ambassadors. Products in the market<br />

employ brand ambassadors-luminaries/ famous<br />

personalities from different walks of life to<br />

endorse their product. Our own experiences tell<br />

us how effective it is to utilise brand ambassadors<br />

especially for public outreach programs<br />

e.g. Amitabh Bacchan for polio eradication<br />

campaign. It may not be out of place to have a<br />

brand ambassador for our campaign e.g. how do<br />

villagers / small shop keepers in and around an<br />

Air Force base understand the importance of bird<br />

hits and the significance of cleanliness around<br />

the airport? By either using a personality to<br />

endorse such a message or using an ‘aam aadmi’<br />

with whom they can identify themselves.<br />

Do we need a professional agency to run a<br />

campaign for us? Be it Flight Safety or preventive<br />

health, I for one feel, Yes! There are professionals<br />

in this field who have core expertise in<br />

developing such programs and we need to utilise<br />

their expertise in designing and executing such<br />

projects.<br />

This article is an attempt to make us think<br />

again as to how we can run programs to achieve<br />

certain objectives, in particular, related to Flight<br />

Safety and/ preventive health. The need of the<br />

hour is to put in place professionally designed,<br />

driven and executed campaigns that are focussed<br />

and relevant to the target population. Only then<br />

will we be able to achieve tangible results in<br />

these key areas.<br />

- Gp Capt Narinder Taneja<br />

INDIAN AIR FORCE 2 0 1 2 N o v e m b e r Aerospace Safety 23


Sqn Ldr Vijaya Kumar<br />

24<br />

Aerospace Safety N o v e m b e r 2 0 1 2<br />

INDIAN AIR FORCE


I<br />

am not an external member of an activity; I am<br />

the very part of the ongoing activity.<br />

I clearly know answers for the following<br />

questions:<br />

<br />

What are the SOPs, facilities and<br />

publications required for the task?<br />

<br />

What am I supposed to do?<br />

<br />

What can go wrong?<br />

<br />

What does it take to ensure safe<br />

completion of the given task?<br />

I always believe that only a good worker can<br />

become a good supervisor; I am a good worker<br />

and I can ensure safe completion of the given<br />

task.<br />

I always clarify my doubts about the given<br />

task and I never keep any doubts with me.<br />

I always bring out to my superiors the<br />

difficulty faced by the personnel in carrying out<br />

a given task.<br />

I always maintain in my personal diary the<br />

critical snag and accident/ incident data about the<br />

system I work on and take adequate precautions<br />

to avoid recurrence of the same.<br />

I never supervise two different activities<br />

simultaneously.<br />

I take excuse myself if I am not in a position<br />

to supervise an activity due to any reason and I<br />

ensure that some other supervisor supervises the<br />

activity.<br />

If I feel some pressure I go back to my superior<br />

and share my views. I never pass on the pressure<br />

down the line.<br />

I am very particular about following SOPs. If I<br />

see some deviation from SOPs, I stop the activity<br />

and ensure all SOPs are adhered to.<br />

I strongly believe that by following SOPs<br />

and by disciplined supervision, we can ensure a<br />

pleasant ‘Aerospace Safety’ environment.<br />

I clearly understand that I am vested with the<br />

great responsibility of ensuring Aerospace Safety<br />

through my supervisory skills.<br />

I always ensure that my supervisory activity<br />

is performed to the best of my ability and in<br />

accordance with the procedures laid down in the<br />

manuals.<br />

I always ensure proper documentation and<br />

these documents always comply with Aerospace<br />

Safety norms.<br />

I always feel proud of being a good supervisor.<br />

- Sqn Ldr Vijaya Kumar<br />

My IAF; My Station; My Aircraft; My Pride!<br />

INDIAN AIR FORCE 2 0 1 2 N o v e m b e r Aerospace Safety 25


WO PK Swain<br />

All tools are serially numbered.<br />

Why and when did this practice start?<br />

Time: Good old days in 1996.<br />

Location:<br />

MIG 21 fighter squadron of the IAF.<br />

26<br />

Aerospace Safety N o v e m b e r 2 0 1 2<br />

INDIAN AIR FORCE


A<br />

MIG 21 aircraft was cleared for<br />

Ground Run. A few seconds after<br />

engine start up, fuel was found to<br />

be leaking from the starboard side of the<br />

fuselage. The engine was immediately cutoff<br />

and everyone rushed to the aircraft to<br />

find out what had gone wrong.<br />

The STO suggested that the rear fuselage<br />

be removed so that the point of leak could<br />

be located. Soon, a gang started working on<br />

this. Meanwhile, the engine tradesman came<br />

running and told everyone that the ‘L’ shaped<br />

compressor screw driver was missing. This ‘L’<br />

shaped Compressor Screw Driver had screw<br />

driver tips at both the ends of the ‘L’. It was<br />

used by engine tradesman for opening the<br />

engine compressor panels. It was also used<br />

by the radio tradesman to open the radio<br />

panels.<br />

The STO ordered everyone to<br />

immediately deposit their tools so that<br />

the person who had lost the tool could be<br />

identified.<br />

Meanwhile the rear fuselage was<br />

removed but the source of leak could not<br />

be located. Suddenly an engine tradesman<br />

shouted that many compressor blades were<br />

damaged. The airframe i/c found out that<br />

there was a small hole on the starboard side<br />

inner fuselage wall. Flexible fuel tank No 5<br />

was fitted close to that and it was suspected<br />

to be leaking. The STO ordered the removal<br />

of the fuel tank. All of us were surprised<br />

to find a metal part in the fuel tank. It had<br />

pierced into the fuel tank, causing the leak.<br />

The Tool Crib i/c confirmed that one<br />

of the ‘L’ shaped screwdrivers was not<br />

accounted for. One of the tradesmen said<br />

that he had seen the Radio Fitter take the<br />

‘L’ shaped tool from the Engine Fitter’s tool<br />

bag but the Radio Fitter said he had put it<br />

back after sometime. But the doubt was still<br />

lingering.<br />

A Court of Inquiry was ordered.<br />

The findings of the COI were:-<br />

The Radio Fitter had left his tool on the radio<br />

panel and returned the Engine Fitter’s tool to the<br />

tool crib instead of his own.<br />

When a ground run is given on MIG 21 aircraft,<br />

the nose oleo leg gets compressed and the aircraft<br />

stoops (dips) a little in the front due to engine<br />

thrust. Therefore the tool which was left on the<br />

radio panel started moving towards the air intake<br />

(due to vibration) and eventually got sucked into<br />

the engine.<br />

The engine sustained damage due to the FOD<br />

by ingesting a tool. One of the broken pieces of<br />

the tool also pierced the flexible fuel tank causing<br />

the fuel leak.<br />

The Engine Fitter and Radio Fitter were found<br />

to have not checked their tools on completion of<br />

their job. The WO i/c DSS too had added to the<br />

lapse by signing for independent FOD checks<br />

before offering the aircraft for ground run. The<br />

STO did not ensure accounting of tools prior to<br />

start of ground run.<br />

Recommendations by COI:-<br />

Each and every tool is to be serially numbered<br />

by engraving and the serial number of the tool is<br />

to be written in the ‘Tool Crib Daily Issue’ register<br />

against the tradesman drawing that particular<br />

tool.<br />

Since then the practice has continued till date.<br />

Lessons learnt:-<br />

<br />

Always count your tools before and<br />

after the ground run.<br />

<br />

Own up to the mistakes made by you<br />

rather than hiding them.<br />

<br />

Avoid borrowing tools.<br />

- WO PK Swain<br />

INDIAN AIR FORCE 2 0 1 2 N o v e m b e r Aerospace Safety 27


Wg Cdr N Dhar<br />

28<br />

Aerospace Safety N o v e m b e r 2 0 1 2<br />

INDIAN AIR FORCE


There was a hushed silence in the briefing room<br />

when the Mission Leader disclosed the target.<br />

The target had been a closely guarded secret<br />

for some time now with speculations and rumours<br />

doing the rounds. Food and accommodation had<br />

been difficult to come by recently with large scale<br />

deforestation on the rise. Avian HQ had come up<br />

with a plan to recce new feeding grounds down<br />

in the plains. This was one such feeding ground<br />

which had been selected for a probe and went<br />

by the name of ‘Alottafilth Nagar’. The specialist<br />

from the ‘Avian Intelligence Group’ got up and<br />

strutted pompously to the podium ruffling the<br />

feathers of the Mission Leader in the process. The<br />

Intel Bird started briefing using a fresh Powerpoint<br />

presentation. I guess ‘Powerpoint’ was an affliction<br />

that transcended genetic boundaries too. The<br />

Intel Bird chirped, “My dear friends! As you know<br />

‘Alottafilth Nagar’ holds the key to our food and<br />

energy requirements. We must recce this feeding<br />

ground successfully in order to fend off the crisis<br />

we are facing right now. However, as we know, all<br />

good things are fattening, illegal or dangerous.<br />

This feeding ground is dangerous to say the least.<br />

The single most factor that makes this mission<br />

daunting is the geographical location of ‘Alottafilth<br />

Nagar’. ‘Alottafilth Nagar’ is bounded on the North<br />

by huge Sulphur springs and geysers. Believe me<br />

the stink is overpowering. Humans are often found<br />

wallowing like cows in that stuff. On the East and<br />

West are huge skyscrapers. Last but not the least,<br />

on the South, right on the edge of ‘Alottafilth Nagar’,<br />

is the fighter base ‘Can’t Believe My Rotten Luck’.<br />

From our present location our ingress will have to<br />

be from the South. As if ingressing over this well<br />

guarded air base wasn’t enough, we have to egress<br />

through the Sulphur springs too.” “It is a tough life<br />

but somebody has got to do it,” someone quipped<br />

from behind. “Well, we need to run through the<br />

defences threadbare before undertaking this<br />

mission,” said the Intel Bird.<br />

“These guys have bird watchers/shooters<br />

deployed all around the airfield throughout the<br />

day and they are well equipped with twelve<br />

bore guns, German whistle/cracker deploying<br />

pistols, binoculars and walkie talkie sets for<br />

communication. The shooting efficiency of these<br />

shooters is suspect though. Just a handful of them<br />

are sharpshooters. Most of them couldn’t hit a barn<br />

door at five yards. We have mapped their positions<br />

and will avoid flying directly over them. Their guns<br />

too are old and not very efficient, with an effective<br />

range of fifteen metres at most. So unless you<br />

are unlucky or stupid enough to fly directly over<br />

these shooters, you should be ok,” Intel chirped,<br />

thoroughly enjoying himself now. “Yeah and they<br />

are really into those gas cannons which are placed<br />

at the edge of the runway. They call them ‘Zon<br />

Guns’. But they hardly ever change their location<br />

and our guys are kind of getting used to them<br />

now. So they are no big deal unless they change<br />

the location of their ‘Zon Guns’. Another thing we<br />

really need to do is to locate a similar target area<br />

somewhere else close by and practise our runs<br />

out there. These humans are getting pretty good<br />

at mapping and trend generation; this way we<br />

will be able to maintain the element of surprise.<br />

Okay, the next part is really important; formation<br />

to fly! We are going to fly small elements of four,<br />

nothing more than that. We don’t want to show<br />

off our formation skills with those mass 100 bird<br />

formations that the humans are in awe of. Those<br />

huge formations are picked up too easily and it is<br />

easier for them to take pot shots at us. Even with<br />

their shooting skills, they just might hit something<br />

and we don’t want to risk that. And remember the<br />

golden rule: when the flak starts coming up just<br />

soar to greater altitudes like 100 m and above.<br />

They have nothing to get you there excepting 0.22<br />

inch rifles, of which not very many are available to<br />

the humans.” The mission brief was over and the<br />

raptors got busy updating their mission planning<br />

grey cells. This was dangerous business and they<br />

did not want any Faux Pas!<br />

On ‘D’ day at dawn, the ‘Eagles’ sat preening<br />

and sharpening their beaks. The air was ripe with<br />

tension. The bonhomie was forced and soon<br />

everyone just retired in a corner, cocooned in<br />

their own thoughts. The Mission Leader was a<br />

wizened old eagle with hundreds of missions<br />

INDIAN AIR FORCE 2 0 1 2 N o v e m b e r Aerospace Safety 29


under his beak. He knew it was the newcomers<br />

who would get the chop if they were not careful.<br />

The wetbeaks usually lost their nerve and broke<br />

formation leading to aircraft hits. Such attrition<br />

was not really acceptable. ‘Big Chief Long Beak’<br />

back at HQ was known for chewing out Mission<br />

Leaders who lost their under trainees in the first<br />

few missions. Well, he had done all he could as far<br />

as briefing and training was concerned, but it was<br />

always the unexpected that got you in the end.<br />

The wave got airborne on time and set<br />

course for the first waypoint. The Mission Leader<br />

thanked God for the natural ‘state of the art’<br />

onboard navigation system that they were fitted<br />

with. This would never fail unless someone blew<br />

up their CPU and then it wouldn’t really matter,<br />

would it? They flew at a comfortable height of<br />

100 m without bothering about being picked<br />

up. The enemy had no bird detection radars<br />

and there were no firing posts to bother about<br />

till they reached close to the airfield. The tactical<br />

routing kept them clear of most of the known<br />

danger zones like other airfields. The terrain<br />

started dropping away gently and the Mission<br />

Leader admired the countryside. Beautiful green<br />

rolling hills! Suddenly the leader was jolted out<br />

of his reverie with the call “Bogie 12 O’ clock!”<br />

Instinctively the formation retracted their wings<br />

and ducked. Four fighters crossed on top of them.<br />

“Phew! That was close,” thought the leader. But<br />

there were two more fighters trailing and lower,<br />

which hit the starboard element. All four from the<br />

starboard element went into the intake of the left<br />

aircraft. They could see the fighter pitching down<br />

and crashing taking with it four of their comrades.<br />

“Damn! The fighters generally never came down<br />

this low. Had the fighters stuck to their usual<br />

heights we would all be happy” the Mission<br />

Leader ruminated.<br />

As they closed in to the airfield, a few stray<br />

shots were encountered which fell away well<br />

below them. These humans were like hordes<br />

of ‘Don Quixotes’ waving at the windmills with<br />

their antiquated twelve-bore rifles. The raptors<br />

were not going to get down to lower heights<br />

unless dictated by their mode of ‘food recovery’.<br />

Suddenly two members of the lead element<br />

dropped down flapping in agony. The leader<br />

knew that one of the human marksmen was<br />

taking them out using a 0.22 inch rifle. This was<br />

the unexpected that they had been dreading.<br />

They were fast approaching the airfield and<br />

started easing up using the thermals. Some were<br />

slow in easing up and then there were those who<br />

got lured by the open garbage dumps near the<br />

messes meant for feeding the humans. Almost<br />

immediately most of these were shot at with<br />

twelve bore rifles. Attrition was about 4%. Quite<br />

a few got away with wing cells punctured. The<br />

leader was livid. He had briefed these guys not<br />

to deviate from the briefing. This is the price they<br />

had to pay for indiscipline. Thank God this base<br />

30<br />

Aerospace Safety N o v e m b e r 2 0 1 2<br />

INDIAN AIR FORCE


had guns which were in poor condition and were<br />

being wielded by humans who were even worse<br />

marksmen.<br />

There was a sudden flutter amongst their<br />

ranks which soon settled down. They could hear<br />

some avian distress calls emanating from devices<br />

installed on runway edges. The leader sniggered.<br />

This was hilarious. It was like tickling them. These<br />

bird calls were not specific and weren’t going<br />

to do them any harm. The ‘Zon Guns’ too which<br />

were banging away at the same old locations in<br />

the background, sounded like monotonous noisy<br />

friends.<br />

Time to get out of the danger zone! The<br />

wave managed to reach ‘Alottafilth Nagar’ and<br />

carried out a successful recce of the prospective<br />

feeding ground. It was great that the admin<br />

safety establishment at ‘Can’t Believe My Rotten<br />

Luck’ had so far been unable to influence the civic<br />

authorities of ‘Alottafilth Nagar’ regarding proper<br />

garbage disposal in the vicinity of the airfield. The<br />

exit via the sulphur springs was horrendous. The<br />

definition of stink was rewritten for generations to<br />

come. But no ground fire or air interceptions were<br />

encountered. Mission accomplished without any<br />

further attrition!<br />

That night, the wizened old leader sat on his<br />

perch and mulled over the missions he had flown<br />

in all these years. One mission blended into the<br />

next as he fast forwarded them in his tiny mind.<br />

And then it came to him. It was the humans who<br />

were not designed to fly and yet were flying<br />

supersonic jets, had more brains and yet were<br />

intruding into their airspace. The onus of safety<br />

was on the humans. The birds had to go about<br />

the business of looking for food everyday and the<br />

humans had to ....., well they had to fly too I guess.<br />

Maybe we just had to look out and stay out of<br />

each other’s way much more than we were doing.<br />

Happy Landings!<br />

-Wg Cdr N Dhar<br />

Solutions to the Air Traffic Control Puzzle<br />

INDIAN AIR FORCE 2 0 1 2 N o v e m b e r Aerospace Safety 31


On 30 Apr 12, Flt Lt AK Upadhyay (30849 G) Adm/ ATC and 700939 R Sgt Anil Kumar<br />

AFSO were on duty in ATC tower. During the period of their duty, a four helicopter<br />

Mi-17 formation was airborne for an SHBO mission. On the return leg the leader of the<br />

formation announced on RT that his No. 2 was experiencing rise in MGB temperature with<br />

oil pressure dropping below laid down limits and that his No. 2 would be carrying out a<br />

precautionary landing. The DATCO immediately asked for their GPS coordinates. Without<br />

losing time, he plotted the GPS coordinates on the map. During this period, the IC Ops<br />

alerted all concerned individuals/agencies. The captain of the helicopter was contacted<br />

on his mobile to check the safety of the crew. They were further guided to the nearest<br />

town/village. A minute to minute update on the crew was provided to all concerned. This<br />

ensured a quick activation of the agencies involved with the post accident plan.<br />

Flt Lt AK Upadhyay and Sgt Anil Kumar displayed a high degree of situational<br />

awareness and professionalism in dealing with this emergency.<br />

Good Show Flt Lt AK Upadhyay and Sgt Anil Kumar.<br />

(R Marwaha)<br />

Air Cmde<br />

PDAS<br />

On 29 Aug 11, Sqn Ldr GPS Brar (28714 G) F(P) and Flt Lt M Rana (29251 K) F(P) were<br />

authorised to fly an RTR mission in an AVRO ac. During pre flight inspection for this<br />

mission, Sqn Ldr GPS Brar and Flt Lt M Rana noticed a small paint scratch resembling a<br />

crack on the port wing between engine nacelle and the fuselage. On investigation, a<br />

one inch crack was found on the upper surface of the wing. A detailed investigation,<br />

subsequently revealed a crack on the supporting stringer as well and few loose rivets.<br />

Sqn Ldr GPS Brar and Flt Lt M Rana displayed a keen sense of observation and a high<br />

degree of professionalism in detecting a crack which might have led to a catastrophic<br />

disaster.<br />

Good Show Sqn Ldr GPS Brar and Flt Lt M Rana.<br />

(R Marwaha)<br />

Air Cmde<br />

PDAS<br />

32<br />

Aerospace Safety N o v e m b e r 2 0 1 2<br />

INDIAN AIR FORCE


797614-F Cpl Shantanu Chandra Inst/Fit while on posted strength of a Jaguar<br />

Squadron having DARIN–II aircraft, undertook an innovation based repair work of<br />

the FDR milking out equipment. The DATS –300M consisting of PC, tape recorder and<br />

cassettes which are required for analysing data (Parameter & Voice) is not supplied<br />

by the OEM for DARIN – II aircraft. Hence, the DATS of PC was suitably configured for<br />

milking of operational data. However, voice data could not be retrieved for analysis<br />

due to non availability of tape recorder and cassettes in the local market. Thus, the<br />

activity was taken on concession.<br />

Cpl Chandra , with his relentless efforts, managed to retrieve voice data by<br />

connecting the data acquisition and storage unit (DASU) of DARIN – I system to the<br />

aircraft and interfacing it with an audio jack, purchased from local sources, to the<br />

GRE laptop of DARIN – II system. Consequently, the concession on an operationally<br />

important activity was removed.<br />

Cpl Shantanu Chandra displayed a high degree of professionalism and dedication<br />

to duty by innovating a system thereby removing an important concession from the<br />

fleet.<br />

Good Show Cpl Santanu Chandra.<br />

(R Marwaha)<br />

Air Cmde<br />

PDAS<br />

On 05 Mar 12, Sqn Ldr Jagat Behari Dash (28230 G) Adm/ATC had stopped at a<br />

Crossing Point to cross the R/W. The barrier at this location was closed to facilitate<br />

take-off of a Mi-8 helicopter. When the helicopter got airborne, he noticed a dead bird<br />

on the R/W. The officer rushed to the ATC and informed the same to the SATCO, who<br />

in turn alerted the aircraft through the DATCO. The captain of the helicopter was asked<br />

to check all vital parameters. The captain transmitted that all the parameters were<br />

normal. However, the captain of the aircraft abandoned his mission and returned for<br />

an external check. A thorough check revealed a bird hit on one of the main rotors.<br />

Sqn Ldr JB Dash displayed a keen sense of observation and a high degree of<br />

professionalism in noticing and reporting a bird-hit incident.<br />

Good Show Sqn Ldr JB Dash.<br />

(R Marwaha)<br />

Air Cmde<br />

PDAS<br />

INDIAN AIR FORCE 2 0 1 2 N o v e m b e r Aerospace Safety 33


On 04 Jan 12, 734936-S Sgt AS Praveen AFSO was detailed to perform the duties of<br />

runway controller. During this period a MiG-27 was cleared for take - off. During the<br />

take-off roll of the ac, the runway controller observed fuel leakage from the port wheel<br />

bay of this aircraft. He transmitted this to the aircraft. Subsequently, the DATCO also gave<br />

a call to abandon take-off. The pilot acknowledged the calls and abandoned take off.<br />

The aircraft was switched off on the runway and towed back to the dispersal. Subsequent<br />

analysis confirmed the fuel leakage. Had this fuel leak gone unnoticed, it could have<br />

resulted in a grave emergency.<br />

Sgt AS Praveen displayed a high degree of professionalism and situational awareness<br />

in detecting a potentially hazardous situation.<br />

Good Show Sgt AS Praveen.<br />

(R Marwaha)<br />

Air Cmde<br />

PDAS<br />

On 12 Mar 12, 779783-G Cpl Sikandar Khan AF/Fit was detailed to carry out First Flight<br />

servicing of a Mi-8 Helicopter. During the checks, he noticed a Hydraulic oil leak<br />

from the ‘Non Return Valve’ beneath the hydraulic cradle. This was not a routine check<br />

and was difficult to detect under normal conditions. If this leak had gone unnoticed, it<br />

could have led to an incident/accident.<br />

Cpl Sikandar Khan displayed keen a sense of observation and dedication to duty in<br />

averting a potential accident/incident.<br />

Good Show Cpl Sikandar Khan.<br />

(R Marwaha)<br />

Air Cmde<br />

PDAS<br />

34<br />

Aerospace Safety N o v e m b e r 2 0 1 2<br />

INDIAN AIR FORCE


On 02 Mar 12 , 766345 H JWO T Pratap Flt/Gnr was detailed as Flt/Gnr for a<br />

conversion training sortie on a Mi-8 helicopter. During the sortie he observed<br />

fluttering of ‘the tape covering the tail boom joint’ of another helicopter which was<br />

operating from the adjacent helipad. He promptly informed his captain who in<br />

turn informed the crew of the adjacent helicopter. Subsequently, the gunner of the<br />

other helicopter went out and held the tape. A safe switch off was carried out. The<br />

tape, if left unnoticed could have fouled with the tail rotor leading to a disastrous<br />

consequence.<br />

JWO T Pratap displayed a very high degree of situational awareness and<br />

professionalism in detecting a potentially hazardous situation.<br />

Good Show JWO T Pratap<br />

(R Marwaha)<br />

Air Cmde<br />

PDAS<br />

Gp Capt Rajesh Purohit VSM (19170-T) F(P) is posted as the Chief Instructor, Fighter<br />

Training Wing, at AF Station Hakimpet. He is a Cat ‘A’ QFI with a vast instructional<br />

experience and flying experience of Jaguar, Hunter, Kiran and HPT-32 aircraft.<br />

During the month of Nov 11 he has achieved the land mark of total service flying<br />

of 5000 hours of accident free flying. The officer has shown extra ordinary enthusiasm<br />

and passion for flying. His enormous experience in fighter flying is praiseworthy.<br />

Good Show Gp Capt Rajesh Purohit.<br />

(R Marwaha)<br />

Air Cmde<br />

PDAS<br />

INDIAN AIR FORCE 2 0 1 2 N o v e m b e r Aerospace Safety 35


Nest: The nest is a rough platform of<br />

twigs and rags placed in a tree. Nest<br />

sites may be reused in subsequent<br />

years.<br />

Breeding: September to May; varying<br />

locally.<br />

Food Habit: Black Kites are most often<br />

seen gliding and soaring on thermals.<br />

One of the most dangerous birds for<br />

Aerospace Safety which has caused<br />

quite a few Cat I accidents.<br />

36<br />

Aerospace Safety N o v e m b e r 2 0 1 2<br />

INDIAN AIR FORCE


REPORT UNSAFE ACTS<br />

USE ONLINE TOOLS<br />

Round-the-clock contact of PD Aerospace Safety: Tele: 011-26172738, Mob: +91-9717095606 e-mail: pdfs_iaf_in@indiatimes.com<br />

Articles/Suggestions may be sent to: Editor, Aerospace Safety Magazine, Institute of Flight Safety, New Delhi-110 010 e-mail: editorfsmiaf@yahoo.com

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!