Looking forward to the next update!!!
Oh yes, still some exciting features to add before we get to v1.0. The past 2 beta releases only contain minor bug fixes.
-
After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.
Airline Pilot Logbook
- Thread starter powrful1
- Start date
Oh yes, still some exciting features to add before we get to v1.0. The past 2 beta releases only contain minor bug fixes.
Jetjock737
Lurker
All,
Neal Culiner, the creator of Logbook Pro, is a former A-10 pilot and an acquaintence of mine. I sent him a note asking if he'd be interested in partnering with Lenchan in the creation of an Android version of LBP. Here's his reply:
--------------
Hello Jim,
Thank you for the e-mail. Android is coming soon, my goal is the November time frame, decoded to real world means December!
You may not be getting the newsletters, here's the recent article on development priorities:
http://logbookpro.com/newsletters/2010/09/#roadmap
I recently bought a Droid X to become proficient with the Android ways so I'm in the Android gang now and hope to have Logbook Pro for Android coming soon.
If you're not subscribed to the newsletters which is where the Android app will be announced, you can do so here:
http://logbookpro.com/lists
Thanks again for the contact and hopefully soon we'll have something for you.
Sincerely,
Neal Culiner
President, NC Software, Inc.
http://www.nc-software.com
-Are you using the latest version? http://logbookpro.com/versions
-Have you reviewed the documentation? http://logbookpro.com/docs
-Please review our support resources available: http://logbookpro.com/support
-Protect your data from catastrophic failure. Use our Online Backup service to keep off site backups: http://logbookpro.com/backup
--------------------------
So, the good news is, something's coming in the next few months. The bad news is, it's not Lenchan's. I was hoping there would be some collaboration, at least for Lenchan's financial sake. The way he's going, his app will do everything we need to interface with Logbook Pro, so it may ultimately be the way to go.
Regards,
JJ
Neal Culiner, the creator of Logbook Pro, is a former A-10 pilot and an acquaintence of mine. I sent him a note asking if he'd be interested in partnering with Lenchan in the creation of an Android version of LBP. Here's his reply:
--------------
Hello Jim,
Thank you for the e-mail. Android is coming soon, my goal is the November time frame, decoded to real world means December!
You may not be getting the newsletters, here's the recent article on development priorities:http://logbookpro.com/newsletters/2010/09/#roadmap
I recently bought a Droid X to become proficient with the Android ways so I'm in the Android gang now and hope to have Logbook Pro for Android coming soon.
If you're not subscribed to the newsletters which is where the Android app will be announced, you can do so here:
http://logbookpro.com/lists
Thanks again for the contact and hopefully soon we'll have something for you.
Sincerely,
Neal Culiner
President, NC Software, Inc.
http://www.nc-software.com
-Are you using the latest version? http://logbookpro.com/versions
-Have you reviewed the documentation? http://logbookpro.com/docs
-Please review our support resources available: http://logbookpro.com/support
-Protect your data from catastrophic failure. Use our Online Backup service to keep off site backups: http://logbookpro.com/backup
--------------------------
So, the good news is, something's coming in the next few months. The bad news is, it's not Lenchan's. I was hoping there would be some collaboration, at least for Lenchan's financial sake. The way he's going, his app will do everything we need to interface with Logbook Pro, so it may ultimately be the way to go.
Regards,
JJ
Neal Culiner, the creator of Logbook Pro, is a former A-10 pilot and an acquaintence of mine. I sent him a note asking if he'd be interested in partnering with Lenchan in the creation of an Android version of LBP. Here's his reply:
...
Android is coming soon, my goal is the November time frame, decoded to real world means December!
No surprise here, I guess. It's just a matter of time that all current vendors will release an Android version.
Well, the release timeframe of intelliPilot v1.0 also happens to be November
I understand that Android LBP is an add-on for LBP PC, so for pilots who are already using LBP PC, this Android add-on is a great value proposition, especially with the sync capability.
intelliPilot is not a clone of LBP, and the design objectives are different. We aim to support import/export for various logbook software, and cloud sync will come soon in addition to standalone mode.
It would be really interesting if intelliPilot is allowed to integrate with LBP Cloud Sync.
Hi, I hope you enjoy this major update. It has many improvements - just look at the change log! A few more exciting features (e.g import) are coming before we get to v1.0
Yes, we worked hard to fix the layout problems with Sense - tested on actual devices now. Funny enough, it is still puzzling that the Sense screens look a bit different from the ones on our product page. I noted in particular that the entry field background in Sense has a 2D look, while our one has a 3D look.
Anyway, keep the feedback coming.
Firstly this is an excellent app i have just spent the last few hours updating my last paper logbook and transferring all of the hours to intelliPilot.
I am sure by now you have a huge list of improvements but just to add my two pence worth:-
I am a co-pilot in the UK and in Europe we break hours down slightly differently, as a co-pilot flying jets I will amass PICUS (Pilot In Command Under Supervision) hours when its my turn to fly the sector, rather than PIC hours. Only a captain can accrue PIC hours. When it is not my sector i will log P2 hours. Any chance of a 'European' button which changes the layout/reports slightly? I have attached photos of my logbook headings to hopefully explain this a bit better. (please excuse the handwriting, probably explains why i need an electronic logbook)
I would echo previous requests for rolling summary totals to measure compliance with the law. 28 days and 365 are quite important.
Can we auto populate instrument time through default options?
How about automatically working out night values based on sunset and sunrise times?
If the above is possible then the Day/night T/o & landings should be possible to auto populate?
As far as inputting time/date how about the rolling sliders that Android 2.2 uses for selecting time and date? These are great, would make data input easier.
When the 'from' time in the flight details is populated can that time then populate the 'to' box so these values are closer to the actual to time? (easier to change)
How about auto-fill captain(co-pilot) name and a comments field for useful info about that person. With a large fleet its difficult to remember!
How about more information on the airports, its quite useful to have equipment available at the airport during the briefing stage, but this might be getting into a different app!
Overall though amazing what has been achieved in such a short period of time. Its a very stable beta, i have e-mailed you with a couple of very minor bugs i found.
Many Thanks
Scapa
I am sure by now you have a huge list of improvements but just to add my two pence worth:-
I am a co-pilot in the UK and in Europe we break hours down slightly differently, as a co-pilot flying jets I will amass PICUS (Pilot In Command Under Supervision) hours when its my turn to fly the sector, rather than PIC hours. Only a captain can accrue PIC hours. When it is not my sector i will log P2 hours. Any chance of a 'European' button which changes the layout/reports slightly? I have attached photos of my logbook headings to hopefully explain this a bit better. (please excuse the handwriting, probably explains why i need an electronic logbook)
I would echo previous requests for rolling summary totals to measure compliance with the law. 28 days and 365 are quite important.
Can we auto populate instrument time through default options?
How about automatically working out night values based on sunset and sunrise times?
If the above is possible then the Day/night T/o & landings should be possible to auto populate?
As far as inputting time/date how about the rolling sliders that Android 2.2 uses for selecting time and date? These are great, would make data input easier.
When the 'from' time in the flight details is populated can that time then populate the 'to' box so these values are closer to the actual to time? (easier to change)
How about auto-fill captain(co-pilot) name and a comments field for useful info about that person. With a large fleet its difficult to remember!
How about more information on the airports, its quite useful to have equipment available at the airport during the briefing stage, but this might be getting into a different app!
Overall though amazing what has been achieved in such a short period of time. Its a very stable beta, i have e-mailed you with a couple of very minor bugs i found.
Many Thanks
Scapa
Attachments
Sorry about the late reply.
Thanks, glad you like it.
We'll see how we can accommodate this. BTW, do you do Dual?
We have introduced 'Quick Range' in v0.4, and it allows you to see the flight hours for the last 7, 28, etc days. Does this satisfy your requirements? Full help is available in the Summary screen.
Yes, we're considering adding an option, similar to defaulting pilot time to duration.
This is planned but may be a post v1.0 feature. Calculating sunrise/set times are not difficult, so auto determination of day/night takeoff/landing is straight forward. Auto day/night times can be tricky for long haul, and requires more effort. But we plan to implement this.
Not exactly sure what you meant? We're using standard widgets on 2.2. Oh, are you using a HTC Sense UI phone? They use sliders for choosing date and time, but stock Android doesn't do that.
Understand what you're saying - will have to think about it. The problem here is that if you change the 'from' time, we can't be sure if the 'to' needs to be changed. Perhaps this is only useful when the 'from' time is changed the first time (and the 'to' time hasn't changed yet).
You can set your name in Settings now. We can add another setting option for the other pilot if you fly mostly with the same pilot.
What sort of comments do you have in mind? Some examples would be useful.
There is a comment field in the airport record. Have you tried using that?
Thanks for your feedback.
Thanks, glad you like it.
We'll see how we can accommodate this. BTW, do you do Dual?
We have introduced 'Quick Range' in v0.4, and it allows you to see the flight hours for the last 7, 28, etc days. Does this satisfy your requirements? Full help is available in the Summary screen.
Yes, we're considering adding an option, similar to defaulting pilot time to duration.
This is planned but may be a post v1.0 feature. Calculating sunrise/set times are not difficult, so auto determination of day/night takeoff/landing is straight forward. Auto day/night times can be tricky for long haul, and requires more effort. But we plan to implement this.
Not exactly sure what you meant? We're using standard widgets on 2.2. Oh, are you using a HTC Sense UI phone? They use sliders for choosing date and time, but stock Android doesn't do that.
Understand what you're saying - will have to think about it. The problem here is that if you change the 'from' time, we can't be sure if the 'to' needs to be changed. Perhaps this is only useful when the 'from' time is changed the first time (and the 'to' time hasn't changed yet).
You can set your name in Settings now. We can add another setting option for the other pilot if you fly mostly with the same pilot.
What sort of comments do you have in mind? Some examples would be useful.
There is a comment field in the airport record. Have you tried using that?
Thanks for your feedback.
Hi Scapa,
i know of some people (mostly from UK) logging all the hours "flown" as "PICUS"
I've been flying in Europe and ,apart from some exceptions, i've never seen someone logging CoPilot times that way
However, as far JAR-FCL 1.080 is concerned
PICUS (Pilot-in-command under
supervision)
Provided that the method of supervision
is acceptable to the Authority, a co-pilot may
log as PIC flight time flown as PICUS, when all
of the duties and functions of PIC on that flight
were carried out, such that the intervention of
the PIC in the interest of safety was not
required.
The PICUS time is needed only for having the minimum 250h of "PIC" time for a possible future ATPL or command upgrade and cannot be counted as "PIC" hours for other purposes
I don't want to start reading between the lines of JAR-FCL, however i consider that you can log your hours as "PIC" in Intellipilot, while recording the real PIC name for the flight
Would be the same using a Paper Logbook JAR-FCL 1.080 compliant
Regards
David
David,
Yes i think it is a UK thing, most co-pilots tend to log P1 hrs as PICUS i think.
The only dual hours I would do would be in a light aircraft under instruction.
Great news, this would be good, the ICAO Annex 1 definition of night is: "The hours between the end of evening civil twilight and
the beginning of morning civil twilight or such other period
between sunset and sunrise, as may be prescribed by the
appropriate authority."
Not sure about the FAA but the CAA (UK) say the time from half an hour after sunset until half an hour before sunrise (both times
inclusive), sunset and sunrise being determined at surface level. Semantics but might be of some interest.
Yes quite right its a desire and they are HTC Sliders, shame, they are really good!
It sounds a bit pathetic but something like "two kids, diverted to xxx due weather" just to jog the memory, as we tend to fly with many different people and its nice just to have something to start with after two years of not flying with someone.
Yes that would work i will start populating that i think.
Thanks for all of the hard work, i will definitely be purchasing the full version!
Yes i think it is a UK thing, most co-pilots tend to log P1 hrs as PICUS i think.
The only dual hours I would do would be in a light aircraft under instruction.
Great news, this would be good, the ICAO Annex 1 definition of night is: "The hours between the end of evening civil twilight and
the beginning of morning civil twilight or such other period
between sunset and sunrise, as may be prescribed by the
appropriate authority."
Not sure about the FAA but the CAA (UK) say the time from half an hour after sunset until half an hour before sunrise (both times
inclusive), sunset and sunrise being determined at surface level. Semantics but might be of some interest.
Yes quite right its a desire and they are HTC Sliders, shame, they are really good!
It sounds a bit pathetic but something like "two kids, diverted to xxx due weather" just to jog the memory, as we tend to fly with many different people and its nice just to have something to start with after two years of not flying with someone.
Yes that would work i will start populating that i think.
Thanks for all of the hard work, i will definitely be purchasing the full version!
Scapa did have some good ideas. I also like the clock slider... It works much better then the tap, tap to change. Anyway to implement this on Sense UI? (Screen shot below).
A crew member comments field would also be neat if it could remember info about other crew members and auto fill comments when you enter the crew members name again. Just a way to jog your memory about some of the things you talked about or information about the person you are flying with.
Example:
Married, 3 kids, golfer, commutes to SFO
or
Lunatic, can't fly - watch him close!!!!
I don't put other pilots info in my "People" phonebook contacts since I might not see or fly with this person again. Maybe a seperate contact database for fellow-pilots? There may already be a way that I haven't found in having two seperate contact list. I tried grouping to co-workers but I can't filter just co-workers in Intellipilot when I search the NAME field. I also would not want their info syncing to my PC or Google account(some people might want this). Anyway, it would be great if we could seperate our phone contacts from co-workers and also be able to keep some comments on each individual.
I am still impressed with the last update!!! I have tried the incremental export and it is working great. Since you added all the new fields on the extra tab, I did have to redo my fields for import to Log Book Pro. - No big deal. Everything is working great, even X-C and approaches(type and number). You even improved the summary page and covered all the possible ways to filter, You must have been taking notes...
This app is very usable right now and I would gladly pay you the $15. Thank you again for doing this and doing it in such short time!!!
A crew member comments field would also be neat if it could remember info about other crew members and auto fill comments when you enter the crew members name again. Just a way to jog your memory about some of the things you talked about or information about the person you are flying with.
Example:
Married, 3 kids, golfer, commutes to SFO
or
Lunatic, can't fly - watch him close!!!!
I don't put other pilots info in my "People" phonebook contacts since I might not see or fly with this person again. Maybe a seperate contact database for fellow-pilots? There may already be a way that I haven't found in having two seperate contact list. I tried grouping to co-workers but I can't filter just co-workers in Intellipilot when I search the NAME field. I also would not want their info syncing to my PC or Google account(some people might want this). Anyway, it would be great if we could seperate our phone contacts from co-workers and also be able to keep some comments on each individual.
I am still impressed with the last update!!! I have tried the incremental export and it is working great. Since you added all the new fields on the extra tab, I did have to redo my fields for import to Log Book Pro. - No big deal. Everything is working great, even X-C and approaches(type and number). You even improved the summary page and covered all the possible ways to filter, You must have been taking notes...
This app is very usable right now and I would gladly pay you the $15. Thank you again for doing this and doing it in such short time!!!
Attachments
Lenchan,
Thanks for the great work on a logbook for android. I am new to the program and it is coming along very well. Are you planning on implementing some sort of import of schedule? A nice feature for airline guys. The page with the flights lists gets very long after a little use; is there any way to filter this page by day, month, week, etc...? They flight input page works very well also, however is there a way to have the flight number default to the number keypad for quicker flight number input?
Thanks again for the program. Great looking interface.
Dan
Thanks for the great work on a logbook for android. I am new to the program and it is coming along very well. Are you planning on implementing some sort of import of schedule? A nice feature for airline guys. The page with the flights lists gets very long after a little use; is there any way to filter this page by day, month, week, etc...? They flight input page works very well also, however is there a way to have the flight number default to the number keypad for quicker flight number input?
Thanks again for the program. Great looking interface.
Dan
Keith02
Lurker
Can we make multi-leg entries so we dont have to make a new entry for each leg flown throughout the day? At my job, I fly as many as 8 legs a day and having multi leg entries would make things much easier.
Also, why must the airport be listed in the database? It would be much easier to simply allow any input the user wants in the airport field. It would also lighten up the application since it wouldnt have to have such an extensive database of airports. Many pilots, myself incuded fly to private airports, backcountry fields, waterways (seaplanes!), etc etc, that dont allways have an ICAO identifier... just a thought.
Otherwise, great app! Fix the airport identifier "issue" and I will gladly pay more than $15 for this app!
Also, why must the airport be listed in the database? It would be much easier to simply allow any input the user wants in the airport field. It would also lighten up the application since it wouldnt have to have such an extensive database of airports. Many pilots, myself incuded fly to private airports, backcountry fields, waterways (seaplanes!), etc etc, that dont allways have an ICAO identifier... just a thought.
Otherwise, great app! Fix the airport identifier "issue" and I will gladly pay more than $15 for this app!
Keith02
Lurker
All,
Neal Culiner, the creator of Logbook Pro, is a former A-10 pilot and an acquaintence of mine. I sent him a note asking if he'd be interested in partnering with Lenchan in the creation of an Android version of LBP. Here's his reply:
--------------
Hello Jim,
Thank you for the e-mail. Android is coming soon, my goal is the November time frame, decoded to real world means December!
http://logbookpro.com/newsletters/2010/09/#roadmap
I recently bought a Droid X to become proficient with the Android ways so I'm in the Android gang now and hope to have Logbook Pro for Android coming soon.
If you're not subscribed to the newsletters which is where the Android app will be announced, you can do so here:
http://logbookpro.com/lists
Thanks again for the contact and hopefully soon we'll have something for you.
Sincerely,
Neal Culiner
President, NC Software, Inc.
http://www.nc-software.com
-Are you using the latest version? http://logbookpro.com/versions
-Have you reviewed the documentation? http://logbookpro.com/docs
-Please review our support resources available: http://logbookpro.com/support
-Protect your data from catastrophic failure. Use our Online Backup service to keep off site backups: http://logbookpro.com/backup
--------------------------
So, the good news is, something's coming in the next few months. The bad news is, it's not Lenchan's. I was hoping there would be some collaboration, at least for Lenchan's financial sake. The way he's going, his app will do everything we need to interface with Logbook Pro, so it may ultimately be the way to go.
Regards,
JJ
If intellipilot continues to improve as it has in the last few months, I will stick with it. Logbook pro has annoyed me to no end with the android issue. With 300,000+ android device activations EVERY DAY, it boggles my mind as to why developers such as Logbook Pro ignore the platform. It makes me mad too since I have been an Android user since the G1
I switched from the Iphone... hahaWe're considering supporting multi-leg flight entries. In the meantime, to reduce the entry time, you can use the context action "Add New Leg".
Having the airport details stored (e.g. timezone, co-ordinates) will allow us to support local time and auto day/night calculations. Do you have a large number of airports/airfields without ICAO/IATA/FAA codes?
You can enter your own airports, and we have pilots using the unused range of ICAO codes to enter airfields, etc.
I am new to this app (and new to Android, for that matter), but very glad to see it available and so well supported out of the gate. Nice work!
I am currently between flying jobs, groundschool not til May, so cant comment on the app yet. Very encouraging comments though, looking fwd to using it and gaining a massive advantage in keeping my hours logged all neat and tidy like. Leads me to one big question though: Are you intending to offer a PC based app to accompany this Android app? I currently use an excel design of my own, but have next to zero functions associated with it (too much work, too little skill to make it easily happen). A PC app would be very, very well recieved i am sure, and i for one would pay at least a few $$ for it. I think its common knowledge that Log10Pro is a brilliant piece of software (replete with a companion iPhone app), but why should PC/Android users not have something even better
Keep up the good work, I will chime in with my feedback once I start logging again.
I am currently between flying jobs, groundschool not til May, so cant comment on the app yet. Very encouraging comments though, looking fwd to using it and gaining a massive advantage in keeping my hours logged all neat and tidy like. Leads me to one big question though: Are you intending to offer a PC based app to accompany this Android app? I currently use an excel design of my own, but have next to zero functions associated with it (too much work, too little skill to make it easily happen). A PC app would be very, very well recieved i am sure, and i for one would pay at least a few $$ for it. I think its common knowledge that Log10Pro is a brilliant piece of software (replete with a companion iPhone app), but why should PC/Android users not have something even better
Keep up the good work, I will chime in with my feedback once I start logging again.
What kind of app are you looking for? I have Logbook Pro and IntelliPilot and they work together seamlessly. There are some tweaks that I would like to see, but I export my hours from Intellipilot and import them into Logbook Pro with little to no problems. The main problems I have are the hours don't always show in the correct columns and when transferring from hh:mm to H.M, I end up losing .1 or .2 hours. An easy fix once I review all the flights that I've imported.
Well, with all due respect, times ending up with inaccuracies, in the wrong rows/ columns is kind of a big deal. I don't transfer my times often, so when i do, i need to be pretty well certain things end up where they should. In a word, i want a PC app that works seemlessly with intellipilot. That's why i asked (it was mainly directed @ the devs that frequents this thread). Log ten pro is just such a solution, but sadly is Mac only
I like the new Auto Day/Night feature. The Day/night time is working great! One thing I think needs to change is the T.O. and Landings. I don't think it should add a T.O or a Landing if you are not the flying pilot.(it should just leave the T.O. and Landing blank) If you are the flying pilot then it should give credit for the T.O. and Landing, day or night.
Once you get to version 1, I hope you can keep the export data fields in the same columns for future updates. Or please let us know if you change them. I have a saved import map for Logbook Pro. that needs to be edited every time you change the export fields.
Thanks again for writing this app. I use it daily at work and it is working great.
Once you get to version 1, I hope you can keep the export data fields in the same columns for future updates. Or please let us know if you change them. I have a saved import map for Logbook Pro. that needs to be edited every time you change the export fields.
Thanks again for writing this app. I use it daily at work and it is working great.
Well, with all due respect, times ending up with inaccuracies, in the wrong rows/ columns is kind of a big deal. I don't transfer my times often, so when i do, i need to be pretty well certain things end up where they should. In a word, i want a PC app that works seemlessly with intellipilot. That's why i asked (it was mainly directed @ the devs that frequents this thread). Log ten pro is just such a solution, but sadly is Mac only
C4X,
Not sure but I think what Baseal is refering to on the wrong columns importing to wrong place: This software is still in beta and Lenchan is adding new features with every update. He is also adding more data that is exporting. I have Logbook Pro also. In Logbook Pro you can import the data and save a map file to tell logbook pro where to put each column. If Lenchan adds or rearanges the export then our map is off for the import to Logbook Pro. You just have to edit your map file or start over and creat a new import.map file. This is the only way I have seen the data be imported to the wrong column. I have not experience the time problems he is seeing.
Yes, very true. This was also pointed out by other pilots, and the latest v0.5.2 version released yesterday fixed that
Yes, will sure do. Sorry about the changes in export file column ordering in beta versions. BTW, do you mind sharing your import map for LBP? I think it would be useful to put it up so that other pilots can use it.
That's great. Thanks for your feedback.
No problem Lenchan... here is my import.map for Logbook Pro.
This may not work for everyone and you may need to edit or tweak it to fit your Logbook Pro setup. Depends on if you log time and setup Logbook Pro like I do. I do not import everything from Intellipilot (only the stuff I log).
PS - I haven't flown or done an export/import since this lastest Intellipilot update. If anything was added or changed to the export then this import file will not be correct.
I also Import the FO name (co-pilot) into the remarks column of Logbook Pro.
Here is an screen image of my Logbook Pro. If you log the same data then this import file might work for you. Please backup your Logbook Pro before trying my import.map file. Just in case it all goes nuts you can restore.
This may not work for everyone and you may need to edit or tweak it to fit your Logbook Pro setup. Depends on if you log time and setup Logbook Pro like I do. I do not import everything from Intellipilot (only the stuff I log).
PS - I haven't flown or done an export/import since this lastest Intellipilot update. If anything was added or changed to the export then this import file will not be correct.
I also Import the FO name (co-pilot) into the remarks column of Logbook Pro.
Here is an screen image of my Logbook Pro. If you log the same data then this import file might work for you. Please backup your Logbook Pro before trying my import.map file. Just in case it all goes nuts you can restore.
Attachments
Ok, thanks. No worries, we'll have a look, make relevant adjustments and make the map available as a LBP import example on our product page and assign the credit to you. If you wish to, PM me your real name
The latest update include a new duty hours field, so the layout has changed a bit.
Just curious, LBP can log individual approach type, but it doesn't seem to be able to export/import the information?
Ok, thanks. No worries, we'll have a look, make relevant adjustments and make the map available as a LBP import example on our product page and assign the credit to you. If you wish to, PM me your real name
The latest update include a new duty hours field, so the layout has changed a bit.
Just curious, LBP can log individual approach type, but it doesn't seem to be able to export/import the information?
No need for credit to me but thanks for the offer. Please feel free to share and edit as you wish. I'm on vacation for a week and once I fly again and have some more data to export, I will edit the import.map for the duty columns and upload here. However, I do not log duty in LBP so I would skip the duty in the map.
Yes LBP does import the App type. And the export/import is working. I only log IMC (Instrument Meteorlogical Conditions-in the clouds)approaches and not visuals. So in my LBP anywhere you see a number 1 there was an IMC App. logged. If I click on the APP field then another small window opens with the approach type... In this popup you can select the App type and how many of each. Here is a screen shot of the App type. I wish LBP could log Cat 1,2,3 ILS. They are grouped together as just ILS. Maybe one day LBP can add the different ILS app and catch up to Intellipilot.
Attachments
I wish LBP could log Cat 1,2,3 ILS. They are grouped together as just ILS. Maybe one day LBP can add the different ILS app and catch up to Intellipilot.
Genuine questions for pilots using intelliPilot with LBP ...
Do you use intelliPilot simply because there is no Android version for LBP yet? Or do you just need intelliPilot as a mobile frontend for data capture, and you still prefer to use a desktop app?
If there were an intelliPilot desktop version, what additional features would you like to see on top of the existing features of intelliPilot (Android version)?
The main reason I use LBP was it was a way to sync from my Palm device and then print. LBP has a program called APDL(Airline Pilot Daily Log) that is palm based software. APDL will import the schedule from many airlines. When you flew the trip you could compare actual to scheduled. Then when you got home you could sync to your PC and the data would sync into LBP. From LBP I could then easily print a standard Jeppeson style Master Log for my hard copy. I dumped my palm phone and came over to the droid. I saw a FO the other day that still had his Palm Centro for APDL and had the EVO for his phone. He now has Intellipilot on his EVO.
If you created a PC version of Intellipilot and had options for printing, that would be great. You would need to have print templates for the standard and master logbooks to make things easy for the end user. The templates should be customizable or we should be able to create our own.
Also, I didn't have to change the import.map file. The new fields you added for duty time went to the end of you export file and didn't affect my import map.
If you created a PC version of Intellipilot and had options for printing, that would be great. You would need to have print templates for the standard and master logbooks to make things easy for the end user. The templates should be customizable or we should be able to create our own.
Also, I didn't have to change the import.map file. The new fields you added for duty time went to the end of you export file and didn't affect my import map.